UI drawing speed of VRayMtl

[gandhics]

You may try to turn on these options.
Another thins is set material/map browser to display text.
Also 2021.2 has material/browser speed improvement.

[gandhics]

After watching the video, I think the thumbnail rendering setting is too high.
Is there any way to adjust by myself?

[^Lele^]

Also 2021.2 has material/browser speed improvement.

Was here an acknowledgement of poor performance from AD, then, for 2021.1?
I'm asking as i found absolutely no trace of said issue, or of the improvement supposed to come with 2021.2.
Do you have a snippet of the changelog, or better still a link? I must be reading the wrong pages.

[squintnic]

id upgrade for better material preview speed!

[gandhics]

Was here an acknowledgement of poor performance from AD, then, for 2021.1?
I'm asking as i found absolutely no trace of said issue, or of the improvement supposed to come with 2021.2.
Do you have a snippet of the changelog, or better still a link? I must be reading the wrong pages.

It was reported by a big studio on beta.
I think they had 20,000 material in the scene or something.
It was not about preview speed.
It is more about the crazy amount of material in the scene or material loaded library.
I personally never had that many material so it was kinda hard to confirm personally.
But, I heard it did great for that studio.

[Oleg_Budeanu]

Is there a setting, where I can change the quality of the preview? I think it would be nice to have, I am ok with noisy previews for some projects, where I am using materials from libraries I am familiar wtih.

[^Lele^]

post #2?

[squintnic]

curious to know if this is a vray bug or a autodesk bug?

[Oleg_Budeanu]

post #2?

It's not what I meant. I like the new preview. It would be nice to have a setting, which will control the noise amount for those previews, making it faster. For example, for mateditor slots it's ok to have more noise (as they are smaller), than for the "double click" previews, where there should be less noise. Thus the material editor previews will render much faster. And if it's needed - you open the big preview, set up the quality and work with the material.

[3d-laboratory]

In my configuration it seems not to be a problem with the render speed in the slots (at least after the first rendering after opening CME), it is a problem with the speed of showing the material parameters which is very slow with VRay materials, but very quick with AutoDESK physical materials. I opened a sample scene with a setup for Arnold from the AutoDESK sample files for MAX2021. The performance in the CME is also slow with Multi/Sub-Object materials. Again quick if you change between physical materials. But the best is: the render setup dialog is quick as in 2019. So at least the slow opening of the render dialog seems to be a problem of the communication between 3dsMAX and Vray 5.
Added 1 week later: Also in AutoCAD I have slow filling of floating windows which slow down workflow....seems to be a graphics driver issue...

[timmatron]

This is my first day using Vray 5.1 and Max 2020....coming from 2014 and Vray 3.6, which has been great, haha. I was loving just about everything until I started using the material editor. This is painfully slow!!!

The slow part is when cycling through maps, not even making any changes. So is this a Max thing?? Ugh.

[3d-laboratory]

Can you tell me something about your hardware. I´m wondering that there are only a few users who seems to have this problem. It is not only about to wait. In my configuration with Max 2021 and VRay 5.1 the CME window dissolves, comes back, dissolves again and so on. Because of the very quick response with the AutoDESK physical material I think the problem is the interface between MAX and VRay. Some people may have powerfull hardware, that the waiting time is not so painful. I thought, i7-3930k at 4GHz with six cores, 32GB Ram, SSD and Quadro P4000 is not bad. But when I changes to Win10 3 months before I has to notice, that also Microsoft again pays no attention, that their new operating system runs at least with the same speed as Windows 7. Ugh....

[timmatron]

Can you tell me something about your hardware. I´m wondering that there are only a few users who seems to have this problem. It is not only about to wait. In my configuration with Max 2021 and VRay 5.1 the CME window dissolves, comes back, dissolves again and so on. Because of the very quick response with the AutoDESK physical material I think the problem is the interface between MAX and VRay. Some people may have powerfull hardware, that the waiting time is not so painful. I thought, i7-3930k at 4GHz with six cores, 32GB Ram, SSD and Quadro P4000 is not bad. But when I changes to Win10 3 months before I has to notice, that also Microsoft again pays no attention, that their new operating system runs at least with the same speed as Windows 7. Ugh....

I have a 1st gen AMD Threadripper 1950X with 64GB and GTX1080. Guess it's almost time for another upgrade!

I rebooted my machine last night and after that the CME wasn't as bad. So I'll keep an eye on it and see if I can tell what triggers it if it happens again.

[3d-laboratory]

Same here, it is quicker if I only have one session 3dsMAX open. But I usually work with two open sessione and one AutoCAD session and also a lot of other programms open, Photoshop etc. Under Windows 7 with MAX 2019 and Vray NEXT I never had a problem. What a waste of hardware all over the world because programmers doesn´t care for the ressources and all is blown up in order to meet security needs.

[^Lele^]

This is a known issue, since max transitioned to Qt controls.
The old windows UI controls we are used to seeing in Max are now translated to Qt equivalents under the hood.
This meant, in one fell swoop, that anything not native Qt would incur a severe penalty (meaning everything in Max but the Arnold Shaders and Render settings. Those are native Qt, and blazing fast.)

There is but one solution to this, and it is redoing the relevant UIs in native Qt, and we are actively investigating this avenue.
I say "investigating", because for the likes of us, supporting back to max 2016, which is a version without Qt, this would mean a lot of extra work, and could mean having to maintain two versions of the builds, and so doubling up work for Qt-enabled and non-Qt-enabled versions each time there is one change.
The likes of Arnold, that support only from the version they first came with -which was Qt enabled-, have a leg up in this respect.
Alas, a solution will be found, and implemented, at some point soon.

Still, other parts of Max are being rewritten to Qt, so there's hope yet that a (much!) quicker workflow is on the horizon.
Just it's going to take some time, and not exactly for lack of trying.

In the while, remember setting the QT driver to d3d9 is the best option to try and mitigate the drawing speed issues.
It's by far the quickest (up to 40%), and unerringly consistent, of the lot, and sadly not the default option (by my reckoning, that's d3d11).
Other than that, as it's mostly single-core action, the quicker a core can boost, the quicker the translation will go, and the UI redraw.