Time accuracy is affected by the number of threads. When the number of threads increases, the longer the code waits for 1 second to execute, the greater the error from the actual time.
When the number of threads is smaller, the code execution time waiting for 1 second is shorter than the actual time.
When using an infinite loop of waiting for 1 second code as a timer, the error increases over time and is affected by the number of threads.
No matter what spacecraft, what command module, or waiting for "x" seconds, there are significant errors.

Bug Rejected Found in 1.0.8.0
Sandbox View

4 Comments

  • Log in to leave a comment
  • Profile image
    Dev Pedro

    @lhanfei04 it's not necessarily a drop in fps, but how sometimes the addition of each frame's delta time may not add up to a second, and the error just accumulates

    +1 1.7 years ago
  • Profile image
    175 lhanfei04

    @Pedro Thank you for your suggestion.

    1.7 years ago
  • Profile image
    175 lhanfei04

    @Pedro But when I tested, there was no frame rate drop.And the configuration of my phone is very high.

    1.7 years ago
  • Profile image
    Dev Pedro

    Wait x seconds is heavily dependent on the FPS, for precise timings it is recommended to use a reference time, like time since launch

    +1 1.7 years ago

No Upvotes

Log in in to upvote this post.