Printable View
Hey, I somehow ended up with a few bad objects in my game, i replaced the models, and deleted the events, but it still won't release the bad models!
I have tried building the application, playing it using f7, and f8, and some of them just will not release (Even when I use the delete key in the objects list, after looking over the entire frame and not seeing them there)
I dont have them as global objects so IDK what the deal is...
I hope I have your question right. F7 F8 are reserved for widows I think. I am sure that other forum members will correct me on that statement if it is wrong.
Once you get bad objects I have found it is best to recode. Do you have backups?
Upload the file with bad objects and draw one of the coders' attention to it - hopefully they'll be able to find out what went wrong.
Which version do you use?
If you are using behaviors, you might want to look for references to the bad objects in the behavior event lists. That might be what is keeping these zombie objects alive.
Otherwise, assuming you are not too deep into your application, you may want to copy the "good" objects and events to a fresh MFA.
Also be sure your running build 248 before reporting bad objects.
Many causes have been corrected from the older versions.
but yes if you have bad objects or even better a file you can reproduce bad objects at will we would love to see it in action.
I have Version 2.0 Build R248 I ended up just recoding the things :\
It was an active object that I copy pasted the top half of the ISO towers under miscellaneous and then middle ages in one of the image packs.. Nivram, f7 is run frame, f8 is run application... And I was also using one of the ISO knights from the same location, i can try to replicate the bad objects, I'm using pretty much the same code, just organized the groups a little more this time...I made the mistake of deleting the file that I had :\
I keep hearing the rumours of these Bad Objects but I have never seen one, I don't even know what it is; if you tell me what they are then maybe I can help you.
You can't help Dragonguy. Most users never encounter them.
Somehow very rarely something becomes corrupt and MMF can't identify an object. The key to solving this is reproducing it.
I.E. have a MFA file with a list of steps that will cause a bad object.
Can I have a Link please Jeff.
Lol, rumors? They are very serious, I've encountered bad objects in 3 of my games. I don't think anyone really knows what causes them though. They basically just make a certain object void, as in all code/aspects of the object, no matter how perfectly it was structured, will not work. It also changes the object's icon to a wierd red cracked egg? I can't really tell what it is to be honest lolQuote:
Originally Posted by dragonguy
However, one time I deleted an entire group of events and got a very strange error that said a few objects were related to bad objects, and should be immediately replaced (or something like that) I was so frustrated I closed MMF because I thought I had a bad object that would ruin my game, but I opened it later to see if anything happened and everything worked fine..so..definately confused me but hey I didn't lose my game :D
I try to keep a trillion backups of each of my projects. It reduces my frustration level, even though I have to code more. At least the whole project doesn't go away. This has saved my bacon more than once, although not just from bad obects.
MMM... Bacon, oh sorry I have a lot on my mind. Camleman says that they're icon is a weird cracked egg? Never seen that. Iv'e seen bomb objects in the event editor where I have forgotten to copy an object in to the next frame after copying events from frame to frame but thats about it really.Quote:
Originally Posted by nivram
I get the "weird cracked egg" when dealing with behaviors. Here's one way:
1. Create an active object.
2. Give it a behavior and create some random events with the AO in them.
3. Copy the events.
4. Delete the active object.
5. Paste the events into the Event Editor.
The active's icon should now have been replaced by a "weird cracked egg." Is this a bad object?
Well as far as I know the "weird cracked egg" or bomb or w/e is just a placeholder for a "voided" object(ie. an object that has events, but not the object itself in a frame) so what you described doesn't create a bad object. I think that might be a starting point of getting a bad object though, as I copy and paste alot of events and have gotten quite a few bad objects :\Quote:
Originally Posted by Jaffob
Yes, a bomb is not harmfull. It will disappear when you paste the missing object in the application.
What is dangerous, is when you get a message box saying that some objects are bad.
One time in my game, I had an object that I think was a Created Item. But if I tried to delete it, a C++ library error would pop up and close the application.
Another time I had an event with a sequence of logical ORs. If I deleted a few conditions and then hit "Undo" I would get an internal error.
Are these bad objects?
You will definately know if you have bad objects, if you do get one a window will popup telling you they exist in your app. So if you haven't gotten that specific message you should be good.
As was said, though they are extremely rare now, if you ever do get that warning about a bad object please save that file immediately, (with a new name if you like) and get it to Clickteam.
Any notes about what you were doing that led up to the warning should be included.
That is how we have solved the problem so far and it is the best way to assure it is prevented. Even a rare occurrence of it is something we want to see and fix in a patch.
Thanks!
Well, since there is a post on it I will add: I had a pad object a few weeks ago, that occured a save after I tried to move some of my events to be behaviors for an active instead of the main code. It ended up screwing a bunch of stuff up (partilly to my not planning for it to begin with) so I reverted it back to its original state, but it then said I had a bad object.
The wierd thing is, the object that went bad had NOTHING to do with the events I was trying to make into behaviors.
I fixed it by just dropping the same object from an older save and haven't had any problems since.
As stated before, MAKE BACKUPS. Any time I figure something out I'd been stuck on for a while, or something that took me a long time to program in, I make a new backup. Lets just say... Current project I'm on is build 187, and it covers over 2gb worth of old files. (I've deleted some of the older versions and started keeping only every 10th up to the most recent 15-20 to save on space, heh)
I just had a bad object error that is probably going to cost me several days worth of work, since I had been lax about backing up for a little while here.
Just like chaos, I had an object which was completely unrelated in every single possible regard went bad while working with another object. My only action was making a copy/pasted version of another object, and assigning it copy/pasted code. However, I don't think the source code would do much good for clickteam, since the project is so ridiculously large it could take months to understand how things work.
So that sucks
hahaha I found an extraneous copy of a version from yesterday in my recycle bin, nevermind! My puppy had chewed on my mouse and now it double clicks on single clicks, and I had made a copy by accident. Go figure!
Clickteam Backup Puppy 2009 :) I'm glad you got it back.
Sending on the source file would still be appreciated.
Puppy saves the day!
my bad object deleted my frame....and i hadnt back ups..
You probably use Windows 98, Wordpad and MSIE 5.0 too, right? :) . Nevermind - back to the topic... I hadn't these bad objects, and I hope I will never encounter this error. Otherwise i will call for my little green friends and I will give them requests to blown up Clickteam's buildings ;). I like to see a way to reproduce bad object message that always works.Quote:
Originally Posted by paskahousu
Maybe really Yves's code is buggy?
Hey Darkhog. I use Win98 for a test bed computer. Never experienced bad objects. Sometimes it is slip by the programmer, although some people, the way I understand it, have had bad objects for no "apparent" reason.
I've had Bad Objects only when I've actually done something I knew wasn't a good idea, but did it anyway. Most of the time it's when I try to copy and paste, and by most I mean, that's where all the rare occurrences of this already rare issue, seem to show up. Otherwise, I've really not had much of a problem with them showing up. And when they do show up, a simple "Replace" with the correct object, tends to fix the problem, but that could just be because mine were from importing.