Maya 8.5??
-
revenger222
- Posts: 3
- Joined: Thu Jun 14, 2007 11:33 am
Maya 8.5??
is there an exporter for maya to indigo for maya 8.5? latest ive been able to find is 8.0. Please anyone, tell me if there is, where can i get it, and if its not out, how much longer to wait for one? thanks 
- ThatDude33
- Posts: 216
- Joined: Wed Jul 05, 2006 1:26 pm
- Contact:
We (me, arneoog, yourdaftpunk, Benedikt Kircher, and (sorta)ctzn) stopped working on it a while ago. I may or may not decide to start working on this again.. depending on my disposition.
Last edited by ThatDude33 on Sun Jun 17, 2007 11:33 am, edited 1 time in total.
Matt B. >>Maya To Indigo<<


Benedikt Kircher is to credit too, she did quite some work. Her exporter should work with Maya 8.5 provided that you don't use IME (wich is not develloped anymore, AFAIK) but obj export instead; search amongst the previous topics revenger222, you'll find the download, and welcome !
Edit: Here's the last link:
http://www2.indigorenderer.com/joomla/f ... php?id=350
Edit: Here's the last link:
http://www2.indigorenderer.com/joomla/f ... php?id=350
obsolete asset
- ThatDude33
- Posts: 216
- Joined: Wed Jul 05, 2006 1:26 pm
- Contact:
So sorry... I've been gonefor a long time and I feel bad that I missed that. I'm gonna edit it.CTZn wrote:Benedikt Kircher is to credit too, she did quite some work. Her exporter should work with Maya 8.5 provided that you don't use IME (wich is not develloped anymore, AFAIK) but obj export instead; search amongst the previous topics revenger222, you'll find the download, and welcome !
Edit: Here's the last link:
http://www2.indigorenderer.com/joomla/f ... php?id=350
Matt B. >>Maya To Indigo<<


No reason to feel bad, you were not there that's it ThatDude 
The last idea on track was to merge bkircher version with your version of MtI, also a SVN repository has been created by Radiance to track down versions and allow developers to work together, I hope it will be used any soon for Maya...
Last version of MtI may work for 0.8, only the normal_smoothing statement has to be added by hand in the XML, IIRC. It also takes profit of Indigo's support for OBJ format by exporting meshes from Maya into separate OBJ files (preserving normals yay), and instancing is supported but I really would like someone to tell me how it works (prefix thingy but wich prefix ?).
"Lazy Development" is ok to me; while no guaranty of a result is expected from anyone I'm still interested into talking of development, in fact I would like a consensus on what is next to do, so in case dev occurs it would go in an accepted way.
Again, glad you're back ThatDude33
Revenger222, I'll do my best to support you on using MtI
The last idea on track was to merge bkircher version with your version of MtI, also a SVN repository has been created by Radiance to track down versions and allow developers to work together, I hope it will be used any soon for Maya...
Last version of MtI may work for 0.8, only the normal_smoothing statement has to be added by hand in the XML, IIRC. It also takes profit of Indigo's support for OBJ format by exporting meshes from Maya into separate OBJ files (preserving normals yay), and instancing is supported but I really would like someone to tell me how it works (prefix thingy but wich prefix ?).
"Lazy Development" is ok to me; while no guaranty of a result is expected from anyone I'm still interested into talking of development, in fact I would like a consensus on what is next to do, so in case dev occurs it would go in an accepted way.
Again, glad you're back ThatDude33
Revenger222, I'll do my best to support you on using MtI
obsolete asset
-
revenger222
- Posts: 3
- Joined: Thu Jun 14, 2007 11:33 am
- ThatDude33
- Posts: 216
- Joined: Wed Jul 05, 2006 1:26 pm
- Contact:
hey guys, instead of arguing that you "might" blablah, why don't you have a look and fix some inconsistencies (and eventually learn from bkircher).
There is no reason to go into an extensive developing activity, the backbone is there already and it needs some fixing and improving. I mean:
Keep it easy, Indigo is continuously in dev so a lazy dev scheme for MtI is ok, just have a quick look from time to time and fix or ehance and then let it alone. If you want to go far, manage your horse
I support the idea of extra attributes for materials rather than an object editor, it's less hassle to implement and more the way Maya works internally.
Yay !
BTW I just tested last version from bkircher with Maya 8.5 and I couldn't get a final working export, fixing multiple obj export is a high priority
Also get used with the SVN repository, ask Ono (or do a search in the forums).
obsolete asset
zefixzeluja, last time i checked there was still a he.Benedikt Kircher is to credit too, she did quite some work.
Great that there is some live in this forum.
Anyway, I would have to check if the last code on this site is the same I use, but I'm quite confident that it works: In fact, I'm right now using it for an interior rendering with Maya 8 and Indigo 8.
You have to clean up the scene, though, avoid duplicate names, maybe check that your geometry is legal for the obj. import part, ungroup your objects, etc., or:
write a fix.
There are some features that were not implemented or only as stubs back then, and still are...
It would probably be fun trying to implement mti with python, in one nice clean file with some helper scripts...
to be continued....
Hey bk, glad to see you here again ! I've been such a loose companion that I thought you'll never come back !
Is ungrouping objects necessary (got lots of groups in scene) ? Are you using multiple obj export or single (one of the two isn't working isn't it ?) ?
Btw can you explain how I can use instancing please ? Enough questions for now
These last days I've done very negligeable improvements to Sun creation, like you cant create two Suns and if you try, the original Sun is selected, and if you check "physical" env and launch export without previously creating a Sun a default one is created at export time instead of dropping an error message, well stupid stuff like that... that's my level at coding actually
next step is to make Sun a directional constrained to the origin of the scene instead of a pointLight so we can preview the direct illumination with precision.
Till recently I thought Extra Attributes or Object Editor where exclusives, but in fact the editor is a GUI for tweaking extra attributes isn't it ?
Cheers, very glad ^^
Is ungrouping objects necessary (got lots of groups in scene) ? Are you using multiple obj export or single (one of the two isn't working isn't it ?) ?
Btw can you explain how I can use instancing please ? Enough questions for now
These last days I've done very negligeable improvements to Sun creation, like you cant create two Suns and if you try, the original Sun is selected, and if you check "physical" env and launch export without previously creating a Sun a default one is created at export time instead of dropping an error message, well stupid stuff like that... that's my level at coding actually
Till recently I thought Extra Attributes or Object Editor where exclusives, but in fact the editor is a GUI for tweaking extra attributes isn't it ?
Cheers, very glad ^^
obsolete asset
Who is online
Users browsing this forum: No registered users and 4 guests

