The in-close environment looks pretty good, but the LOD IQ is absolutely disgusting. I mean, what the hell are the distance textures in these shots? The buildings look like the backgrounds of NES games. You can literally count the pixels in some of those textures. The fact that you have to brute force something that swaps in low-resolution textures at 50 feet is extremely disappointing.
The in-close environment looks pretty good, but the LOD IQ is absolutely disgusting. I mean, what the hell are the distance textures in these shots? The buildings look like the backgrounds of NES games. You can literally count the pixels in some of those textures. The fact that you have to brute force something that swaps in low-resolution textures at 50 feet is extremely disappointing.
Can anyone with 16 GB of Ram try running the game with 8 GB and see if that affects frame rates? I wouldn't expect it to, at least not very much if at all, but this game maxes out my 8 GB.
I must say however, this game is drop dead gorgeous, I mean looking at the screenshots being posted here and all.
What are the chances the Division will not be a repeat of WD and Unity? Oh man. Get ready for GM200 SLI to play 2012 graphics at 60 fps at 1080p![]()
Ubisoft is getting hammered with complaints. They now have a live blog running for game fixes. Game performance is their most widely reported issue.
http://assassinscreed.ubi.com/en-US/community/liveupdates/index.aspx
This is nothing new for bUbisoft, this has been thier deal ever since Rainbow Six 3.16-32GB RAM "needed" to not stutter on an SSD sounds more like "broken game engine streaming code" than "this game is so epic your PC is obviously too slow!" It seems the more resources you give devs, the less they can do with them...
The game (in its current state) is issuing approximately 50,000 draw calls on the DirectX 11 API. Problem is, DX11 is only equipped to handle ~10,000 peak draw calls. What happens after that is a severe bottleneck with most draw calls culled or incorrectly rendered, resulting in texture/NPCs popping all over the place. On the other hand, consoles have to-the-metal access and almost non-existent API Overhead but significantly underpowered hardware which is not able to cope with the stress of the multitude of polygons. Simply put, its a very very bad port for the PC Platform and an unoptimized (some would even go as far as saying, unfinished) title on the consoles.
It's the xmas season the suits put them under pressure for. A game coming out at some other random time has less motivation to hit a date, IMO. This is also extremely humiliating for Ubisoft. I think they won't be soon repeating these mistakes. This is absolutely costing them money. A lot of people refuse to buy this, and of those who know no better and can't care less about the debate, they go to amazon and see half the reviews are 1/5 they look elsewhere.What are the chances the Division will not be a repeat of WD and Unity? Oh man. Get ready for GM200 SLI to play 2012 graphics at 60 fps at 1080p![]()
I don't know about the validity of this, but if it's true, it's pretty damning on Ubisoft's ability to properly code:
Good thing AMD and Ubi are working together to solve thisWe are aware that the graphics performance of Assassin’s Creed Unity on PC may be adversely affected by certain AMD CPU and GPU configurations. This should not affect the vast majority of PC players, but rest assured that AMD and Ubisoft are continuing to work together closely to resolve the issue, and will provide more information as soon as it is available.
"GloriousWalrus 15 minutes ago
Every time I got to the southernmost part of the map, the game crashes. A lot of missions are therefore blocked to me.
That freezing issue with the southern portion of the map has been fixed with patch 1.2.
Apparently the problems are AMDs fault :awe:
AMD Graphics Cards Compatibility with Assassin's Creed Unity
Good thing AMD and Ubi are working together to solve this![]()
![]()
AMD's weak sauce CPUs combined with their inefficient DX11 drivers cannot be a good combination :whiste:
