I originally tried something similar but the count of lasers kept fluctuating. If I had 2 lasers hitting it, it would say 2 most of the time but sometimes it would say only 1 was hitting it, and it would oscillate while it was on no less.
It was more basic, just being hit by a laser incremented a variable and each tick the gate would retrieve the variable, do the logic, then reset the variable.
Nonetheless, that does seem like a cleaner approach than mine, thanks for the advice!
The reason it does this afaik is because of how Algodoo calculates lasers.
Me and UnityDogGaming04 were doing tests with lasers and, iirc, we discovered that lasers are calculated on a per-frame basis rather than a per-tick basis. Changing the simulation speed or the simulation frequency won't change the lasers.
This is of course from memory and as such it might be wrong, but the point is that lasers are just plain weird!
I wasn't really testing for non-60 frequencies because it was already super laggy at 60hz. It would be even laggier at a higher frequency!
Also, I'm surprised someone only just know figured out I renamed the Codecruncher. My friend told me to do that I wanna say about 6 months ago and it was too funny for me to refuse.
For the record (although I don't think this needed saying), it doesn't work on the Lithium. Not only because it has no expansion port, but because the CPU is completely different and it doesn't use Chives.
(that's fine though since it has unlimited file slots)
Right - the rules here are pretty solid - edge cases are pretty rare and if your scene follows the rules you should be good.
Just use common sense (no swearing, no profanity, nothing rated R, no spamming, etc) and you'll be fine!
There's also the matter of announcement and chatbox scenes which aren't allowed, as well as secondary accounts and stuff. (I don't like my username but I can't create a new account so I'm stuck with it, lol)
As for announcements, announcements in comments are allowed - just not in scenes.
For example, since this is a comment, I can announce that today I made something I'm pretty proud of!
If I created a scene showing off the thing I'm proud of and talking about it that would be okay, but just creating a scene that doesn't really do anything mentioning in the description "i just made this scene because i wanted to say i made something today im proud of" would get me banned*.
*There is a warning system in place for your first few offenses, however back in my early days on the box I didn't understand the rules and I used all of my warnings for announcement scenes.
Yes, I deleted most of them except for a few "milestone" ones.
The reason was that they weren't real computers (they couldn't run any code) and the quality was pretty poor.
I had also deleted a lot of my old scenes (I wanna say around 70%!) that were really low quality. Even to this day, when I upload I still end up deleting the scene pretty often because I'm not satisfied with how it came out.
Just a question - if something goes wrong like opcode 1111 is called, or you try to move a number like 7 into a place that doesn't exist, what will it do? Will it just do nothing or will it send an error?
Also, I don't fully understand how MOV works.
If I do understand it correctly, it works like this, right?
mov (mode), (value/register), (register)
Also, do I have permission to create a processor that runs this ML?
I think I killed it. It does not like it when I poke it with a screwdriver!
That's actually kind of realistic - guys, you really should be careful around capacitors. Take a CRT for example - always discharge a CRT before working on it, even if it's unplugged - just one zap from those capacitors and you and the CRT are done.
What if it's about someone who has the magical ability to use Thyme and the other Algodoo tools and is tasked to solve problems with them? That would be kind of interesting.