OTOY Forums

@JimStar, your explanation sounds reasonable, but if this is a Maya limitation then how come V-Ray and Arnold don't break the hypershade when they're unloaded?

rslaverne wrote:Just curious, what were the two lines of code you used to temporarily fix this? If you don't mind sharing.

-Will

@rslaverne,
The 2 lines of code are from earlier in the thread where Jim suggested a workaround to remove the option variables that are causing the problem. Wenneker's solution was adding the the code to mel script to run at startup every time you open Maya.
I just copied those lines to custom shelf button so it only does it when I want it to.
Either way works.

zboog wrote:@JimStar, your explanation sounds reasonable, but if this is a Maya limitation then how come V-Ray and Arnold don't break the hypershade when they're unloaded?

Yeh my thoughts exactly.

@Jim - It's probably safer to not fix by hack the Maya startup code as you suggested.
Last thing you want to do is introduce other workflow/pipeline problems to then require troubleshoot or fix.
If this is really a bug in Maya, have you logged bug report to Autodesk about it?
Again, I wonder how other third-party render plugins are getting around this problem.
Is there another way to add Hypershade functionality on plugin initilisation?

OK guys, it's solved.
I've found one more way how to do this safer. Just checked it - no problems neither with other plugins nor with hypershader.
Will be released in next version.

Any update on when this might come out?