I am trying to open an MMF2 .mfa file into Clickteam Fusion 2.5. It opens fine, but when I save it as a Fusion 2.5 file and reopen it, multiple frames are corrupted and don't load, starting usually around frame 4 or 5. I've tried reordering the frames to see if a specific one is causing the corruption, but I can't find any patterns. My project file is around 460 MB. Is there a reason this is happening?
Do you still have the demo somewhere on your system? This can be caused by the 3-frame limit of the demo.
I can't find the demo on my system. I tried reinstalling Fusion, and that didn't fix the problem.
FYI here is the message I'm getting after the frames load... could it be an issue with old objects? Or the demo hidden somewhere I'm just not seeing? error copy.png
This looks like a different error
I think the MFA file is corrupted
Look and see if you can find any files with the same name and a number after them like .001, .002 and ect.
Those are auto backups of your MFA file (unless you turned this off)
If you want to send a link to that file in question we can take a look and see - but something really odd is happening to it.
Thanks for the reply, Jeff. The MFA still opens and can be worked on in MMF2, however, so not sure what the disconnect is between the two softwares. I will PM you the direct download link to the MFA.
Through trial and error I believe I have solved the problem. When I load the old MMF2 MFA into Fusion 2.5 and uncheck "include global events" for all the frames, then save the project and reopen, everything loads. Additionally, when I recheck "include global events" for all the frames after the file has been saved, and save again, and reopen - voila! It opens fine.
This appears to be some kind of global glitch that happens when you port an MMF2 file over to Fusion 2.5. On top of that, I have some rather unusually large and complex frames, and it was these frames alone that were causing the problem. More specifically, the large frames would corrupt and delete all the subsequent frames, but would themselves remain intact. So I conclude that the bug is caused by a combination of 1. a frame with a large amount of data and 2. the "include global events" box. I'm guessing it causes some kind of memory problem, not sure about specifics. But again, if the boxes are unchecked, project is saved, and boxes are re-checked, the issue is resolved.
If this is not a known bug I would suggest it be added to a central list for future versions of Fusion.
Posting Permissions
Reply With Quote