By using this site, you agree to our Privacy Policy and our Terms of Use. Close
Biggerboat1 on 27 February 2019
Edit Thread
Nate4Drake said:
Biggerboat1 said:

When you say "The 2,4 GHz CPU could be already well above what is needed for the 4+ TF GPU of Lockhart, while the 3,4 GHz CPU enough for Anaconda Architecture" I don't think you're taking into account the different target resolutions...

Here's a video explaining the relationship between resolution and CPU use - the conclusion - the CPU usage stays the same regardless of 720/1080/4K - so the premise of your statement is flawed - there's no reason to downgrade the CPU in Lockhart just because it is outputting at a lower resolution... If the 2 skus were targeting different frame rates, then yes, you'd have a point, but resolution, no...

You are perfectly right on this, but it was not my point.    With a faster CPU and GPU you can achieve higher frame rate at higher resolution, together with more advanced physics, animations, system collision, better AI, etc etc.   CPU is mostly stressed by higher frame rate and all the things we have already said ↑↑↑, while GPU by higher rez, higher geometry(CPU too), tessellation, effects, etc.   That's why I said 2,4 GHz and 3,4 GHz for Anaconda, in order to have not only Higher Resolution and better graphics due to the more powerful GPU, but also higher frame rate and better physics, AI, and all the "non-graphic" calculations/app.

 I saw that video, yep, it explains very well what you said.  Really cool video and well done!

I don't see why they'd target different frame rates as that would cause major issues & needlessly complicate things...

It means you absolutely couldn't have any Anaconda game run at 30fps as that would result in a slideshow on Lockhart - sub-30fps doesn't exactly scream next gen...

If they use the same CPU across both, different GPUs as leaked, a bit less RAM for Lockhart due to smaller 1080 textures and potentially even a smaller hard drive for Lockhart (though that is contrary to leak), again due to lighter assets then you have 2 boxes that are equally equipped to deliver parity over the the 2 different resolutions. The amount of money saved through weaker GPU, less RAM, potentially smaller hard drive should be adequate to offer the lower sku at a good discount. There's no need to hobble the CPU - that would just cause headaches for developers.