ljudice opened this issue on Mar 20, 2003 ยท 10 posts
ljudice posted Thu, 20 March 2003 at 9:34 AM
I tried to search past messages to no avail - but I know I had this happen to me once before - and have seen it discussed here. After a disk disaster (new disk installed, Windows 2K all running fine) I reinstalled Pro-Pack and now this is happening: - When it opens, no default figure is viewable - but it is there - as you mouse over joints, you can see body part outlines appear. - when a file is loaded the same thing occurs - it's sort of there, but not visible - nothing renders due to "out of memory". I increased paging files on two disks to 4095 each - and the system has 1 GB of RAM. I think this was my old setup. Any ideas? Thanks very much, Lou
geoegress posted Thu, 20 March 2003 at 9:40 AM
try delete in the rsr files. they may be corrupted. poser will rebuild them automaticly
geoegress posted Thu, 20 March 2003 at 9:41 AM
ohh- and check to be sure the cr2 or what ever is pointing to the correct location of any obj's used
judith posted Thu, 20 March 2003 at 10:00 AM
Have you checked your video card drivers?
What we do in life, echoes in eternity.
E-mail
| Renderosity
Homepage | Renderosity
Store | RDNA
Store
PeterWahoo posted Thu, 20 March 2003 at 10:54 AM
The "Out of Memory" error message usually comes after you receive an error message stating that a particular geometry file can't be found. An example: You try to load Voluptuous Vicky when you don't have DAZ's Victoria installed. If you have Windows 2000 or Windows XP, you might get an "Insufficient Disk Space to Render" message. That has something to do with a conflict between Poser and your Windows Swap File. Translation: you don't have enough room on your hard drive. You might try installing Poser on a different hard drive. The swap file fix advocated by Curious Labs is ok if you still have enough room on your hard drive. That issue can be deceiving since we don't always know just how much space is needed.
ljudice posted Thu, 20 March 2003 at 11:29 AM
Thanks for the tips.... Some more details of the problem: - system has three drive: 30GB, 120GB and 120GB. So system disk has about 22 GB free. - problem occurs after clean boot without loading any files - ie. the default dork comes up - is there - but is not visible. Rendering just dork hangs poser....
PeterWahoo posted Fri, 21 March 2003 at 6:21 AM
Attached Link: http://www.curiouslabs.com/
Out of curiousity, did you install the latest Poser ProPack service release? If not, go and get it. Oh, gosh you may want two updates. I see the SR3 Updater and the Pro Pack Updatere, For users of Pro Pack who have more the 1 GB of total memory. (RAM + virtual memory = more than 1 GB.)ljudice posted Fri, 21 March 2003 at 7:57 AM
Peter, thanks! I deinstalled ProPack last night and reinstalled just P4 (I also run P5 but on another machine). Brought it up - installed on a different disk, with about 114 GB of free space and SAME THING - default dork is there, joints illuminate when the mouse goes over them, but no shaded characters and renders hang. So I went and REDUCED the size of the paging file - and it started working (set to 10 min 100 max - I had previously had it set to 4095 max). I am almost 100% sure I had installed all the updates before - but I am sure you are right - this is related to virtual memory in some way, so I will do it all again. Thanks again! Lou
PeterWahoo posted Fri, 21 March 2003 at 9:43 AM
You might just try letting Windows handle Virtual Memory all by itself. I'm a techie, and never mess with the swap file because I'm timid. But I can't help notice the update Curious Labs made for people who have over 1GB of memory, including the swap file. By the way, I run Poser 4 and Poser 5. Each is installed on a totally separate hard drive from my Windows hard drive. Things have always worked better for me that way.
ljudice posted Fri, 21 March 2003 at 11:40 AM
Believe me, I don't touch what isn't broken!!! When I first ran into the problem, I assumed it was the infamous pagefile size problem, so I increased it to the maximum 4095. I suspect something else was/is going on though... BTW, my tech experience in computers in limited to VMS (!) and over in that world - page files and swap files are totally separate animals. I am assuming that in windows people are using the two interchangably and referring to the pagefile - which can be set under "my computer" properties... Thanks again, Lou