Forum Moderators: RedPhantom
Poser - OFFICIAL F.A.Q (Last Updated: 2025 Feb 24 11:54 pm)
I can backup your assumption - the queue renderer often gives me different results than renders made directly in Poser.
Here is a little discussion about a likewise problem
http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2830354&page=1#message_3814546
I'm not always right, but my mistakes are more interesting!
And I am not strange, I am Limited Edition!
Are you ready for Antonia? Get her textures here:
The Home Of The Living Dolls
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 again to see if anyone else has come across this problem.The above image shows two renders of my latest gallery image, which uses a procedural tile shader I'm working on (just about done, I think). They were rendered at exactly the same size and with exactly the same render settings:-
Top: directly in Poser Pro
Bottom: via Poser Pro Queue Manager.
The tile density in the QM rendered image is exactly twice that in the direct render.
Has anybody else seen this? Does anybody know why it should do this, or how to stop it?
(edit) Note: if I open the QM-saved scene in Poser and do a direct render, it looks like the top one.
"If I were a shadow, I know I wouldn't like to be half of what I should be."
Mr Otsuka, the old black tomcat in Kafka on the Shore (Haruki Murakami)