Heya all, before I email CL about my problem I want to know if someone else have this problems. Everytime I import a 3ds file I get a C exception error, same is when I try to load PhilCs new dress. Same in clothroom ... when I want to start a calculation I get this error. Maybe it is my PC but I'm not sure. I'm using a Compaq workstation SP 750 with a Xeon 866, 512 MB RAM, Poser 5 with SR1b. I hope someone can help me Chris PS: what was CLs bug report email again?

bugs@curiouslabs.com

thank you Anthony :)

I just got the C exception, however, I was not using a #DS file, just normal Vicky and lights, no clothes, no nothing. I never got this error before the patch.

I just got it too for the first time. Marque

I'm thinking it's a dog, plain and simple. And wondering if it really did get beta tested all that time that we were waiting. Go ahead and jump on me but I am really disappointed in this whole thing. Should have listened to my intuition when CL kept us in the dark and fed us all that BS and threw us scraps about this program, guess now we know why. Marque

I got it while importing a 3ds file last night and sent CL a bug report. However, I've noticed that it doesn't happen with ALL 3ds files. (I tested about half-a-dozen).

I get mine while rendering.Usually when I`m trying to render displacement maps & hair. Sent bug report. There is SR2 coming out sometime during the week. So CL told me when I contacted them about the huge downloads & no resume. Thats sorted now & SR1 now fully download & installed. But still get C exception errors. I shall wait for SR2 & see how I go from there. Its a shame that there are so many bugs, unfortunatley its not uncommon because the new features are great.

as I see more people has problems with C errors ... good that they have send a bugreport to CL so I dont need to do it again ;) I hope with SR2 things get better :) Poser 5 is a great app, I like all the new features but sometimes its frustrating when you get errors and cant step forward in some projects. So please CL bring out the new SR as fast as possible :) Chris

I got my C exception error posing Judy. I also got it trying to open up a *.pz3 file I had created in Poser 5. By the way, is it just me or are Judy and Don very slow to pose? Those parameter dials may be larger but it seems to take a lot of nudging to get anything to happen. I don't like having to enter the numbers each and every time...I prefer to do that for the fine tuning. But I don't have a choice in Poser 5. I can't get the Poser 5 figures to budge any other way. Yes, I've got Inverse Kinetics turned off.

Nope! Happens to me too, P5 is just slow, even after the patch, more memory and a better GFX card. As for the dials, don't get me started, I'm beginning to get really hacked off with having to move them (the window) all the time, (as well as being unable to use them.) How about a patch to embed them back into the desktop where they belong? Though while I'm at it, why did it take 3 years to integrate a load of third party packages into Poser4? It's not like you had to code the stuff yourself, and I imagine they all came with API's that allow for simple integration, though I'd be happy to hear that I was wrong. later jb

Geeze, is there any way to UNINSTALL the service release? I finally got to where I could work AROUND the initial bugs, now Poser 5 is TOTALLY unusable with all the C exception errors.

I had some problems with C exceptions on rendering, but the cause was textures on objects copied over from P4 libraries not being in the right location, which was a simple fix. Still, the program is inefficient and unstable. At least I'm not having the same level problems others are having, despite my AMD cpu.

Report it but don't hold your breath on getting a response back. I haven't yet. A patch to fix the patch better be coming soon.

Can someone explain what the devil a C exception error is? Since this error is totally unknown in the mac world I have no idea of what all these things are.

If it's a 'caught c exception error' it is debugging code in the program. The program makes a booboo and catches it itself. It just can't figure out what to do about it. You can get stuff like that on a Mac too...just wouldn't say the same thing. I'm sure Mac programmers can put debugging stuff in their own code if they wish.

It is an "exception" (or error) which is not caught and dealt with. Errors always occur in the process of running a program, you just have to write the code to catch them, and recover. Then the user doesn't notice the error or have to click OK 5 million times. Looks like CL Missed a few!! I had mine messing about in the cloth room. H:)

I have a suggestion to everyone who thinks Poser 5 is a "dog"- try to return the product. If it doesn't work on your PC, try to get your money back. I say "try" because CL may or may not actually refunds your money. If they don't, try going to your credit card and explain that the new piece of software that you just bought doesn't work properly... and that the company won't take it back. (Let CL deal with VISA and Matercard enough times about unhappy customers and see what happens.) If you still can't get your money back, post your story in this forum. Nothing hurts (or helps) a company's reputation more than consumer's experiences.