Teague Scene Checker (for V-Ray)

Version: 
1.03
Date Updated: 
01/21/2013
Author Name: 
Colin Senner

Changelog: 1.03 -

  • The previous version did not fully correct the issue 2009/2010 users were having.  This one does.  Apologies.

Changelog: 1.02 - 

  • Fixes the error max 2010 users were getting 

Teague Scene Checker (for V-Ray) is a script that checks your scene for known error causing problems with V-Ray as well as informs you of some things that are happening in your scene.  The script currently checks for the following things and informs you so you can optimize the scene. After numerous scenes with outrageous render times Teague decided to invest in a simple, easy-to-use tool to eliminate problems for its artists. #INFO(These are just useful information to know, not really problems, just want to be aware of some of them)

  • V-Ray fur object is in the scene
  • V-Ray material has "Use Interpolation" on (Problematic for animation
  • V-Ray light material has direct light on (can be problematic if there are a large number of faces on the object)
  • Irradiance Map/LC Not set
  • "Use Light Cache for glossy rays" is off
  • Dynamic memory limit set very low
  • VRayDisplacementMod is applied to objects
  • VRayCarPaintMtl in the scene
  • VRayFastSSS/2 materials in the scene

#WARN

  • Detects if you are using Linear Workflow and makes sure you have gamma 2.2 and "Don't affect colors" (There are valid reasons to not have this ticked, but you already know that if you aren't ticking it)
  • Detail Enhancement is on in the Irradiance Map
  • V-Ray material(s) with more than 32 subdivisions
  • V-Ray light with high subdivisions (>24) found

#CRITICAL (Usually show stopping errors for V-Ray, crashes and the like or heavily un-optimized things that can skyrocket render times)

  • Standard lights found without "VRayShadow" or "VRayShadowMap" for their shadow generator
  • V-Ray material with "Use Irradiance Map" off (This thing along is why this script was written.  I absolutely hate this, it has cost me so many hours figuring it out)
  • Raytrace map found
  • Mental Ray lights that are found and unsupported

  The Script's interface is simple.  In the Messages window it shows the info/warnings/critical errors in the scene.  In the "Objects/Materials" window, it identifies what objects have the problems being referenced allowing you to easily change and tweak them.

TeagueSceneChecker_UI

The results of a scene optimization are as follows:

Before:
Scene Before          
After:
Scene After              

If you would like information on extending the script's capabilities, full documentation is available on my site at 
 

Cheers,
Colin 

Additional Info: 

Tested with Max 2010-2013. No problems.

Version Requirement: 
Max 2009+

Comments

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
colinsenner's picture

Martin, thanks for the kind

Martin, thanks for the kind words, hope it serves you well. Glad to help out the community. You work is always an inspiration, keep it up.

Cheers,
Colin

barigazy's picture

+1

I like this tool and whole idea.
Keep up with good work,man
Cheers!

barigazy

mb3d's picture

Tested! and.... IS AMAZING!

Hey Man! very good idea is have a selector Objects whit problems, Congratulations! Works on 3dsmax2009!.
Regards!

mb3d's picture

Excellent

Thanks Collin for share, i will test, and i tell if works for me (3dsmax2009+Vray 2.0).
Martin (MB3D)

colinsenner's picture

I've fixed the issue for Max

I've fixed the issue for Max 2010 and below users with version 1.02. Please download the newest version.

-Colin

fajar's picture

you could add function if

you could add function if getClassInstances xxx!=undefined ....or make array of instances class and call it...like classiOf=#(bitmapTex,VrayProxy,mrProxy,xx)....for i in classiOf where i!=undefined do......

kiran_1979_99's picture

Hi colin, it's great Tool,

Hi colin,

it's great Tool, but iam not able to use.

When running the Teague Scene Checker script, I get this error:

“MAXScript Rollout Handler Exception
– Type error: getClassInstances requires MAXClass, got: undefined”

I’m using 3ds Max2010, x64 (with SP1 and other hotfixes!) on WindowsXP 64

If there any solution for this. Pl letme know.

Best regards,

kiran......

AttachmentSize
01.jpg 224.88 KB
colinsenner's picture

What seems to be the issue?

What seems to be the issue? If you update to version 1.01+ it resolves the issue with vray materials inside multisub objects.

-Colin

lnio's picture

love it!!

hi colin, very useful- love it!!
a littel problem with scanning vraymtl subdive inside multi sub mtls.

Cheers,
LNio

colinsenner's picture

Releasing a fix for max 2009

Releasing a fix for max 2009 with v1.02 it'll be out soon.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.