I've had a problem w/ my copy of Poser recently, maybe one of you could help me address it. Every now and then, upon adding figures or props & garb to a scene, I receive (1) a C access violation, (2) a statement that my machine is out of memory, and (3) the primary figure (always Figure 1) of the piece I'm working in disappearing. As I'm using the older MetaCreations software, I doubt I can receive asssitance from Curious Labs (and as I don't have Internet acces from my home, having them troubleshoot my stuff on the Net is close to unimaginable). Anyone having a similar problem, and other than saving constantly, would anyone have an idea of how I can fix this? BTW, running Poser on a 233MMX with 128meg SDRAM; more than enough to never run out of memory - as long as I don't try to cram 5 figures in a scene... so that ain't it... -Dave

Dave Have you load patch 4.03 from Curious Labs? You can download from they web site. The file is about 11mb. Do you have any way to get it? thebert

The difference between stupidity and genius is that genius has its limits.

I'll have to update my copy after I can get my system to a friend's & patch into his/her phone line; either that or burn it to disk. Thanks for the heads up! -D.

The Poser 4.03 patch, available from the Curious Labs website, fixes the "Caught C exception" error. It doesn't matter if you're using the Metacreations or Curious Labs version of Poser. It's the same program. CL just took it over after Meta dumped it and in fact, almost all of the staff at CL are the people who developed the program from Meta in the first place so they've been with the program from day one. They provide support for Poser 4 in all its incarnations. As for the out of memory, well, that's sort of the catchall for when poser doesn't really know what the problem is which, again, is most likely tied into the "caught C exception" and will probably clear up as soon as you apply the patch. That's how I fixed it when it was happening to me. Kate

Burn it to disk so you have a copy if ... or went your system hard drive goes out. :) The patch does fix the "Caught C exception" error as Kate sayed. On memory, if you are not using high res tuxtures like Asia, Yuma or DAZ High Res, 128mb is ok, but more is better. :) Just reminder if you are running win95/me/98 about 256mb is all it can handle. thebert

The difference between stupidity and genius is that genius has its limits.

Yeah, I'm using 4 purcased directly from CL after theupdate, and invariably, if there is some problem and it can't load an .obj file for some reason (usually a corrupt rsr file), the primary figure ALWAYS vanishes. What a paininnabutt! I've learned the hard way to ALWAYS save right before trying to add ANY new prop, figure, or whatever.

not sure about c violations, but I sure know what you mean about the memory consumption. once I start adding in a buch of high res textures, and move a model around my screen a bit, I've used up alot of my RAM, and I've got 512MB on there, I've got a program that monitors my available memory, so I'm watching it on the taskbar as I do stuff in Poser, hi-res rendering can use up to 200 MB of memory on my machine. Sucks, I know. I'm going to try upping it to 768 MB and maybe finally then I'll be able to have music playing, photoshop open, internet browser open, and model in poser all at the same time.

If your using a MAC try assigning more memory to poser.

Any advice on C violations in P3? (Prehistoric user.)