Maya 2017 - Render Setup (Can't switch renderlayer visibility)

Maya 2017 - Render Setup (Can't switch renderlayer visibility)

strubefabian4
Contributor Contributor
5,163 Views
11 Replies
Message 1 of 12

Maya 2017 - Render Setup (Can't switch renderlayer visibility)

strubefabian4
Contributor
Contributor

Hello together,

 

we got a Problem with the new Render Setup in Maya 2017.

Problem: We have different renderlayer in it and it works at the beginning. At one Point, we are unable to Switch the renderlayer visibility.

It is loading forever and from that time, we can't work with that Scene anymore. Even if we create new layer we get the same Problem.

It Shows an error in the Script Editor:

"# RuntimeError: TypeError: file C:\Program Files\Autodesk\Maya2017\Python\lib\site-packages\maya\app\renderSetup\model\connectionOverride.py"

Hope someone can help us, even how we can avoid getting this error would be fine. We don't even know what causes it.
Thanks.

5,164 Views
11 Replies
Replies (11)
Message 2 of 12

slackstudios
Explorer
Explorer

I sure wish I had a solution for you. I just ran into the exact same problem. Were you able to come up with a solution? 

 

Running Maya 2017 with update 3

0 Likes
Message 3 of 12

tony.su
Autodesk Support
Autodesk Support

You can try it in Maya 2017 upgrade 4 or Maya 2017 upgrade 2.



Tony Su
Product Support
0 Likes
Message 4 of 12

strubefabian4
Contributor
Contributor
Well, it didn't happen again since we are on Update 4. I'm not sure if it will fix the "broken scenes" but I would try to update Maya and set up the render layer one more time.
0 Likes
Message 5 of 12

Anonymous
Not applicable

Having the same problem here with Update 3 and 4. 
Right now creating a new layer and moving collections over to the newly created layer works sometimes. This eternal loading problem sometimes seems to jump to a different renderlayer when upversioning the scene. It causing me a quite some headaches.

Message 6 of 12

ignuf
Contributor
Contributor

looks like i'm having the same issue with Maya 2018.1 .... anyone else having this ?

0 Likes
Message 7 of 12

ignuf
Contributor
Contributor

script editor is displaying this error message :-

 

# # File "C:\Program Files\Autodesk\Maya2018\Python\lib\site-packages\maya\app\renderSetup\common\devtools.py", line 7, in wrapper

# # raise RuntimeError("Abstract function called from: " + self.__class__.__name__ +"."+ f.__name__ +"("+ str(inspect.getargspec(f))+")")

# RuntimeError: Abstract function called from: VRayRenderElementStrategy.contentType(ArgSpec(args=['self'], varargs=None, keywords=None, defaults=None))

#

0 Likes
Message 8 of 12

ignuf
Contributor
Contributor

in my case it was render elements 

 

i deleted all the render elements (Vray) and I could switch between layers no problems 

0 Likes
Message 9 of 12

darrenwallace3d
Participant
Participant

I had the same issue. Deleting render elements didn't help me sadly. I did how ever notice a hazard symbol on my Lights sub render layers. It appears on collections when something that has been added to a collection has since been deleted. For things like meshes I'd just remove the deleted item from the collection list and it would go away. But I couldn't see a way to fix this with a Lights layer so I deleted those layers and I can now switch between layers again. But I need to setup all my Lights layers again. Seems as though Render Setup bugs out when items it's referencing are deleted or altered. From now on I'll try make sure everything is in place before setting up Render layers. Bit of a pain when wanting to reuse a scene with it's layers intact when deleting or adding objects breaks the setup.

0 Likes
Message 10 of 12

Bob_Bobbington
Contributor
Contributor

Any other suggestions then just updating? This hasn't helped me.
Thanks!! *high five*

0 Likes
Message 11 of 12

Anonymous
Not applicable

Having the same issue. Maya ... Not Responding.

 

Sometimes if I am patient and wait 5, 10, sometimes 15 minutes, it will resolve and let me continue working.

 

I left one station running for over 30 minutes after switching render layers, and it never resolved. Had to End Task.

 

Very frustrating and it's killing my workflow

0 Likes
Message 12 of 12

Anonymous
Not applicable

I have the exact same issue, but with Maya 2018.2 Has anyone found a working solution?

 

EDIT: found this mel command that searches for faulty nodes: fixRenderLayerOutAdjustmentErrors