Moderator: BK
um. this is not intended looks like any DS light added to a scene is also reported as new plain standard camera, thus the plugin believes there is a new camera, and adds it as octane camera settings to what is in fact a light source. hm; i must admit i never thought about that being possible. nor do i wanted that behavior.SimonJM wrote:In addition to the plugin hiding the DS camera setting of focus point (or whateve rit's called!) I have just noticed that, in addition to it attaching Octane settings to Lights it also hides the light intensity setting - most annoying!
from what i have read, luxury does that - it converts ds lights for luxrender. imHo not the best idea ever... the results i have seen so far (if not tuned) are extremely overexposed, show hard contrasts, and are in general oversaturated, or in other words do not return what luxrender is able to do, if a scene is properly illuminated. and it would have been the same with octane (of course, as the same principles do apply).SimonJM wrote:I suspect it happens due to that fact that you can use lights to view through, so get 'announced' as having 'camera-properties' when they load, much as you say.
Much like you I suspect we'd wish to divorce DS lights from anything Octane-related - unless there could be some cunning way of automagically converting them to an Octane equivalent (like taking a suitably named Distant light and using the orientation to prep the long/lat settings of sunlight, converting a spotlight to an IES-driven model of a spot, etc.). I often peek through a DS light, just to confirm it is pointing just where I want it to. In any event camera-related properties are strange to see on a light and I'm glad they will be going!
Users browsing this forum: No registered users and 0 guests