Got more bugs after some experiments:
1. Upon opening maya scene with some octane materials in it(like 10 or so) and with hypershade opened, maya start to refresh material swatches, and crashes after maybe 5-6 materials. No any error messages, just a sound and probably some invisible modal window with error message(because maya ui becomes unresponsive).
Temporary fix is to open hypershade _before_ the scene, minimize it, load scene, hit render button, then cancel, it's probably initializes something inside and then hypershade can be used again.
Crash dump here:
https://dl.dropboxusercontent.com/u/142 ... 12.1323.7z
2. In the same scene there's some confusion with materials happening _sometimes_: on the first render right after scene was opened, i had glass and ceiling materials swapped few times at least. After hitting render button, cancelling, and rendering again everything becomes ok.
Make unique names is on in rglobals.
3. Is it possible to assign proper names to SGs/shaders/all other nodes when they're being pulled from LiveDB? I mean when user hitting "create node" for, say, "abonoz with lake" shader, one expecting some reasonable name instead of "octaneGlossyMaterial1SG", for example "abonoz_with_lake1_SG", "aboznoz_with_lake1_mat", "aboznoz_with_lake1_imagetex1".
4. I don't know, maybe someone already asked about it: are there any way to achieve the same effect responses have in maya camera in photoshop/afterfx? Maybe some curves/macros/etc? Any information how to reproduce the effect? Sometimes it's useful to have raw hdr and perform CC in another package.
5. At least twice when i tried to render from command line with -v 1 option, Maya stopped after loading scene, kept using like 30% of all cores and did nothing else until i Ctrl-C it. Not sure how to debug this.
6. And well, since i've written that wall of text, one more thing: i really think that render globals is not a proper place for LiveDB. It's small, it's not created to be a material library. Some separate hypershade-like window would serve for that purpose much better. Maybe you could use visor tab for that(which would be logically correct, and i think have all the required ui elements to be a mat library).
Upd:
7. At least one case where all the octaneLightTransforms decided to jump to the center of scene, keeping their pivots at their designated locations.
Upd2: it's just happened again:
Illustration:
Thanks.
PS: Maya 2014 x64 win64.
