ScriptSpot home

Teague Scene Checker (for V-Ray)

Downloads

3ds Max compatibility
See original listing claims
Community compatibilityNo compatibility reports yet

No reports yet for the available releases.

Community reviewsNo reviews yet.

Listing details

Version
1.03
From original requirements
2009 or newer
Original version requirement
Max 2009+
Author’s update date
Legacy votes
11
Listing created
How compatibility works

Compatibility comes from the author’s supported range or requirements in the original listing. A tested version records what the author tried.

“2020 unconfirmed” in the catalog means support for 3ds Max 2020 is still unknown.

Community reports record successful tests on specific releases.

Posted by

colinsenner

Colin Senner

More by this author

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 

Setup & notes

Tested with Max 2010-2013. No problems.
Comments (19)
PanKuczy

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!

Reply to PanKuczy
shineoooo

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

Reply to PanKuczy
Colin Senner

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

alnoman

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?

Branko Živković

+1

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

Martin

Tested! and.... IS AMAZING!

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

Reply to Martin
Colin Senner

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

Martin

Excellent

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

fajar

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

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

Attachments
Reply to kiran
Colin Senner

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

-Colin

lnio

love it!!

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

Cheers,
LNio

Reply to lnio
Colin Senner

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

-Colin

Colin Senner

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

chakib

All i can say is...

...BRAVO !

Big thanks for this very useful script !

malucow

Wow

Man, Relink bitmaps its already my most used script on daily work, but you made it again, now this will be my second most used script, incredibly useful, thanks for sharing it!

Reply to malucow
Colin Senner

Too Kind

You're way too kind. But thank you. Glad you enjoy it. I promise I'll update Relink Bitmaps soon. I'm going to try to this weekend, I'm aware of some problems. If you need anything else, let me know via email on my site. Cheers,
Colin

crystal3d

Great Idea, i liked it alot!

But as any great tools it has some problems and i am willing to report it as much as i can.

#W1 - My dynamic memory limit is 0 so it is unlimited but TSC reports it as low so i guess "0" value should be defined as "high enough".

Reply to crystal3d
Colin Senner

crystal

Great catch. I didn't realize you could set this value to 0. I'll get this corrected for the next build.

Thanks for the help Crystal3d!