[FART] Computing(Fast Algodoo Real-Time)

[cdh473]

I am currently working on a laser computer that GENERALLY works like a real one, it uses lasers and thyme mainly.
I have been doing a few projects/experiments to make sure this was completely possible.
I have found a couple of things that may complicate this project.

Here is a basic example of how the disk reader will work:
http://www.algodoo.com/algobox/details.php?id=30575

Known bugs/issues:
Custom variables don't save with scene

[Conundrumer]

I think I would call that a memory stick, since there's absolutely no optical information.

[cdh473]

It wasn't meant to be a finished idea of how it's going to be done.
Like i mentioned earlier, it has that variable bug, so unless Algoryx fixes that, we will either have to re-write the data every time we open the scene, or just come up with some new way of doing this.
I suggest the latter.
I'm thinking just use a default variable instead of the custom one(data).

[Frank]

AirFrictionMult works as a spare variable if the object isn't going to move. If it's never going to collide with anything, restitution and friction work too. There's always controllerAcc for a spare float too. There are several spare bool true/false variables governing geometry controllers too. If you really need lots of numbers, you can use the texture matrix, but the way Thyme handles arrays that one's a pain in the butt. But it does have something like eight or ten floats in it.

[RA2lover]

100th post in the algodoo collab section!

also, i'm not sure if this can be considered RT, because lasers update at an variable frequency(looks like it change s from computer to computer), and that frequency is usually smaller than the sim.frequency