enjoyMentalRayStringOptions, a UI to easely use MR string options

Become a member of the CGSociety

Connect, Share, and Learn with our Large Growing CG Art Community. It's Free!

THREAD CLOSED
 
Thread Tools Search this Thread Display Modes
  04 April 2011
Smile enjoyMentalRayStringOptions 0.96, a UI to easely use MR string options

Hi all!

I'd just finished the "beta" version of my script to quickly have a way to handle mental ray string options without have to wait too long.



The main goal here is not to provide the best integrated/nice UI but avoid to manage mental ray string options "by hands".

For now, it work for me. Should work for you, but if you have probs, don't hesitate to post errors (prefered with "Show stack trace" and "Line number in errors" options checked )

Put the script in your (for example):

C:\Users\userName\Documents\maya\scripts


To use it, open the script editor, create a new Python tab and just paste:

import enjoyMentalRayStringOptions
enjoyMentalRayStringOptions.Ui().create()


Hope you like!

FG Passes don't seems to work on Maya 2012. Seems to be a bug of MR.

Release Note:
  • 0.98 - Add a lot of new 3.11 string options
  • 0.97 - Add "mila glossy samples" string option in misc
  • 0.96 - Add a lot of new string options
  • 0.95 - Add "light relative scale" string option
  • 0.94 - Many improvments
  • 0.93 - Add finalgather passes.
  • 0.92 - Add iRay string options.
  • 0.91 - Add "samples per object" and "finalgather legacy" options.
  • 0.9 - Original release.

PS: Thanks to Sylvain Berger for his script k_progressiveRendering wich make me start this more general string options manager.
Attached Files
File Type: zip enjoyMentalRayStringOptions.zip (13.8 KB, 477 views)
__________________
My blog (fr)

Last edited by Narann : 04 April 2013 at 09:49 PM.
 
  04 April 2011
Thank you for the script
__________________


Bucket Watcher
 
  04 April 2011
I will give it a try Thanks for sharing
/Rachid
__________________

phenomena2008sp1.zip
 
  04 April 2011
Might want to add "samples per object" boolean to Unified. And "finalgather legacy" boolean to get around the MAP rebuild bug.

Other than that, looks great.
__________________
My opinions are always my own...and maybe a friend's, but never my employer's.
 
  04 April 2011
Thanks for feedbacks! I will do that as soon as I can (go to work now )

I didn't find "samples per object" in the doc:

http://docs.autodesk.com/MENTALRAY/...nified_sampling

But this is in release note:

http://docs.autodesk.com/MENTALRAY/...s/relnotes.html

So I suppose this option is not yet documented. I will aslo add others features of the page.

Same for "finalgather legacy". I didn't find it. :/ even in the options doc.

If I've miss something, don't hesitate to give me the documented page!
__________________
My blog (fr)
 
  04 April 2011
It helps to have a few different eyes looking at the docs. I miss things time to time as well.
__________________
My opinions are always my own...and maybe a friend's, but never my employer's.
 
  04 April 2011
Originally Posted by Bitter: Might want to add "samples per object" boolean to Unified. And "finalgather legacy" boolean to get around the MAP rebuild bug.


I had added the "samples per object".

I've found a lot of string options in the release note... But no "finalgather legacy"

- "finalgather precomputation legacy"
Bug fix: Fiixed possible assertion/crash when finalgather precomputation with legacy mode was aborted. v3.9.1.2

- "finalgather flip bad geom normal"
During finalgather precomputation, no longer check if the angle between interpolated normal and geometry normal is below 90 degrees and flip geometry normal in such cases. The large angle can be a result of a string bump mapping is applied.

mental ray 3.8.3.23 and earlier versions printed a warning and flipped geometry normal, assuming that the issue originates from an incorrect shader. Many old shaders which computed the irradiance on the back side failed to flip the geometry normal.

The old geometry normal flipping behavior can be enabled. v3.9.0.6

- "finalgather precomp legacy" (Wait... What? You mean "precomputation" no?)
For compatibility with mental ray 3.7 and prior, single pass finalgather progressive display can be enabled. v3.7.50.4

@Bitter and others.

Could you just confirm the string options about final gather legacy?
__________________
My blog (fr)
 
  04 April 2011
I believe it is a newer option.

"finalgather legacy" on

This has to do with storage of the final gather points in the original format and not the MAP container. The other string options affect how it is computed. That should be avoided. We just want to use the older storage method.
__________________
My opinions are always my own...and maybe a friend's, but never my employer's.
 
  04 April 2011
Originally Posted by Bitter: This has to do with storage of the final gather points in the original format and not the MAP container. The other string options affect how it is computed. That should be avoided. We just want to use the older storage method.

Ok, I added it! I upload the file to the first post.

Don't hesitate to give me feedbacks.
__________________
My blog (fr)
 
  04 April 2011
nice work
iray?
__________________
my mental ray book my website
 
  04 April 2011
Originally Posted by dagon1978: nice work
iray?

Ow! I completly forget that! (I don't have the iray.dll )
I will do that as soon as possible!
__________________
My blog (fr)
 
  04 April 2011
Ok, iRay options are in!

But I can't test them... So If you are a iRay user, don't hesitate to feedback!

I found a undocumented iRay option in the release note (3.9.0.13) wich I added: "iray mode".

I also had prob with some options...

Quote: "iray max path length" num int

The default is unspecified, targetting highest quality by the use of virtually unlimited, more precisely sufficiently high, path length.


And

Quote: "iray threads" num int

The default is unspecified, resulting in reasonable CPU contribution to maximize overall performance.


For now, I put 0 instead of "nothing". Did this work? Did -1 could be considered as "unspecified"? :/

Any suggestions?
__________________
My blog (fr)
 
  04 April 2011
For "iray max path length" I would default to 4. This would net you enough depth to pass through a physically correct window for example.

I would probably leave the threads alone. But that's personal preference.
__________________
My opinions are always my own...and maybe a friend's, but never my employer's.
 
  04 April 2011
Hi Narann

Thank for share your stuff.
Do you think it's possible to add FG+IP+IR mode ?
 
  04 April 2011
I always put the defaults values referring to the doc. And this two option was not clear so I've put 0.

I just ask if iRay behavior is the same when you put nothing or when you put 0 (or maybe -1) to put the value wich will have the same behavior than iRay when you put nothing.

I want to be the less intrusive as possible in the behavior of iRay.

__________________
My blog (fr)
 
Thread Closed share thread



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
CGSociety
Society of Digital Artists
www.cgsociety.org

Powered by vBulletin
Copyright 2000 - 2006,
Jelsoft Enterprises Ltd.
Minimize Ads
Forum Jump
Miscellaneous

All times are GMT. The time now is 04:03 PM.


Powered by vBulletin
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.