By using this site, you agree to our Privacy Policy and our Terms of Use. Close

Oh no! This is such a bad comment to make.

First, what is the criteria for 'maxing out' a console? If I wrote some code that was inefficient and tried to put 1,000 complex objects on the screen at once using Havoc, and if that code failed to run on the 360/PS3 would I have maxed them out?

No, I'd just have bad code.

Now I'm not saying they're lying, but really this tells us more about their code than the 360. It tells me their current engine has a limit for objects, etc. for the 360. It doesn't mean the 360 is 'maxed out'. Another engine might better exploit the architecture and allow for more objects, etc.

It's the same with the MGS IV for PS3 stuff. I'm sure the code was good for MGS IV, and perhaps for that engine/code it squeezed all the code could from the PS3, but that doesn't mean later code, with better SDKs, etc. won't squeeze more from the same PS3.

The only good quote I ever saw like that was when Insomniac published an internal review of their own engine. Unfortunately this was taken way out of context by many but it was good because they simply noted how they used the PS3, what code ran where and what memory, etc. it utilised, and noted areas they thought more work could allow their engine to squeeze more out of the console.

So pls remember, really this info tells us about Volition's current engine on 360, it does tell us about some theoretical limit on the 360 for objects, detail, etc.

Oh, and Happy New Year everyone!



Try to be reasonable... its easier than you think...