When I run this simple event it works in exe but doesn't work when I export to html5.
Please login to see this attachment.
Don't have an account yet? Then register once and completely free of charge and use our wide range of topics, features and great options. As a registered member on our site, you can use all functions to actively participate in community life. Write posts, open topics, upload your pictures, put your videos online, talk to other members and help us to constantly improve our project and grow together! So, what are you waiting for? Become a part of us today!
Login or registerTo get support for a technical issue such as installing the software, to query a purchase that you've made/would like to make, or anything other than using our software, please visit our Customer Service Desk:
Open a TicketWhen I run this simple event it works in exe but doesn't work when I export to html5.
Please login to see this attachment.
Which event does not work, setting the gravity or the collision with the ground ?
Could you be more specific ? You could also post an .mfa example here, so that we could test it.
When I run this simple event it works in exe but doesn't work when I export to html5.
Please login to see this attachment.
You should upload an image of the event list editor to see all the code
Please login to see this attachment.
the event with "every" doesn't work. I'll pass you the mfa. Neither gravity nor the counter do anything.
This bug appears to be caused by a typo in the Movements.js file, which results in the getGravity function incorrectly referencing a variable that it tries to return.
The function tries to return "this.mp.MP_GRAVITY", when it should be returning "this.MP_GRAVITY".
You can 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 Movements.js file, and changing line 946 like so:
Please login to see this attachment.
Note: Make sure the editor you are using to make changes to the file is running with Administrator permissions or it will be unable to save the changes.
Thank you very much it works! I have a whole game with multiple events like that and yesterday I wasted the whole day with no success! Thanks again!
Will this bug be fixed in the next version of fusion2.5 or html5 exporter? Or will I have to remember to change this file if I have to reinstall the exporter?
In this regard I wanted to ask you a question. But when I update fusion2.5 dev, are my exporters also updated?
Thank you very much it works! I have a whole game with multiple events like that and yesterday I wasted the whole day with no success! Thanks again!
Will this bug be fixed in the next version of fusion2.5 or html5 exporter? Or will I have to remember to change this file if I have to reinstall the exporter?
In this regard I wanted to ask you a question. But when I update fusion2.5 dev, are my exporters also updated?
Happy to help, glad to hear you can continue working on your project!
I don't work for Clickteam so I can't promise the fix will get in the next build, but it seems likely since it is such a simple fix. Hopefully Fernando will see this and make the change on his end.
About installing Fusion updates. The update installer will indeed update all installed exporters along with the main program itself. As a note to that point, if you re-install the current build of Fusion you will have to remember to make this change again since it will be overwritten.
thanks. But out of curiosity, how did you discover ""this.mp.MP_GRAVITY""? Also can you directly recommend making this change as it is a simple bug to fix but very important for the games?
thanks. But out of curiosity, how did you discover ""this.mp.MP_GRAVITY""? Also can you directly recommend making this change as it is a simple bug to fix but very important for the games?
I discovered it by hitting "F12" in my browser and looking at the console for JavaScript errors. It told me which line of which file was producing the error, and that's how I found the typo in the return statement. I did this with the "HTML5 Development" build type and the "Generate single source file" option in the HTML5 runtime settings disabled. This produced an un-obfuscated development build of the runtime split into different files, which made things easier to deal with. That build type can't be used for the release build of a game, but it does help with things like diagnosing issues.
I can recommend this fix since it simply fixes a typo that allows the preexisting code to work normally, it doesn't add any additional functionality or change how the runtime functions.
The reason everyone doesn't run into this issue on HTML5 appears to be because that return statement will not be triggered in that function unless the Movement type of the object it is dealing with is set to "Platform".
thanks so much I will try to analyze any other problems since html5 is my favorite exporter. I hope they fix the bug in the next version
This bug appears to be caused by a typo in the Movements.js file, which results in the getGravity function incorrectly referencing a variable that it tries to return.
The function tries to return "this.mp.MP_GRAVITY", when it should be returning "this.MP_GRAVITY".
You can 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 Movements.js file, and changing line 946 like so:
Please login to see this attachment.
Note: Make sure the editor you are using to make changes to the file is running with Administrator permissions or it will be unable to save the changes.
Why they don't update and fix it? I mean, it's a paid program
Why they don't update and fix it? I mean, it's a paid program
They do update and fix things. It's just slow because they try to fix as many things as possible before they update, because making an update is complicated.
They do update and fix things. It's just slow because they try to fix as many things as possible before they update, because making an update is complicated.
Plus, to my knowledge, this bug can only occur when dealing with an object that uses the classic platform movement type, not the newer physics based platform movement or the Platform Movement Object.
This bug is also present in older builds such as Build 291.6 from 2018, so it's a pretty old issue that seems to have slipped under the radar. I guess people just don't use the classic platform movement type on HTML5 that much (or at all).
Plus, to my knowledge, this bug can only occur when dealing with an object that uses the classic platform movement type, not the newer physics based platform movement or the Platform Movement Object.
This bug is also present in older builds such as Build 291.6 from 2018, so it's a pretty old issue that seems to have slipped under the radar. I guess people just don't use the classic platform movement type on HTML5 that much (or at all).
In any case it must be corrected as soon as possible
Don’t have an account yet? Register yourself now and be a part of our community!
Almightyzentaco (Fusion 2.5 Tutorials)
Captain Quail (Firefly Tutorials)