Mon, Nov 25, 8:59 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 25 12:38 pm)



Subject: Error on Rendering


tiggersprings ( ) posted Fri, 19 January 2018 at 11:09 AM · edited Fri, 22 November 2024 at 11:44 AM

I'm trying to render a very simple scene and get this when I tell Poser to render.

erroronrender.jpg

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?


tiggersprings ( ) posted Fri, 19 January 2018 at 4:00 PM

Erm... Pardon my bandaged fingers. That should have been 16 gigs of RAM.

I think I found the problem .cr2 references. I'm going to have to sit down and see if I can edit them out or something.


Digitell ( ) posted Fri, 19 January 2018 at 5:47 PM

I have had this issue on numerous occasions. I usually reboot my system and that fixes it. I have a tendency to leave my computer on days on ends and Poser dont like that.

If you havnt tried it already, try to reboot your computer then give it another go.

Hope it helps!




ypvs ( ) posted Sat, 20 January 2018 at 4:46 AM · edited Sat, 20 January 2018 at 4:46 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


tiggersprings ( ) posted Sat, 20 January 2018 at 9:57 AM

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.


ockham ( ) posted Tue, 23 January 2018 at 10:47 AM

"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


tiggersprings ( ) posted Wed, 24 January 2018 at 10:36 AM

Absolutely. I've been running each thing I re-install through Runtime Repair and EI's Poser Product Checker before I rezip the item and install it in my new runtimes, but once in a while, they don't catch something like this.


Privacy Notice

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.