 |
Isn't com_fixedTic 0 a sufficient and complete fix for this? If we really want to make it fluid then someone needs to dive into the rope code in search of hardcoded const's |
 |
Yes, disabling "Uncapped FPS" removes the problem completely. So it is not critical for release, hence scheduled for 2.08. I understand that it is not a simple problem, but I hope someone could fix it in some future =) |
 |
If someone goes into this issue, maybe it could also be investigated why rope-swing is so clumsy. |
|
|
These crazy rope physics also affect the player when he is attached to it, btw. Try it e.g. on the training mission. Although I have a decent rig, running the latest Debug build (rev. 7897) resulted in 20 to 30 fps. In the training mission, I just jumped on the hanging rope over the channel and was thrown around like crazy, eventually landing in the water, while awkwardly still being attached to the rope. |
 |
I'm gonna try a little hack to improve 2.07 until a proper solution is derived: game_local.cpp if ( idSessionLocal::com_fixedTic.GetBool() && com_timescale.GetFloat() == 1 && !physicsObj.OnRope() ) Edit: Doesn't work when applied to just game_local... |
|
|
Nbohr1more, please do not hack everything to make it work. It might happen soon that nobody will be able to understand how different modes interact with each other. I understand that debug visualization tools are much easier to send to non-capped mode than support them properly, and they are not for ordinary player. But please do NOT toggle uncapped FPS for ordinary gameplay. |
|
|
Understood. I wasn't really happy with this workaround anyway. |
|
|
One more forum thread about the topic: http://forums.thedarkmod.com/index.php?/topic/20173-limit-timestep/ Basically, I have a feeling that the problem is caused by instability of ODE solver approach (which is most likely explicit Euler) on large timesteps. The suggested fix is to limit timestep of any game tic by 17 ms. |
|
|
Done in svn rev 8435. Now with com_fixedTic = 1, game tics are limited by 17 ms (com_maxTicTimestep). When com_fixedTic = 0, then all game tics are exactly 16 ms --- as before. In both modes, at most 10 (com_maxTicsPerFrame) tics are modelled each frame. If frame takes more than 170 ms, then game time perceptively slows down. |
- Anonymous
