Why are the material preview spheres such low quality now? It makes it incredibly hard to fine tune glossiness when it’s so noisy like that. Do I have a setting wrong?
I find this, unfortunatelly, quite unfinished part of Vray 5.
Not to mention the speed in slate mtl editor which is frustrating. Was so much hoping this woudl get fixed for final release.
Endless blue spinning wheels, delays and all other ugly stuff too.
Is there a way how to revert to the old preview method please?
Cant find the post where it was mantioned.
One woudl have thought this woudl be a breeze on 3990X but i am having very disappointing experience here.
Settings > System > Native 3ds Max Material Swatches checkbox. I was hoping I had some settings screwed up during the update but if this is how it’s supposed to be that’s pretty disappointing.
now that i ve really plugged Vray 5 into most of the projects i get little quirks all over the place
thanks btw
it doesnt work switching the native 3ds max swatches.
tired restartin max too
We’ve measured the swatches render times and they are not slower than any other renderer. If we raise the quality they will definitely become slower.
Martin, you need to update the swatches (rerender them) after you switch to native. It’s a Max behavior to keep caches of the previous thumbnails and you have to update them manually.
I am really gettgin quite terrible delays trying to work wiuth material though.
In IPR it almostbecomes easier to turn it off and tweka the mat and rerun IPR.
Simply deleting even empty mtl editor view and i get the blue spinning wheel…the mouse poiter gets pixelated, i have to wait 15-20 seconds and then i can work again.
Sometimes every node i touch does this.
needless to say slate material editor is crappy by itself lately, especially in 2021.1
when i switch to regular mtl editor all is running well
@matanov are the shaderball render settings hard coded or are they based on your main vray render settings?
Yea, that’s a a bit disappointing. I would revert to the old preview if I could since this one is almost unusable for materials with blurry reflections. The fact that the swatch rendering happens only on a single CPU thread doesn’t help either. Can Chaos make the preview render on more than one thread? This should allow for much higher quality previews at better speeds, no?
BTW, I found a strange workaround for the problem, but it’s quite cumbersome, and not really useful for everyday use. Right click on the material, click “Open Preview Window” and enlarge it. The more you enlarge the preview window, the more the preview quality of the small swatch at the top of the material increases.
What’s wrong exactly? I still haven’t updated to 2021.1.
How about separate render settings for the material swatches? Tying the materials preview quality to the render quality is not very convenient.
There are a few solid niggles and apparently unavoidable limitations when working with the material editor (it’s twenty-five years old tech, after all).
We’re investigating ways around some of those, but it’s not straightforward.
Since we have some complains about performance issues with that TR generation (still trying to find out if it’s us or there are defective batches), can you please send us a pack of materials that are refreshing slow on your machine and a video demonstrating it? We will compare the performacne with our ThreadRippers.
ok so i ve done some more testing…
installed newest nvidia studio driver and downgraded my WINDOWS 10 PRO 64 bit FOR WORKSTATIONS to regular WIN 10 PRO 64 bit.
So far the slate mtl editor is far better.
i will try upgrading back to WORKSTATION version of WIN to see if something changes again.
Wow. Thanks for the bother.
Not at all, it was actually quite quick.
Not sure youre aware but upgrading/downgrading WIN to WS version takes only 10 seconds. I was actually very upset when i found out about this after i spent 600 bucks for the WIN upgrade.
What it does is that it only activates certain win features like SMP etc.
I had no idea, no.
To me the latest OSes (say, i was last comfy with NT4, perhaps? ^^) seem a bloat-bomb, and often enough have inexplicably blown in my face (no, ofc i must have done something wrong, i know.).
So now that my win10 installation is working, and survived the latest big update unscathed, all i do is use it gingerly for fear of a reinstall.
Personal limit, I’d readily concede.
The latest Windows 10 update - version 2004 has a major SSD/NVMe defragmentation bug which may shorten the lifespan of your SSDs/NVMe’s. You may want to stop automatic defrag on you SSDs/NVMe’s until Microsoft roll out a fix.
anyway, its doing again 
although slightly better.
deleting slate mtl editor view always gives me something like 30 second delay…first i see pixelated mouse arrow and then i get blue spinning wheel…after that the view gets deleted. Looks like this is heavily dependent on whats inside the view. Large material structures tend to be even slower.
I didn’t have that active, but will check if it turned it back on by itself. Thanks for the pointer!
A new, older scene a nd all works well.
i am struggling to understand whatcauses this. Perhaps it will be worth sending the slow one to chaos