Quote: "Use the arrow keys to move the unicode square thats all it does..."
Really? What's the point?
Quote: "use the red slider and drag it to set the frame rate."
Again, what's the point? Oh, by the way, that slider doesn't have physical limits, and so it can slide totally off the bar, right and left.
Quote: "Note that each time the purple thing hits the textbox the text changes."
Umm... What text?
42flowermaster -- I truly don't intend to be critical or sarcastic about your scene, but I must admit that, without detailed instructions and explanations, I don't have the foggiest idea what you created. I suspect others are equally bewildered.
Okay, that explains the problem. You see text but I do not! All I see are little squares.... lots of little squares.
Now I'm sure you understand the source of my confusion.
I did take a look at your code in that text box, and all I see there is an array of text squares. There are no alphabetic characters. So maybe you are using a character set that my computer doesn't recognize, what you are calling "unicode".
My browser is "FireFox" and that might be the problem. I'll take a look at this scene on another computer. My wife uses a laptop which is a different brand than my desktop, so maybe that will make a difference. I'll let you know (that's if I can get her to give up her computer for five minutes!)
Edit: Luckily she wasn't using her computer, so I loaded your scene, and I also had to load Algodoo (she has no idea what Algodoo is). And her browser is different than mine. It's Chrome. The result? SAME PROBLEM. I opened up your scene and copied the contents of your local variable named _txt and this is what I copied: "▣▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢
▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢
▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢
▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢
▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢
▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢
▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢▢"
So, since my computer AND my wife's computer cannot render your unicode text, then I would bet that other users here on Algobox are experiencing the same issue.
Edit2: Why does the character set need to be "unicode"? Why not use the default character set or some other common one that most people would have?
Yes, your most recent update. I don't like it because it's nothing but a car mowing down pedestrians. You have to avoid that giant car crusher, but besides that, it doesn't take much skill or dexterity to press the button that makes the car move. It's not really a "game" in my opinion. It's just an outlet for angry kids who want to kill people but they know they can't actually do it in real life, so they get their kicks killing fake people in video games.
Wow, this was a difficult one to figure out! I spent a couple of hours on it trying different things, and I think I figured out what's happening.
Apparently, if any object that is glued to the background (such as those yellow bars) happens to get its velocity changed from zero to some value (not a normal thing to do), then ALL other objects that are glued to the background also get their velocity[x,y] set to the same value! That includes the plane, which just happens to be at some weird angle in your scene. When any non-glued object falls against a glued object (such as the plane) the non-glued object will get propelled in the direction and speed of the glued object's velocity value!
This is a bug which cannot be fixed at this time, but I will report it to Algoryx so they can decide what, if anything, they will do about it. For now, just make sure that any object which is glued to the background does not get it's velocity values [x or y] changed. I soon plan on uploading a demonstration scene which shows examples of this bug.
I have a modern/fast computer, and so it normally can display just about every ASCII character set available. Until your scene came along, I did not run into this problem. So, I am at a loss to understand what's going on. I was hoping that other people would chime in here to let us know if they have the same issue that I am having.
Now, with this new version, I see a maze of light and dark rectangles. I can move the "cursor" around between those light and dark rectangles sort of like moving through a maze. Is this what you intended?
It looks like the same kind of bug you found before. That is, all items glued to the background pick up the same vel value. Nothing new.
Now, instead of spending your time trying to create weird glitches, why not just post some interesting scenes that other might enjoy? Great idea, right?
I had no idea that this scene would become so popular when I made it. As of this date (3 weeks from the upload date), it has been downloaded 4426 times. Amazing!
Update: Now (7/23/21) it's a little over 2 months from upload, it has been downloaded over 10,000 times. Incredible! I can't wait to see what the number will be ONE YEAR from upload.
I have a suggestion....
You can click on anyone's user name to see a list of scenes that they have posted here on Algobox. For example, you can click on my name to see all of my own scenes that I have posted since 2012 when I started posting scenes. Many of my scenes are remakes of the old arcade games like Pacman, Sea Wolf, and a lot more. Check them out! You will no longer be bored!
GemWolf7-- Hmmmmmm.... Yes, I see that. You used to be lonewolf811, but then in 2018 you were banned, and then in 2019 you registered your current account and you became active again. You some how snuck under the radar because when someone is banned forever, we usually catch them if they try to register again under a different name. Well, in your case, I'll let it slide because you haven't caused any problems since you registered GemWolf7. Thank you for that.
.
.
(See, Xray can be a good guy regardless of what some people think and say about him!)
The laser really isn't "backwards". The dim beam is simply a reflection off some other object, maybe far away. If you go into the Script Menu and reduce the number of maxRays to 1 or 2, then the beam will only reflect off of the object directly in front of it. The higher the number of maxRays will allow the beam to reflect that many times off various surfaces. You can also reduce the fadeDistance to a small value so that the beam hits only objects that are within a short distance of the laser.
JPgamersmines150 -- First, what do you mean by "point to"? A circle and a square cannot "point", so you need to clarify that question.
Basically, the current position of the cursor can be read by app.mousePos. It provides the position as X and Y coordinates which can be read individually like this: app.mousePos(0) which is X, and app.mousePos(1) which is Y. You can make an object stick to the cursor as it moves with this simple script: e.pos = app.mousePos If you put that script in postStep, the object will stick to the cursor only when the scene is running. If you put it in upDate, it will stick to the cursor constantly even when the scene is not running.
Edit: I found a scene which does what I believe you were asking for. Check it out: Cursor Following Laser