I'd love a test link. Only thing keeping us from 100% switching to 2015 is this plugin!

So a little more info: I did a 'fresh' install on another computer, and don't have this issue. Weird!

Possibly is it old Max plugin/DLLs files from older builds still being in the Max folder? I tried removing what I thought were the old files, as what you have to 'install' has changed over time ...

When I first started working with Octane in Max, I could un-check the 'visible' parameter on an Octane Light and have it not appear in the rendering, yet still project light into the scene.

Ever since I updated to the latest stable build for Max 2013, if I set a light to not be visible it also ...

+1
I believe however, Autodesk will never allow this... After observing its monopolistic policy i have to say - forget it! Revit code is something protected and secret.
I wish anybody proved I'm wrong!
Kacper

You're wrong. :D

All someone needs to do is write a plugin. Revit's API is .NET based ...

Probably not. DXF isn't as much as a standard as you think. The problem is that Textures are handled differently within DXF by different systems. For example, with Revit exports to DXF, things are grouped by the layer export standards (i.e. by object category) and not by material. Materials are in ...

The only easy and sane path right now is to export your Revit models to FBX, and then import those models into MAX.

Once you're in MAX you can then export to whatever you want to.

FBX exporting in Revit is seriously broken and ONLY works with MAX. Even Autodesk's own converter won't work 100% of ...