Getting corrupt objects often

[Wes_Richards]

Three times I've gotten corrupt objects and restarted my project, once every few days. I'm worried to continue working with Fusion. Is the problem linked to copy/paste? If I never use copy paste for anything inside Fusion will it solve the problem?

[schrodinger]

I often had corrupted objects when deleting qualified objects referenced and/or created on run-time in the editor.
Yes, that's a really bad idea!
But frames were becoming too messy, I was young and didn't think of the "create at start" option

If you're using "copy-paste" for objects,
you may better go with "duplicate" (for same instances) or "clone" (for different copy),
that should be 100% safe.

Although I never had problem with copy-paste on my fusion installation,
maybe you accidentally deleted some referenced object in the event editor, thinking it was a copy(clone) while it was the "original"?

[Wes_Richards]

I didn't think of that. In some cases I was starting my project from scratch and when I noticed a corrupt object, I hadn't deleted any objects yet at that point. But I think the object that was corrupt may have initially been copied from an older file. I assume this is what I did and ended up with a corrupt object.

I think I can work on my project, from scratch, without using copy/paste ever, if this will solve my problem. I was curious if copy/paste is the known cause of this issue.

I'll have to look into the possibility deleted objects are causing my problems. Thanks for the info.

[Yves]

Out of curiosity, what do you mean by "corrupt object"?

[schrodinger]

As for me,
I was referring to the "broken eggs" icons (I think that icon has changed at some point?),
which -to my memory- hinted a message like "missing reference" to an unexisting object.
I can't recall the message precisely since (luckily) I don't see them from a long time
(just after I stopped deleting from the frame "qualified" objects that were created on runtime...)
I guessed Wes_Richards was talking about those kind of errors

In some cases I was starting my project from scratch and when I noticed a corrupt object, I hadn't deleted any objects yet at that point. But I think the object that was corrupt may have initially been copied from an older file. I assume this is what I did and ended up with a corrupt object.

Again, If I recall correctly from my previous experience,
those "broken eggs" didn't pop up immediately after object deletion, but in following "re-opening" of the same .mfa.
So I'd say this coud have been the cause?