MtI 3.4

Announcements, requests and support regarding the MAYA exporter
User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

MtI 3.4

Post by CTZn » Tue Dec 11, 2012 10:25 pm

This is a beta release.

Installation:
- Extract the archive content on disk.
- In Maya, open the Script Editor window.
- Source mti_installation.mel.
- Follow instructions.

In order to use Indigo during a Maya session, the exporter must be initialised once by clicking any Indigo shelf button. That will make Indigo available among other renderers.

Please post bug reports and questions here.

This release adds a partial renderer integration, tangent space normal maps support, orthographic cameras, clipping planes, section planes (through the MtI menu), params and shared params, MEL in ISL, easy per camera environments and more bugfixes than I could record.

I care about user inputs a lot, I'm too close not to need feedback thanks !

Changes:

3.4.17 b
  • fixes the showstopper error introduced in 3.4.17 when using environment
    fixes medium related tag issues ("Scene parsing error: Found unexpected element [...]")
    'mti_settings.mti_renderableCamera' is being obsolete, getCurrentCamera() is prevailing
    • Please let me know of camera detection issues with MtI.
3.4.17

Editor:
  • f-stop is not showing up anymore for orthographic cameras.
Export:
  • Fixed bug preventing the actual environment material to be used
    fixed error "mti_GEN_param: no such case: 'bool'."
    suppressed obsolete(?) tag 'scattering_coefficient_spectrum'.
    fixed error with Indigo reporting a blend texture out of bounds
General:
  • removed debug lines
Integration:
  • MtI will initialize for a new scene if Indigo is choosed as the current renderer and a render is started, instead of requiring to click on a shelf icon.
    • This eventuality becomes possible if MtI was initialized during the same Maya session for a previous scene.

Shelf:
  • Clicking the Sun shelf icon will select the directional light if it existed. This is a restoration of the primary behavior.

3.4.16

+ fixed: attributes from a mesh connected to a nurbsTesselate would reset.
+ added array attribute 'textInput' to indigoText
  • connect the 'text' attribute of an indigoText to the textInput of another to append ISL code (multiple/branched inputs supported).
+ non-bump, frozen textures were exported with gain, offset and gamma at zero
+ fixed collapsed layout in editor
+ install: added obsolete file remover at some point (dict)
+ animated parent
+ orthographic cameras
+ camera clip planes with culling option
+ section plane node with culling option
+ changed launch method on Windows (more reliable ?, cmd, render and hypershade windows visible) due to a file IO bug. Temporary.
+ raw MEL output support in ISL code.
  • colour must now be composited from the relevant float attributes (outColorR, incandescenceB etc).
+ added suport for ISL params, including shared params and their UI.
  • Params in Maya are custom attributes added to an IndigoText wich long names start with "param".
    Shared params are params added to a supported material.
    Params can be managed through the "Attributes" menu
    of the Attribute Editor or the "Param" menu of the Indigo Editor.
+ per object/camera keyframes setting
+ per camera environment, one switch and one connectable RGB slot. Hassle free.
+ tangent space maps.
+ MtI now registers Indigo as a renderer.
  • Now uses native rendering commands, icons and windows, including Render Globals and region rendering.
    The Indigo Settings window is gone, just like the render icon from the Indigo shelf.
    Note that rendering still happens in the Indigo GUI or console, integration is limited to ergonomics.
+ Many bugfixes.
+ Indigo Editor is now always resizeable.

PDF documentation beta (3.4.16).

mti_3.4.17 b - current
Attachments
mti_3.4.17.zip
busted release - do not download for regular usage.
(281.26 KiB) Downloaded 388 times
mti_3.4.16.zip
deprecated
(157.63 KiB) Downloaded 645 times
obsolete asset

User avatar
Zom-B
1st Place 100
Posts: 4700
Joined: Tue Jul 04, 2006 4:18 pm
Location: ´'`\_(ò_Ó)_/´'`
Contact:

Re: MtI 3.4

Post by Zom-B » Tue Dec 11, 2012 11:48 pm

looks like a neat list of changes and features, good work mate!
polygonmanufaktur.de

User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

Re: MtI 3.4

Post by CTZn » Wed Dec 12, 2012 5:32 am

I took my sweet time :) You are welcome to help me spotting 3.4 features I may have missed !

Attached a view of the Indigo Editor for an indigoText node, connected to the displacement slot of a shading group.

The code features one param and two MEL inclusions. As a matter of fact that shader is animated ;)

The param menu has four items to create common (non-vec3) params, create color params, edit and delete params.

edit: params themselves can be animated/scripted/connected as per normal node attributes.
Attachments
Indigo_Editor_indigoText.jpg
obsolete asset

User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

Re: MtI 3.4

Post by CTZn » Wed Dec 12, 2012 6:06 am

And for the shakes a better performing version of the shader, assigning the value directly to an ISL variable:

Code: Select all

def eval() real:
let
	time = `currentTime -query`
in
	pow(
		fbm(
			vec2(
				texi() + time / 100.0,
				texj() + time / 100.0
			),
			31
		),
		6.0
	) * 10000.0 / paramTest()
Any MEL code that Maya can evaluate can be inserted into the ISL code between two ``. Beware not to hit strings or arrays !
obsolete asset

User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

Re: MtI 3.4

Post by CTZn » Wed Dec 12, 2012 6:28 am

The new per camera environment tab.

Connect an indigoSpectrum, emissive material or indigoText as background material, or use plain RGB. A supercolor is mandatory here then, around the million.

Environment maps (latlong EXR) must be applied to the emission (incandescence) of an emitting material.

At some point I'll add a dropdown list of the directional lights available to allow several simultaneous times of the day in the scene. The first available directional light is used, a default light is created eventually.
Attachments
Indigo_Editor_camera.jpg
obsolete asset

User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

Re: MtI 3.4

Post by CTZn » Wed Dec 19, 2012 10:03 pm

Attached an update to the PDF documentation wich was missing from the release.
Attachments
mti user documentation.pdf
This documentation is at a beta stage and is therefore lacking and subject to changes.
(165.79 KiB) Downloaded 500 times
obsolete asset

ior
Posts: 166
Joined: Tue Aug 24, 2010 11:47 am

Re: MtI 3.4

Post by ior » Wed Jan 09, 2013 1:59 pm

CTZn wrote:+ camera clip planes with culling option
There are no options on indigo editor.
Do I change the near far clip in the camera shape attributes?
What about the culling option?
CTZn wrote:+ section plane node with culling option
Where can I find the node? I thought it would appear in the hypershade.
Last edited by ior on Wed Jan 09, 2013 2:11 pm, edited 1 time in total.

ior
Posts: 166
Joined: Tue Aug 24, 2010 11:47 am

Re: MtI 3.4

Post by ior » Wed Jan 09, 2013 2:10 pm

Using redo previous render, the current render camera is not assumed if rendered in indigo.

User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

Re: MtI 3.4

Post by CTZn » Wed Jan 09, 2013 6:53 pm

Hi ior
ior wrote:
CTZn wrote:+ camera clip planes with culling option
There are no options on indigo editor.
Do I change the near far clip in the camera shape attributes?
What about the culling option?
The camera shape near and far clip distances are used if Auto Render Clip Plane is checked off. This will forcibly create two camera clipping planes.
ior wrote:
CTZn wrote:+ section plane node with culling option
Where can I find the node? I thought it would appear in the hypershade.
It is currently available in the MtI menu Create Node > Section Plane. You can make a shelf button for it with the following command:

Code: Select all

mti_CHK; createNode indigoSectionPlane;
obsolete asset

User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

Re: MtI 3.4

Post by CTZn » Sat Jan 12, 2013 4:55 am

Updated to MtI 3.4.17

Editor:
  • f-stop is not showing up anymore for orthographic cameras.
Export:
  • Fixed bug preventing the actual environment material to be used
    fixed error "mti_GEN_param: no such case: 'bool'."
    suppressed obsolete(?) tag 'scattering_coefficient_spectrum'.
    fixed error with Indigo reporting a blend texture out of bounds
General:
  • removed debug lines
Integration:
  • MtI will initialize for a new scene if Indigo is choosed as the current renderer and a render is started, instead of requiring to click on a shelf icon.
    • This eventuality becomes possible if MtI was initialized during the same Maya session for a previous scene.

Shelf:
  • Clicking the Sun shelf icon will select the directional light if it existed. This is a restoration of the primary behavior.
obsolete asset

User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

Re: MtI 3.4

Post by CTZn » Sun Jan 13, 2013 3:15 am

ior wrote:Using redo previous render, the current render camera is not assumed if rendered in indigo.
I could not reproduce this (redo previous render always worked for me), was it fixed in MtI 3.4.17 by any chance ?
obsolete asset

ior
Posts: 166
Joined: Tue Aug 24, 2010 11:47 am

Re: MtI 3.4

Post by ior » Tue Jan 15, 2013 3:05 pm

Hi CTZn.
CTZn wrote:I could not reproduce this (redo previous render always worked for me), was it fixed in MtI 3.4.17 by any chance ?
It got worse.
Now I cannot render at all. Before, if I rendered the default pespShape camera it make this error:

Code: Select all

> mti_CHK_export:
	"C:/Users/me/Documents/maya/projects/default/"
// Error: file: C:/Users/me/Documents/maya/scripts/mti_GEN_.mel line 112: No valid objects supplied to 'xform' command. // 
updateRendererUI;
and the mouse arrow turned in to a thinking circle, but if after this I choose another camera to render it would restore normal behavior and the render would be fine.

But now every camera I chose to render turns the mouse arrow into thinking circle end I have to close maya to solve this. It gives this error:

Code: Select all

> mti_CHK_export:
	"C:/Users/me/Documents/maya/projects/default/"
// Error: file: C:/Users/me/Documents/maya/scripts/mti_GEN_.mel line 556: 
$envNode = ,
$black = 1,
$mapped = 0,
$makeDummyMat = 0 // 
updateRendererUI;

ior
Posts: 166
Joined: Tue Aug 24, 2010 11:47 am

Re: MtI 3.4

Post by ior » Tue Jan 15, 2013 4:03 pm

how about spherical camera?

User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

Re: MtI 3.4

Post by CTZn » Tue Jan 15, 2013 4:20 pm

Acknowledged one inconsistency and one stupid mistake, mti 3.4.17 is busted. I'm not proud I called it a hotfix.

Many thanks for the reports ior.

The thinking icon over a frozen viewport is fixed by clicking one shelf button or by running the following command:

Code: Select all

mti_CHK;
[/size]

Sadly this doesn't fix bugs :P I'll do this.
obsolete asset

User avatar
CTZn
Posts: 7240
Joined: Thu Nov 16, 2006 4:34 pm
Location: Paris, France

Re: MtI 3.4

Post by CTZn » Tue Jan 15, 2013 4:32 pm

ior wrote:But now every camera I chose to render turns the mouse arrow into thinking circle end I have to close maya to solve this. It gives this error:

Code: Select all

> mti_CHK_export:
	"C:/Users/me/Documents/maya/projects/default/"
// Error: file: C:/Users/me/Documents/maya/scripts/mti_GEN_.mel line 556: 
$envNode = ,
$black = 1,
$mapped = 0,
$makeDummyMat = 0 // 
updateRendererUI;
On a side note, if you feel so you can fix my stupid mistake by deleting simply the error statement over four lines. It was really meant to interrupt the code because I was too lazy to seek the data in a log, and errors are never considered by my code cleaning snippet :oops: Still, that's weird.

Hope that helps meanwhile.
obsolete asset

Post Reply
49 posts

Who is online

Users browsing this forum: Majestic-12 [Bot] and 25 guests