RenderSetup and cascaded references Maya 2017 U3

[a.reimer]

Hello,

I am experiencing strange errors when using cascaded references, meaning reference files loaded by reference files. Those will then be loaded in a shot render scene.

Maya 2017 Update 3 64 bit on Windows

After setting these up I get a lot of such errors:

// Error: line 0: (kInvalidParameter): Argument is a NULL pointer
# Traceback (most recent call last):
# File "C:\Program Files\Autodesk\Maya2017\Python\lib\site-packages\maya\app\renderSetup\model\sceneObservable.py", line 70, in wrapper
# return f(*args, **kwargs)
# File "C:\Program Files\Autodesk\Maya2017\Python\lib\site-packages\maya\app\renderSetup\model\sceneObservable.py", line 299, in _afterCreateReferenceAndRecordEditsCB
# refFn = OpenMaya.MFnReference(referenceNode)

And in the render setup many layers have lost collections or attribute overrides where there were none before.

Anybody experienced such behavior too?

Andreas

[NandoStille]

+1

[stooch]

+1 

is anyone going to answer this?

[heileif]

1+

[sean]

+1

I'm experiencing error as well.  Not sure of cause, may be related to unloaded cascades.  Trying to fix currently.

[a.reimer]

Did anyone have the chance to test it with 2018? We had no time to upgrade yet.

[mweier]

Just started happening to me on Maya 2018.  Was rendering with cascaded references fine yesterday, but after some further reference tweaking now it's not and I get this error:

Error: line 1: RuntimeError: file C:\Program Files\Autodesk\Maya2018\Python\lib\site-packages\maya\app\renderSetup\model\sceneObservable.py line 354: (kInvalidParameter): Argument is a NULL pointer

[a.reimer]

Hm then it looks like we will have fun with our first bigger 2018 production.

So there was no change since I talked with the support early this ear.

[stooch]

Just fyi I built our pipeline to use alembic caches and got rid of nested references out of our lighting / rendering scenes. We only reference in shaders and environment models using python scripts. Lots of problems with maya render layers too. Especially render setup.

[cbarnettXCM33]

+1

Anyone figure out anything farther on this? Not sure it really causes an issue for us at render time but it spits out about ~150 lines in our logs and is a pain to dig through.

Cheers!

[timo.stampa]

still the same with maya 2018.3

+1

[parabhdeep]

Could you elaborate how you are doing this?