Sure Xray! In algodoo there is a built in function called "Bench_steps(n)" which does the same code as my "benchmark" function except "Bench_steps(n)" prints to the console.
The code basically gets "System.time" which is like "sim.time" except it never stops and also is a more specific number.
Next, it forces the simulation to run 100 steps (i.e Sim.Step_N(100);)which is just like running the scene but it does it as fast as it can! (A step is one total scene calculation for 1/(frequency of scene) of a second)
Then it gets the system time again, finds the difference and it shows how long it took to do 100 simulation steps!
The buckle moving is from floating point precision. Algodoo is trying to keep track of 1000's of different variables and to save ram and performance it isn't 100% accurate. Every time you undo your scene it shifts some items.
Thank you! Yeah I know it just drops the weight, it was confusing just getting it to do that! I'll look into making it lower slowly either the way you said or another!
The code has proper syntax. The update uses an if statement so if sim.time == 0 it will define gearbox which wont go forever once the scene is played.
The gearbox needs to know the users personal scene's sim frequency. Some people use 1000hz others use 60hz
After multiple factory Algodoo resets i think it fixed it. It works after the reset, for me, please try again Xray. Thank you so much for looking over it and helping!!!!!
Oh thank god!!!! I'm 100% sure it was the addition of "scene.my" to the function! Thank you again for your help!!
The scene is meant for users who make a vehicle in another scene and use this scene to generate their gearbox. Some people make their scenes using 100hz or some other frequency other than this scene's. Sorry if that doesn't make sense but it is necessary trust me.
You did a very good job don't worry!! and thank you!
Haha over looking small things!! I realized after looking at my code for a while the onClick function didn't use "scene.my.gearbox()" it was just "gearbox()"
Oh wow yes that's the whole process! I would suggest users to select the gearbox and copy and paste it as needed. I think that's easier for novice users.
I just figured it out! If you type into the console "Sim.limitAngVel = +inf" it removes the restriction of max angvel = (freqency * 1.56). The wheel is still unstable and the axle can "explode" but it will spin at any speed