Forum Coordinators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 21 6:06 am)
One option is to repeatedly render a one object scene working through all the items to see which one is the problem. It might even work if you hide most of the objects- not sure if Poser will still load the hidden data
Poser 11 , 180Gb in 8 Runtimes, PaintShop Pro 9
Windows 7 64 bit, Avast AV, Comodo Firewall
Intel Q9550 Quad Core cpu, 16Gb RAM, 250Gb + 250Gb +160Gb HD, GeForce GTX 1060
That's pretty much what I did, rebuilt the scene item by item and rendered. I found the problem and chopped the problem references out of the cr2 in a text editor. I figured I really couldn't break it too much and could always copy a fresh copy of the cr2 back over. Renders now post-hacking so I guess I'm good to go.
It would be nice if Poser kept an error log for things like that, though.
"It would be nice if Poser kept an error log for things like that, though."
Ditto that. Would make it much easier to relocate the missing pics, or switch them to NO_MAP.
My python page
My ShareCG freebies
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.
I'm trying to render a very simple scene and get this when I tell Poser to render.
All products in the little scene are recently installed and I personally did pre-installation troubleshooting on everything in the scene to make sure there wrere no bad texture references before installing each item into my new runtime.
I'm using Poser Pro 2014 in Windows 10 Home 64-bit on a PC with 156 Gigs of ram. Does Poser log what file is causing this error somewhere?