Thanks for reporting this. I have added it to the help issue tracker

I do the same. I meant to report this but keep forgetting. strFind is the bomb. strContains is the ugly duckling.

@ITzTravelInTime Yes, they did, didn’t they. Fuze feels like a (good) history lesson :-)

This is definitely a bug and I shall go file it in our issue tracker. Thanks for pointing it out (and the code!)

I've found out how to reproduce this bug - you have to go to media menu and preview any 3d model. After that sprites scaled with one negative value become invisible in programs.

@jacobmph Sure, I can explain that a little further. To use images included in F4NS you can press the media key on the on-screen keyboard to open the media section, and from there you can paste image names into code. However, in the version the same is not true of images created with the image editor. In the current version, you'll have to remember the name of the image you've created and want to use, and load it with loadImage("name").

The next patch should add an entry for your current project in the media section, which you can easily select and view the images you've created with the image editor that are in your current project. You'll then be able to paste the names into your code, instead of having to remember them.

Let me know if that was able to answer your question!

Gotta give @pico8-jihem props for pushing the envelope. Better to find these issues out sooner than later 😄

Works ok on my patched version.

To be honest, the whole assigning 0 to a dimension on creation just confuses me. It's one thing to use 0 when reading/writing to an array because of it being base-0, but on creation, it's base-1, as using 0 I would think would cause it to make a non-element array. There's the whole array-expansion bit by assigning data to an out-of-bounds element though.

I really don't know outside of the info in the help sadly

https://fuzearena.com/help/view/open

Thank you again RaptorJesus! Keep 'em coming :)

Thank you RaptorJesus!

I've had a couple of emails from users with this same bug. Will certainly be fixed in an update.

Maybe they are planning on providing more. I mean, why return a handle at all and make use of it if they planning to only limit it to one timer?

@Alexander that was my thought too, but i checked the archive and it all seemed fine.

@SoulGamingInc let me know when you've got time to go through this and at worst case I'll recreate what you've done already!

As a side note to this.... It happened once earlier when I removed the Joycon while docked...
Found another way to initiate the bug aswell:
If you hold down both left and right CTRL on keyboard for about 5+ seconds it will also start this...

home button will revert it back to normal as its the only way i know how to stop it...

@Jonboy ok, thanks for the information! (also I am not on airplane mode)

You've stumbled upon something that I found on I think my 2nd night. If you for example increment a counter and print the result on screen when a button is pressed then you'll be expecting it to increment by 1 each press but the loop is so fast that it'll go up by quite a lot. So as you now know you keep checking until you know the button WAS pressed but isn't any more. THEN you do you action and you're golden. It might seem like a quirk but it's actually perfectly normal having to "debounce" a button.