Vray 3.3 and Maya 2016 extension 2

[yolov]

And what's your viewport driver set to? The setting can be found in Maya's settings and preferences > Display. Set it to OpenGL Legacy Profile (if it's not already set to that) and see if that helps.

[CAPTURE_MM]

Hello Vlado,

no rendering just loaded the plugin, I think the channel box could cause the issue maybe. I have the attribute editor docked together with the channel box so I can switch them via tab.
The problem sometimes occured when entering values into the channel box like scale for example.
I couldn´t relate the issue to the attribute editor so far.

[CAPTURE_MM]

Hello Alex,

it was set to opengl core profile (compatibility), I changed it to legacy, restarted maya, but problem persists.

[yolov]

OK, it was worth a try. We'll try and see if there's something we can do about it, if it's related to vray.

[CAPTURE_MM]

Okay thank you!
So you can reproduce the problem?

[snivlem]

OK, it was worth a try. We'll try and see if there's something we can do about it, if it's related to vray.

I think Autodesk UI dev on CGTAlk said it was to do with VRay.

[vlado]

Would have been nice to also mention it to us...

Best regards,
Vlado

[ricoholmes]

It's a very "in your face"bug I'm afraid, and renders marking menus completely unusable (muscle memory kicks in for the most often used ones, but certainly can't choose materials etc).

Easiest way to reproduce the bug:
Create poly primitive,
Load Vray Plugin,
Right click channel box and freeze an attribute.
Marking menu corruption.

Also, DR crashes Maya with a fatal flaw here every time, every scene (though everything renders fine on single machine).

Win 10
Maya 2016.5 (clean, no other plugins)
Nightlies 26749

[vlado]

Yes, will take a look.

Best regards,
Vlado

[CAPTURE_MM]

Also, DR crashes Maya with a fatal flaw here every time, every scene (though everything renders fine on single machine).

DR is working fine here so far.
Stepping back through the history is painful slow, but not sure yet if this is also vray related.

[vlado]

Which history?

Best regards,
Vlado

[CAPTURE_MM]

Undo queue...even for simple tasks like polygon selections undoing them takes quite long. A colleague of mine had the impression that it was vray related as well, but I think this is hypershade related and mostly happens if the hypershade window is open.

[ricoholmes]

DR is working fine here so far.

Hmm that's alarming. Never had a problem before. OK will start troubleshooting.

Edit: DR Works fine with Fixed, Adaptive, Adaptive subdivision. Crashes every time on Progressive

CAPTURE_MM does yours work on progressive ?

[yolov]

Undo queue...even for simple tasks like polygon selections undoing them takes quite long. A colleague of mine had the impression that it was vray related as well, but I think this is hypershade related and mostly happens if the hypershade window is open.

What's your vray build?
Can you check the history queue for vray-related commands when this happens. We fixed something that sounds a bit like this issue a few weeks ago.
You can query the undo queue with this line in MEL: undoInfo -q -pq;

[alainfx]

I think Autodesk UI dev on CGTAlk said it was to do with VRay.

Here is the message posted by lucericr (Maya UI Team), on 04-21-2016, 04:17 PM :

http://forums.cgsociety.org/showthre...28#post8174328