Chaos Corona for 3ds Max > [Max] Resolved Bugs

Serious MAX freezes while using slate material editor

(1/3) > >>

Ink Visual:
Hi,
In some of our files slate material editor is often freezing 3ds max for 3 minutes or so.
Opening the slate material editor itself can also last ages - 3-5mins.
Editing simple materials and applying them to objects in the scene can also cause lag, or freeze max completely.
This however does not happen with compact material editor, files are perfectly usable while using it.

Anticipating questions,
-this happens even if material editor is cleaned of all the materials.
-merging all the objects to the new scene does not help.
-merging files in groups to identify the problem didn't give us much of a success,
we think the issue might be associated with some scatters/proxies/shaders brought from the older scenes that were using older Corona versions,
but we could no identify particular cause of the above

We use Max 2019 (in Max 2021 problem is still present), Corona 6 Hotfix 1

Can you please help us to identify the problem?
I am just about to archive the scene for you as well as provide the dump file.

Thanks in advance

Maybejensen:
Following this thread. I have the same problem..
 I avoid slate as much as I can these days. Feels like it's slowing me down instead of increasing productivity.

pokoy:
One idea - if you are using distance maps in your scene, maybe they are being updated in the background by Slate. Make sure to *not* display scene materials in the Slate browser, maybe this helps.

There are performance issues with Windows UI scaling, too. If you are using it, see if changing it to 100% helps.

In general though, Slate is going crazy with the internal notification system and that's what is making it slow in general.
Slate's material/map browser is really slow here. I can't use Slate on our heavy assets, literally *any* change to a material which involves the Slate browser - assigning or changing maps or materials - takes minutes.
Autodesk is aware of this since quite a few years, pages of reports and discussion have been going on for a really long time. There were some attempts to improve this in 2021 and 2021.3... but still, the old material browser is much much faster.

One Autodesk dev suggested to :

-close Max
-open 'SME.ini 'located in 'C:\Users\YOUR_USERNAME\AppData\Local\Autodesk\3dsMax\2020 - 64bit\ENU\plugcfg_ln'
-change the line 'LibSceneMtlOptionFlags' from its current value to '0'

and see if it helps... in my case it made no difference whatsoever.

Like I said, the problem is not going away probably unless SME 2.0 is there. How long will this take... years, probably.

BTW, you can still use the old material browser, maybe this helps. Try it out by changing 'UseOldMtlBrowser' to '1' in the same ini file.

If you want to see a change, report it as a bug, make sure to post on the Area etc. Most rendering devs have not much experience in using Max in a production environment, or are long gone from any production role, and simply have no idea how much it slows down people and make working impossible for some.

pokoy:
Just stumbled over this:

https://forums.chaosgroup.com/forum/chaos-common/chaos-common-off-topic/1101103-3dsmax-2021-material-editor-rollout-s-l-o-w

and this:

https://knowledge.autodesk.com/support/3ds-max/troubleshooting/caas/sfdcarticles/sfdcarticles/3ds-Max-UI-lags-or-seems-sluggish-even-on-very-fast-multi-core-CPUs.html

Not sure it's helpful, it's more like Autodesk is realizing there actually *is* a problem and no real solution.

Ink Visual:
Many thanks for all the tips Pokoy,
I do hope SME 2.0 will bring some positive change, as it seems to be becoming our day-to-day issue hugely affecting production speed.
I will try using the methods you posted links to. Some of them I have already tested, unfortunately without much of a change.

In the meantime, I have sent the problematic scene and the dump file via dropbox uploader.
Here are file names:
1789_slate_material_issue
1789_slate_material_editor_dump

My main aim however, is to identify what in particular does cause the problems I described.
Some of our scenes work just fine, even with more complicated nodes, the SME is not the fastest but we do not experience excessive lags or freezes,
The scene that I'm referring to though, is an extreme example of the file that is simply impossible to work with when SME is open.

Navigation

[0] Message Index

[#] Next page