drake4 said:
fatslob-:O said:
drake4 said:
fatslob-:O said:
drake4 said:
Scoobes said:
drake4 said:
superchunk said:
drake4 said:
superchunk said:
RE the shaders...
Can someone post a source of actual devs saying it has 160 vs 320? I've had 320 for a very long time due to Chipworks and NeoGaf threads discussion combined with various tech sites. |
How do you have 320 shaders when neogaf onfirmed it was 160 shaders, and in the very same thread the project cars dev said it was 192 shaders , 320 shaders has been ruled out already ruled out by neogaf and othere tech sites unless your not keeping up with the descussion and want to ignore the facts.
|
gaf's thread on the GPU has 320 in its OP.
|
http://www.neogaf.com/forum/showthread.php?t=710765 this was the updated version of the wiiu specs thread, the othere one was never updated cause the OP never got to it, or stopped updating since it was such a long process to figure out the specs.
here is the direct quote from the NFSWU/project car dev Martin Griffiths
Not sure where they got that info from but the WiiU GPU has 192 Shader units, not 160. It also has 32MB of EDRAM, (the same amount as Xbox One) so comparing just the number of shader units against a PC card doesn't give a representative performance comparison. On the CPU side, WiiU also supports multi-threaded rendering that scales perfectly with the number of cores you throw at it, unlike PC DX11 deferred contexts which don't scale very well. The current WiiU build runs around 18-25fps with 5AI with all post (FXAA/Motion blur etc) enabled, which is fairly good given only the fairly cursory optimisation pass that it's had.
|
Nice find. That actually fits pretty well with a supposed dev we had on here that stated it was between 160-200 shaders.
|
even with this confirmation, i bet the op still won't update his chart so his console of choice looks better, 320 shaders has been ruled a long time ago the only descussion going on is 160-192 shaders.
|
Even if it had 192 shaders or 160 it really doesn't matter in the end because the WII U will end up being weak on all fronts regardless judging by it's meager 12.8 GB/s bandwidth. So even if the WII U had 320 shaders nintendo or any developer for that matter wouldn't be able to utilize it's power because of it's limited bandwidth just like how the X1 is starved like hell for it LOL.
|
I heard developers can get past that problems of the bandwidth cause of the 32mb of edram, which would be enough for a 320 shader gpu, but microsoft has 768 shaders, and is relying mainly on the 32mb of esram, which is jut not enough for high demaning games at 1080p.
|
The only reason console manufacturers even use embedded ram in the first place was to reduce cost and save bandwidth when depth buffers and back buffers are being used in the process as well as applying alpha blending operations on the scene. For the most part it is the ROPS that benefit the most from it on the GPU seeing as how all of these buffers are heavily used by the ROPS. I say that 32 mb of eSRAM is better considering the fact that it can more elegantly implement a software tiled rendering due to it's higher bandwidth.
|
when its all said and done, even though nintendo made a weak console its more balanced then the xbox1 which has a medium range gpu, with a huge bottle neck, i mean devs are even stuggling to run current gen games at 1080p. nintedno console was never meant for 1080p gaming but a 320 shader gpu would have been a nice step up to what we have on 360/ps3, even if the games were to run at 720p, at the very least we would get better framrates and AA solutions.
|
Actually the X1's solution is more balanced seeing as how it doesn't have an anemic CPU or memory bandwidth compared to the WII U. 4A games cancelled metro the last light on WII U cause they figured out that the CPU could only do 15 Gflops LOL.
Essay Pro