You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Level on which the issue is apperent: m6-exterior
Specific Script Command: $world.physicsvar ( "gravity" , 80 );
Script Command translates to Gamecode:
How to recrate: Load the Level in Singleplayer and make sure you have V-Sync Off and you com_maxfps set to something above 75 FPS, like for example 120 and compare the speed at which you glide down after a jump with fps at (com_maxfps 75) an (com_maxfps 120). The higher the FPS the slower you will glide down.
Conditions: g_gametype 0; g_gametype 1; dedicated 0;
Singleplayer/Listen Server, Offical Relase 1.1, the GOG Version has a "fix" that limits the FPS to 85 at which the issue isn't as apparent.
The issue does not occur on dedicated servers, it is reasonable to assume that it has to do with something where the game uses CLIENT 0 gameframes for the calculations. There probably is a math inaccuracy or a limit missing. I have not really looked into that issue.
The text was updated successfully, but these errors were encountered:
Level on which the issue is apperent: m6-exterior
Specific Script Command:
$world.physicsvar ( "gravity" , 80 );
Script Command translates to Gamecode:
sv_currentGravity->value
How to recrate: Load the Level in Singleplayer and make sure you have V-Sync Off and you com_maxfps set to something above 75 FPS, like for example 120 and compare the speed at which you glide down after a jump with fps at (com_maxfps 75) an (com_maxfps 120). The higher the FPS the slower you will glide down.
Conditions:
g_gametype 0;
g_gametype 1; dedicated 0;
Singleplayer/Listen Server, Offical Relase 1.1, the GOG Version has a "fix" that limits the FPS to 85 at which the issue isn't as apparent.
The issue does not occur on dedicated servers, it is reasonable to assume that it has to do with something where the game uses CLIENT 0 gameframes for the calculations. There probably is a math inaccuracy or a limit missing. I have not really looked into that issue.
The text was updated successfully, but these errors were encountered: