Bug: MMF2 Deleted My Events

[Michael_Gummelt]

I was cutting and pasting a few events inside one of my event groups, ran the game and noticed something was wrong with one of my objects. It was doing the event that created it every frame. When I checked my event list, every single event that has to do with that object was *deleted* except for the 4 events that create that object. These events it deleted erroneously (especially since I didn't *tell* it to delete *any* events) were in several different groups all over the Event Editor. Something is seriously messed up, here.

Also, I have an object that showed up in the Frame Editor that I didn't put there (and I don't have "show created objects on). If I try to delete it, it tells me it's going to delete events, too. Which doesn't make any sense, if it's a created object (which it is), why would it delete all of it's events? And I had removed this object from the frame editor before, only to have it mysteriously appear before.

These are some pretty serious, annoying bugs and makes me think my project is deeply hosed, now. What if there are other events it deleted I don't know about?

>

[Michael_Gummelt]

I was cutting and pasting a few events inside one of my event groups, ran the game and noticed something was wrong with one of my objects. It was doing the event that created it every frame. When I checked my event list, every single event that has to do with that object was *deleted* except for the 4 events that create that object. These events it deleted erroneously (especially since I didn't *tell* it to delete *any* events) were in several different groups all over the Event Editor. Something is seriously messed up, here.

Also, I have an object that showed up in the Frame Editor that I didn't put there (and I don't have "show created objects on). If I try to delete it, it tells me it's going to delete events, too. Which doesn't make any sense, if it's a created object (which it is), why would it delete all of it's events? And I had removed this object from the frame editor before, only to have it mysteriously appear before.

These are some pretty serious, annoying bugs and makes me think my project is deeply hosed, now. What if there are other events it deleted I don't know about?

>

[Harvy]

The "created objects" in the frame editor really are created objects. Some are displayed even when "show created objects" is unchecked (which is a bug, imo). If you deleted them before, it would have erased any events associated with them (as the warning message usually says).

[Harvy]

The "created objects" in the frame editor really are created objects. Some are displayed even when "show created objects" is unchecked (which is a bug, imo). If you deleted them before, it would have erased any events associated with them (as the warning message usually says).

[Francois]

First of all, I hope you have kept a version of your file before the problem. As a default, the autobackup feature of MMF2 is set to 5 (if I remember well), so you should have in your save directory 4 copies of the previous versions of your application. Just retreive the one without the problem.
Now, if you could recreate the problem, say, find the exact manipulations that deleted the events, and created the extra object, this would be fantastic. And send me the file before and the way to proceed. Please please please can you do that?

[Francois]

First of all, I hope you have kept a version of your file before the problem. As a default, the autobackup feature of MMF2 is set to 5 (if I remember well), so you should have in your save directory 4 copies of the previous versions of your application. Just retreive the one without the problem.
Now, if you could recreate the problem, say, find the exact manipulations that deleted the events, and created the extra object, this would be fantastic. And send me the file before and the way to proceed. Please please please can you do that?

[Michael_Gummelt]

[]First of all, I hope you have kept a version of your file before the problem. As a default, the autobackup feature of MMF2 is set to 5 (if I remember well), so you should have in your save directory 4 copies of the previous versions of your application. Just retreive the one without the problem.
Now, if you could recreate the problem, say, find the exact manipulations that deleted the events, and created the extra object, this would be fantastic. And send me the file before and the way to proceed. Please please please can you do that? [/]

I sent links to 3 versions of the project to Yves. One is before this bug, one after. All I did was cut & paste some events in the "Projectiles" group...

[Michael_Gummelt]

[]First of all, I hope you have kept a version of your file before the problem. As a default, the autobackup feature of MMF2 is set to 5 (if I remember well), so you should have in your save directory 4 copies of the previous versions of your application. Just retreive the one without the problem.
Now, if you could recreate the problem, say, find the exact manipulations that deleted the events, and created the extra object, this would be fantastic. And send me the file before and the way to proceed. Please please please can you do that? [/]

I sent links to 3 versions of the project to Yves. One is before this bug, one after. All I did was cut & paste some events in the "Projectiles" group...

[Michael_Gummelt]

[]The "created objects" in the frame editor really are created objects. Some are displayed even when "show created objects" is unchecked (which is a bug, imo). If you deleted them before, it would have erased any events associated with them (as the warning message usually says). [/]

Yeah, I never turned this on, I don't think, so I don't think that's my problem, here.

[Michael_Gummelt]

[]The "created objects" in the frame editor really are created objects. Some are displayed even when "show created objects" is unchecked (which is a bug, imo). If you deleted them before, it would have erased any events associated with them (as the warning message usually says). [/]

Yeah, I never turned this on, I don't think, so I don't think that's my problem, here.