PDA

View Full Version : IK error!!

PaulG21
03-27-2004, 03:54 PM
I'm working in a file with an IK system set up but every time I try and save the file, a message appears telling me that the 'software has encountered a problem'. I'm given the option of clicking either 'retry' or 'quit without saving'. If I click 'retry', the message just flashes back up again, so I have to tick a box labelled 'Don't show me this error again' and then click 'retry'. However, when I do this another window appears and tells me that an error has occured and the application will now close. It asks if I want to attempt to save a copy of the file that I'm working on. If I click 'yes' then a file is saved in the 'autoback' folder but is seriously damaged i.e missing bones, geomatry. This is only happening in the files I have been recently been working on that have an IK system in them. When it first informs me there is an error I am given instructions to contact discreet and give them the following information:

In file:'.IKManager.cpp'

Line: 1483

Don't know what it means but I hope someone can help me!!

Thanks
thorn3d
03-27-2004, 06:52 PM
It sounds as if something related to your max installation is corrupting the files.

Have you recently made any changes to your install? Added scripts, plugins, some new shader - ANYTHING at all?

thorn
PaulG21
03-28-2004, 11:38 AM
The only plugin I've added myself is the 'attribute holder' modifier that you are told to install during one of the tutorials that is in the 3dmax tutorial book. Other than that, nothing.

Would you suggest that I re-install max?
Iain McFadzen
03-28-2004, 12:05 PM
An assertion error occurs when max tries to read or save a piece of data that it doesn't understand. In other words, your file contains something that has become corrupted. This could be an object, controller, material, anything really, and there's no way of knowing what caused it.

There really isn't any way you can save the file, all you can try to do is to salvage as much of its contents as possible.

Start by merging everything into a new scene. If the corruption is somewhere in the file that isn't directly related to it (such as a material that appears in the editor but not the scene), then merging everything should fix it.

If it still breaks, then merge half of the scene objects into a fresh scene. If this new scene isn't broken, then you know the corrupted object resides in the other half. From there, split the broken half into two, and check to see which half is still broken, and so on and so on until you have narrowed the offending corruption down as far as you can go. Once you've done that, go back to the original, merge everything except the broken objects into a new scene, resave and recreate whatever is now missing.

You only really need to think about re-installing Max if you are repeatedly getting corruptions in unrelated files .
PaulG21
03-28-2004, 12:55 PM
Iain, I just tried what you said. sort of anyway. I opened a new file, merged everything from my corrupted file in and then deleted my whole IK system! It will be a pain in the arse to redo all that but it seems to have worked. Thanks for the help!
CarlosA
03-28-2004, 09:13 PM
i think i know what it is.
sometimes on riggs that use the attribute holder. if you open and save the rigg on a machine that does not have it installed, it will delete and brake all conections to the now missing attributes such as reactor controllers and wireing.
the first thing you should check for, is if the attribute holder modifier is still applyed to the objects it should be applyed too.
if it's not then you need to figure out what controllers were hooked up to our now missing attributes and reset them to xyz controllers.
good luck!
cheers,
Los.
also you might want to turn off auto save while your doing these.
CGTalk Moderation
01-17-2006, 08:00 PM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.