JAG opened this issue on Jun 07, 2006 · 2 posts
JAG posted Wed, 07 June 2006 at 2:35 AM
Are you suddenly discovering that Poser 6.02 is freezing up while loading textures on Pz3 files during the render process anytime that you have more than one figure...or too many hi-poly props in a scene. This is not normal and if it suddenly starts happening to you...and files that once rendered fine...start to freeze and lock up...you're not alone. I have battled back and forth trying to figure this issue out for a while. I still don't know the cause necessarily...but I believe I've figured out that it has something to do with corrupted code files in the Poser exe. files. You can fix the problem by following the steps below:
Make a full and complete backup of your entire RUNTIME file from Poser 6.
Store it on disk or somewhere where it can be retrieved.
Use the e-frontiers UNINSTALL POSER 6 executable file found in your windows program menu.
Poser ain't uninstalled by no means. So now go erase the entire POSER file manually inside your C:/Program Files/Curious Labs/ ---- with e-frontiers versions...you may have a different name. I've got the Curious Labs original 6.0 ...so my folder is "Curious Labs."
Now that it's gone, gone...restart your computer [reboot it]...and use your Poser 6 software disk and completely reinstall Poser...once it's installed again...you'll have to re-enter you serial numbers and all that good stuff. Also if you have the original 6.0 version like I do...you then need to reinstall the 6.02 upgrade which can be downloaded from e-Frontiers website.
Once that's done...go in and replace your entire RUNTIME file with the backup you made at the beginning.
Open Poser...you'll need to reset your workspace...but your RUNTIME files will be just like before...in other words, all your Poser files are returned.
What we've done is completely erase and reinstall the Poser operating files.
Don't ask me what causes the crazy glitch to begin with. I noticed after performing the reinstall, my textures also began to load faster and render times decreased significantly. Again, I have no idea if anyone else has suffered a similar program failure...but at least now you know how to fix it.
Warning ahead of time though...you MUST manually delete the entire Poser file...because attempting to "repair" or install over the old files does not fix the problem. Believe me...I tried that first out of paranoia of losing Poser files. But everything went fine...and so far my render issue is fixed for the time being.
If anyone has anything to add...like perhaps an actual explanation for the render engine failures, please feel free to post it here. I might also add the failure problems occurred both in P4 and Firefly engines...the issue lay with the Poser operational code somehow...and not with a failure of the actual engines...
Hope I can help somebody not pull their hair out...I certainly know I've got a few less hairs on my own head after this particular bug.