VRAY 4 MAYA SHADERLIBRARY - Version 1.1.1 including Videotutorials released!

[ultrasonic]

VERSION 1.5 released

SAME LOCATION AS ALWAYS:
http://www.fullblownimages.com/downl...derLibrary.rar

You will like it! The only thing that changed is the script. so if you own a previous version and have your preview scenes working, you just need to replace FBI_shaderLibrary.mel from the archive.

The previewScenes are still from Maya 2009. I'll take care of them in the next release.

Changes in Version 1.5

[REQ] support sub-directories in TEXTURES folder  --- BETA --- please report bugs...i put some lines of debug-info in the code // TEXTURES MUST BE STORED IN YOUR PROJECTS SOURCEIMAGES DIRECTORY!!!

[NEW] UI Redesign:    - directory browser moved to the left 
                    - added information what renderer is currently in use.
                    - highlights directories that contain the word *shader* (not case sensitive) for faster navigation - mail me if u have more suggestions for highlighting

[REQ] Possibility to rename shader before export - only workin for single shader export...not when multiple shaders are selected // THX to throb!

[REQ] Delete shader confim dialog 

[BUG] shaders do not get uploaded anymore if missing textures are found

[jensl]

snivlem - From Maya 2008 and onward there's an option when opening your scene to 'ignore version.' This usually gets in newer files to open without issue.

ultrasonic - I've plopped in this new version and the UI and improvements are great! I'm having some issues with shader import, though. Exporting shaders works as usual, but for some reason the folder structure is changed when importing them back in. The folder structure is correct when exported (and in the shader library itself, within /TEXTURES/), but when imported the folder names are changed. I was testing this using some really long file names, but it seems the 'work.jens' folder was what actually caused the problem (changed to 'k.name'). Here's the debug:


DEBUG - GLOBAL_TEX_DIR: ...../shLib/TEXTURES/ - RELATIVE_TEX_DIR: ...../shLib/by_job//job_name/.tileFloorSG_textures/
DEBUG currentFileName: ...../MAYA/sourceimages/work.jens/zonkswithadunkachinobonkfolderborograve/CERM012_babdadeeeedooobaaaa.jpg
DEBUG sourceroot: ...../shLib/TEXTURES/
DEBUG targetroot: ...../MAYA/sourceimages
DEBUG relativeName: k.jens/zonkswithadunkachinobonkfolderborograve/CERM012_babdadeeeedooobaaaa.jpg
DEBUG currentDestDir: ...../MAYA/sourceimages/k.jens/zonkswithadunkachinobonkfolderborograve/
DEBUG newFileName: ...../MAYA/sourceimages/k.jens/zonkswithadunkachinobonkfolderborograve//CERM012_babdadeeeedooobaaaa.jpg
// Replaced 5 names.

[ultrasonic]

I am currently bugfixing this...you get an emergency release asap!

BTW: can u press SHARE IT! so i can debug with the shader itself?

[ultrasonic]

Please re-download....it should now say version 1.5.1 in the window title...besides the bugfix I added one more requested feature

Changes in Version 1.5.1

[BUG] IMPORT was temporary screwed up...hope this is fixed ... THX TO JENSL from chaos-forums for reporting this bug!!
        also added more debug info...
        
[REQ] option to "auto-apply" the imported shader to the current selection - requested by throb...

NEW INTERFACE:

[jensl]

Hah alright! It still works well enough, but I'm not going to argue if you want to do an emergency release. I have shared this shader, it's total junk and just for testing, really, but this way you can check the names and such.

This does bring up another question - Where do these uploaded shaders go, who can access them, etc? Anyways I mention this because if there is any absolute pathing, the shader .ma contains server names, job/folder names, and other info which is ideally kept private.
----

Alright plopped 1.5.1 in and the file pathing problem looks to be fixed. Now that was fast.

Jens

[ultrasonic]

the go directly to the website here:
http://www.fullblownimages.com/shaderlibrary/

as soon as it is uploaded it is visible at the website

I see a chance of anonymising stuff like your projectname and server....but i need to replicate the structure below the sourceimages folder...but that the only thing i need to do. i'll note this as a request!

EDIT: I got your shader workin! Worked without an error...relinked nicely and also copied to sourceimages...everything with version 1.5.1 from here FBI_shaderLibrary

[jensl]

Ahh, I see. Very cool. Will there be packs of these uploaded shaders zipped up, or is the idea that shaderLibrary users should download and install these themselves?

[snivlem]

With V-Ray SP1, the memory taken to render this scene is astronomical!

Just wondering if anyone else is getting insane memory usage when exporting shaders (or if it is my end) - each shader export is roughly using 7 gigs of memory for me.

[aweidenhammer]

I like this script. I've been using it a bit, and I think I'll put it into production soon. I've got a small collection of vray shaders I'd be happy to contribute.

One question (maybe this has been updated):
Why name the materials by the Shading Group? I would rather the name be pulled from the vray shader. We rarely name shading groups, since they get swapped so much. They are really just a set that tells maya that a shader should be attached to these objects, and have little to do with the shader itself. I constantly find myself redoing my shader export to the library, because the SG wasn't named... even tho I'm a stickler for naming materials.

[ultrasonic]

I am glad you guys are happy with the script!

I am also currently workin on an update which fixes some maya 2011 issues (especially the strange crashes which don't happen in previous maya versions).
I am also looking into the issues you guys have posted...

There will also be a thumbnail size chooser and less buttons - there will be a right click menu for all other stuff except the import button.

Another major change will be the preview scenes, which will now be split into some more files depending on your maya version. This is especially needed for Mental Ray.

There is also an issue with newer builds of Vray which cause the previews to become overexposed. I fixed that by removing textures from the area lights.

I hope i can release it in a few days...

cheers
Oliver

[ultrasonic]

Version 1.6 released

It's done! Version 1.6 is out...for now only for VRAY Users...

I will update all MentalRay features later and post on cgtalk too, but i want to hear your feedback first.

Link as always:
http://www.fullblownimages.com/downl...derLibrary.rar

It's tested on Linux (Maya 2011/2009) and Windows (Maya 2009 only).

See the changelog below and have fun!
cheers
Oliver

Changes in Version 1.6

[NEW] u can now choose your thumbnail size (only works on maya2011 and newer)

[NEW] right-click menus on every thumbnail - we also got more space and less buttons ;)

[BUG] you can now import shaders from newer maya versions (you must have "ignore version" turned on in your "open" options and you must have loaded at least one scene...does not work when maya is freshly started and "untitled" )

[BUG] when you have multiple versions of maya on your system it is now guaranteed that previews get rendered with the correct version

[BUG] render command changed from render to Render (with capital R) for linux

[BUG] fixed shader preview for vray, because lighting changed with a newer vray build (texture mapped area lights were broken)

[BUG]  fixed the black whole where the vray logo was once

[BUG] the script crashed on maya2011 when one tried to change the Path manually - this is now disabled - u can only use the browse button or the navigation on the left

[NEW] preview scenes depending on maya version e.g. renderShaderPreview_vray_2011.ma or renderShaderPreview_vray_2009.ma

[NEW] possibility to say "yes to all" or "no to all" when asking for texture overwrite

[NEW] donate button to help me feed the kids ;) it will be greatly appreciated!!! the shaderlibrary itself will always be free of charge!

[ultrasonic]

With V-Ray SP1, the memory taken to render this scene is astronomical!

Just wondering if anyone else is getting insane memory usage when exporting shaders (or if it is my end) - each shader export is roughly using 7 gigs of memory for me.

nope...around 250-300 MB in mayabatch here....what maya version are u using?

I like this script. I've been using it a bit, and I think I'll put it into production soon. I've got a small collection of vray shaders I'd be happy to contribute.

thx man! looking forward to seeing them....

One question (maybe this has been updated):
Why name the materials by the Shading Group? I would rather the name be pulled from the vray shader. We rarely name shading groups, since they get swapped so much. They are really just a set that tells maya that a shader should be attached to these objects, and have little to do with the shader itself. I constantly find myself redoing my shader export to the library, because the SG wasn't named... even tho I'm a stickler for naming materials.

I see your point, but i need to stay with the shadingGroup..otherwise it would mean major changes which may break a lot of stuff....maybe in version 2.0

[snivlem]

nope...around 250-300 MB in mayabatch here....what maya version are u using?

THanks, I actually fixed this - from memory the insane memory usage was due to textures in the area lights.

[jasonhuang1115]

Great job! Oliver. Thanks for sharing the library and the script.
I got quick question though. I could find the "scroll down" bar while browsing your website at the LATEST COMMUNITY UPLOADS. I've tried with three broswer (Firefox, Google Chrome, and IE). Is this just me?

[ultrasonic]

THanks, I actually fixed this - from memory the insane memory usage was due to textures in the area lights.

Yeah...area light texture were broken...don't know when this happened. But i also fixed this in 1.6

Great job! Oliver. Thanks for sharing the library and the script.
I got quick question though. I could find the "scroll down" bar while browsing your website at the LATEST COMMUNITY UPLOADS. I've tried with three broswer (Firefox, Google Chrome, and IE). Is this just me?

ups will fix that soon EDIT: FIXED!