after a while driving this car it might break due the jittery and laggy motion.
this has the same reason as the mistery about the jittery motion in Minecraft Inf dev where players could visit the far lands.
so the further you go the more inacurate the motion gets.
Thanks Xray. I will delete the code i forgot to delete in "update",
i think you mean those boxes i only left there for debugging purposes for experienced users.
Its also good to know where the difference is between "update" and "postStep".
And yes, i forgot to put some controlls into the description,
i was just afraid of getting banned for uploading stuff too many times.
Update: meanwhile i was searching in algodoo wiki for how to make a "If ... Then ... Else ..." and did some coding. anyway thx, im gonna read every single Letter in your reply.
oh yes, for the problem with the code that gets forced to change the value of one variable is something i couldnt fix due to the design issue that this motor has, unless i take it the ability to spin in two different directions, wich wouldnt be a benefit at all.
Specs:
CPU: i7 9700k [12Mb Intel smart cache, 95W TDP, 8 Cores] (Overclocked to 5.1 GhZ Clock and cache frequency with Intel (R) Extreme tuning Utility)
GPU: 2060 Super (Overclocked with OC switch from manufacturer (Asus ROG: Strix series) to ~1470 Mhz Clock speed & ~7000 Mhz Memory Frequency)
RAM: 16GB GDDR 4 3200 MhZ
Additional info:
Only Algodoo and the Intel (R) Extreme tuning Utility and its monitoring software (wich also sucks a small bit of performance) was opened while benchmarking.
the first test might be the highest score you get because your cpu still might be cool then, but after the first try your CPU might be throttling already.