Vray 3.3 and Maya 2016 extension 2

[snivlem]

Ah, I didn't realise. It's no problem at all.

[t.petrov]

We can try to work-around it again, but the best course of action is to report the problem directly to Autodesk, so they know it affects many people.

[snivlem]

Done!

If anyone else on this thread is experiencing the same thing please report it here;

http://download.autodesk.com/us/supp...elProduct=Maya

Hopefully they can do this for the next service pack

[beenyweenies]

I'm getting this issue all the time, I'm only just now learning about the channel box issue so I'll try that now. I'm also reporting it to Autodesk, just wanted to make sure you guys know it's still an issue!

WIN10, Maya 2016.5 SP1, Vray 3.42

[snivlem]

Is there a known issue with V-Ray nodes in the attribute editor? I'm seeing render overrides lose all their settings on v-ray related attribute editors and wondering if this was a known issue? I have to investigate further but it's happened quite a few times in order for it not to be some random bug.

[beenyweenies]

Not sure about this specific issue, but generally speaking Ext2 is a piece of sh*t. I've personally moved back to 2016 for now, way too many bugs.

[t.petrov]

Is there a known issue with V-Ray nodes in the attribute editor? I'm seeing render overrides lose all their settings on v-ray related attribute editors and wondering if this was a known issue? I have to investigate further but it's happened quite a few times in order for it not to be some random bug.

I don't think so. We'll be happy if you can share any details how to reproduce this.

[cum. m+d]

Regarding the missing marking menus.

I am facing the same issue mentioned months ago. We are using Maya 2016.5 Extension 2 SP1 with Vray 3.40.04 and I am still facing the same problem. Has anyone got a work around yet?

[beenyweenies]

Regarding the missing marking menus.

I am facing the same issue mentioned months ago. We are using Maya 2016.5 Extension 2 SP1 with Vray 3.40.04 and I am still facing the same problem. Has anyone got a work around yet?

I've moved on to Maya 2017 and many, many issues are no longer present. My personal experience was that 2016.5 was a total disaster and full of bugs. 2017 has been the most stable and reliable version I've used in years.

I know it's not always possible, but I would recommend you move up to 2017.

[cum. m+d]

Thanks for the feedback beeny. I was discuss with my team internally. We have people telling us that 2017 is ALSO buggy as hell and we should wait till the service pack is out.

[alainfx]

On the following thread, 2017 is described as the worst release ever :
http://forums.cgsociety.org/showthre...&page=15&pp=15

It's difficult to know if it's true (without testing it yourself), as each year someone says that

[pechart]

It's a mess right now. 2017 is not ready for production in many points, right now (for me, at least!). But to use MASH you need to use it, because the insanly crappy implementation of the render set system in 2016.5 makes that version unusable for us, too. Let's hope for 2017.5 or 2018. Or 3001.

[francomanko]

yeah i agree, autodesk have dropped the ball with 2017, some of the bugs just show they must be having issues with testing or lack of. The ui is so screwed, really frustrating to use.

[waaazoo]

yes, Maya 2017 UI is annoying with a lot of bugs. It's better since update2, but there is still a lot of mess. I'm just using it for testing purposes.
I'm still doing a lot of work on Maya2014, which is really stable I never used the latest versions of Maya, but it's getting worse...

[francomanko]

Its always a little worrying, the little bugs I find are more telling, the cant reload a file texture bug in initial release, then they fixed it in 2 but added another bug to it. The remove mentalray but then having errors due to there not being mentalray That's surely indicative of problems in their testing dept. I seem to remember this happening with maya 2009 being a really good release, then 2010, 2011 being poor, maybe they are affected by planet alignments