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

The issue is the 1.5 would be hard to get out of the Parker in general.  That's double the GLFOPS and will also result in more heat which will require more cooling for which the Switch's fairly compact active cooling may not be able to properly supply.  It's much more likely they will just shoot for 1 to 1.1 TFLOPS and wring out every last drop of performance.  That's why you would go with Nvidia, efficiency.  

Basically, I could see augmenting the Parker to get a 35% performance boost to get real world performance parity or something close with Xbone.  I don't see how they could get a 100% performance boost without driving the price way too  high and within the design constraints of the Switch in general.

Well, Im nowhere near a tech expert, and Im actually quite uninformed in this subject, but with the "closer to the 1.5 TF" could could simple be that it manages to squeeze out 1 or two extra TF in terms of performance to rend the game closer to 1080p or/and at 60 fps instead of the 720p that suposedelly the handheld has.Again, Im supposing that is possible and please correct me if Im simly wrong.But isnt, according to the article, the Switch using full floating points, couldnt it theoretically with a cooling system that handles it, achieve the double of the efficency and getting close to the 2 TF? 

Not everything can be done in 16fpp, that's why standard GFLOPS and TFLOPS are measured based on 32fpp. Now having good 16fpp performance can be good for those who take the effort to take advantage of it by having those things the can be done in 16fpp handled in that way, but it won't double performance.  The big issues are cost, battery, and heat though.  I just don't see a means by which Nintendo and Nvidia could get anywhere near 1.5 to 2 TFLOPS while keeping the cost down, battery acceptable, and heat in check.  It's much better to take advantage of Nvidia's ability to make maximum use of each GFLOP and shoot for something more reasonable like 1 to 1.1 TFLOPS and use the advantage over AMD's tech to get real world performance parity (or very close) with the Xbone since that could almost certainly be done with the systems price, battery, and cooling targets maintained.