ZLOy wrote:I have a few suggestions for further integration in Maya, if it can be supported by Octane:
- Save presets for the octane materials and cameras.. it often used for saving time - when you need create a few same matirials and apply same settings
Now its nothing happens when I use "create preset' and "save preset"
Maya can't do this simple thing - save presets of
complex attributes.
No matter, is it "
in place" complex data value, or attribute is connected to another node. Only simple values: string and scalar.
It is very simple to do, I could rewrite all these generic Maya scripts to fulfill that - but it will be the ugly hack, as after Octane installing it may vanish the same ugly hacks in the same script of another plugins, or be vanished later by the same ugly hacks of another new plugins just installed after Octane... :puke: Not my way.
I will think about it later, perhaps I will be able to find some more elegant solution... Or Maya will finally make it the right way in its preset processing script (with note in caption of Maya 2013 "
Creation Date: 2001")...
ZLOy wrote:- assign texture node to material by drag`n`drop tetures nodes from Hypershader to the checker icon in attribute editor
The same thing.
Maya does not catch drag events of shader nodes (e.g. from Hypershader) to Maya's "user data" UI controls. It's weird... But we can't use simple attribute connection controls (which can catch these events) in these places, as the users of this plugin asked me to make the "
default in place editable values" of
complex attributes. E.g. Octane Texture pin
must be connected to some Octane Texture Node, and if you do not have the "default complex value" - you must create all texture nodes after creating the material node, and all these different nodes will be connected to all complex attributes of material (and other nodes to all complex attributes of all these nodes, etc...). To make the live easier, the "in place values" were made - you are not forced to have these explicit nodes connected, instead you have the implicit
complex values set to each complex attribute directly, and the Maya's
user data UI control is placed above to give you the ability to edit the values of this complex attribute.
So, as a final of this long explanation - Maya does not deliver the drag events to its own user data controls. Weird issue.
So, for us - or one, or the other...
Fix it back? 