MtI 2.x beta 2

[Lemo]

Haha I should have saved the image instead of a direct link :p
Anyway that was not such a bad idea after all...I mean a shorter name could be a step closer to user-friendliness.
Check the difference between complex "developer" language and simple version:

• -MtI_2.x_beta_3
  -Mayigo 0.2.3

Could also work with something else:
-Mindigo (Cindigo-like)
-Mingo (chinese style?)
-Mayo ('nnaise?) <- to go with some Sketchup

[Soup]

I like Mayo

[CTZn]

I got your point about versioning Lemo. I finally opted for a scheme similar to Indigo's early betas. I'd rather not change that again though, for the sake of consistency.

$oup, how about calling MtI MtI, to start with ? Just like my nickname: Cee-Tee-Zen

No really there's no hurry for a sexy name before a sexy exporter. My two cents.

[CTZn]

So, where are we... could one work the previous versions out, or ?

Right now I've got MtI to find and name objects properly, however that's still merely tested.

Do you prefer a fast and wild update or a later, tamed one (by the next week) ?

[CTZn]

Update within the next 24h, sorry for the hold up so far.

[CTZn]

round the clock.

Fixes.

[Lemo]

Source script > mti_installation.mel

Code: Select all

sourced mti_CB.mel
sourced mti_DG.mel
sourced mti_EDI.mel
sourced mti_EM.mel
// Error: Cannot find procedure "mti_filters". // 

C'est grave doc?

[CTZn]

thanks for the fast testing Lemo, up'ed.

[Lemo]

Yay files are now named after the scene

So when do you plan have that viewport feedback for the Indigo Shader?
I mean it's kinda depressing to work with a black shadow

[CTZn]

I'm much concerned by this aspect but that won't happen before 6 months at least for the indigoShader. Meanwhile I will be expanding the support for Maya shaders and possibly other renderers, bit by bit. That will reduce the impact of that black shading in viewport.

Support for display layers is coming, should have been there already.

I'll post a roadmap for the beta 3 and create a requests thread.

[Lemo]

Okay I guess I'll go for Maya shaders then.
I thought it'd be better to use the indigoShader, but apparently not
In the end what are the differences between your modified mayaShader and your indigoShader?
Also, is it possible already to create a glass material with a phong ?

[CTZn]

Glass and glossy glass are provided only by the indigoShader at this time. For other materials I always use Maya's lambert and phong, and layeredShaders.

Again I am much willing to improve this aspect of MtI and we will discuss the ways together soon. But more than concerned, I am worried about eventual show-stoppers. Even more since no images are posted. It's not a blame but a matter of concern for me as an exporter writer

As long as there is no bug-fixing required I am willing to develop aspects of interest for users. Only users will declare MtI stable.

Update:

- display layers support for geometries
- sphere primitives

Sphere primitives are nurbs spheres with just a makeNurbsSphere as history (the default).
Sphere primitives in Indigo do not deform and can not be scaled non-uniformly, nor displaced. They render faster than polygon spheres and with a smaller memory footprint.

Nurbs surfaces will be supported soon through render tesselation. This will come with their currently lacking UI.

[Lemo]

wow nurbs

[CTZn]

Nothing big, it may just prevent yourself to do the conversion to polys; you may still have to tweak the tesselation as required (maybe some parameters will be forced). The resulting meshes will support subdivisions at some point if not from scratch.

Fixed the issue you reported last. One less show-stopper, thanks.

Keep them coming Everyone, show me your typos and say hi !

[Soup]

I assign a blinn to an object, select the object with the Indigo palette open and get this error:

Code: Select all

// Warning: Object type is not managed // 
// Error: No object matches name: blinn1.emt //