What's New in 3ds Max 2019.3 Update

[glorybound]

If you put a few dollars in his paypal account and email him and ask him nicely there's a rumour you will receive a link..... However I think he's disappeared now for a few months.

I am over it and I am not playing his game. It is childish and I moved on.

[Morne]

took about an hour to install on a HDD

[glorybound]

Same here. Heck, it took 45 minutes to install their free DWG viewer. Mind you, that does not include download times.

[gandhics]

If this is still not fixed, I won't touch 2019 with a stick.

This is apprently each renderer issue. Arnold is fully Qt and have no problem.
I think Vlado mentioned he is working on.

[gandhics]

A little post about 2019.3
http://cganimator.com/3dsmax-2019-3-...port-osl-hlsl/

[^Lele^]

This is apprently each renderer issue. Arnold is fully Qt and have no problem.

Again, my experience differs, with Arnold being untreatable in its latest version while rendering, due to extreme flickering, in both 2018 and 2019 (any sp.).
We don't flicker, and haven't done so, for a long time with nightlies, again in my own experience.
No idea what trickled to our release version, mind you, we may still have issues i am not aware of.

[anthonyh]

Again, my experience differs, with Arnold being untreatable in its latest version while rendering, due to extreme flickering, in both 2018 and 2019 (any sp.).
We don't flicker, and haven't done so, for a long time with nightlies, again in my own experience.
No idea what trickled to our release version, mind you, we may still have issues i am not aware of.

I can`t even get Arnold to work. I can assign it as the engine but as soon as I try and make any material in the material editor it just instantly crashes max. No idea why, can`t find anything about it online. Not that we`d use it but I`d like to test it out sometime.

[^Lele^]

I can`t even get Arnold to work. I can assign it as the engine but as soon as I try and make any material in the material editor it just instantly crashes max. No idea why, can`t find anything about it online. Not that we`d use it but I`d like to test it out sometime.

It's a very educational experience, i'd encourage you to try it out.
As for using it in production, i have no experience of it, much less so within Max, but can't say i'm longing for any, to be perfectly honest.

[anthonyh]

It's a very educational experience, i'd encourage you to try it out.
As for using it in production, i have no experience of it, much less so within Max, but can't say i'm longing for any, to be perfectly honest.

Well I do want to try it, it just doesn`t work. Strange because I can hit render ok but when I try to create any materials it crashes max completely, weird.

[gandhics]

Again, my experience differs, with Arnold being untreatable in its latest version while rendering, due to extreme flickering, in both 2018 and 2019 (any sp.).
We don't flicker, and haven't done so, for a long time with nightlies, again in my own experience.
No idea what trickled to our release version, mind you, we may still have issues i am not aware of.

I'm not taking about flickering.
I meant the double clicking issue.
That is the issue which Tab UI doesn't like Qt.
And... Render Setup is all Tabs.

[^Lele^]

I'm not taking about flickering.
I meant the double clicking issue.
That is the issue which Tab UI doesn't like Qt.
And... Render Setup is all Tabs.

Oh you mean the clicking once to focus and twice to get to the control/button itself.
Annoying, but leaves the software usable.
Unlike the flickering, for which there are two ways only to stop it: kill max, or wait for the render to complete (that's valid for us too, hey. not having a dig at Arnold.).

On the max 2019.3/OSL maps post: all those i see are UV-mapped, not truly volumetric.
Is it a viewport limitation, and they then render right (and differently from the UV-mapped viewport), or is it an OSL thing?

[vjaramillo]

Not installed it yet. Not planning to in the near future as, 2019.2 is buggy. The only attractive update in .3 is the Viewport active shader.

[Alex_M]

Not installed it yet. Not planning to in the near future as, 2019.2 is buggy. The only attractive update in .3 is the Viewport active shader.

And not crashing every time you use Exclude/Include lists. I think that's quite "attractive" too.

[gandhics]

Oh you mean the clicking once to focus and twice to get to the control/button itself.
Annoying, but leaves the software usable.
Unlike the flickering, for which there are two ways only to stop it: kill max, or wait for the render to complete (that's valid for us too, hey. not having a dig at Arnold.).

On the max 2019.3/OSL maps post: all those i see are UV-mapped, not truly volumetric.
Is it a viewport limitation, and they then render right (and differently from the UV-mapped viewport), or is it an OSL thing?

Hmm.. we don't get flickering while rendering. But, we changed envvar to direct for Qt.
All The OSL map shown in my post is 3D procedural maps.
2D UV mapped OSL has been always OK.
This OSL > HLSL is for OSL map in any spaces.
As of now you can see most OSL map including 3rd party maps properly in viewport in Realistic Material with Maps mode.
2020 will support even more cases.