Featured Articles

IDC says PC market is rebounding

IDC says PC market is rebounding

Research firm IDC has published its latest report into the state of the PC market and while there are some signs…

More...
TSMC steps up development of 10nm process

TSMC steps up development of 10nm process

TSMC, the world’s biggest chip foundry for hire, has reportedly stepped up development of its 10nm manufacturing process.

More...
Broadwell 14nm desktop comes late in Q2 2015

Broadwell 14nm desktop comes late in Q2 2015

A while ago we mentioned that Broadwell won’t show up in the desktop space this year and we got it right.…

More...
AMD A8-7600 Kaveri APU reviewed

AMD A8-7600 Kaveri APU reviewed

Today we'll take a closer look at AMD's A8-7600 APU Kaveri APU, more specifically we'll examine the GPU performance you can…

More...
EVGA GTX 780 Classified reviewed

EVGA GTX 780 Classified reviewed

The EVGA GTX 780 Classified has been dethroned as the company’s fastest non-Titan card following the introduction of the GTX 780…

More...
Frontpage Slideshow | Copyright © 2006-2010 orks, a business unit of Nuevvo Webware Ltd.
Friday, 30 May 2008 14:55

Ubisoft's says no Direct 3D 10.1

Written by Slobodan Simic

Image

It won't come back to Assassin's Creed

As you may remember, Ubisoft's Assassin's Creed was the first game to have some use for DirectX 10.1, at least part of it. But as soon as that was discovered, as it was the "hidden" feature of the Assassin's Creed, Ubisoft has issued the famous 1.02 patch that has removed this feature.

Our colleagues over at Pcgameshardware.de have done an e-mail interview with Ubisoft, and tried to get some info on this situation. You may have heard the explanation for the DirectX 10.1 support in Assassin's Creed before, but just for the sake of the argument, we will do it once again.

According to Ubisoft, they have found that they could optimize a pass by reusing an existing buffer, which is one of the great features of DX10.1 API. But unfortunately, at least according to Ubisoft, the performance gains that were observed in the retail version were inaccurate, since the implementation was wrong and a part of the rendering pipeline was broken.

This was only notable when anti-aliasing was pushed into play, but in any other scenario both Dx10 and Dx10.1 use the same rendering pipeline. According to that same interview, the mentioned feature was buggy and Ubisoft had to remove it.

When asked about the plans of getting the D3D 10.1 back to Assassin's Creed, Ubisoft responded that there is no plan to re-implement support for DX10.1. Like we expected anything different from a TWIMTBP title.

You can check out the entire interview and some screenshots here.


Last modified on Friday, 30 May 2008 20:27
blog comments powered by Disqus

 

Facebook activity

Latest Commented Articles

Recent Comments