Yes, you are absolutely right. Seems that I was a bit too focused in the load value
I was scratching my head because I could not reproduce the results in the video again...
And I found that it only happens while I'm recording the screen, so this must be an error calculating the speed when the cpu is overloaded.
Oscilloscopes are updated in a different thread that the simulation, but if you reach the maximum of your cpu then everything goes down the hill, the application starts to miss timer events or the timer can't keep the speed.
I will try to figure out how to solve this, but I don't even know what is exactly happening.
Changing the oscilloscope values can make the simulation faster or slower.
For example the oscilloscope at the bottom has 3 active channels, then:FastSimulation
circuit: at 1ms time div
, this is 10 ms for the screen, so around 10*31k*2 = 620 k samples per channel, so 1.86 million samples to read when updating the screen.SlowSimulation
Circuit: at 5 ms time div
, is 9.3 million samples.
Also setting voltage offset for example add some calculations, making it worse.