@#$!@# Q@$!%$ 2#$%@#$% and $%@#$%@# !@#$@# not to mention @#$@$% #^@#@^#@^# so I think I am forced to @#$@#$@%!^ !#$%#%#$%# with the very @#$%@^% they rode in on, with a little bit of @#$*%#$$%^#%. Those @#$#@$@#$ over there, I swear, twice even, that if I ever see those #$%@$%@#$%@# I may just Q%$@#%$&@$% and thier little dog too! Arg! -Darth_Logice

The trick is to save the file BEFORE the program crashes. :) BTDT (been there done that) PhilC

You know, those pesky little RSR's really bother me!! Jack

Trouble is if you want to save before poser crashes then you have to save every 4 1/2 minutes. Shouldn't the message read DID NOT catch C exception 4Q2:OU812? If they really caught the error program wouldn't crash, Would it.

ROFL... that is like Windows. If you boot it up without a keyboard plugged in, it will say: "Keyboard not found, hit any key to enter" NOW IS THAT SCREWED UP??? LOL Jack

I have found that running nortan crash guard has cut my exception handler errors in half but it still sucks when they happen

PATCH PATCH PATCH PATCH (everybody chant with me here) PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH (anyone at Meta getting any of this... best damn app for human figures out, but it has some roaches we can't smoke!)

PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH PATCH

Have you noticed this never happens after a quick five minutes work on a scene, always after you have sweated all night. I get the error when I try to load a saved PZ3 files, sometimes when I render. The stupid thing is, poser crashes, so I hit control-alt-delete, and guess what.... Poser asks if I want to save the changes.

Here's a few tips: 1) Turn off that ground shadow thing in the display menu. It asserts if you have too complex a model. 2) Every once in a while, if I have a troublesome figure, I open the cr2 in a text editor and make sure all the storageOffset lines have 0 0 0 as parameters. Sometimes Poser sticks 0 0.3478 0 or some such nonsense and this can cause crashes. Also the last line of the cr2 which is also an offset line should be 0 0 0 3) Clean out the root directory of poser of any irrelevant files. 4) erase the 0bj rsr files now and then, especially the nude woman and nude man models. They get reconstructed by poser but sometimes get corrupted. 5) make sure any models you import do not have funky texture coords. This maybe hard to do if you don't have a 3d tool. If Poser tells you a prop has bad texture coords then don't use it. 6) I usually don't need 3 lights with 3 shadows, just 3 lights with 1 shadow. Poser has to render the scene once for each light that has a shadow. The camera is placed at the light and the scene is rendered to create what's called a stencil buffer. The size of that buffer is determined by the buffer setting for the light. Again this can reduce crashes if the scene only has one light with shadows. 7) I have a backup of the Poser.rsr file. when my system goes bonkers I restore the backup. This tends to clean a few things up. 8) Layers, layers, layers. 9) Watch for circular conform links for clothes ie shirt conforms to figure who conforms to pants who conforms to shirt. 10) when using the joint editor do NOT select an unparented prop while the joint editor window is up. This can assert big time. hope these help.

Thanks Mason! I think I speak for everyone when I say Great tips...(and I thought Masons were just bent on world domination :) ) -Darth