Hair in Maya Yeti Redshift fail

[markeljfp]

Greetings Knights

Up front information:

rrVer 8.2.13

Maya 2018.2

MtoA 3.0.1.1

Redshift 2.5.63

Yeti 2.2.4

Again, but different.

We're having problems where the hair on one of our characters is now not loading. The rest of the model renders just fine.

The following errors appear in our logs:

R 59| 00:00:00   323MB WARNING |  unable to load dynamic library C:\RR_localdata\renderer_plugins\maya\win_x64\2018\yeti\bin\pgYetiDLRender.dll: The specified module could not be found.

R 60|

R 61| 00:00:00   323MB WARNING |  unable to load dynamic library C:\RR_localdata\renderer_plugins\maya\win_x64\2018\yeti\bin\pgYetiPrmanRender.dll: The specified module could not be found.

R 62|

R 63| 00:00:00   323MB WARNING |  unable to load dynamic library C:\RR_localdata\renderer_plugins\maya\win_x64\2018\yeti\bin\vray_pgYetiVRay.dll: The specified module could not be found.

R 64|

R 65| Warning: line 1: filePathEditor: Attribute 'aiStandIn.dso' and label 'Standin' have been saved already.

R 66| Warning: line 1: filePathEditor: Attribute 'aiVolume.filename' and label 'VDB' have been saved already.

R 67|

R 68| API error detected in plugins\mtoa\Main.cpp at line 631

R 69| : (kFailure): Unexpected Internal Failure

R 70| 00:00:00   326MB WARNING |  unable to load dynamic library C:\RR_localdata\renderer_plugins\maya\win_x64\2018\yeti\bin\pgYetiDLRender.dll: The specified module could not be found.

R 71|

R 72| 00:00:00   326MB WARNING |  unable to load dynamic library C:\RR_localdata\renderer_plugins\maya\win_x64\2018\yeti\bin\pgYetiPrmanRender.dll: The specified module could not be found.

R 73|

We have the yeti plugin present (and we're using it successfully with the likes of Arnold). We're rendering across multiple (about 15) machines and the error seems consistent

Wondering if anyone else has any experience with this, or any suggestions as to where to look to correct the problem.

Hopefully

Mark Ludford

Jellyfish Pictures

[RR, Schoenberger]

Hi

 

The error message „The specified module could not be found“ does usually mean that the plugin/shader does not find a required Dll.

But the shader Dlls stated are all libraries for a different renderer. And therefore the missing Dlls are the one of the renderer.

The Redshift shader seems to be implemented into Redshift and is not shipped with YETi https://www.redshift3d.com/product/features#all

 

If the yeti cache path was setup relative to the scene file, then please try to disable Local Scene Copy for the job.

 

 

regards,
Holger Schönberger

 

Please use the rrKnights Tavern
or our support system for new questions.

--
If you reply, the message is send to the user group which is sufficient.
("Reply All" just sends the message twice to the last author which is not required)
---
You received this message because you are subscribed to the Google Groups "Royal Render Knights Tavern" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rrKnights+...@googlegroups.com.
Visit this group at https://groups.google.com/group/rrKnights.
For more options, visit https://groups.google.com/d/optout.

[markeljfp]

Hi

I have tried adding the .dll and .mll files to the path

[RR]\render_apps\renderer_plugins\maya\win_x64\2018\yeti\bin

with no positive effect.

I've checked that the versions are compatible (Yeti 2.2.4 to Redshift 2.5.68)

I have added the following to redshift__inhouse.rrEnv

REDSHIFT_COMMON_ROOT = \\jfpstorage\Workflow\Plugins\Redshift\v2.5.68\Plugins\Maya\Common
REDSHIFT_PLUG_IN_PATH = \\jfpstorage\Workflow\Plugins\Redshift\v2.5.68\Plugins\Maya\2018\nt-x86-64
REDSHIFT_COREDATAPATH = \\jfpstorage\workflow\Plugins\Redshift\v2.5.68
REDSHIFT_SCRIPT_PATH = %REDSHIFT_COMMON_ROOT%\scripts
REDSHIFT_XBMLANGPATH = %REDSHIFT_COMMON_ROOT%\icons
REDSHIFT_RENDER_DESC_PATH = %REDSHIFT_COMMON_ROOT%\rendererDesc
REDSHIFT_MAYAEXTENSIONSPATH = %REDSHIFT_PLUG_IN_PATH%\extensions;\\jfpsohostorage\plugins$\Maya_Plugins\Maya_2018\Yeti-v2.2.4\plug-ins
MAYA_PLUG_IN_PATH = %REDSHIFT_PLUG_IN_PATH%

which I have seen elsewhere and seems to work for us from a local rendering point of view.

I'm open to any suggestions

Cheers

m

[markeljfp]

It has occurred to me to ask if there needs to be a line in redshift.rrEnv to include the redshift__inhouse.rrEnv

Best

m

R 70| 00:00<span style="font-size:10.0pt;font-family:"Courier New";color

[RR, Schoenberger]

>It has occurred to me to ask if there needs to be a line in redshift.rrEnv to include the redshift__inhouse.rrEnv

No, both files are always loaded.

 

Note: Both files are for Redshift Standalone (.rs files).

If you use maya, then you have to edit the Maya…rrEnv files.

[RR, Schoenberger]

 

PS: I can do some tests via remote tomorrow.

I just need a simple redshift+YETI test scene. To see if it is the setup or the scene.

There are some YETI tests for Arnold and VRay we used for the cloud.

If you have 3 minutes, please load the scene /production/z_testscenes/Maya…/…YETI…  in the Maya version you use,

switch the renderer to Redshift, save it with a right name (renderer and maya version) .

Then test-render in Maya to verify YETI is visible and submit it to the farm.

[RR support, Schoenberger]

Ok, YETI itself is rendering on your farm as seen in the test scene output.
So it seems to be an issue with the YETI settings.

I assume the hair is set to cache mode and the cache files are not
found on the farm.
Either because the path is relative and the job option Local Scene
Copy is enabled or you use a drive letter that is not mapped on the
farm.

[markeljfp]

Hi Holger

The settings I mentioned earlier in the redshift__inhouse.rrEnv apparently got moved to the maya.rrEnv and now all is good.

Many thanks for all the tips!

m

[RR support, Schoenberger]

Hi

I rechecked all settings in maya.rrEnv and Extensionpath was missing.
And I was wrong that Redshift supports YETI (mis read their statement
on their website). The YETI vendor provides the shader for Redshift.

The YETI plugin folder will be set for redshift with the next RR
version as well.