Thanks for sending me your file. The crash might be due to corrupted events, the debug version of MMF2 reports weird things. EDIT: or it could be a bug in the new beta versions of MMF2 (released in the beta tests forum only). I'll ask Francois to take a look. I'll let you know.
Yves do you planned for the HWA application work in 16bit color of Windows?
I don't remember what are the problems, but at the moment there are more prioritary things to do. I'll add that to my list of things to check, I don't remember anything about this issue.
I have a feature suggestion.
Since I'm using global events quite heavily, there is something bothering me since the first day. After importing objects, they do not show the correct alterable value names in the event editor. Could you please add that? Because right now I always have to look those objects up in the frame editor and memorize which alterable value does what before I can work with it in global events.
Also new animations do not show up in the global event manager at all. So whenever I want to do something with an animation in a global event, I have to cut the whole event, paste it into a frame where the imported object is, add/change the event with the animation and cut&paste it back into the global event manager.
So in short: global events should show correct alterable value names of imported object as well as new animations that those imported objects have.
This is a known issue, I think it won't be fixed in MMF2, it needs fundamental changes that can't be done before MMF3. The global events don't know the real objects, they just know their name and their type. Objects with the same name and type could have different properties in different frames.
There was one feature that was proposed earlier to fix the problem where Global objects go 'out of sync' across frames.
It would be good if changes made to a Global Object overwrote and updated that Global Object across all frames nomatter what.
At the moment, MMF2 only seems to do that if it detects that a Global Object is identical across all frames, which is clever but it also kinda defeats the purpose of Global Objects.
It should just warn you before it goes ahead and imposes changes to a Global object if it is not already identical across the application.
I think this was proposed before and it would make life very easy and make use of MMF2 very reassuring that your Global Objects were uniform.
---
Blue66, I suggest that you write a level engine that is identical (and which can be transplanted across each level). The Global Event Editor is clever but I don't recommend putting your level engine in it.
How do to always not expand the frame tree in workspace toolbar when inserted new object?
If not exist this ability in current version, could you this option add in future build?
Still MMF2 Unicode is crashing on Start-up because of following extensions:
Newgrounds Object by Jamie
Tile Line of Sight by Eliyahu <- Corrected with the latest update:
http://www.triplezap.com/files/extensions/los.zip !!
Have both extensions been made with the old version of EDIF that was crashing the Unicode version? If so recompiling them with a more recent version should fix the problem?
I am trying to update to #253 from #249 but install freezes at 53% on Chokobreak.chm.
Any Advice
(WINXP SP3)
Posting Permissions
Reply With Quote