It might be checking for some Steam API functions that mismatch.Īlso in this state, exporting as an. I don't think it's checking modifications to mmf2u.exe itself as I can mess around with that in a hex editor and start it with steam and export/runtime stuff just fine. CCA files generated, but bigger ones compared to when you leave SmartSteamEmu files near the main executable, it must still being detected somehow. If you hide the SmartSteamEmu files, you get a "This application has been built with an incompatible version of Clickteam Fusion" error and still get weird. (The same error occurs if you run a sub application and point it to a broken. Which the runtime generates "File error!". There's also code in the main mmf2u executable that detects the presence of SmartSteamEmu.dll and SmartSteamEmu folders been in there since R292 or so.Īlso SmartSteamEmu.ini being present will hide some extensions for some reason?Īttempting to export or use the runtime buttons while SSE is detected will generate purposely unfinished CCA files. This would be compatible with both 32 bit and 64-bit windows.Well I tried and this is as far as I can get guys.Īs for the explanation, R293+ use steamstub drm. Therefore, This is a complete offline installer and standalone setup for Clickteam Fusion 2.5 Developer.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |