Unable to switch render layers in render setup

2,548 views
Skip to first unread message

john clausing

unread,
Jun 30, 2017, 11:49:07 AM6/30/17
to maya_he3d
i've heard rumors that the inability to switch layers in render setup is an "update 3" issue.....i have found NO workarounds and it makes maya unusable.
i've also heard "update 4" resolves this issue though there is nothing on the Maya updates release notes about this

anyone know any thing?

thanks,
john

Maido Hollo

unread,
Jun 30, 2017, 2:54:02 PM6/30/17
to maya_he3d
I have no solutions and I can only conform that there are something wrong with render layers in u3. At some point, which I couldn't figure out patterns for the time I used, it started to do two things: 
1) loading cursor appeard and did not dissapear (even though it changed the layers, but I remember weird behavior also), restarting Maya helped
2) didn't change change layers at all and I couldn't debug it also, rebuilt the layers when needed but kind of started to avoid them

Hopefully u4 helps

Stephen

unread,
Jul 1, 2017, 11:00:59 AM7/1/17
to maya...@googlegroups.com
Not sure if it's a 2017 update issue or the old render layers issues with references  
  ( if shape nodes change or shader names change in referenced file this will always break something in a reference file.  And render layers especially.   Even more so with face assignments.   Unfortunately render layers get seriously messed up and error out even on changing layers.  Rather than just failing and moving on. ( still sucks. But at least you get the opportunity to fix the issues ) ) 
  
  But you can try the fixRenderLayers scripts in maya 


There is another one. I'll jump on my computer and give you the exact name if I can find it.  

Hth 

-=s 




--
You received this message because you are subscribed to the Google Groups "maya_he3d" group.
To unsubscribe from this group and stop receiving emails from it, send an email to maya_he3d+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

stephenkmann

unread,
Jul 1, 2017, 11:21:09 AM7/1/17
to maya...@googlegroups.com
nope It was  "fixRenderLayerOutAdjustmentErrors;" that you want to run
 ( hopefully )

gl
-=s

To unsubscribe from this group and stop receiving emails from it, send an email to maya_he3d+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Johan Schreurs

unread,
Jul 3, 2017, 8:23:48 AM7/3/17
to maya_he3d

My two cents worth:


Definitely do not mix files with legacy render and files with the new RenderSetup system. It won't work and it the manual says is not supported. So pick one system and use it consistently.

If you cannot switch to a certain render layer then try to delete that layer and re-create it. It is probably less pain and loss of time than to drag along bad layers and deal with renders that keep failing on that layer.


If Maya does not let you delete the broken layer (or it crashes) than there is a  a last resort that lets you get rid of ALL render layers in the Render Setup.
So you will need to recreate all your layers. Fortunately with the RenderSetup system you can export your layer setup to a JSON file. Perhaps that can save you some work.
My advice in that case would be to export the RenderSetup layer by layer. That way you can recreate the good layers one by one, and you're able to avoid the layer that is broken.


To clean out your Render Setup, open the Script editor, open a new Python tab  and run follown the lines of python code below:

import maya.app.renderSetup.model.renderSetup as renderSetup rs = renderSetup.instance() rs.clearAll()


I hope you find a good solution.



Op vrijdag 30 juni 2017 17:49:07 UTC+2 schreef john clausing:

john clausing

unread,
Jul 5, 2017, 9:08:08 AM7/5/17
to maya_he3d
unfortunately....this was a brand new scene created in 2017 u3....so it isn't to do with mixing legacy files

ill try that script, thank you

john clausing

unread,
Jul 5, 2017, 9:11:25 AM7/5/17
to maya_he3d
ill give that a shot.....interestingly, if i import the scene into an empty one and try to build a new set of  render layers, i get the same issue after a time.
What i've noticed is that there will be "phantom" layer nodes that "version up" my names which seems to co-incide with the errors. For instance i have a "Beauty" pass, when i import the "clean" scene into an empty scene and attempt to create a "Beauty" pass, it creates "Beauty1" leading me to believe that for some reason, there's garbage in the file carried over.
To unsubscribe from this group and stop receiving emails from it, send an email to maya_he3d+...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Stephen

unread,
Jul 5, 2017, 8:11:02 PM7/5/17
to maya...@googlegroups.com
With legacy layers if you do not delete them in files you are referencing. They will persist. And often will not get connected correctly to the layer display.    
  So you end up with hidden layers.  Maya will always level up on naming.  ( why naming is so fricken important in Maya )  
   My standard has been to always delete all layers on files that are going to be referenced / imported / or passed down the pipeline in any way.   
     
    If this is later free files being referenced and clashing within the creation file then it sounds like a "new feature". ( bug ). 
    
  Best bet is to list all layers by type and if they don't show up in the UI. Reconnect them or delete them. 

Hth. 

-=s 




john clausing

unread,
Jul 6, 2017, 1:52:16 PM7/6/17
to maya_he3d
funny thing....these aren't legacy layers.....they are collection and overrides created 15 minutes before that have been "nominally" deleted but persist......definitely a bug

Stephen

unread,
Jul 6, 2017, 6:09:53 PM7/6/17
to maya...@googlegroups.com
Oh. You waited over 15 minutes ? 
  Yeah. You can't do that. They normally harden and cure and become permanent (un delectable ).  after about 10 minutes  

   :) 


-=s 




Reply all
Reply to author
Forward
0 new messages