Wii U version of Project CARS facing troubles, likely cancelled

[Alby_da_Wolf]

hsrob said:

Hynad said:

megafenix said:

Read accurately, if the 60fps is the 100% that we want to reach, then 30fps is 50% of that goal, meaning that if we increase 30fps again that would be another 50%

 

the same applies for 23fps to 30fps

how much is 23fps from 30fps(100% we want to reach), then the 7fps that we are missing are the ?% we still have to accomplish to get the 100%(30fps) since the 23fps percentage has already been achieved

 

The base isn't 30fps. That's the wanted outcome. You're looking at it in the wrong direction.

To achieve 30 fps, they don't have to work from 30 to 23. They need to get a percentage increase from 23 to 30.
They need to work up from 23. Not down from 30.

So, the % increase from 23 to 30 is 30%. Since 7 fps are missing to achieve that, and that number (6.9, in fact) is 30% of 23.

I have to agree with Hynad here. There is a convention for how we state these things, for a reason.

30 is 50% of 60, 60 is the comparator i.e. what you are comparing to. When you are are talking about an increase e.g. from 30, 30 is the comparator. So a 50% increase is 45, a 100% increase is 60.

If we consider 30fps as the ultimate goal, then 30 is the comparator and they have achieved 23 of 30 or 77% of their goal. If we are talking about an increase from 23, 23 is the comparitor. They require a 7 frame improvement from the current base (=7/23), they require a 30% increase from 23.

So we could say:

- We need a 30% increase from our current frame rate (23)

- We have achieved 77% of our goal (30)

Any other way is unconventional and bound to cause confusion.

This. While one can say correct things with his method too, it's not the correct one to say what's the increase needed from current performance.