Featured Articles

Intel releases tiny 3G cell modem

Intel releases tiny 3G cell modem

Intel has released a 3G cellular modem with an integrated power amplifier that fits into a 300 mm2 footprint, claiming it…

More...
Braswell 14nm Atom slips to Q2 15

Braswell 14nm Atom slips to Q2 15

It's not all rosy in the house of Intel. It seems that upcoming Atom out-of-order cores might be giving this semiconductor…

More...
TSMC 16nm wafers coming in Q1 2015

TSMC 16nm wafers coming in Q1 2015

TSMC will start producing 16nm wafers in the first quarter of 2015. Sometime in the second quarter production should ramp up…

More...
Skylake-S LGA is 35W to 95W TDP part

Skylake-S LGA is 35W to 95W TDP part

Skylake-S is the ‘tock’ of the Haswell architecture and despite being delayed from the original plan, this desktop part is scheduled…

More...
Aerocool Dead Silence reviewed

Aerocool Dead Silence reviewed

Aerocool is well known for its gamer cases with aggressive styling. However, the Dead Silence chassis offers consumers a new choice,…

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