Printable View
I'm sure many people have had this bug (tried to search the forum, but didn't come up with results, though). What is this about? So sometimes the frame editor makes an extra duplicate or copy of some object and places it at 0,0. For example just a moment ago I created one new object and now when I look at the frame editor, there are two of exactly same objects.
Is this a serious bug?
Using R247 on Vista.
It is a coding issue. It either has to do with your order of events, or an event being re-triggered. Without an example, we can't really be sure of the problem.
I dont think this is his coding as he said it is in the frame editor not during runtime.
Yep, in frame editor, not runtime.
can you post an example so we can see???
Interesting, I found this bug and I then I didnt want to delete the extra object at 0,0 I just moved away.
A question. Is this object marked as "global", or did you drag the original object from another frame?
Giovanni, it's not a global object and I haven't dragged any objects from other frames.
I just created a new object, then made some "create object" events in the event editor for this object (this has always something to do with the bug) and after that when I went back to the frame editor, the extra duplicate had appeared at 0,0. It's an exact copy of the original object (for example when I assign a group for the original object, this group change applies also to the extra duplicate object).
Actually, in the event editor, sometimes when I select the "create object" function and use the "relative to"-feature there to point to some object, MMF2 doesn't display this object in its origial location but at 0,0 (as an extra duplicate). I think the bug somehow starts from here.
I'm unable to post an example right now, but anyway, let me know if you have some details on this issue based on your previous experiences. Thanks.
Yes, if you do a create object action relative to an object that is not in the frame, it will create one in the frame to give perspective as to where the object will be created relative to that object. I've never experienced it staying in the frame after that though, so I can't really help much more than that. It may have something to do with qualifiers if you are using qualifiers.
The object is already in the frame, so that really doesn't explain the problem in the first place either (create object action). Thanks anyway.
I have been experiencing this as well. I agree that it has something to do with creating objects relative to other object's positions. The sucky part is that when multiple objects are displayed this way, they are all overlapped at 0,0. AND you can't select them to try and move them. They seem to be "virtual" copies or something. I am worried that they will start hindering my level placement when I finally start making objects that are much larger on screen.
Is there a workaround to remove them?
mobichan, when you have experienced this has it been only in the "create object relative to" action or have those extra duplicates remained in the frame editor also after you have applied the action (and went back from event editor to frame editor)?
I have had this many times in the first phase (extra duplicate is created temporarily in the "create object relative to" part), and now a couple of times also so that the duplicate remains in the frame editor. I can move it around and even delete it.
I haven't done any real tests to find out the exact conditions of it, but since the objects that are behaving this way are the ones created relative to another object, I am assuming that is the reason.
And I am unable to select them. My file has had them the entire time I've been developing my game, so if someone needs an example, I can post it.
Mobichan
Did you already tried "Arrange->Unlock ALL" ? maybe the objects are somehow locked.
For the workaround I suggest to put a qualifier and destroy all at start of frame. I tried this, but I had to follow the "destroy" action with a creation of a single object offscreen, because some of the following events behave weird if there's a comparison with no object present in the frame the first time it runs (as if there's a need for the runtime to found at least one object instance in the frame when it runs)
Since this is difficult to reproduce, Im still not able to write a satisfactory bug report.
I tried Arrange->Unlock All, but nothing changed. We are talking about a display issue in the frame editor (not at runtime) so I don't know why a Qualifier would change anything. It sounds like your solution is for a runtime issue.
That's weird because I can freely move those duplicates around the frame and change their properties (has an immediate effect also to the properties of the original object) etc.
Funny I didnt try to solve the problem or give an specific "solution" but trying to figure it out with you guys how to reproduce or workaround this problem so we can properly report this bug to clickteam.
One thing we know for sure, this is something about the frame editor and the creation of object relative to other object.
At this point, none of us are sure if this has something to do with anything (qualifiers, etc.)
Guys, this is a feature, not a bug :)
While in the frame editor, go to the Arrange menu and untick Show Created Items.
Hehe, nice try, mine wasnt "ticked", and probably this option may be the source of the bug(?)
Mine isn't ticked, but I am still seeing the problem.
I think this issue is fixed in the next update of the build 248 (or at least you should be able to delete these objects if it's not automatically fixed in old applications).
Sorry, I didn't realize my duplicates were on a locked layer. I was able to delete them after unlocking the layer. But it's good to know it will be addressed soon. :)