Algodoo

It's supposed to be a floppy disk drive. No, no no! This is all wrong!

EDIT: It appears to be fixed now. Thank you!

It had to have been a bug.

That was strange.
Part of me wonders if I somehow got malware on my computer. That wouldn't make sense though because I never download anything..?

Cool map though!..?!

That sucks.
Thank you for telling them though!

I misread editable as edible and thought for a second that the car was made out of candy.
A candy car would taste great though!

[Redacted]

This scene did indeed give my chives computer a [BAD] time.
Nice work!

You have officially created a masterpiece.

What about gasoline engines? Could try something like that!

Thank you!
I apologize for replying so late -- but I think I would like to go through with that idea.

Thanks!

I apologize for my inactivity, I've been going through a lot in life lately.

I haven't been working on any computers, sorry!

At the moment I don't plan on continuing any AHOX scenes -- I feel like my AHOX scenes were really low quality and I keep finding bugs left and right in my sloppily coded computers.

If I do release more computers, more than likely they will just be proof of concepts and not AHOX machines.

Edit: I changed my mind and a new one is in the works! No guarantees on the release date but incase you wanted any, here is some information about the computer!

The computer is going to be an all-in-one (the monitor and computer tower will be part of the same object) that runs AHOX Basic 2.0.

If you're wondering, I'm planning on naming it "AHOX Beryl" and naming the processor "Oxide".

No promises though!

Hi Xray!
My apologies but I changed my mind and now I think it would be best if I didn't change my username.
Thank you!

Thank you!

I haven't been working on any AHOX computers though -- the closest I have to a new AHOX computer is an All-In-One Lithium.

Edit: I have started work on the AHOX Beryl!
No promises but I'm hoping to release it soon.

Hello!

In case you are curious, the reason this happens is because of something called Floating Point Precision. Computers have limited precision with decimal numbers -- think of it like having a number that's limited to 10 digits.

Each digit can be any digit from 0 to 9 and you can place a decimal point wherever -- but 10 digits is all you get!

Of course, that would work for small numbers, such as 2.500000000.

But what about larger numbers?

Let's try 999999999.0. We only have 1 digit for fractions.

Worse yet, if we add 1, we can't fit *any* fractions! Only whole numbers can be represented above 999999999.9 with this method.

Of course, this is a dramatic oversimplification -- I don't actually know that much about how floating point numbers work, but I'm fairly certain its something similar to this. Another important note is that computers use Base 2 for floating point numbers rather than Base 10, but that's a whole other can of worms!


So, what you are seeing is Algodoo facing a similar issue, which is what results in the choppy movement!

Pretty fun, huh?

Weeeeeeeee

I have bad news.

I have just found a giant bug in this computer that would unfortunately severely compromise performance to fix!

Basically, lookup functions like the ones that look up variables use the regular "for" function and thus have a pretty shallow limit. If you have too many variables, they will stop working!

I am currently working on the next AHOX computer and I encountered this bug and fixed it by replacing these fors with xFor, but now performance has been compromised.

Can anyone help?

EDIT: It's okay now!
I optimized something else I was putting off until later and it's even faster than the Lithium was now.
That's the one benefit of having messy code, I suppose!

I can't download the scene because my browser is freaking out about the HTTP connection.

If you haven't tried it, try selecting all of the components and enabling no self collision!

Hope this helps!

I managed to get the scene and I think I know of a solution!

First, select all of the objects and turn on no self collision.

Then, select all of the axles and open the Script Menu. You should see a variable called "LegacyMode". It will be set to 1 -- try setting it to 0!

Hope this helps!

Ugh.
Unfortunately, split isn't working properly and I'm now remembering why I didn't include it in the Lithium Manual.

I gave it a basic test and for some reason it worked in the test, but its still not working properly. Worse yet, if I right click on the processor and enter the script menu after it fails to run, it crashes Algodoo!

I am going to have to release a hotfix unfortunately along with the new version of BoltOS.

Alright, I have added your request to BoltOS!
Thank you for your feedback!

Import basically appends a program to the currently running program, allowing you to use functions from the imported program within the currently running program.

I hope this helps!

I do wonder how difficult it would be to create a Chives emulator within AHOX Basic.

I feel like it could be done, but my main concern is the speed.

xD You're right, i completely forgot. (That and I had a looot going on in 2023, so...)

I have been toying around with something similar that's compatible with both AHOX Basic and Chives processors though!

:bonk: :bonk: :bonk: :bonk:

Doing the laundry just got so much more fun!

Hey Xray! I had a question regarding the rules.

Is it okay if I ask for people to tell me if they don't understand something in my scene so I can correct it? (Unless they're one of my friends, they would have to do so via comments)

I am working on a scene that has some pretty complicated instructions and I'm not confident in my abilities to write good instructions

Thank you!

Indeed! Wait works completely different now!

Random fun fact btw -- Internally, exit is essentially just Wait but with an infinite wait time.

Whoops! There should be a system variable for the program counter!
Try using @pc - I might have forgot to add it to the manual
Hope this helps!

Edit: Ohhh wait, I see what you mean. Derp
I thought I added variable functionality to goto but upon testing it it appears I didn't.

I should probably get around to doing that eventually then...

Fun!

I found a few bugs though:

1. If I type the name of a .UIF that doesn't exist, the computer crashes.
This is the error and memory dump:

[ERROR] Undefined Function failedRender at line 720
System Halted!

MEMORY DUMP
variableNames = [uif, file, img_width, img_height]
variables = [nonexistant, -1, error, error]
pc = 710
failedCommand = if file="-1" then goto failedRender
stack = []
sp = -1
functionNames = [keycheck, downloadedViewer, keycheck2, uifIntro, uifViewer, uifDownload, lithiumdownload]
functions = [7, 12, 25, 29, 62, 107, 120]

2. If I say no to returning to the OS, I return to the OS -- but if I say yes, I am asked to open another UIF!

3. Downloading the UIF viewer doesn't work for me:

[ERROR] Undefined Function at line 1170
System Halted!

MEMORY DUMP
variableNames = [df, ver, k]
variables = [uifview, 2, Downloading...
[ERROR] Undefined Function at line 1170
System Halted!
Press A to view memory dump.
]
pc = 1160
failedCommand = let k=section("def downloadedViewer", "def uifDownload")
stack = []
sp = -1
functionNames = [keycheck, downloadedViewer, keycheck2, uifIntro, uifViewer, uifDownload, lithiumdownload]
functions = [7, 12, 25, 29, 62, 107, 120]

Also, BasicNotepad crashes whenever I press Enter.

For clarity, all of these bugs were recorded on an AHOX Beryl.

I hope this helps!
Thank you for writing these!

Perhaps!
But for now anyway, I would like to take a break from the computers if that's okay. I've been kind of stressing out over them and my brain is goop.

I hope that's okay.