By using this site, you agree to our Privacy Policy and our Terms of Use. Close
curl-6 said:
Zkuq said:

I don't know or remember enough of some of the games you mentioned, but here's my thoughts on the ones I think I do:

  • Far Cry 2/3: I don't see anything too CPU-heavy, and usually there aren't even that many NPCs either. That said, they would probably have looked significantly worse at 30 FPS, because I feel like they were already pushing it a bit at the time and haven't aged too well. They looked great at the time though, but in hindsight they're not as great.
  • Red Faction Guerrilla: Haven't played it yet, but I can definitely see the amount of physics-based destruction being quite heavy for the hardware. Since destruction is such a core element of the game, they probably designed the amount of destruction based on the hardware.
  • Assassin's Creed: Probably varies a bit, but I can see them being quite CPU-heavy due to the amount of NPCs. I know at least Origins is known to be quite demanding CPU-wise, and I can see that being the case with the older titles as well.

Far Cry 2 had a ton of physics from destructible foliage (which even reacts and bends out of the way when you touch it, something many modern games don't even do) and structures to fire that spread and are influenced by factors such as wind like in BOTW, you could even shoot individual twigs off trees and bushes. 3 also had fire propogation, plus just how draining having an open world with aggressive data streaming was on 7th gen hardware.

Maybe I'm overestimating the capability of 7th gen console CPUs, but I don't think this sounds particularly demanding or anything that couldn't easily be downgraded without much more than visual impact. Not much of what you mentioned needs to run every frame either, especially at 60 FPS. Destructible foliage for example is something that most likely has the biggest performance impact when the actual destruction occurs, which is definitely not every frame all the time, it's a very short period or perhaps even instantaneous depending on how it's implemented. Fire spread seems like the major thing that I forgot, but personally I'd be surprised if it was too bad either (it doesn't need to run at 60 FPS either, probably not even at 30 FPS).