Maya 2017 with Arnold

[angus_davidson]

You can still get MR from the Nvidia site. I think you now need to purchase it though. I doubt Nvidia are going to pay it that much attention though. iRay will most likely be their main focus.

It was a good move to include arnold, some of the integration done has made it really easy to get up to speed. Before the softimage plugin was always in a much better place.

That been said we are sticking with Octane as its just a crap-ton faster

[Bullit]

Thanks for the link talent103.

It seems Nvidia is intended into sabotaging themselves. Who buys or even try a render engine with that kind of examples?

[rray]

I'm glad they didn't do what I expected, which was switching Arnold to pay-each-application-plugin-seperately

[Bullit]

But now you lost a render engine which you could put rendering in various computers to one you cannot even continue working.

[Mathaeus]

So. is it just me or the workflow of the new Time Editor is very familiar?

Can't say, it seems I've managed yesterday, to kill both Graph and Time editor somehow, by managing 'workspaces' , also a new feature... anyway got them back with Maya Classic workspace and saving as new one, something like. To be fair, one thing I appreciate in Maya is a bit more of possibilities *before* going into Mixer, like copy paste animation between hierarchies. Actions from Graph Editor are nicely recorded in Script Editor, so on.
Definitively will checkout, especially how Time Editor deals with animation offsets, for now I believe it's good thing...
Workflow and such, still 'good old' Maya. For small example, it's only 3d app on planet, able to kill (or heavy damage at least) a custom rig, by single action from shader editor..... yeah exactly that.... "Famous" 'delete unused nodes' from Hyper Shade actually deletes any chain longer than 2 or 3 solely math nodes, unless they are locked, while lock isn't displayed anywhere on node, and so on and so on....

[Rork]

Ahhh.... the 'delete unused nodes' command.

THE way to mess with a-hole colleagues or naive interns

Not that Maya needs something like that, it's weird enough in it's ways as it is......

[Daniel Brassard]

@Mathaeus

Anyway back to topic, anyone knows what does it mean message about 'openCL not supported by nVidia drivers newer than 361, set appropriate env variable'. Got OpenCL to work by setting the env variable MAYA_OPENCL_IGNORE_DRIVER_VERSION=1, but is it better to rollback to older driver, or to live with this env variable.

Concerning OpenCL, can you provide a little bit more details?

https://developer.nvidia.com/opencl

According to the release notes, the latest driver for NVidia supported by version 368.81 WHQL of the Release 367 driver is compatible with OpenCL v1.2

http://us.download.nvidia.com/Windows/3 ... -notes.pdf

[Mathaeus]

According to the release notes, the latest driver for NVidia supported by version 368.81 WHQL of the Release 367 driver is compatible with OpenCL v1.2

Yeah I've read that too, but it seems that Maya has a different opinion. That's why I'm asking . This is from Maya output window:

Code: Select all

OpenCL evaluator is attempting to initialize OpenCL.
OpenCL is only supported on NVidia drivers up to version 361.75.  To enabled OpenCL for this driver version set MAYA_OPENCL_IGNORE_DRIVER_VERSION=1.

That's with driver version 368.81. So, Maya GPU override doesn't work. With older version of driver, or mentioned env variable, it's fine.

[Daniel Brassard]

Which version of Maya are you on?

[Mathaeus]

Which version of Maya are you on?

Don't get me wrong, but, did you read the topic and thread? Autodesk Maya LT 2017 2017, btw.

[luceric]

According to the release notes, the latest driver for NVidia supported by version 368.81 WHQL of the Release 367 driver is compatible with OpenCL v1.2

Yeah I've read that too, but it seems that Maya has a different opinion. That's why I'm asking . This is from Maya output window:

Code: Select all

OpenCL evaluator is attempting to initialize OpenCL.
OpenCL is only supported on NVidia drivers up to version 361.75.  To enabled OpenCL for this driver version set MAYA_OPENCL_IGNORE_DRIVER_VERSION=1.

That's with driver version 368.81. So, Maya GPU override doesn't work. With older version of driver, or mentioned env variable, it's fine.

368.86 is the first driver that works fine again.
you'll get crashes with drivers between 361.91 and 368.86
in the future, Maya will be updated to allow opencl again on 368.86 and up.

[Daniel Brassard]

@Mathaeus

Don't get me wrong, but, did you read the topic and thread? Autodesk Maya LT 2017 2017, btw.

No need to be rude, I can read just fine. Just confirming which version you have: Maya LT, Maya full, etc. Sometime a subversion can have bugs introduced that are not necessary apparent in the full version. Clearly not the case as Luceric mentioned.

Thanks Luceric for the clarification.

[Mathaeus]

So. is it just me or the workflow of the new Time Editor is very familiar?

Definitively, while Time Editor thing is much more visual. Regarding such tools, I think, huge immanent problem with them is, once Mixer controls the animation, there's sudden switch from completely visual controls, to abstract words, LeftGrpArmUp_rotz or animClip_22_hold_up07_fall002 and so. It seems they did everything to keep the workflow still visual, and that's great. Let's say this 'expand' in pic, even it's not editable, it gives a nice visual remainder, what's happening in clip. Groups on left side are recognized automatically by Maya, from pretty much unusual rig (for Mayan's practices). Noticed in other forums, that some people had less luck using built-in rigs, hehehe . Anyway who knows for what reason.
Because is not tied to character like old Maya Trax, could be used for anything, like sequences of camera animation
I'm afraid this is also a sad remainder, which app instead of Maya, deserves such improvement of non linear animation, but, well, at some point we should move on...



Other than that, in bounds of Maya LT, Node Editor behaves differently.
All in all nice... for around 350 Euros yearly (that's LT final price where I live), plenty.... nobody else offers such arsenal of tools.