Featured Articles

Analysts expect ARM to do well next year

Analysts expect ARM to do well next year

British chip designer ARM could cash in on the mobile industry's rush to transition to 64-bit operating systems and hardware.

More...
Huawei and Xiaomi outpace Lenovo, LG in smartphone market

Huawei and Xiaomi outpace Lenovo, LG in smartphone market

Samsung has lost smartphone market share, ending the quarter on a low note and Xiaomi appears to be the big winner.

More...
Intel Broadwell 15W coming to CES

Intel Broadwell 15W coming to CES

It looks like Intel will be showing off its 14nm processors, codenames Broadwell, in a couple of weeks at CES 2015.

More...
Gainward GTX 980 Phantom reviewed

Gainward GTX 980 Phantom reviewed

Today we’ll be taking a closer look at the recently introduced Gainward GTX 980 4GB with the company’s trademark Phantom cooler.

More...
Zotac ZBOX Sphere OI520 barebones vs Sphere Plus review

Zotac ZBOX Sphere OI520 barebones vs Sphere Plus review

Zotac has been in the nettop and mini-PC space for more than four years now and it has managed to carve…

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