Printable View
I was wondering why this sometimes occurs that an object gets corrupted. MMF2 gave me an warning message that there is a a bad object used in the events and replaces it with a shortcut. I make backups very frequently so this isn't a serious problem, but I'm just interested why some objects in some instances become "bad objects"? Are there any potential reasons why this happens in MMF2?
Have you updated MMF2 to the latest version recently?
CT would be very happy if you could find a way to reproduce it so the bad objects appear.
I've been using the build 244. I know there is a newer one, which I'll get soon.
Anyway, there was this strange thing in my app. When I tried to delete one object ("object 1"), it gave the "bad object" error for another object ("object 2"). Then, I removed the object 2 totally from the frame (first all the events and then the object itself) and after that I was able to remove also object 1 without problems.
This is an important project and I would like to estimate the risks involved in this "bad object" error. Does anyone have an idea if these errors can keep appearing in the future. Is the mfa file corrupted? Or is it OK for as long as the bad object problems appear?
The problem has probably been fixed already then
Ok. Does anyone (like CT) have more exact experiences with these cases? So:
1. "Bad object" is detected from the mfa file
2. Go back to earlier saved mfa
3. Replace the "bad object" with a new object
4. Continue development from there
-> Is the mfa likely to be OK after this or could it still be corrupted (which would show later on in additional errors)?
I think some people still get the bad object issue, but we havent been able to locate it precisely though i do think some issues with it were fixed. So i would recommend going to build 247 in the first instance.
If you can replicate it in that build then please let us know.
Thanks
Jason
Hey Teddyq, you've got to update to the latest build always. You never know, you could be downloading something that MMF has been updated to, but you are using an outdated version of MMF.
-Proper coding methods helps prevent this alot. Have you ever used an eraser on paper too much? The result is a hole torn through the paper... heh
-So first to make it through a large serious project, you have to plan it as much as you can first.
I'm not saying you can't change things in MMF without problems but I've learned that you really need to save alot after you make a change, and try not to delete and move too many things around something eventually will break and that just means you don't really have a well thought out approach to your idea.
->Then again I change stuff all the time and I never get that bad object thing. I think it might have to do with what exactly you delete, if it is something complicated that might cause it...
>>Shrugs<<
Just had a bad object a couple of days ago when I was doing the following:
In frame 1 I had a active object that I constantly updated, that belonged to the Editor part of my game, on frame 2 I had the actual game. I got lazy to add up all the new animations and directions so I decided to copy paste this active to frame 2, I did so without a problem. Than headed over to the Event Editor and changed all events to go with "active 2", after that I tried to delete the old active by selecting it from the Frame editor on the left side. I clicked on "active" it disappeared and "active 2" became "active". I thought "What the hell is going on" and seconds later first MMF freezes then crashed (did not check the actual error). I launched MMF again and got the Bad object error message, so I switched back to a backup.
I also have to say that my system was running for like 20 days! without a reboot and MMF was open for like the last 5 days. Which of course could be the main problem.
I think that might be it. But when I've ever gotten that bad object thing, I think that might be the "exact" way it happend for me too.
So this could be a problem of MMF tracking a "shortcut"?
The same thing breaks in Windows! Dead Shortcuts happen in windows sometimes.
Could this be the notorious clue to the bad object bug?
Broken Shortcut links?
Maybe it is not possible to eliminate the bad object bug, but block the process that allows it to happen in the first place, like with the qualifier/inside bhaviors problem.
It's like walking into a room and turning around to see that the door has disappeared. Like an Ublient.