It's unchecked by default, but some objects seem to show up anyway. It is possible to mess things up if you delete them.
It's unchecked by default, but some objects seem to show up anyway. It is possible to mess things up if you delete them.
It's unchecked by default, but some objects seem to show up anyway. It is possible to mess things up if you delete them.
[]It's unchecked by default, but some objects seem to show up anyway. It is possible to mess things up if you delete them. [/]
Ah, well, if that's the case, that would explain it... though the ship isn't showing up at 0,0... it's off to the left and above 0,0...
[]It's unchecked by default, but some objects seem to show up anyway. It is possible to mess things up if you delete them. [/]
Ah, well, if that's the case, that would explain it... though the ship isn't showing up at 0,0... it's off to the left and above 0,0...
[]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 think I have a 100% reproducible way to do this (I accidentally replied to a different thread with this).
Here's what I did: I selected all the events in my "Input 2" group, *cut* them (and that, I think, is where the badness happened), created a new group and pasted the events in.
Afterwards, the objects created by the events I cut and pasted had been removed from all conditions and actions except for the events I cut & pasted. What is interesting about this, and what I think the source of the bug is, is this:
The events I cut & pasted contained *all* the actions that could create the objects that got messed up. They are not placed in the scene in the frame editor. I think that when I cut those events, it assumed those objects were no longer in use and just removed them from all the events (much like what happens when you try to remove an object from the frame editor that is not created in any events... except there's no warning or notification in this case).
The problem is, I'm cutting so I can paste somewhere else. But because it actually removes those events when I cut, I think it's deleting them as if I don't need them at all anymore. Which is absolutely not the case. I imagine it would be a pain to treat events in the clipboard as still existing, so I guess the solution is to put a warning on cutting events that have the only creation actions for objects. Recommend dragging & dropping or copying & pasting and *then* deleting the old events.
Hope this helps!
[]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 think I have a 100% reproducible way to do this (I accidentally replied to a different thread with this).
Here's what I did: I selected all the events in my "Input 2" group, *cut* them (and that, I think, is where the badness happened), created a new group and pasted the events in.
Afterwards, the objects created by the events I cut and pasted had been removed from all conditions and actions except for the events I cut & pasted. What is interesting about this, and what I think the source of the bug is, is this:
The events I cut & pasted contained *all* the actions that could create the objects that got messed up. They are not placed in the scene in the frame editor. I think that when I cut those events, it assumed those objects were no longer in use and just removed them from all the events (much like what happens when you try to remove an object from the frame editor that is not created in any events... except there's no warning or notification in this case).
The problem is, I'm cutting so I can paste somewhere else. But because it actually removes those events when I cut, I think it's deleting them as if I don't need them at all anymore. Which is absolutely not the case. I imagine it would be a pain to treat events in the clipboard as still existing, so I guess the solution is to put a warning on cutting events that have the only creation actions for objects. Recommend dragging & dropping or copying & pasting and *then* deleting the old events.
Hope this helps!
Ah yes that makes sense. The thing is that there should always be a reference to the object somewhere. (either placed in the frame editor or with the 'create object' action.
Instead of deleting the object in the frame editor and make it stay in the game only by having the 'create object' action, you should instead just leave them in the frame editor and then destroy them on the start of the frame.
If you delete an object in the frame editor that has events associated to it MMF2 will warn you, but it doesn't seem that check is there if you delete the action that creates the object. Francois should probably add the dialog there as well so make sure that this doesn't happen.
Ah yes that makes sense. The thing is that there should always be a reference to the object somewhere. (either placed in the frame editor or with the 'create object' action.
Instead of deleting the object in the frame editor and make it stay in the game only by having the 'create object' action, you should instead just leave them in the frame editor and then destroy them on the start of the frame.
If you delete an object in the frame editor that has events associated to it MMF2 will warn you, but it doesn't seem that check is there if you delete the action that creates the object. Francois should probably add the dialog there as well so make sure that this doesn't happen.
Or make it easier to include objects that aren't placed in the frame editor. I hate cluttering up the frame editor with 50 unnecessary objects, but as we've seen before the "create object" events sometimes don't properly keep track of objects unless they exist in the frame editor.
Or make it easier to include objects that aren't placed in the frame editor. I hate cluttering up the frame editor with 50 unnecessary objects, but as we've seen before the "create object" events sometimes don't properly keep track of objects unless they exist in the frame editor.
Posting Permissions
Reply With Quote
