Build 293.10 - Release version

I hope the time is finally right to add the possibility to flip an active object!

+1 for native flipping an active object without shader necessity.

Yeah hope that's coming soon, don't know how proper active flipping, of all things, is still not in by default in Fusion and for all platforms after all these years.
But hey I don't code, what do I know.

yes please add a flip fuction. it will save a bunch of game resources.

Would be cool to have a thread exclusively about Build 294 already or something like that, feels like the hype's died down a bit

Quote from Peeblo

Would be cool to have a thread exclusively about Build 294 already or something like that, feels like the hype's died down a bit

Please login to see this link.

BUG:

You can insert/paste "Ghost Code/Actions" in the Event List Editor. If you create a Child Event, [Right Click] on the empty line titled "New Condition" and Paste while an Action is on your Clipboard (Though I'm uncertain if plain text breaks things as well), it seemingly does something and the Editor even recognizes this an an undo-able modification.

Please login to see this attachment.

I've encounter this application breaking issues multiple times in the paste, with my only option being to delete large groups of code in order to remove this invisible code. I'm crossing my fingers that this is the main cause so that we can finally fix this and I don't have to worry about it showing up again

Quote from Volnaiskra

There's a glitch that happens when the Layers Toolbar is docked and folded on the side of the screen while using a non-maximised Frame Editor window. When you're dragging an active object on the Frame Editor, the Layers toolbar seems to mistake the edge of the Frame Editor for the edge of the main Fusion window, and automatically unfolds whenever the active object happens to touch the edge of the Frame Editor. This can be a bit laggy and distracting, but the main problem is that it prevents the Frame Editor from scrolling when this happens (and since you dragged an active object to the edge, scrolling the Frame Editor is probably what you were trying to do).

This glitch happens on both left and right sides (ie. if you dock the Layers Toolbar on the left, then it'll also unfold if you drag an active object to the left side of the Frame Editor window)

Please login to see this picture.

Quote from NaitorStudios

Guys, you do realize that the next update will completely replace the API used for the graphical interface and be DPI aware, meaning these issues will probably not be present there, right?

It's still there

Never mind me - just discovered the Skin Editor!! -- only played with it for 15 minutes -- I'll be able to quickly make something pleasing to my eyes!

Please login to see this picture.

not sure why I can't edit or delete my post... posted in the wrong thread, excuse me!

Quote from DaveC

not sure why I can't edit or delete my post... posted in the wrong thread, excuse me!

About 2 years ago, they had a sign up that said that due to maintenance works, some forum functionality like editing will be down for a couple of weeks..........We haven't been able to edit posts since then X)

Quote from Volnaiskra

About 2 years ago, they had a sign up that said that due to maintenance works, some forum functionality like editing will be down for a couple of weeks..........We haven't been able to edit posts since then X)

lol classic Clickteam

Bug: Create is case sensitive, while Create by Name is not:

Please login to see this picture.

Would it be possible to get a new expression currentLoopIndex that gave you the loop index of whichever fast loop was in the current event's "on loop" condition (without having to explicitly specify the name of the fastloop)? It would make using loopindexes a little easier and more readable. It would also make reusing code between different fastloops easier. And it'd prevent bugs caused by changing a fastloop's name but forgetting to update subsequent loopindex expressions.

Quote from Volnaiskra

Would it be possible to get a new expression currentLoopIndex that gave you the loop index of whichever fast loop was in the current event's "on loop" condition (without having to explicitly specify the name of the fastloop)? It would make using loopindexes a little easier and more readable. It would also make reusing code between different fastloops easier. And it'd prevent bugs caused by changing a fastloop's name but forgetting to update subsequent loopindex expressions.

maybe not possible, as fusion doesn’t save loop index by stack (you can retrieve loop index after loop), which can just return the last one.

Speaking of loops, would it be possible to get the number of how many times a loop has run? would be useful in some cases.

Quote from Linky

Speaking of loops, would it be possible to get the number of how many times a loop has run? would be useful in some cases.

Retrieve loop index out of the loop will return the total number of loops if I got you correctly.

The INI++ (v1.5) Rename Item action is broken. It ignores the "new" name and tries to rename the "old" name to the "old" name. When run, this causes a Crash To Desktop.

Please login to see this picture.

Please login to see this picture.

whenever i try to start ctf after installing this update, it just brings me to the creating frame window and then closes after half a second. ctf loader is still present in the task manager.