I assume that what Dade posted about the "float bumpmapsampledistance" [0.00001] made some kind of sense. Anxiously awaiting the day where I don't have to do a bunch of editing of .lxo and .lxm files in BBEdit after every export.
I'm working on it. I hope I have sorted the last problems this week end. If not I will release a preliminary version (without the support of C4D R9.6).
forgeflow wrote:Edit: I'm discovering the importance of light groups. Couple of questions:
1) Is it possible to automatically put the Sun in it's own light group when you add the light tag to the Sun object
2) Can the sun and the sky be in separate light groups or are they always tied to each other?
1) You can create a light group by entering a light group name into the light tag. This will not happen automatically. If you want so, I can make it automatical.
2) If you create a light of the type "Sun + Sky", you can't split them into two light groups. You would have to create two lights then: One for the sky using light type "Sky" and one for the sun using light type "Sun". Usually the relative brightness between sun and sky shouldn't be changed, as they are coupled to create realistic results.
forgeflow wrote:Yet another Edit:
I have a number of hanging lamps in this scene - and I am using the shape of the lamp globe as the shape of the Lux Area Light (which works just fine btw.). However, all of the lamps are instances of the one set of geometry in C4D. However, when I export this to Lux, each instance repeats the entire geometry setup of the one light object. Does Lux support instancing, and if so, then the exporter should export a C4D instance as a Lux instance, yes?
Instancing is not supported yet in LuxC4D