2017: scriptJob at startup is causing the render settings window to be empty

[borbs727]

I'm using a userSetup.py to run a tool at startup.  It works great in 2016, but it's breaking in 2017.  

If you put the code below into a userSetup.py (I just placed this test userSetup in one of the default Maya python path directories) and run Maya, you'll see that the first 2 evals work fine, but they don't run the code when I need it executed (after VRay is initialized).  The last one, the script job, executes the code at the right time, but it breaks the render globals window.  Is this a bug? Thanks!

#userSetup.py

import sys
import maya.cmds as mc
import maya.utils

def print_text():
	print 'ran script'
	
#mc.evalDeferred('print_text()')
#maya.utils.executeDeferred('print_text()') 
mc.scriptJob(runOnce=True, e=["idle", print_text])

[Anonymous]

Hi !

I have the same issue here. If you open a brand new scene ( without any plugin ) you will see when you open the render settings window that it creates the tab right there. That means that when the code is executed before that first opening of the panel, stuff is missing inside and it blows everything apart.

Kind of sucks ...

[borbs727]

I'm still having this issue in 2018!!