Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 20 6:12 am)
Wow! Sorry but I have never had that happen to me, I'm sure someone will come along that knows what to do :)
Poser 9 SR3 Â and 8 sr3
=================
Processor Type:Â AMD Phenom II 830 Quad-Core
2.80GHz, 4000MHz System Bus, 2MB L2 Cache + 6MB Shared L3 Cache
Hard Drive Size:Â 1TB
Processor - Clock Speed:Â 2.8 GHz
Operating System:Â Windows 7 Home Premium 64-bitÂ
Graphics Type:Â ATI Radeon HD 4200
•ATI Radeon HD 4200 integrated graphicsÂ
System Ram:Â 8GBÂ
That happened to me quite frequently when rendering to a separate window. It was usually followed by a complete lockup of Poser. Rebooting the computer would occasionally allow a complete render, but not always, and the more complex the elements of the scene were the more likely the problem was to occur. I believe the source of the problem is exhaustion (maybe fragmentation) of memory resources. Sounds pompous :) but is easy to fix--I now make sure a program called MemTurbo (www.memturbo.com) is running before I do any rendering. With MemTurbo running, I have no rendering failures (well, artistic ones, but those are MY fault). Turn off MemTurbo, and try to render the same scene with the same settings--guaranteed lockup. Traveler started a thread regarding RAM leak crashes and freezes a week or so ago--do a search on "RAM leak" to read what others have to say. Good luck solving this problem. I know how frustrating it can be.
JB-- Mem Max started the ball rolling, but as I recall there was discussion about several other programs as well. Multiple solutions to the same problem. My original guess was video drivers as well--except that, for me, the problem spanned multiple computers, and a variety of video cards. As to why it happens to some folks, and not others--I dunno, frankly. Maybe it's a combination of the complexity of the scene (large texture maps, lights, shadows, and the number and nature of figures and props involved), available RAM (installed, and what's left after any background programs are taken into account), and the size and resolution of the "new render" window. If someone IS having this problem, and their video drivers are up to date, a program that automatically recovers RAM when the available amount drops below a certain level might make the difference. Hey, Marybeth, could you try rendering that scene you showed us in your message with all the boxes in "Render Options->Surface Materials" unchecked? Do you still have problems that way? Just curious.
I had this happen also. I had tried most of the above suggestions, including "mem turbo" and nothing worked. I ended up installing Win2k (I had Win98) on my PC (from sctatch not upgrade and installing poser from scratch. All of my previous PZ3's now rendered perfect, I have not seen this problem again. Win2k (or XP) is the way to go...forget the old Win9x OS's.
This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.
Marybeth