Karba wrote:Thank you for your feedbacks.
We will fix things as soon as we can. Jimstar will help me soon.
You know, I've been in pursuit of maxscript - octane compability for ages.
I would like to draw you and all max members attention to these linkshttp://patrick.reformstudios.com/2015/0 ... ht-lister/
andhttp://patrick.reformstudios.com/2015/0 ... y-plugins/
These links will give you good understanding of the script is being written.
It's a script to manage Scene contents. Which will help to manage a lot of lights at one go, manage material properties (eg. materials with emmissions) in a refined menu. The script is being written by a great guy named Patrick Macdonald His web page
As he claimed that script would automatically support any 3rd-party plugins you used.
So, I've contacted him and signed up for a beta asked if he could test his unreleased software with octane for max.He said,
"Ok, I tried out Octane render, and your suspicions proved correct, it isn't exposed in the usual way to maxscript like other plugins. "He added,
"I also notice that Colin Senner of "Relink Bitmaps" fame has also had similar problems with Octane and hadn't made much progress when making advances to the developers. (http://www.colinsenner.com/scripts/reli ... ent-page-2
) Without going through the same efforts as Colin I don't know if things have changed, but in the meantime I suggest you contact them yourself and ask them to expose all the renderer and material/light/camera parameters to maxscript to allow 3rd-party tools like Mission Control and Relink Bitmaps easier access to their plugins' classes.
Sorry I can't be more help at this stage, but I'm busy trying to get the core code of Mission Control ready for release. Once I have more time I'll be able to get in touch with Octane''s developers and hopefully find a way to integrate the plugin with the tool."And I asked
Would you tell me what I should I tell the devs to correct or improve? regarding maxscript compatibility.. He said,
To get you started, my first discovery is that when you attempt to access the renderer parameters, the plugin returns nothing. So, to confirm this make Octane your current renderer and then try these two lines. currRenderer= renderers.current
Do this for both Scanline renderer or Vray and lastly for Octane to see the difference.
As far as I can see Octane for max has one major fault and this is it. If you work on it, and let maxscript object classes, object properties, material properties, render setting properties, lights, texture properties exposed to maxscript than we can use good scripts out that what would greatly change the way we work.
If Karba or Jimstar would I like to get in touch with Patrick I can send you his email.
He is not a friend of mine and I didn't get his word for it but I genuinely think he might help you in conjunction with compatibility with this script.
Or at least tell me whether or not you'll add maxscript support at all.