Teague Scene Checker (for V-Ray)

Submitted by colinsenner on Tue, 2012-12-11 14:31

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.

The results of a scene optimization are as follows:

Before:

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+

Links

Homepage URL:

http://www.colinsenner.com

Download URL:

http://www.colinsenner.com/scripts/teague-scene-checker

Comments

Submitted by colinsenner on Wed, 2021-02-10 12:14.

Adding these to the next

Adding these to the next version (5 years later), if that's alright with you.

Submitted by shineoooo on Mon, 2019-03-25 09:06.

Thanks for sharing!

Thanks for sharing! One question, did you get this to work with latest Vray Next?

Submitted by Pankuczy on Wed, 2019-02-20 11:10.

Two features added

Amazing script!
Thanks for sharing it with us.

I've added two additional checks if anyone's interested: one for checking if REGION RENDERING is turned on in VFB, and the other for checking if 'RENDER HIDDEN GEOMETRY' is on in the Render Setup\Common rollout. (With the latter option accidentally turned on it costed me almost whole day to figure out what's wrong with my scene that it renders awfully long).

Here are the lines to add:

/******************* Check for Render Hidden Geometry ******************/
if rendHidden then (
	addProblem #warn #RenderSetup "!!! Render Hidden Geometry is turned on" )
 
 
/*********************** Check for Region Render ***********************/
local regiontest = vfbControl(#getregion) as string
 
	if not (matchPattern regiontest pattern:"*0, 0, 0, 0*") then (
		addProblem #warn #RenderSetup "!!! VFB Region Render is turned on" )

Cheers!

Submitted by ratatouille on Wed, 2017-08-30 21:01.

support up to 2017?

Hey, dont you have support up to 2017?
or is there any default vray options do the same thing teague do?
or how should we get the teague facilities?

Submitted by colinsenner on Wed, 2013-01-23 18:24.

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

Submitted by barigazy on Mon, 2013-01-21 16:05.

+1

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

bga

Submitted by mb3d on Mon, 2013-01-21 13:47.

Tested! and.... IS AMAZING!

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

Submitted by mb3d on Mon, 2013-01-21 13:34.

Excellent

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

Submitted by colinsenner on Thu, 2013-01-17 10:58.

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

Submitted by fajar on Wed, 2012-12-19 03:13.

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......

About this site