topic Re: Old shaders and maps setup UI is not fully visible in SME in 3ds Max Forum

Old shaders and maps setup UI is not fully visible in SME

kirgiz81 — Sat, 17 Aug 2024 16:48:03 GMT

My setup:
43' 4K TV as monitor
CPU AMD 3900X
GPU: RTX 2060 Super Turbo + RTX 3080 Turbo
Clean install of Windows 10

The problem

In SME setup interface of old materials (such as "Blend", "Standard (Legacy)" and maps (all from "General" section: "Bitmap", "output"... except "Advanced wood") is not fully visible/reachable.

Other maps and shaders appearance is fine.

I had this problem with 2024 and 2025 3ds Maxes, and with last Windows 10 and 11 all clean installs of both OS and 3ds. No plugins.

The problems goes away with font scaling 150% in Windows, but I need 100% as I have large TV as monitor.

I tried every Autodesk recommendations about scaling - they didn't work

I mean this one: https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/DPI-scaling-using-4K-monitors-is-wrong-or-not-working-properly-using-newer-versions-of-3ds-Max.html

I reinstalled Windows 10 several times, creating boot flash with two methods: 1) using MediaCreationTool, 2) Using Rufus.

Second (Rufus) setup helped - clean installed 3ds Max's SME had no problem with UI, but after some time - the problem came back. With Windows10 installed with MediaCreationTool - the problem in 3dsMax was from the start.

Each Windows install was with formating drive C, and with latest OS version from Microsoft.

P.S. Checked 2023. No problem with it, coming back to old version.

Re: Old shaders and maps setup UI is not fully visible in SME

Byteman — Sun, 18 Aug 2024 15:05:07 GMT

It has been mentioned in the forums recently. It is about encoding type setting in Windows.

Keep the "Use Unicode UTF-8...." checkbox unchecked. At the expense of losing your non standard characters in non-unicode programs.

Re: Old shaders and maps setup UI is not fully visible in SME

kirgiz81 — Mon, 19 Aug 2024 02:15:42 GMT

Byteman Enormous thanks to you!

My "Current System locale" settings was changed, now with English it's all good!

Re: Old shaders and maps setup UI is not fully visible in SME

shaimukhanbet — Mon, 06 Jan 2025 15:03:51 GMT

It didnt work for me.

Re: Old shaders and maps setup UI is not fully visible in SME

Byteman — Mon, 06 Jan 2025 17:01:17 GMT

Please double check the setting, because that part of Windows is prone to exiting without applying the setting change.

If the problem still persists, check the settings around fonts and screen scaling, dpi etc. This happens due to font width mismatch.

Re: Old shaders and maps setup UI is not fully visible in SME

sevil_dcs — Thu, 12 Jun 2025 17:38:29 GMT

perfect it worked

Re: Old shaders and maps setup UI is not fully visible in SME

tblancoX5EZX — Tue, 08 Jul 2025 19:39:56 GMT

I'm having the same issue with Max 2025. Max 2023 works fine. I followed all the steps in this thread and another thread (https://forums.autodesk.com/t5/3ds-max-forum/problem-window-setting-are-cut-inside-slate-material-editor/td-p/12027593), but none of the solutions have worked. Even when I undock the menu, it will not let me extend it or scroll to the side that is being cropped off.

Re: Old shaders and maps setup UI is not fully visible in SME

infoTDTXZ — Tue, 09 Sep 2025 08:10:05 GMT

The Accepted Solution did not work for me either. Nor did the Compatibilty Settings around high DPI. I can't really use the material editor this way. This is not acceptable for such a high price product. Any updates regarding this?

Re: Old shaders and maps setup UI is not fully visible in SME

tim_panopio — Tue, 10 Feb 2026 09:17:36 GMT

Hi, I was wondering if anybody has a solution for @tblancoX5EZX and @infoTDTXZ?

Honestly, I have the same problem similar to theirs, hoping someone has a solution to this?

Re: Old shaders and maps setup UI is not fully visible in SME

Byteman — Wed, 11 Feb 2026 14:58:30 GMT

@tim_panopio @infoTDTXZ @tblancoX5EZX

The culprit of this shift in UI elements is essentially the size of the font used on that part of the UI, one most probable reason is the encoding type, I strongly suggest checking any software that might be responsible for the font sizing.