Algodoo

I have found a solution to the problem, so I am going to delete this scene.

Nice fireworks!

Nice! One time I got a score of over 3000!

That's Newton's Law.

Basically, when something (in your case a wheel) is spun, whatever is spinning it is spun in the opposite direction with the same amount of force.

So it's not thrusters, it's physics!

You could also set InertiaMult to +inf.

Either solution will work

No problem!

I have fixed it. Thank you for the feedback.

Weird, I like it!

I have ripped the cursor out of the laptop and it is now a physical object.

I am unstoppable!

I right clicked on the background and turned off clouds.
Hope this helps!

It's good, but can I make a few suggestions?

1. Add basic AIs to all of the blobs aside from the little food blobs.
These AIs can be as simple as moving in random directions to having seperate wander and chase modes.

2. Make it control like the original, i.e. use trigonometry functions to make the red ball move towards the mouse without the drag tool.

3. Zoom the camera out a bit more by default, it's hard to see anything.

Other than that I'd say you did a good job!

I see the basic AI you added and I like it.

Anywho, do you mind if I make a scene response showing what I meant by "trigonometry functions"?

It just changed, that's all.

It works!

Amazing!
Pretty sure this is similar to how Softbodies work in other games.

I might make a scene about that soon - It's a really interesting topic and it's very useful for avoiding scene.my.

Long story short you have to go through some Thyme loopholes, but it's manageable.

You did a great job!

I saw what you said and I fixed the issue with set - you should be able to put spaces in variables now.

If you do end up finishing 1.0, I'd put a check in your program to make sure the computer running the program supports strings with spaces.

You could do it like this:

set 0 1 2
if vr0 = 1
gotofunc outdatedVersion

I apologize for Chives being so limited - I started programming it over a year ago and back then I wasn't nearly as good at programming as I am now.

I fixed an issue with set - variables can now contain spaces.

yes

I've considered making a Chives emulator of some kind, however it would definitely be really slow.

I'm working on optimizing this thing and, don't get your hopes up but I may come out with a model that's significantly faster. If I can get it around the vicinity of 300hz (AHOX Helium could run well up to 720hz) then I'm going to add graphics!

I already have a name for the project as I've had it planned out for a while - AHOX Silver.

I won't bore you too much with the technical details but I am atleast planning on making a Chives computer with a Silver display regardless. Chives is limited, but it's very fast as a result.

If I can speed it up but can't reach the 300hz goal, then I'd probably name the computer something like Hydrogen, and there wouldn't be a graphical mode.

I'm still unsure how to bring about updates to AHOX Basic: do I do what I did with Chives and release a new computer ever so often, or do I do what I did with the AHOX Helium and release hotfixes and new features over time to the same scene?

My apologies, for some reason the manual said insert, the command is import.

Good job figuring that out.

Honestly I forgot how Chives computers even worked, and the code is so messy that I think it would be more efficient for me to try rewriting one from the ground up than to update a current one again.

I'm working on a related project that I don't know whether or not is practical, but basically I'm thinking of creating a character-by-character expression parser to put in the next AHOX Basic computer, if i ever make one.

Doing everything manually would probably be slower than utilizing string.split since Thyme is obviously slower than C++, which is what string.split was (presumably) made in.

However, it could pretty easily get around the issues that the parser has, and with how many operations the current one already uses, it could actually be faster? X to doubt though.

Regardless though, I do highly doubt AHOX Basic will ever be as fast as Chives.

fun

Here's a technical explanation for what is happening here and why.


Computers store decimal values in "floating point numbers".
As a floating point number gets larger, it becomes less precise.

One way to think of a float is like this.

Let's say A is a really low precision float with just 3 decimal values.

Storing 1 in A would be as simple as 001.

Storing 1.1 would be done as 01.1.


This works fine for any number up to 99 with up to 1 decimal point, but you can't put a decimal point on 100.

100.?

There's no room to put a decimal place after 100!

This is an oversimplification of course - floats are not in Base 10 and Algodoo doesn't use floats with only 3 digits. But, I'm hoping this is still a good explanation.

Feel free to correct me if I'm wrong by the way!

Probably not because they require a keyboard.

Managed to do all of it but the friend part.

I spawned in an Algodoo chatbot I made previously and asked it a question, does that count?

If I had an iPad, I'd test it out for ya!

..But no, I don't. I have an Android tablet, though. But that can't run Algodoo.



This talk about versions makes me curious - Can Algodoo run on Apple Silicon? I heard there's something called Rosetta 2, and that makes me wonder if that's why Algodoo 2.1.4 hasn't come out for M1/M2 macs.

What do you mean? I'm able to make the object turn.

A way to actually stop objects from turning is to right click on it, click "Script Menu" and type "+inf" under the inertiaMult box.

Part of me wonders how hard it would be to actually set up some sort of attraction-based radio with 8 channels.