[SOLVED] HTML5 - found ( may be ) a small quirk with a workaround

The problem with your "bad" object is that it has a qualifier on it. So in this case, the object isn't actually "bad", nor is it corrupted. If you remove the qualifier from the "bad" object, the event on line 2 will work on HTML5.

It looks like creating an object that has a qualifier attached to it inside of a "Run this event once" statement causes the error on line 1395 in RunLoop.js. This will only occur if the frame has a transition on it though. If the fade-in transition is removed, then the object's will be created without an error.

You can make the event behave correctly on HTML5 by adding a "Start of Frame" condition to your code. This is also why line 8 works on both platforms without a problem.

Please login to see this attachment.

This will change the behavior on both Windows and HTML5 though, and the objects will be created before the fade-in transition, not after like they are on Windows without the "Start of Frame" condition.

My best guess as to why this problem occurs on HTML5 is that the part of the code in RunLoop.js producing the error runs before the frame is fully loaded during the fade-in transition, and thus can't properly process the qualifiers on the objects that don't yet exist.

You should be able to fix this yourself by going to the Data\Runtime\Html5 folder in your Fusion installation directory (typically C:\Program Files (x86)\Clickteam Fusion Developer 2.5\Data\Runtime\Html5 for non-Steam users), opening up the RunLoop.js file, and changing line 1385 from this:

if (oilPtr.oilRealQualifiers != null) {

(1/29 Edit: removed bad code suggestion, see Please login to see this link. for newer fix)

Hi semar,

If you could PM me the MFA you are using that would be great. And yes I agree, using fades seems to cause a problem with qualifiers that wouldn't normally occur in a frame without a transition on it.

As far as the patch I suggested in my earlier message, I found that it could mess up behaviors with qualifiers (such as collisions).

(1/19 Edit: removed code suggestion. See Please login to see this link.)

I am going to keep investigating this, and I'll update you with any fixes I'm able to make.

Note: If you ever need to revert all the changes you made to the Html5 runtime without going back through all the files you changed, then you can just re-install the latest Fusion update, which will return the runtime files to their original state.

Hi semar,

Thanks for the MFA.

I think I may have found the problem in the runtime. I will provide it here once I do some more testing.

It is still a change in RunLoop.js and actually makes my previous fix unnecessary since I believe it addresses the root of the problem.

Quote from semar

This is indeed really nice to know !

Hi semar,

The problem with the qualifiers seems to be that there is code inside of RunLoop.js that is called only if a frame has a transition applied to it (such as fade in). When that code runs, it calls a function named unBranchPrograms that clears out the list of qualifiers, which results in that null error when the program tries to access them after the fade in. I've come up with a way to fix this.

Fix 1:

This fix involves deleting line 668 in RunLoop.js that calls unBranchPrograms after a fade in, which will prevent the qualifier list from being cleared out.

Please login to see this attachment.

Fix 2:

This fix involves adding a line to RunLoop.js. Just add this.rhEvtProg.qualToOiList = this.rhEvtProg.qualToOiListFull; below line 668 as shown below:

Please login to see this attachment.

You can also undo the patch I suggested for line 1385 in my earlier messages as it is unnecessary and didn't target the root of the issue.

(2/5/25 Edit) The correct fix was actually to remove this.qualToOiList = null; on line 4365 in Events.js as per Yves' Please login to see this link.

Disclaimer:

I didn't write the runtime, nor am I familiar with all of its components, so I can't guarantee this is definitely the correct solution. I would at least try this fix though and see if you encounter any issues (whether they are related to qualifiers or not). If you do, please mention them here.

Quote from semar

IT WORKS !!!

Many thanks tobydavis for your patience and time ! Now I can finally use the standard transitions also in HTML5 !

I really appreciate your work and the detailed informations. You have even corrected/updated your posts above - I'm deeply impressed !

You own a pizza margherita and a beer from me

I've tested the whole project right now, and also by the second level the transition works like a charm !

Thanks again for your kindly effort tobydavis - really, really appreciated !

Best regards,
Sergio

Display More

Glad to hear your project is back up and running! I'll have to take you up on that pizza offer if there is ever another Click Convention

It looks like this bug was introduced in Build 295.2. I can't be sure of the details, but there were changes in relation to qualifiers in Events.js (such as the addition of the prepareQualifierList function) that may have caused problems with the previously unproblematic code in RunLoop.js that is triggered after the completion of a transition.

I believe that Fix #2 is the better one at this point, so I would go with that until there is an official fix (hopefully in Build 296).

Regards,
-Toby

Quote from Yves

I think your first fix was the good one (removing the line that sets qualToOiList to null in unbranchPrograms). In a previous optimisation the initialization of this array was moved to another routine, and apparently I forgot to remove this line.

Hi Yves. I've restored Fix #1 in my earlier comment so other people can see it. I was just really cautious about recommending deleting a line as the fix for the problem.

I'm glad to hear one of my fixes ended up being correct and I wasn't totally off base here

Quote from Yves

Ah sorry, I misunderstood what you meant in your first fix as it was hidden. Actually the correct fix is just removing the line that sets qualToOiList to null in unBranchPrograms, you shouldn't remove the call to unBranchprograms

Code

	unBranchPrograms: function ()
	{
		this.bReady = false;
		this.limitBuffer = null;
		this.listPointers = null;
		this.eventPointersGroup = null;
		this.eventPointersCnd = null;
	},

Oh I see. I guess that's the downside to removing things from my comments. I was hoping to cause less confusion for anyone who came across this thread in the future, but I guess I did the opposite. Thanks for clarifying where the actual problem was.