 |
Trunk Rev 7870 force capped FPS when timescale is enabled |
|
|
Rev 7875, further improvement to this fix |
|
|
Rev 7887 trunk. Now timescale truly works with uncapped rendering. (Previous fixes simply capped FPS when timescale was enabled.) |
 |
The same issue exists with 2.08 now. |
|
|
Regression confirmed. In SVN, timescale only works with capped FPS... |
|
|
Broken by 4924 Rev 8435 Limit Tic Duration: Old code game_local.cpp: int idGameLocal::getMsec() { if ( idSessionLocal::com_fixedTic.GetBool() && com_timescale.GetFloat() == 1 ) return time - previousTime; else return USERCMD_MSEC; return time - previousTime; Probably just needs an "if com_timescale.GetFloat() <> 1 set to USERCMD_MSEC" condition. |
|
|
This doesn't work: int idGameLocal::getMsec() { if (com_timescale.GetFloat() != 1.0 ){ return USERCMD_MSEC; } else { return time - previousTime; } |
 |
I have written an article about this sort of things: https://wiki.thedarkmod.com/index.php?title=Time,_frames_and_ticks And I think timescale should not work with uncapped FPS, because it accelerates async ticks, and uncapped FPS mode runs independent of async ticks. Another similar cvar g_timeModifier should work as usual, although it is dangerous because it can break physics easily if set too high. On the other hand, I can timescale multiplier at the place where timesteps are computed, before timestep cap happens --- that should have desirable effect. |
|
|
I have a prototype working locally (see 0005324). But I guess I won't commit it before GUI refactoring is finished =( |
- Anonymous
