Vray 3.3 and Maya 2016 extension 2

[yolov]

That's strange. Can you confirm the build date and number? It's printed on the top of Maya's output window.

[snivlem]

It looks like it is fixed here but the VP2 is not very usable now as no V-Ray shaders display texture and objects are invisible, not sure if the two are related or if you guys are in the middle of upgrading the viewport display. Just something i noticed in the new build.

Under the new OpenGL scrict/core, VRayMtl goes orange.

[yolov]

Try the Legacy OpenGL Profile, we haven't got all the things up and running for the new profiles.

[snivlem]

Yes, the legacy profile is broken since last two nightlies. It's not an issue though, I can use older nightlies but I thought I should mention this.

Quadro K2200.

[yolov]

OK, we'll have to have a look at this too. I'll keep you updated.

[pixelmonk]

good thing I checked here.. same bug as snivlem with VP2.0 not showing vray shaders at all w/2016.5 and build vray_adv_33501_maya2016.5_x64_26779. Had been messing around with another ver of maya and finally got back to 2016.5 to this. I do love nightlies though!

[asi.sudai]

For sure, sorry for not sharing this earlier.

[2016/May/24|14:44:16] V-Ray: V-Ray for Maya version 3.30.02, revision 26719 from Apr 5 2016, 17:01:29
[2016/May/24|14:44:16] V-Ray: V-Ray core version is 3.25.01

Using Maya 2016 Extension 2
Cut ID: 201603022110-988944-2

[corestudio]

Is there an OS X version yet for 2016 Ext 2?

[yolov]

Is there an OS X version yet for 2016 Ext 2?

No, not yet, but we're working on it.

[corestudio]

ok, thanks. I guess it's back to Ext 1

[spacematt]

No, not yet, but we're working on it.

Dare you estimate a timeframe? Is it in bad shape or just waiting on a fix for the last niggle?

[t.petrov]

We're actively working on it and when it is ready we will report back.
If there aren't any unforeseen road blocks we'll have it in a few days.

[spacematt]

Ok, that's useful to know, thanks.

[snivlem]

Bad news - it seems the font issue is back on the official 3.4 build.

[t.petrov]

We've reported this to Autodesk, it is up to them to fix the root of the problem.
We're just trying to workaround it here.