When you create a backdrop and switches the color of the origin active, it will make previously created backdrops to be invisible until the active changes colors again.
This will cause a strange flickering where some backdrops may be visible (with colors changed since they share the sprites of the active) and some may be invisible.
Looks really interesting, but doesn't look intended. Changing the colors of the backdrops I get, no problem there, but making them temporarily invisible looks wrong...
It seems like this is also affected by Load Frame action, so when you replace the frame once, some will get invisible some visibile, they will replace the sprite normally
(which is kind of interesting actually, didn't knew you could do this)
Here's a example of the bug:
Backdrop flickering bug.mfa
If you check "Don't include at build time" on a frame properties and have a "Next frame" action on the frame before it (or "Previous frame" action on the frame after it) it will close the application instead of skipping it.
Happens with built-exe as well, not just when running from inside Fusion.
As the title says that's perfectly it, when I rotate or resize an object in the frame editor it changes the actual sprite which isn't something I like much.
So it would be nice to have an option that doesn't affect the actual sprite and just initialize the angle / scale of the object.
I know I can ofc just have values stored that can do this...but I also want a visual representation in the frame editor, just like how it already looks, but without it changing the actual sprite.
I was very happy do discover recently the ability to set the caret position for the edit box!
However, setting it to anything else than 0 causes an instant crash on my system.
Does this happen for everyone? If so it would be great if this could be fixed!
I don't know if this is possible by any means as it's hardcoded in Fusion to set zoom to 100%
But maybe it can be added? if possible that will be really nice for much feasible path editing
First of all it appears to be a very old bug so I don't know if it can be fixed
When testing for an object that doesn't overlap with another object it just doesn't scope correctly with multiple objects while it works perfectly fine with Object doesn't overlap with a backdrop
ofc that can be solved with for each loop check, but the problem is for each loop is very heavy with a lot of objects