The more threads i add ( 6 threads in this vizzy) the slower the seconds counter goes. When compared to Time Since Launch, it's down to almost 33%
Bug
Rejected
Found in 0.9.601.0
| View |
4 Comments
- Log in to leave a comment
-
-
8,443 crowxe3.4 years ago
@Tweedle_Aerospace That's strange, i've never noticed it, maybe it's more aggressive when having more threads.
-
4,774 TweedleAerospace+1 3.4 years ago
Yeah I have noticed this when making counters. I have seen this many times before reported. Since 9.3 I think.
2 Upvotes
Log in in to upvote this post.
The problem is the flight computer can't keep up and is falling behind. By default, the flight program will execute one thread at a time for up to a total of 25 instructions per frame. In this case, there are several threads that are stuck in while loops, so each frame only one thread is being executed since it's using up all of the instructions per frame. One way to mitigate this is to introduce a Wait 0 Seconds instruction as the last instruction in a while loop. This will cause the flight computer to stop executing that thread (until the next frame) and move to the next thread. Otherwise, it will just loop back to the beginning of the while loop and continue processing until it reaches 25 instructions and then no other threads will execute that frame.
If that still does not fix the problem, then you can try increasing the max number of instructions per frame via XML-modding: