limited clock mode not accurate enough?

[MichaelPanda]

i use limited clock mode in Panda and set fps limited at 30. when i read the built-in fps meter of Panda , often i read 29 or 28. 29 is fine, computer always has a little error in calculating float number . but 28 means the program slows down. but i am quite sure it was Panda slept a bit too much , not that my CPU couldn’t catch up.
can the clock limiter be more accurate?
or is the FPS meter not accurate?

[yukiyamane]

The accuracy of Windows time may not be good by default. I think this code can improve the accuracy.

from ctypes import windll
windll.winmm.timeBeginPeriod(1)

[rdb]

See this thread:

【Solved】Limited framerate is not stable

I limited the frame rate to 24 because I wanted to create a cinematic look. globalClock.setMode(ClockObject.M_limited) globalClock.setFrameRate(24) However, the frame rate is changing all over the place. For example: 22.9, 23.7, 23.2 self.setFrameRateMeter(True) When I record the screen with OBS, it is choppy. Is there any way to stabilize the frame rate?