Needing a little bit of help with an issue I am experiencing with 3DS Max - 2022 and 2021…
See the image attached.
Basically every time I start up 3Ds Max, i have these error: Missing Vray greyed out warnings. They compound ontop of each other after I close and open 3ds max.
I can get rid of them by going to Customize User Interface: Quad Tab - Right clicking and deleting each of the missing errors.
The problem is that A: This is not working as intended - B: Its cumbersome and slow and multiplies each time I close 3ds Max and it also shows up in the viewport selection tab as missing vray etc.
I have done the following -
Reinstalled 3ds max 2022 from the ground up - Removed all plugins from the computer etc - Fresh install of 3ds max 2022 and vray - First open after install, everything is fine. Close max, reopen and boom, the missing vray windows are back.
Removed the ENU Folder to reset plugins - works initially but ultimately reverts back.
My theory is that the plugins are having an issue loading from the script start up folder located under the appdata path - C:User/Appdata/local/autodesk/3dsMax/*Version*/ENU/Scripts/Startup
If anyone has any suggestions send them my way please!
Hi, I am pondering on this, but still can’t figure it out.
The Startup scripts shouldn’t be the reason to mess it as they shouldn’t be making the items go missing if not loaded. They can however be adding new entries in the menu, but the V-Ray’s install scripts are normally running once after an installation.
As of the moment can you tell me on this machine that reproduces it are there these files present:
1) “C:\Program Files\Autodesk\3ds Max 2022\en-US\UI\MaxStartUI.mnux”
2) “C:\ProgramData\Autodesk\ApplicationPlugins\VRay3dsMax2022\scripts\vrayinstall.txt”
OK, the vrayinstall.txt should be deleted after the first run. But even if it’s not it will just trigger the menu re-install so it shouldnt be causing the issue itself. I guess the problem is that the items are listed as missing on the next run and the re-install cannot recognize them. But why could they be is still a mistery
Seems like if the directories somwhere on the path to the macroscripts are hidden it prevents the loading too. E.g. the full path on my machine is “C:\Users\akazandzhiev\AppData\Local\Autodesk\3dsMax\2022 - 64bit\ENU\usermacros” and just making the “Autodesk” directory (only it) hidden prevents loading.
For some reason we had a machine here that was having the “Autodesk” and “3ds Max” directories hidden. So can you check all directories along the path?
Yes and then we’ve tried it with two other machines here. It also seems to be a new thing implemented in 3ds Max 2021/2022, so I hope it will help in your case too.
So I checked the files you mentioned, everything was fine.
I looked into the autodesk forum link and it seemed that the files for my user account were not given proper access - C:\Program Files\Autodesk\3ds Max 202X: at this location. I followed their steps and made sure the user account and admin account had the right access and now all seems good! I closed max and reopened several times and all is good!
I am using Windows 11, so I am not sure if this is by design or just a W11 problem, but the user profile AppData folder is hidden by default since years under Windows. So all user macroscripts get blocked in my case and it seems for others too.
I moved the script usermacros folder from it’s original location up to the Autodesk folder in the homefolder, which fixed the problem.
From here…
%LOCALAPPDATA%\Autodesk\3dsMax\2023 - 64bit\ENU\usermacros
to
%USERPROFILE%\Autodesk\3ds Max 2023\ENU\usermacros
The %USERPROFILE%\Autodesk\3ds Max 2023\ directory is there anyways and there are no hidden folders in this path.
Sorry for the necropost but I’ve been trying to figure this out all week and finally got it. I’m on Windows 11 and 3dsMax 2024, the steps I used to fix it were:
Open command prompt (as admin if it isn’t working)
cd %USERPROFILE% (to navigate to your user folder)
attrib -h AppData (to unhide AppData)
cd AppData (change directory to appdata folder)
attrib -s Local (remove the system attribute from the Local folder)
Not sure why this is a thing, but it works for me now. If the steps above don’t work just check every directory along the path to your ENU folder for h (hidden) or s (system) attributes (by typing attrib /d to list directory attributes)
