A developer tells this anecdote from a project from the PS2 era. They showed a pretty late build of the game to their publisher, very few weeks before the game had to be ready to begin the distribution process, and the FPS appeared at a corner of the screen, never quite falling below 30FPS, but often making important jumps. The people from the publishing company said that “Everything about the game looks fine, except for the FPS. 30 FPS is unacceptable, and we cannot publish it if you can’t reach a consistent 60 FPS”.
You don’t need to know much about development to understand that making such a demand weeks before the launch of a medium-sized project is asking the impossible, and so did this dev team. In the end, they changed the function that took the real calculation of the FPS so that it returned a fraction of the difference between 60 and the real FPS, so the next time the publisher took a look at the game, the FPS counter would always show a value between 58 and 60, even though they didn’t have the time to really optimize the game. The publisher didn’t notice the deception and the game was a commercial success.
Did you not see the part where it said “PS2 era”? The turning rates of the player/camera in any console first person shooter from those times are downright sluggish by mouse/keyboard standards, but the games were also designed around that slower pace.
A developer tells this anecdote from a project from the PS2 era. They showed a pretty late build of the game to their publisher, very few weeks before the game had to be ready to begin the distribution process, and the FPS appeared at a corner of the screen, never quite falling below 30FPS, but often making important jumps. The people from the publishing company said that “Everything about the game looks fine, except for the FPS. 30 FPS is unacceptable, and we cannot publish it if you can’t reach a consistent 60 FPS”.
You don’t need to know much about development to understand that making such a demand weeks before the launch of a medium-sized project is asking the impossible, and so did this dev team. In the end, they changed the function that took the real calculation of the FPS so that it returned a fraction of the difference between 60 and the real FPS, so the next time the publisher took a look at the game, the FPS counter would always show a value between 58 and 60, even though they didn’t have the time to really optimize the game. The publisher didn’t notice the deception and the game was a commercial success.
The game was called “Tetris” btw
deleted by creator
30 is unplayable? I guess I haven’t played all these games then.
deleted by creator
Did you not see the part where it said “PS2 era”? The turning rates of the player/camera in any console first person shooter from those times are downright sluggish by mouse/keyboard standards, but the games were also designed around that slower pace.
deleted by creator
Then why tf are you even commenting?? Some people smh
deleted by creator