Sat, Jan 11, 4:02 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2025 Jan 11 12:18 am)



Subject: What is causing this??


  • 1
  • 2
kobaltkween ( ) posted Thu, 25 October 2007 at 9:29 AM · edited Thu, 25 October 2007 at 9:31 AM

could you post a screenshot of your render settings?  and also show how this looks rendered in Firefly, with another screenshot of settings?  the P4 render engine was very old, and i think it hasn't been quite what's actually  used in "Poser 4" renders since Poser 6.  i say that based on what could be a faulty memory of some posts, not so much my own experience, but i'm pretty sure others have witnessed discrepancies that show it doesn't actually duplicate P4/PPP rendering exactly.



Seliah ( ) posted Thu, 25 October 2007 at 9:52 AM

Aye... I THINK I found the problem, actually...

The default procedurals connect a reflection map (the sphere) to the reflection map node. They also set the Reflection Value to 1.000. However, the Reflection map is not connected to the Reflection Value node at all. So we have a map connected to map node, a value of 1.000 set to the value node, with no reflection map connected to it.

I have to test this yet - but the initial render after connecting the silly reflection map up to the Reflection Value node thus far shows none of that over-exposure of the procedurals. Give me a minute here and I'll double check. But I think this is the cause... o.O

~ Seliah



Seliah ( ) posted Thu, 25 October 2007 at 10:35 AM

Ja. Confirmed. Leaving all default settings to the product's procedurals 'as is', the only thing I changed this time around was connecting the silly reflection map to the Reflection Value node, and it's rendering the way it should, now. o.O Weird. Very, very weird. 

~ Seliah



bagginsbill ( ) posted Thu, 25 October 2007 at 2:55 PM

Umm - not disputing the results, but it not generally necessary to connect the reflection to both the color and the value. The value is simply multiplied with the color. When you connect both, you are multiplying the reflection color with a gray-scale copy of itself. This effectively darkens anything that is below 1 and brightens anything that is above 1. (You could only get above 1 if you were using an HDR image.)

Anyway, it seems that the sum of the reflections and the other lighting was way more than 1, resulting in color clamping. You could also simply type .5 or .3 or something in the Reflection_Value to decrease the reflection brightness.


Renderosity forum reply notifications are wonky. If I read a follow-up in a thread, but I don't myself reply, then notifications no longer happen AT ALL on that thread. So if I seem to be ignoring a question, that's why. (Updated September 23, 2019)


Seliah ( ) posted Thu, 25 October 2007 at 5:49 PM

Quote - Umm - not disputing the results, but it not generally necessary to connect the reflection to both the color and the value. The value is simply multiplied with the color. When you connect both, you are multiplying the reflection color with a gray-scale copy of itself. This effectively darkens anything that is below 1 and brightens anything that is above 1. (You could only get above 1 if you were using an HDR image.)

Anyway, it seems that the sum of the reflections and the other lighting was way more than 1, resulting in color clamping. You could also simply type .5 or .3 or something in the Reflection_Value to decrease the reflection brightness.

 

You know, that much I did know already... that's why I found it so blasted WEIRD. o.O But I've opened brand new scenes, tested it under spotlight, infinite, point, etc... I don't get it! I don't know why it would be the solution, but... O.o It seems to be... very, very, very ODD. LOL



  • 1
  • 2

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.