Scene.my.spots is not defined and so are all of the other variables. nothing works. looks like your other scenes have similar problems download your scenes and see what I mean
If you are going to do this, please redesign it so the marbles don't get stuck. It defeats the purpose of a marble race if you have to manually move the marbles around. Thank you
For anyone wondering about the star trek pinball:
Progress is going great, everything is working all good, still getting in more features and play testing, and finishing the graphics as well. I don't want to post any scenes of my progress because I want the end result to be a surprise, but even in its current state, I think it would be the best pinball experience in algodoo. The teaser is nothing compared to what will come out. This is a small part of it.
i was demonstrating that you could paste what is copied when you copy an object, and it applies to all shapes including complex polygons that you can only copy from, I was going to use my more complicated shaped quarter but settled on a circle for this demo because the surfaces section was massive, took up like half of the script lines since it came from a fine gear. this was meant as a beginner script and was mad to answer a question in the algodoo reddit. Thank you though
For most creators this bug is very difficult to notice since it requires a lot of time and the use of grid aligning for it to be noticeable. I have read about it being documented at least once by someone on an algodoo forum.
It happens in all scenes, randomly starts and stops. It seems to be tied to objects that are the same as it (copy and pasted or cloned ones) and behaves very strangely, here is a video of it happening.
https://www.reddit.com/r/Algodoo/comments/smgd6b/circle_drift_glitch/
Apologies for the large file size. It was actually at 24MB earlier and there is apparently 15MB upload limit so I had to do a bunch of graphical optimizations. I still have a bunch of graphics not added yet so Im not to sure how I am going to fit those in.
I dunno what to tell you, I'm running full speed on a 2013 macbook air, make sure your sim speed is at 120hz. I have no idea why its laggy on your end, I assume you are on a better device than me.
this is pretty cool
the script for the enter key should be backslash n so it would look like
(e)=>{
scene.my.text = scene.my.text + "/n";
scene.my.laz = 0;
scene.my.mot = 1000
}
but the slash is the other type which is \. Not /. i cant type \ n without the space inbetween because this comment is formatted the same so when i type \ n without the space inbetween, it just displays an enter in the end