Thank you! Also, you can make a AutoHotKey script that maps keys like Space to Shift, and Shift to Ctrl, to make the keyboard feel more like a regular keyboard layout.
Okay, that above comment was a joke for someone, but you're not wrong about the beefy computer, because on my main PC with a i7-2700k and 24GB of ram, this runs at like 60fps. I'm on a Radeon RX 570.
There's a bug. If you're on a screen that says something like "press a to install", then you press the key, the key spills over to the input command in the "which sector do you want to install to?" screen. Lowering the clock speed doesn't seem to help for some reason, despite it working on earlier computers.
This reminds me of when I printed out a Chives 4.3 manual, but it wasn't similiar to this at all and I used a very old Little PC with a printer slot. I then made the text resolution on the paper higher.
Beside the File text in the top left corner of the screen, there is a gear icon. If you click that, you go into options. Click on the Simulation tab in options, and disable incompressible fluids.
Came back from inactivity, and this is just revolutionary!
Somebody's gonna make an emulator on this some day. I don't know what it'll emulate, or how it'll even work, but it'll be made.
I successfully solved that problem! Basically, the computer runs Chives commands by sending every command it gets to a function in the CPU called "_process". However, in the Long PC, _process got stripped down so much to a point where it could only run 1 command, "paint", which is actually just the print command. So to fix this, I copied and pasted the _process function from the Helium PC to the Long PC, and now, it can run programs completely fine!
Hey Little, do you think the AHOX PCs would run on Algodoo for iPad? I don't have it right now, but appareantly, you can't script on an iPad. However, that's all I found. It doesn't say if you just can't make and edit scripts on an iPad, or if they are unable to run entirely, regardless of the scene.
I know that coding Thyme on an iPad would be hard, but would it be hard to *run* Thyme code that was already coded in a scene? Or can PC scenes not run on iPad or something, like I mean... I did see a separate "iPad" group on the Algobox search interface when you access it via a browser.
Xray: Thanks! I think that answers my question. (meaning that thyme code does get executed on the ipad, you just cant make thyme code on the ipad yourself)
Little: I appreciate your help regardless. I was just curious by the way, considering that I have an Android tablet too. Anyways, I think Algodoo should work on Apple Silicon via Rosetta 2. (but if it doesn't, you can always try using the iPad version on macOS)
I decided to test this things backwards compatibility and it turned out interesting!
Although, it (obviously) works on the Helium, I decided to go as far back as I could. Turns out, it works on all AHOX computers down to the Competitor Model S & E, which were the 4th and 5th computers of the AHOX PC line-up respectively. Getting the DC-1k info works fine, the status on whether it can boot or not, and reading & writing to it.
However, on the Operator SoC-Powered Programmable PC, (which was the 3rd model in the AHOX line-up of computers) although the test program booted up fine, it couldn't find a DC-1k, even with it plugged in.
I assume this is because of a major chip difference between, because whenever I look at the internals of the Chives computer post-Operator and the Operator itself, I am able to see a major difference between them, like chip size, laser positioning, etc. (also, post-Operator PC the internals don't change much after, so you're able to slap a chip from like the Modifier Lite into the Helium case)
Anyways, for the AHOX Duo and CodeCruncher (now called Number 9 with extra cheese PC, lol), the AHOX Duo just leads to a blank screen, even with the DC-1k plugged in. (i had to put the DC-1k on a block for it to reach the port, but I definitely know it was reaching the Chives chip. i opened the PC up and could see the laser reaching the chip)
It's not an XDisk issue either, since the Duo can read XDisks just fine. Even then, I converted it to a MDisk anyways and got the same result.
Anyways, the CodeCruncher doesn't even have an expansion port and can't even XDisks either, only being able to read MDisks (as reading XDisks returns nothing). However, I manually converted the XDisk into an MDisk, and then opened up the CodeCruncher PC and changed some collision settings to make sure that DC-1k could access the CPU, and I knew that when its laser was touching the CPU.
However, same result. Blank screen. Nothing happened. Just a pure black void, no matter what. And I guess that concludes it!
TL;DR: The DC-1k works all the way down to the AHOX Competitor Model S & E. The Operator SoC-Powered Programmable PC doesn't detect the DC-1k at all, but still boots from the test program, and the AHOX Duo and CodeCruncher (with some modifications to make sure the DC-1k's laser still acceses the Chives CPU) only shows a black screen upon booting the test program disk.
