Hey guys,
I have a problem here where Max 2022 does not save the position of the windows (material editor, render settings, environment dialog etc.)
After each start of 3dsMax, I have to rearrange my windows to the desired layout.
Also, Max does not save certain settings from the preferences window. For example, I disable the selection highlight preview. After the next start, that feature is enabled again.
They are contractually obliged to break stuff when they bring out a new version 
I did notice the highlight preview thing…just thought it was me forgetting something or it crashing…that is annoying indeed.
However, you can edit the .ini to stop it.
It’s in AppData/max22…
Yay 
It seems something is wrong with the .ini itself, because that is where the window positions ought to be stored.
Also, this is happening on more than one machine, so we hope it is not a fault on our end.
I would guess that for whatever reason it’s not writing everything to the ini. on exit.
Which is a bit basic really…but I’m sure they’ll fix it at some point.
It’s definitely not your end problem, as mine was doing the same.
EDIT: I tested a few panels and it’s clear that some settings, or rather, some particular panels’ settings, are saved and others not.
So the viewports one doesn’t save, nor does the gamma/lut…couldn’t be bother to test every one.
I saw you posted to the forum so hopefully it gets actioned asap.
Meanwhile, a bit of a pain I guess, but you can edit the ini by guesswork for positioning…at least it saves that, so you only need to do it once
Yeah, eventually. Like they fixed that double-click bug in the render settings window…
did you try to run max as admin and see if it is any different?
I hadn’t but I did…no change
Running as Admin made no difference.
I tried to investigate the issue by comparing the .ini of Max 2021 and 2022.
The issue can be fixed to the material editor window by copying the values. The material editor window is in the correct position, then.
I tried to do the same for , but there is no such entry in the .ini of Max 2022.
Also, I made this observation:
- open the render dialog, window pops up in the middle of screen 1
- position the render dialog window somewhere else, close the window
- open the render dialog again, it will pop up in the middle of screen 1
So it will not remember its position in the current session?!?
Also, this is happening on all our machines in the office as well as my workstation at home.
Hmm…render dialogue position is in my ini…
MainWindow=1491 363 560 1451
OptionsWindow=23 267 513 911
ZoomLevel=2
DimensionQt=482 762 831 1078
It’s not on our side. Tried pasting the values, but then the window is still popping up on screen 1 instead of screen 2.
Well that is weird in itself. I presumably have the exact same install files for 22 as you do, so something seems to have gone wrong with your installs maybe…
I’m sure there is an answer…just what it is I can’t figure out atm 
On 6 different workstations? That would be weird.
It really would…doesn’t make sense that my ini has different entries.
Is it maybe some permissions issue? I know when I was trying to update some plugs it wouldn’t allow me to, as everything was read only.
A long shot but you never know.
The users are admins on all their machines.
its not just by the positions, its settgins like snaps, units etc.
looks like max is not saving ini or something
There is a reply from on of the support people over at the beta forums. They admit it is an error: "Hi Oliver, thanks for looking deeper in this issue.
I can reproduce the material editor and Render Setup windows not preserving their position on secondary monitor between different session of 3ds Max".
FFFF… Fantastic.
Render dialog issue is different. If you use only one umtra wide monitor like me. It works.
But, if you use multiple monitor, it cause issue.
It is a bug from the particular version of Qt, 5.15.
This will require 3dsMax dev update their Qt version.
There is a solution to the preferences not being saved upon exit: Uninstall V-Ray. No joke, it works.
Re-install V-Ray, problem is present again.
A bunch of folks in the forums thread on the Autodesk site have noted that uninstalling Vray fixes the issue. Hmm.
Alfred, that was me.