VRAY 4 MAYA SHADERLIBRARY - Version 1.1.1 including Videotutorials released!

[tinuz]

Hi,

I used your script before but I just updated and I noticed that you can't export referenced shaders.(gives a rename error) Not really a big deal since you can copy the shader network and then export.
BTW.. I was blown away by the automatic thumbnail rendering!! really cool and handy.
thanks!

[jasonhuang1115]

Hi, Oliver,

Just installed the shader library and it is really wonderful to have this useful and user-friendly script for managing shader library and expanding the library through a community. Big thanks to you and to Paul too for sharing a pre-packaged library of presets.

I ran into a problem and hope you can help me out. The shader library works great with Paul's collection. When I tried to export shaders downloaded from the bazuka's "Vray materials thread", some of them will export correctly with thumbnail preview but most of them won't export with "// Error: Error while parsing arguments" shown in the script editor?

I found that for the ones that won't export, a nurb sphere will be automatically created in the scene as I hit "Export selected shader here". Is this a user error or something else? I searched in the thread but nobody reported this issue.

I attached one of the shaders from Bazuka's thread that will cause export issue for you the examine.

HotMetal.zip

Thanks,
Jason

[jasonhuang1115]

By the way, some the materials already come with a render of its own preview scene so these shaders can be integrated directly (modifying the name of the jpg to shader's name) in the library without export. However, these images are often in different image aspect ratio (usually in rectangular instead of the square shape allowed in the FBI shader library script), so the thumbnail preview in Maya will be squashed. Is it possible to allow thumbnail image with different aspect ratio to be displayed as it is?

cheers,
Jason

[ultrasonic]

By the way, some the materials already come with a render of its own preview scene so these shaders can be integrated directly (modifying the name of the jpg to shader's name) in the library without export.

That is not right...u need to export using the shaderlibrary script because of naming conventions! you cannot just try to import a file from bazuka! it might work, but not as intended.

I am also looking into the "// Error: Error while parsing arguments" issue....someone else already emailed me this problem...

cheers
Oli

[jasonhuang1115]

That is not right...u need to export using the shaderlibrary script because of naming conventions! you cannot just try to import a file from bazuka! it might work, but not as intended.

I am also looking into the "// Error: Error while parsing arguments" issue....someone else already emailed me this problem...

cheers

Oli

Thanks for the quick reply, Oli.
Luckily, I didn't run into any problem or naming issue so far by simply copying shaders downloaded from bazuka's thread (eg. hot_metal.ma) with accompanying thumbnails (eg. rename the thumbnail to hot_metal.ma.jpg) into the FBI_shader_library folder. The shaders imported just fine although the thumbnail is squashed and with weird square artifacts in the background (shown in the attached JPG). The artifacts even appear when I manually generate the thumbnail by:
1. load your "renderShaderPreview_vray_2011.ma" scene
2. import the shader downloaded from bazuka's thread. Assign the shader to the sample sphere.
3. render.
4. save the jpg to the corresponding installation path of the FBI shader library.

Not sure if this is only me? I am on Windows XP x64 with Maya 2011 hotfix 3.

[ultrasonic]

I think this is a Maya 2011 QT issue...since the jpg itself is always ok...in other maya versions everything is looking fine too.

[jasonhuang1115]

I think this is a Maya 2011 QT issue...since the jpg itself is always ok...in other maya versions everything is looking fine too.

I see. Thanks for the reply, Oliver. Look forward to the new version.

[ultrasonic]

v1.6.1 here
http://www.fullblownimages.com/downl...derLibrary.rar

Changes in Version 1.6.1

[BUG] if you select a shader connected to multiple shadinggroups it was detected as a multi-export....fixed!

[BUG] "// Error: Error while parsing arguments" issue with some shader - resolved

[jasonhuang1115]

Awesome!!

Awesome! Going to give a shot now. Thanks and great job, Oliver. A small request: is it possible to make the script to treat the jpeg extension as jpg. The jpg file manually saved out of Maya is with jpeg as the file extension, making me manually modify it to jpg so that the shader library can recognize the thumbnail images.

[jasonhuang1115]

The v.1.6.1 works like a charm. No "Error while parsing arguments" anymore. Interestingly, the thumbnail generated via the export process has no artifacts in the background. Thanks, Oliver.

edit: the artifacts seem to be scene-dependent. If I use Oliver's scene as the "renderShaderPreview_vray_2011.ma" then NO ARTIFACTS. But if I use bazuka's scene, then the artifacts show up.

[stezza]

The issue I have is this, is when I change up to the parent folder the whole interface disappears then comes back again.

[alainfx]

Hello,

Thanks for that great script !

Some shaders are imported without problem, but a lot of them show errors in the Script Editor :
// Error: //
// Error: AEhardwareTextureMaterialChangedCB Carpet.diffuseColor Carpet.message; //
// Error: Wrong number of arguments on call to AEhardwareTextureMaterialChangedCB. //
// Error: Object not found: . //
// Error: Object not found: . //
// Error: Object not found: . //


For example it happens with Wall-->DecorativeWall
(see debug below)
Then each time I select the shader in maya I have the same message :
// Error: Object not found: . //


My configuration :
ShaderLibrary v1.6.1
Windows7 64 bit.
Maya2010.
VRay for Maya 1.5 SP1.


DEBUG - GLOBAL_TEX_DIR: O:/SHADERS_LIB/VRAY/TEXTURES/ - RELATIVE_TEX_DIR: O:/SHADERS_LIB/VRAY/SHADERS//Wall/.Decorative_wallSG_textures/
DEBUG $texFileName before: C:/Paul_Daten/Shaderlib/tex/decor.jpg
DEBUG $newTexFileName O:/SHADERS_LIB/VRAY/TEXTURES//decor.jpg
RELINKED TEXTUREPATH ON shaderImport_decor_1 TO: O:/SHADERS_LIB/VRAY/TEXTURES//decor.jpg
DEBUG currentFileName: O:/SHADERS_LIB/VRAY/TEXTURES/decor.jpg
DEBUG sourceroot: O:/SHADERS_LIB/VRAY/TEXTURES/
DEBUG targetroot: D:/maya/projects/default/sourceimages
DEBUG relativeName: decor.jpg
DEBUG currentDestDir: D:/maya/projects/default/sourceimages
DEBUG newFileName: D:/maya/projects/default/sourceimages/decor.jpg
// Error: //
// Error: AEhardwareTextureMaterialChangedCB Carpet.diffuseColor Carpet.message; //
// Error: Wrong number of arguments on call to AEhardwareTextureMaterialChangedCB. //
// Error: Object not found: . //
// Error: Object not found: . //
// Error: Object not found: . //



EDIT : sometimes I also have this in Maya's Output Window, when rendering imported shaders :
V-Ray warning: Unsupported texture VRayMtl

[ultrasonic]

Hello,

Thanks for that great script !

Some shaders are imported without problem, but a lot of them show errors in the Script Editor :
// Error: //
// Error: AEhardwareTextureMaterialChangedCB Carpet.diffuseColor Carpet.message; //
// Error: Wrong number of arguments on call to AEhardwareTextureMaterialChangedCB. //
// Error: Object not found: . //
// Error: Object not found: . //
// Error: Object not found: . //


For example it happens with Wall-->DecorativeWall
(see debug below)
Then each time I select the shader in maya I have the same message :
// Error: Object not found: . //


My configuration :
ShaderLibrary v1.6.1
Windows7 64 bit.
Maya2010.
VRay for Maya 1.5 SP1.


DEBUG - GLOBAL_TEX_DIR: O:/SHADERS_LIB/VRAY/TEXTURES/ - RELATIVE_TEX_DIR: O:/SHADERS_LIB/VRAY/SHADERS//Wall/.Decorative_wallSG_textures/
DEBUG $texFileName before: C:/Paul_Daten/Shaderlib/tex/decor.jpg
DEBUG $newTexFileName O:/SHADERS_LIB/VRAY/TEXTURES//decor.jpg
RELINKED TEXTUREPATH ON shaderImport_decor_1 TO: O:/SHADERS_LIB/VRAY/TEXTURES//decor.jpg
DEBUG currentFileName: O:/SHADERS_LIB/VRAY/TEXTURES/decor.jpg
DEBUG sourceroot: O:/SHADERS_LIB/VRAY/TEXTURES/
DEBUG targetroot: D:/maya/projects/default/sourceimages
DEBUG relativeName: decor.jpg
DEBUG currentDestDir: D:/maya/projects/default/sourceimages
DEBUG newFileName: D:/maya/projects/default/sourceimages/decor.jpg
// Error: //
// Error: AEhardwareTextureMaterialChangedCB Carpet.diffuseColor Carpet.message; //
// Error: Wrong number of arguments on call to AEhardwareTextureMaterialChangedCB. //
// Error: Object not found: . //
// Error: Object not found: . //
// Error: Object not found: . //

EDIT : sometimes I also have this in Maya's Output Window, when rendering imported shaders :
V-Ray warning: Unsupported texture VRayMtl

I think these error messages are all Maya related and do not come from the shaderLibrary script...i will check it in the evening....

The issue I have is this, is when I change up to the parent folder the whole interface disappears then comes back again.

This is the intended behaviour...i must rebuild the whole UI every time i change a folder...why is this a problem?

[stezza]

It's not really a problem as such that the interface reacts the way it does, it's just it never did this before!
Great script by the way!

[seq]

Hi Olivier,

great script! Thanks a lot! Combined with the materials from Bazuka - this is a dream.

Do you know why the jpegs from Bazuka gets scretched and have these artefacts in Maya 2011?

Perhaps Bazuka would like to name the jpegs of future materials according to the name specification e.g. "water.ma.jpeg"? Then we could use them directly with the FBI_shaderLibrary...

Ciao,
Lars