MayaToIndigo Wishlist
That's funny, I told you they were to be used in conjunction, both are no competitors ! mtiEdi reads values from shaders in order to provide easier simpler access to their attributes, and this includes indigoShaders !
It's not an alternative but a companion, or if you prefer it only replaces the UI not the node ! But it is true that as a consequence, many users may not use the AE interface just because there will be no need to scroll the panel to access all requested attributes (including indigoShader.material), and it refreshes quickly.
Have I made myself clear, dear dev in chief ?
EDIT: I've remembered the right term: it's only a front-end.
It's not an alternative but a companion, or if you prefer it only replaces the UI not the node ! But it is true that as a consequence, many users may not use the AE interface just because there will be no need to scroll the panel to access all requested attributes (including indigoShader.material), and it refreshes quickly.
Have I made myself clear, dear dev in chief ?
EDIT: I've remembered the right term: it's only a front-end.
obsolete asset
Good point vux
There is plenty to do in order to make MtI more user friendly. Shamefully I'm too much of a dabbler to find the motivation when I should.
By now I'm streamlining my workflow with displacement from Maya to Indigo. I felt that many small vids would be better than one big and messy (check it in the Maya and displacement thread). If there is a topic in Maya or MtI you want to be explained better please ask.
Cheers !
There is plenty to do in order to make MtI more user friendly. Shamefully I'm too much of a dabbler to find the motivation when I should.
By now I'm streamlining my workflow with displacement from Maya to Indigo. I felt that many small vids would be better than one big and messy (check it in the Maya and displacement thread). If there is a topic in Maya or MtI you want to be explained better please ask.
Cheers !
obsolete asset
vux
thanks, that's useful info.
What i can probably do is remove the region coords from mti_settings and read the values straight from defaultRednerGlobals on export.
(and perhaps have controls on the GUI linked to these vars for convenience - but it's not possible to connect the scriptnode vars directly to defaultRenderGlobals)
thanks, that's useful info.
What i can probably do is remove the region coords from mti_settings and read the values straight from defaultRednerGlobals on export.
(and perhaps have controls on the GUI linked to these vars for convenience - but it's not possible to connect the scriptnode vars directly to defaultRenderGlobals)
No, with MtI you can export materials as an IGM file that's all*.
Indigo has the ability to unpack packed files in a specified output folder, see the Command line parameter Reference in documentation pdf. Conversely Indigo can pack a scene with dispatched data into one packed file. For now it's none of MtI features, but that is to put on a todo list for when former progresses are validated (and hem, produced actually).
*Correction: each material in a separate igm file.
Indigo has the ability to unpack packed files in a specified output folder, see the Command line parameter Reference in documentation pdf. Conversely Indigo can pack a scene with dispatched data into one packed file. For now it's none of MtI features, but that is to put on a todo list for when former progresses are validated (and hem, produced actually).
*Correction: each material in a separate igm file.
Re: MayaToIndigo Wishlist
Is possible support Maya Background shader, and nurbs as in other renderer via converting nurbs to polys?
Thanks.
Bretik
Thanks.
Bretik
Who is online
Users browsing this forum: No registered users and 45 guests