JDHill wrote:Thanks Richard, I have a clearer picture of what you want now. Still, this solution strikes me more as a hack -- I'd prefer to fix/implement things where they properly belong, and in this case, I do think that means that it should be addressed in maxwell.exe itself.
To that effect, I have put in a request that maxwell.exe would be able to automatically remember the state of your multilight sliders (when possible, but not failing when impossible) between rendering sessions without you needing to manually load emixer files.
Mate I agree it is a bit of a hack but a bloody useful one!
I also agree that there are some fundamental issues with M.exe in regards to emixer files. If one does rely on the ML feature to set lighting levels and I'd say that may be most users (heck that is what the ML feature is for), when working in Studio the inability to load a resident emixer file means that testing in the preview window is at times pointless. In fact I probably do most tests from studio as exports to MXCL rather than in preview for just this reason! If you dig through the main forum wish list you'll find this somewhere posted long ago requesting this feature.
To be honest this is part of my driver for such a hack, it possibly generates biggest dividends when actually working in studio as the scene has as close as possible correct lighting levels and enables "in studio" previews to have some worth.
I would still say though yep agreed as hack it does present some considerable options for improving workflow straight from the box in so many ways and as it has been a long running wish of M.exe to accommodate this nothing much has happened there todate so could still be some time off being an implemented feature even though almost a necessity.