[Cocos Creator 3.6.2] RigidBody2D moving slowly on lower fps

[theamirbeg]

Hi, I’m using Cocos Creator version 3.6.2 the RigidBody2D Linear Velocity is not behaving as per fixed timestamp. On the lower fps it is moving slowly and on higher fps it is moving quickly.

This issue is similar as these posts below:

Framerate, FPS, and physics

I have seen a couple of threads with this issue, but none going into detail and none having a substantial solution. My team and I are currently making a game that relies heavily on 3d physics for platforming. We noticed that on devices with different FPS the physics behaved very differently. The simplest example is our jump. On a 144hz device we’d see a super jump, while on 30fps we’d have half a jump. This issue was initially caused by not setting fixedTimeStep to match the fps. We defaulted …

Framerate, FPS, and physics2D Creator 3.5.2

Hi, We are using Cocos creator version 3.5.2. We noticed that on devices with different FPS the physics behaved very differently. The simplest example is Distance Joint . On a 144hz device we’d see a different movement, while on 30fps we’d have half movement. This issue very similar to below post. @ zzf520 Is this issue fixed?

[muxiandong]

Sorry, this issue has not been fixed yet. We have identified and documented this issue and will fix it as soon as possible. Thank you for your feedback.

[smitpatel88]

@theamirbeg

On the lower fps it is moving slowly and on higher fps it is moving quickly.

This one is really serious issue.

@muxiandong

Sorry, this issue has not been fixed yet. We have identified and documented this issue and will fix it as soon as possible. Thank you for your feedback.

May I know why its not fixed yet? because of this we cant launch any physics based games at all.
As now a days there are lot of devices with 60/90/120/144 hz so physics calculation will be different and game wont run as expected.
This should be fixed on priority.

[gandangf]

I too have the same issue. It’s hard to make a game with physics. It’s not fair. Need a quick fix.

[perfecto]

+1, seems they just focused on features those required by investor, not developers. very sad.

[XAEA]

+1

this hack solved this problem but I’m not 100% sure. this looks working for me.]

update(dt: number) {
    PhysicsSystem2D.instance.fixedTimeStep = dt;
}