Featured Articles

Apple announces its Apple Watch

Apple announces its Apple Watch

Apple has finally unveiled its eagerly awaited smartwatch and surprisingly it has dropped the "i" from the brand, calling it simply…

More...
Skylake 14nm announced

Skylake 14nm announced

Kirk B. Skaugen, Senior Vice President General Manager, PC Client Group has showcased Skylake, Intel’s second generation 14nm architecture.

More...
Apple officially announces 4.7-inch iPhone 6 and 5.5-inch iPhone 6 Plus

Apple officially announces 4.7-inch iPhone 6 and 5.5-inch iPhone 6 Plus

The day has finally come and it appears that most rumors were actually spot on as Apple has now officially unveiled…

More...
CEO: Intel on target for 40m tablets

CEO: Intel on target for 40m tablets

Intel CEO Brian Krzanich just kicked off the IDF 2014 keynote and it started with a phone avatar, some Katy Perry…

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