[purCAB]

I have a small (3 part) assembly that I am trying to render. The assembly has 4 SW lights -- 3 spot and 1 point. The lights are all less than 2 m in distance from a part that is approx .5 m in size. I export to Studio just to double check on everything. All of the emitters appear to be correct in Studio. When I start the render, everything seems fine. The Multilight panel appears OK and the render itself appear OK. However, when I set the "environment" light to 0, the 3 spot and 1 point light do not light the scene. I have tried setting the Multilight sliders to 10000, I have changed to emitter material so that emits 10000 watts. Nothing seems to make a difference. I have used this same technique many times in the past lighting a concrete material against a black background without problem, but I'm using reflective metals for this particular part. The problem does not appear to be insufficient ISO or Shutter.

I know that the general approach is to create "emitter" panels, but I've resisted this approach so that everything is "stock SolidWorks". Any insights or suggestions would be most appreciated.

---
Ken

[JDHill]

How big is the assembly or the MXS? Small enough that you zip either one and email it to me so I can take a look? I've tried to duplicate your basic steps here, but things seem to be working as expected. You mention using reflective materials this time - is there much else around for the reflected light to bounce off of and thereby get to the camera, or is most of the light from the spots possibly bouncing off into space? If the cone-angle is really narrow, those lights can become pretty directional.

JD

[purCAB]

Hi JD.

Total Pack & Go size is around 4 MB.

With regard to the assembly, it's just floating in space, but the direct lighting should have overwhelmed everything at some power setting.

The cone angle is 20 degrees and in SW the (projected) cone completely encompasses the assembly.

Ken

[JDHill]

Pretty sure the gmail address in my forum profile should handle 4MB, if you want to send the MXS. Apparently whatever this is, it's happening somewhere other than the plugin, so inspecting the MXS should work fine.