Ms_Outlaw opened this issue on Dec 08, 2001 ยท 18 posts
Ms_Outlaw posted Sat, 08 December 2001 at 2:20 PM
Buddha32 posted Sat, 08 December 2001 at 2:27 PM
Try going into the options and choosing the "restore factory defaults" under the startup options. I'm not in front of my Poser now, so I am not positive which menu, etc but it shoud be easy enough to find. I don't know what messed it up for you, but that should fix it.
Ms_Outlaw posted Sat, 08 December 2001 at 2:31 PM
Nope, that doesn't work. That screenshot is right after a reinstall the first screen. But I tried again to reset to factory right now and nothing changes.
leather-guy posted Sat, 08 December 2001 at 2:44 PM
Couple of things I would try if I encountered this problem; Try running scandisk/error checking on the drive you have poser installed on. (had acorrupted entry in my textures folder that choked Poser every time until I found it, once) Try disabling hardware acceleration. Try changing screen resolution to another & back again. Check & see if there's an update for your video driver (Saw something similar when a VidDriver file went corrupted on a PC) Try a "clean install" of poser on a different drive (if you have one) or under a different folder if you don't. (if it starts okay, restore your Runtime folders one at a time untilPoser no longer starts to see if one of them is causing the problem.) Each thing you try, check poser after, & if no improvement reset back any changes before you try another.
Lorraine posted Sat, 08 December 2001 at 2:53 PM
sometimes I get that type screen when the program is making repeated looks for texture maps...I minimize poser and wait for the "open" window to appear....sometimes depending on how much I have going on this can take a while...i think it is a refresh issue...
Nance posted Sat, 08 December 2001 at 3:02 PM
Probably have to do the above described torture... but before you do, (I tried to imagine a way to force the display to look that way) make sure the display is not in Silhouette mode with Box Tracking on. (I know, - doesn't explain how it would get that way after a fresh reinstall, or, account for the lockups on renders)
shadowcat posted Sat, 08 December 2001 at 3:44 PM
MaxxArcher posted Sat, 08 December 2001 at 3:49 PM
I get this kind of error when I rendered a few scenes with large (3000x3000 plus) tuxtures and bumpmaps. The PC runs low on resources, which it cannot reclaim. Nothing else to do than saving your work a.s.a.p. and reboot. Dont rely on RamBooster or other memory cleanup programs, they will mess up memory management. Maxx
MaxxArcher posted Sat, 08 December 2001 at 4:04 PM
BTW, I dont think its a Poser problem, but more likely a Video card Driver/OpenGL DLL library/DirectX (come with Windows) problem. For all I know, Poser utilizes OpenGL as a few other graphical programs, e.g. MorphMaster. Older OpenGL libs are quite buggy. Esp. when Poser, Morphmaster and Anim8tor are ran together. When one of them crashes for one reason or another, you can count on the others following soon. I really think that reinstalling Poser wont resolve the problem, despite the memory problems with large textures its quite stable, check your DirectX settings with DXDIAG residing in C:Program Filesdirectxsetup. I dont know of a standard way to check OpenGL settings. Also use your video cards diag/settings tools to check your graphics. Ill check my HD for some tools for OpenGL, let me know if you (or anyone else) want to have them... Good luck Maxx
Ms_Outlaw posted Sat, 08 December 2001 at 4:15 PM
Tried the scan disk, installing to new HD. Nothing works. I didn't install upgrades. Figured there wasn't much point. My version is 4.03. Just ran the directX dignostic. Seems to be fine. Vue works and Zbrush also works without problems. Thanks, guys. Guess I can hope Curious comes up with something.
SAMS3D posted Sat, 08 December 2001 at 4:34 PM
This is Pro Pack right? When did this start to happen? I mean what did you do different that it made the change. Did you just go to your application and open it and it was like that, or did you do something while you were working in it? Sharen
Ms_Outlaw posted Sat, 08 December 2001 at 4:55 PM
It happened last night, Sharon (Friday) Far as I know I didn't do anything different than normal. I remember opening it, it was fine. I minimized and did something (can't remember what. But nothing out of the ordinary) Brought it back and it was like that. I too have seen it look something like this when looking for a stray material, but always cleared up. Again, reinstalling it should clear up anything like that. I would think it was a hardware problem if I had problems with my other stuff that I run with opengl. I don't get it. Something stuck way down deep in my Operating system maybe? Running windows 2000 pro. It sees Poser and says no way?
ScottA posted Sat, 08 December 2001 at 10:20 PM
How did you do the re-install? Did you completely remove the program and all it's folders from your HD before you installed the new copy? There is an .rsr for the program in the Poser folder itself. If you don't delete it and replace it with a good one. Your problem might remain. ScottA
Ms_Outlaw posted Sat, 08 December 2001 at 10:30 PM
Yup I did Scott. Totally clean install. Twice to the c drive once to d... But, will see if I can get an rsr file from a friend and see if that does anything.
Nance posted Sat, 08 December 2001 at 11:35 PM
Have to go with Maxx - look elsewhere. With a clean install, to a new drive, from a CD that worked before, sounds like you've reasonably ruled out problems with the app itself.
Ms_Outlaw posted Sat, 08 December 2001 at 11:42 PM
I figured I had it licked. I deleted it again. Removed directory, then went into registery and deleted every mention of poser, and Curious labs. I thought for sure that would do the trick.... It didn't. Why me? Misery loves company, be nice to know I'm not the only one... guess I am. Lucky me. I give up.
acottted posted Sun, 09 December 2001 at 12:14 AM
I have the same problem - too much virtual ram - your page file size greater than 3 gb and poser freaks - every time or two I render a large scene, I have to increase the page file / virtual size to get a render without running out of disk space (which is what poser says when it gets lost and can't see all the ram and page file even though it is not using all of it) - after I go above 3 gb virtual / page file size, reloading poser gives exactly what you are seeing - if I don't reload poser, it will go on up to 4.095 which is where Win 2000 tops out - if I drop the page file size (go to settings, control panel, system, advanced, performance, etc and reset to below 3000) and reboot to have it take effect - the problem goes away - quirky but can be worked around - I got into this recently when I bought a new high-end computer - I am trying to get poser to fix the bug but haven't got them to yet - Ted
Ms_Outlaw posted Sun, 09 December 2001 at 12:28 AM
Gives ya a big kiss! It works! My hero!!! ~LOL~ Thanks very much! Thanks everyone else to for offering help.