Usually when I see a car reversing, I'm inside of said car -- so I don't pay much attention to the lights.
I'll be sure to add white lights to new vehicles in the future.
I am, however, pretty sure that 2.2.0 and above won't run on older operating systems like Windows 7 (I can't believe Windows 7 is 15 years old -- it's almost as old as I am ). At the very least, they require a 64 bit operating system and processor
Is this like that weird thing where my phone sometimes randomly shows me a picture of a crying cyclops emoji or an annoyed snail emoji in my autocorrect bar?
I've actually been thinking of making something like this myself!
This year I've really wanted to try making more games in Algodoo -- if I end up making something like this myself, would you like some details on how it works?
@s_noonan I decided to try making the problem much worse to see how much memory Algodoo 2.2.3 can use before crashing.
My computer has a total of 32GB of memory (It's a mini PC though, so the GPU and CPU share memory and the CPU only has 28GB)!
When I started writing this comment, Algodoo was already using 18GB which is far more than 2.1.0 could handle!
Surprisingly, at 18GB, Algodoo 2.2.3 runs fairly smoothly! I was even able to save without the "Out Of Memory" error.
I started feeling noticeable slowdowns at 22GB, presumably as my computer starts having to move more memory around. Surprisingly -- after that, Algodoo got super slow for a few seconds before RAM usage plummeted back to 10GB!
It's unclear to me whether this cycle would repeat however, but unfortunately (or, i guess fortunately if you think about it) it took several minutes for Algodoo to reach such a high memory usage, even with me making the problem an order of magnitude or two worse. I have really, really bad ADHD so I can't stare at Task Manager for possibly hours for a simple experiment
As for what I did to make the issue worse, I replaced the force function with a function that recursively defines a copy of itself multiple times and then spawned way more boxes with this new function.....
1. The reason the first thruster box is stationary and the second isn't is because the second one has more power.
The thrusters *are* pointing in opposing directions, but they are not in the same spot. As such, the force is not evenly spread out and both boxes actually move. The first box just isn't powerful enough to overcome gravity.
Using the grid tool to properly align the thrusters with eachother, neither box moves.
2. You simply attached a gear to another gear.
3. The reason the gears freak out is because they are colliding and Algodoo is trying to separate them, but is unable to because of the way you placed them. As X-Ray has said multiple times, Algodoo will break if you abuse it enough.
4. The laser setup in the image and in the scene is not the same. You are using a straight convex lens for 2 lasers pointing towards eachother. This simply focuses the beam to a point until it flares out again instead of making it go in another direction.
5. Algodoo doesn't handle ropes very well.
6. I don't see the confusion with the boxes, personally.
I'm sorry if this comment sounds kind of offensive/rude (i'm not trying to be offensive/rude), I just don't understand the point of this scene...
I also can't understand the "delayed velocity" thing -- the wording just doesn't make sense to me.
Are you talking about dragging an object while the simulation is paused and unpausing it? The object only moves after the simulation is unpaused because objects cannot move without scripts or certain tools (not the drag tool) when the simulation is paused.
I think this year I want to make a lot more Thyme-related scenes similar to when I first started discovering myself (around 2023).
Last year, I mostly just uploaded cars without anything interesting about them. For the cars I upload this year, I want them to be less plentiful and more unique in terms of scripting similar to this CVT buggy.
One thing I might try to do is build my own dyno similar to The Linkage's!
I think it would be an interesting challenge.
A builder for single-geometry menus would be interesting too.
I would need quite a bit of know-how on how Algodoo handles text in order to pull that off though, of course. 2.2.0 did add a lot of new text features though, so who knows!
Sorry!
For question 1 -- take the input and the thing you want to hook it up to, delete the axle attaching the input to the background (not the input connected to the dyno), and align the centers of the two objects. Then, simply glue them together.
2. Mhm!
Thank you for your comment -- sorry for the confusion!
If you have further questions please let me know.
I fixed the issues you and Xray addressed, as well as a few issues I found myself (the dyno being draggable and the graph getting messed up when you drag it + phunlets dont work properly) and I hooked the Dyno up to the V8 by default.
Thank you for your comments!
If you find any more issues, please let me know.
I don't see how the Sprunki scenes are hurting anyone.
People just have their own interests! -- if you don't like it, just ignore it -- but there's no need to be passive aggressive about it!
What is going on here? This is exactly what Xray said you should not do!
As for the scene, I personally am not interested in Sprunki, but I also don't see any issues with liking it or making scenes about it! I make scenes about car engines/transmissions a lot, but that doesn't mean everyone has to be interested in cars -- that sort of thing!
I feel like on a platform like this it's important to recognize that all content isn't for everybody. It's okay not to like Sprunki scenes, but they aren't inherently bad!
P.S. Thank you for clarifying, X-Ray!
EDIT: I just now saw the ban notice.
Thank you! I feel like flamewars/fights make things worse 99% of the time
I hope my comment doesn't come across as aggressive -- I'm not trying to be mean or "bully" anyone -- just offering an explanation!