Bug report: Crash when using tokenizer - Start of frame - Fade in

[Decal]

Hello,

I seem to encountered a bug with the latest build of Fusion 2.5+

When you have a fade in on your frame and then have an event with the start of frame condition that will split a string and then set a string to those elements and then sets other strings to one or more of the elements, then the application crashes.

You can replace the "start of frame" condition with "run only once" but then it will happen after the fade transition is complete.

I have tried both the String Tokenizer and String Parser 2 and the same thing happens with both of them.

I would really like to use the String tokenizer on start of frame before the fade in transition starts.

[Volnaiskra]

I can confirm this crash, though I can't get it to crash with run this event once. With Start of Frame, this is enough for it to crash on my machine:







If you're desperate, then you may be able to replicate the functionality using the native string functions, depending on what you're trying to do. For example, this splits a string into 3 parts using a comma as delimeter. It's clumsy, but it works:

[defisym]

Have you tried this object?

https://github.com/defisym/OpenFusio...oInstall/Files

It’s a tokenizer based on regular expression, but you can safely use normal texts with escape.
Please check if it has the same issue, if so, I can fix it asap, or you can fix it then PR.

[Decal]

Thank you very much for your help.

I have tested your extension defisym, and it works perfectly. It does work at start of frame before the fade in starts and it does not crash the application. String tokenizer and string parser 2 must do something differently that causes the application to crash if it is used before a frame fade in.

I really like your idea Volnaiskra to use find string as a way to parse text. Since I am only parsing simple text with 2 elements, I think I will go with your idea instead, then have a extensionless design for this.

Thank you so much for your help.
I'm not sure if the bug with string tokenizer and string parser 2 is on Clickteams side or the extension developer design, but using Find String or defisym extension StringSplitter it will work fine.

I would definitely use the StringSplitter for more advanced parsing, but for simple 2 elements parsing, I'll go for Volnaiskra Find String idea.

Thank you all

[Decal]

Seems like there are more problems with the fade in and start of frame actions.

When using a list object, you can not set any variable etc, from a line in a list at the start of frame if there is a fade in transition.
This also have to be done after the fade in (run only once) just like string tokenizer and string parser 2

I hope Clickteam can fix this issue.

[Volnaiskra]

Until it's fixed, you might be better off making your own fade (eg. placing a giant rectangle over everything at start of frame then gradually increasing alpha to 255)

[defisym]

Seems like there are more problems with the fade in and start of frame actions.

When using a list object, you can not set any variable etc, from a line in a list at the start of frame if there is a fade in transition.
This also have to be done after the fade in (run only once) just like string tokenizer and string parser 2

I hope Clickteam can fix this issue.

Have you checked the property "create before fadr in"?
Or those objects doesn't have this prop?

[Decal]

How on earth have I never noticed this property before.
I have gone through all of the properties tabs a million times for pretty much all the objects for many many years, and I never knew about this.
I rarely use fade in/out transitions at all, so I have probably just glanced over it, but this fixed everything.

Thanks defisym!
Not only did it fix the list, but I can also use string tokenizer as well because it also has this property.
It was never really a bug to begin with, it was just me not knowing about this property.

Thank you very much