- Thu Sep 16, 2010 2:05 am
#330625
I think that's probably the wrong place for this kind of functionality, Richard. An emitter material in the plugin should feel like a real thing, with watts/efficacy -- I kept the UI using these for real-world familiarity.
I think that a more proper approach to your idea would be for you to be able to export the multilight state of a scene (not emixer, just the current values of the multilight sliders) from maxwell.exe, and then to read it back in automatically next time the scene is rendered. I'd just have it work automatically, where the multilight state was saved into a very simple text file, say with an .ml extension -- when maxwell.exe started rendering, it would look for an .ml file of the same name as the .mxs, and apply the values it found inside, where the emitter names matched up.
Next Limit Team