By using this site, you agree to our Privacy Policy and our Terms of Use. Close
zippy said:
Does it have muddy graphics or jaggies. Im not a graphics whore, but im getting irritated by articles and forums dissing WiiU and its graphical performances. Since im from England i wont be sampling WiiU delights until at least next week or beyond. So i want to hear it from the good people here on VG chartz who own WiiU, does it stand up graphically and are the reports just fanboys stirring up a bit of trouble.


I think that lot of that talk comes from certain BLOPS2 shadows problems (from Neogaf):

http://www.neogaf.com/forum/showthread.php?t=500393&page=4

"Just to add to this thread, I've played a couple of missions thus far and it's not good.

The Digital Foundry article featured the first area benchmarked on PS3 and 360. During some of the parts they show the framerate flucuates between 45-50 fps dropping as low as 40-ish on PS3 during the slowest point. On WiiU? Yeah, that same area (right before the chopper) sinks UNDER 30 fps. It's juddery and choppy. On average the framerate seems to spend a lot of time around 50 fps.

Now, it generally doesn't sink THAT low during gameplay but it spends way too much time under 60 fps. The 360 version is much smoother and even the PS3 version seems to have an edge. The image quality seems more in line with 360 at least, which is to say that it's jaggy as hell, but not blurry like 1.02 on PS3.

The shadows are also nasty. Until you stand right up on them, they appear at a very VERY low resolution and only resolve into higher detail when you press your face right up against them.

http://www.eurogamer.net/articles/di...ops-2-face-off

Regarding those two shots above...

When I returned to that area, the pillows DID appear on WiiU. I don't know why they were missing when I snapped that photo, but they were. Secondly, the shadows DO eventually become the resolution as you see on 360 *BUT* only when you are within VERY close proximity. From any normal distance they are a chunky mess."

 

I think problem is BLOPS2 being lazy port.