MtI rev 32 29 oct 2007
MtI rev 32 29 oct 2007
I think that now we've got pretty good functionality on MtISimple, this is worth a release.
The only significant changes are since rev28:
32. doug
updates:
changed default render settings to match default inifile.txt
bug fixes:
substitute | for - in .obj filenames
threads: set to 0 for auto, else auto_choose_num_threads is overridden.
known issues:
/BELOWNORMAL priority not working
31. doug
removed some extraneous files.
30. bkircher
put the whole shader building into mti_ExportModuleCamera.mel
added phongE as "Notes to Shader Material": The notes of a phongE are
translated as a material, if they start with the string:
<!-- mti_UseCommentAsMaterial -->
The key words mtiKey_ShaderName, mtiKey_GlobalGamma, mtiKey_Exponent, mtiKey_ior can be inserted and
will be exchanged with the appropriate global or phongE value.
Added more material presets.
29. bkircher
added custom settings: export visible only (default); save local to use Alternative directory;
Alternative Directory string; append local to avoid overwriting existing .obj-files.
Minor Bugfixings
28. bkircher
mti_Gen:
- wrong } at end of material-export code
- wrong use of "$skipstandard_phong", could skip writing Phong-shaders otherwise
mti_Main:
- added 35mm button to set film-back to Maya-"35 full aperture"-equivalent
- fixed last button
added 35mm icon
added ConvertAllToPoly.mel back in.
The only significant changes are since rev28:
32. doug
updates:
changed default render settings to match default inifile.txt
bug fixes:
substitute | for - in .obj filenames
threads: set to 0 for auto, else auto_choose_num_threads is overridden.
known issues:
/BELOWNORMAL priority not working
31. doug
removed some extraneous files.
30. bkircher
put the whole shader building into mti_ExportModuleCamera.mel
added phongE as "Notes to Shader Material": The notes of a phongE are
translated as a material, if they start with the string:
<!-- mti_UseCommentAsMaterial -->
The key words mtiKey_ShaderName, mtiKey_GlobalGamma, mtiKey_Exponent, mtiKey_ior can be inserted and
will be exchanged with the appropriate global or phongE value.
Added more material presets.
29. bkircher
added custom settings: export visible only (default); save local to use Alternative directory;
Alternative Directory string; append local to avoid overwriting existing .obj-files.
Minor Bugfixings
28. bkircher
mti_Gen:
- wrong } at end of material-export code
- wrong use of "$skipstandard_phong", could skip writing Phong-shaders otherwise
mti_Main:
- added 35mm button to set film-back to Maya-"35 full aperture"-equivalent
- fixed last button
added 35mm icon
added ConvertAllToPoly.mel back in.
- Attachments
-
- mti-svn-rev32-20071029.zip
- (70.05 KiB) Downloaded 272 times
a note for devs:
I've created a tags folder in the SVN which holds a snapshot of the releases.
For further development, you only need to get updates on the main /trunk/ folder, and commit on the same.
You don't need to keep downloading/checking out the /tags/ folder and it's contents - it's not going to change.
I've created a tags folder in the SVN which holds a snapshot of the releases.
For further development, you only need to get updates on the main /trunk/ folder, and commit on the same.
You don't need to keep downloading/checking out the /tags/ folder and it's contents - it's not going to change.
carry on as you were, i can re-do my mods, most (erm, all) of which were fairly trivial.
this raises a good point though.
I think we should do as I think you mentioned last week or so - start a new thread when you start a phase of mods, stating which revision you are going from, so that others don't forge ahead with other things in the mean time UNLESS someone is willing to re-implement their work once a phase is completed (as I am, seeing as it was a few easy tweaks).
I'll leave it to you to announce your work
this raises a good point though.
I think we should do as I think you mentioned last week or so - start a new thread when you start a phase of mods, stating which revision you are going from, so that others don't forge ahead with other things in the mean time UNLESS someone is willing to re-implement their work once a phase is completed (as I am, seeing as it was a few easy tweaks).
I'll leave it to you to announce your work
Bah I'll do that again, it's no big deal as well. I should have commited yesterday...
May I ask devs to comment the code more and document new attributes they added, it's no shame coz helps a great deal, not to mention time saving for the project and headache preserving for colleagues.
Thx !
Currently adding sun and makeInstances.
May I ask devs to comment the code more and document new attributes they added, it's no shame coz helps a great deal, not to mention time saving for the project and headache preserving for colleagues.
Thx !
Currently adding sun and makeInstances.
obsolete asset
no locks shown here:
i've done a global "remove locks" anyway.
can you try and get a lock yourself, and use the "steal locks" function?
Code: Select all
doug@server1:/mnt/hda/svn-repos$ sudo svnadmin lslocks mti
doug@server1:/mnt/hda/svn-repos$
Code: Select all
doug@server1:/mnt/hda/svn-repos$ sudo svnadmin rmlocks mti
doug@server1:/mnt/hda/svn-repos$
I could get a lock on mti_Main but still not commit:
Anyway here are the files:
After cleanup same happens.Error: Working copy 'C:\work\dev\MtI\trunk' locked
Error: Please execute the "Cleanup" command.
Anyway here are the files:
- Attachments
-
- from R33_MayaToIndigoSimple_CTZn.zip
- - a short readme
- mti_Main
- a pre-icon for mti_makeInstances - (33.44 KiB) Downloaded 297 times
obsolete asset
REV 35:
mti_Main:
- Instancing now adds mti_UseExactName to locators. Still dunno what the initial value should be nor what it does
- updated todo
Ok after destroying the svn dir and creation of a new one everything looks fine !
The question now is: Will we create a thread for each rev or update the first post of a dedicated one ?
mti_Main:
- Instancing now adds mti_UseExactName to locators. Still dunno what the initial value should be nor what it does
- updated todo
Ok after destroying the svn dir and creation of a new one everything looks fine !
The question now is: Will we create a thread for each rev or update the first post of a dedicated one ?
obsolete asset
TODO/BUGS:
* change min. blackbody temp to something lower. i think 6500k is too high seeing as daylight is 5500k and some indancescent lights are even lower than that.
it's fair enough to tell the user that that value needs to be "high" but perhaps a 3000k lower limit is better?
http://en.wikipedia.org/wiki/Color_temp ... t_lighting
* default reinhard settings are not suitable. post-scale is usually always about 1. 2 i think is too high.
* sun may not be working - i'll check in more detail later.
* change min. blackbody temp to something lower. i think 6500k is too high seeing as daylight is 5500k and some indancescent lights are even lower than that.
it's fair enough to tell the user that that value needs to be "high" but perhaps a 3000k lower limit is better?
http://en.wikipedia.org/wiki/Color_temp ... t_lighting
* default reinhard settings are not suitable. post-scale is usually always about 1. 2 i think is too high.
* sun may not be working - i'll check in more detail later.
Who is online
Users browsing this forum: No registered users and 22 guests