It seems to be non-working if VRaySky map is used as texture map in a VRaydome.
To Vlado: is it possible to have a more predictable behaviour on VRaySky in mateditor; I mean, renders are fine but matedit slot is always white
..or am I missing something?
a.
i use a multiplier of 0.01…sky looks fine in the mat editor, with linear workflow.
probably you’re using color mapping, and the sky is very bright, thus white.
it seems logical to me that the sky is always visible if mapped to a dome…the dome should rather be set to invisible then…
I’m sorry, my mistake!
I am talking about the invisible check box in the VRaySun not VRaySky (now it’s correct in the previous post).
If you put the same map first in the environment slot and hit render then you got the sun as a white disk; this doesn’t happen if you use that map as texture map in a dome vrlight.
About the matedit issue I use LWF too (+ reinhard CM) but I’m still having white slot; it seems someway related with the auto update issue that someone already found.
Other missing infos are that if I use the Physical Camera I have to leave the VRaySun to its default value, so I can’t use the “0.01” trick.
a.
yeah the “proper” workflow for sun/sky/cam is to leave the sun and sky at default 1.0 multiplyers and then use the physical camera to control the light. That way the osi and f-stop values of the camera match close with a real world camera.
But your right the mat editor vraysky preview is always blown out.
maybe a sort of autoexposure option for the vraysky matedit slot could be a viable suggestion?
a.
maybe you can wrap the sky into a color correct map, for tweaking.
a smarter material editor woud be awesome!