mti rev 8 17 oct 2007
mti rev 8 17 oct 2007
this is the current exporter mti rev8 for maya 8.5 and indigo 09t6.
also compatible with maya 2008 and indigo 09t8.
please report bugs here.
(this thread exists mostly to test new SVN development and release processes)
also compatible with maya 2008 and indigo 09t8.
please report bugs here.
(this thread exists mostly to test new SVN development and release processes)
- Attachments
-
- mti-svn-rev8-20071017.zip
- (231.58 KiB) Downloaded 306 times
i'm pretty sure that all the file times are preserved, however I have since edited (almost) every file in the SVN (currently rev 11).
I have also moved most of the .txt infos into a single readme.txt in the root and added a TODO.txt
https://svn.hamsterfight.co.uk/listing. ... h=%2F&sc=0
Am I right in thinking that either some scripts in their entirety are redundant, or at least large parts of them are?
Also, there seems to be major inconsistancies between the export's menu commands and the buttons.
I'm sure there's lots more still to report - i need to get using it for a bit.
The easiest way to get into SVN I think is to grab the TortioseSVN client for windows. ( http://tortoisesvn.net/downloads )
then, in explorer, create a new folder where you want to store the mti development files, right click and do a checkout of
https://svn.hamsterfight.co.uk/svn-mti
and hey presto! you'll have got a local copy of the current rev in just 2 clicks.
later you can save your changes ("commit") to the server by right clicking the folder and choosing Commit. (you'll need a username + password to do this).
I urge all current mti developers to PM me for passwords.
I have also moved most of the .txt infos into a single readme.txt in the root and added a TODO.txt
https://svn.hamsterfight.co.uk/listing. ... h=%2F&sc=0
Am I right in thinking that either some scripts in their entirety are redundant, or at least large parts of them are?
Also, there seems to be major inconsistancies between the export's menu commands and the buttons.
I'm sure there's lots more still to report - i need to get using it for a bit.
The easiest way to get into SVN I think is to grab the TortioseSVN client for windows. ( http://tortoisesvn.net/downloads )
then, in explorer, create a new folder where you want to store the mti development files, right click and do a checkout of
https://svn.hamsterfight.co.uk/svn-mti
and hey presto! you'll have got a local copy of the current rev in just 2 clicks.
later you can save your changes ("commit") to the server by right clicking the folder and choosing Commit. (you'll need a username + password to do this).
I urge all current mti developers to PM me for passwords.
ok, i got a meshlight to work as you described in the other thread.
you were right, this isn't a bug, but a consequence of a lack of decent documentation for the exporter.
are we restricted to using blackbody emitters in this manner?
is there or could we implement peak / RGB / uniform?
what about efficacy scaling?
you were right, this isn't a bug, but a consequence of a lack of decent documentation for the exporter.
are we restricted to using blackbody emitters in this manner?
is there or could we implement peak / RGB / uniform?
what about efficacy scaling?
I'm absolutely sure that all files have october 17 2007, 14:47 time stamp 

For meshlights, yes only blackbody is implemented for now, and that new way is the only way before editing the xml itself. Of course one can implement others descriptions !
Thanks for the lil intro to svn, describing the workflow a bit was very instructive on the ease of use of the final stuff. BTW I believe you should ask Ono for a svn, I mean I believe he already set one up ! I'm referring to this post.
Can't answer this one.Am I right in thinking that either some scripts in their entirety are redundant, or at least large parts of them are?
I didn't notice that, I do really not use icones a lot...Also, there seems to be major inconsistancies between the export's menu commands and the buttons.
Sure isI'm sure there's lots more still to report
For meshlights, yes only blackbody is implemented for now, and that new way is the only way before editing the xml itself. Of course one can implement others descriptions !
Thanks for the lil intro to svn, describing the workflow a bit was very instructive on the ease of use of the final stuff. BTW I believe you should ask Ono for a svn, I mean I believe he already set one up ! I'm referring to this post.
obsolete asset
Who is online
Users browsing this forum: No registered users and 31 guests
