DokieMaster opened this issue on Apr 16, 2005 ยท 13 posts
DokieMaster posted Sat, 16 April 2005 at 12:21 AM
I know I'm not even pushing the limit here but Poser 4 hangs on me whenever I try to render 1400x1400 at 300 DPI. Why is it doing this? I have plenty of memory...
SamTherapy posted Sat, 16 April 2005 at 12:35 AM
Max render size in P4 is 4000 x 4000 @ 300 dpi. Are you rendering for print? If not, leave the dpi value at 72; it won't alter the quality of your render in any way.
Coppula eam se non posit acceptera jocularum.
DokieMaster posted Sat, 16 April 2005 at 12:55 AM
This time the size is 512x372 72 DPI. The exact same size I just rendered in the Main Window. In fact, it looks like the problem is any render sent to the New Window (no matter what the size or resolution) freezes the program. Any ideas how to address this problem?
SamTherapy posted Sat, 16 April 2005 at 2:17 AM
Several options. First, have you followed the instructions on the CL website regarding large renders in P4? Next, how much stuff do you have in your scene? If there's a lot, consider splitting your scene into parts for multiple renders. How much RAM do you have? Some people say they can manage just fine with 512 MB but I've always had more than that and sometimes had problems. How much HD space? IIRC, my P4 Pro Pack used to get cranky if there was less than 15 GB space left. One other thing - Poser will sometimes leave a PoserTemp file in its directory if it hangs during a render. This can cause lockups when you next start to render. Shut down Poser, look for this file and delete it if you find it.
Coppula eam se non posit acceptera jocularum.
DokieMaster posted Sun, 17 April 2005 at 2:28 PM
Well, I am still having trouble rendering in the New Window but only this particular model/scene I'm dealing with. I can successfully produce large renders with other model/scenes. My next question is does Poser 4 have a maximum # of polygons it can render and if so, what is that number? Regards,
SamTherapy posted Sun, 17 April 2005 at 8:08 PM
Don't know the answer to that. I suspect it's governed by RAM
Coppula eam se non posit acceptera jocularum.
nruddock posted Mon, 18 April 2005 at 3:15 AM
The number of polygons isn't the only factor.
(See Post 1 and Post 2)
Try removing objects from your scene to see if you can find something that's causing a problem.
DokieMaster posted Mon, 18 April 2005 at 11:14 AM
I haven't looked at either of the two posts yet but as for removing objects from my scene, there is only one object.
nruddock posted Mon, 18 April 2005 at 12:30 PM
Complicated geometry ?
Large textures or other maps ?
Complex lighting setup ? Installed the large memory update ?
Message edited on: 04/18/2005 12:31
DokieMaster posted Mon, 18 April 2005 at 2:30 PM
Model is 61,000 polygons
5 textures at 120,237 bytes, 120,103 bytes, 14,923 bytes, 51,755 bytes, 4,540 bytes
3 lights straight from the Standard poser Light Library
If the memory update is in the Poser 4 Updater on the CL site, then yes. I cannot tell it has done anything.
SamTherapy posted Mon, 18 April 2005 at 6:34 PM
Another possibility is that the geometry rsr is corrupted. You can delete this and let Poser re-make it when you restart it. I have known this cause Poser to hang when I used P4.
Coppula eam se non posit acceptera jocularum.
DokieMaster posted Mon, 18 April 2005 at 6:56 PM
I'm loading this as a saved .pz3 file. Would a problem with the rsr still apply?
SamTherapy posted Tue, 19 April 2005 at 3:21 PM
Not sure about that but a PZ3 can be corrupted, too. Actually, now I think of it, yes it could apply. The PZ3 doesn't contain any geometry, it only references external files.
Coppula eam se non posit acceptera jocularum.