VRay5 silent install xml not taken

[KiboOst]

Hi,

I'm trying to install silently vray5.1.2 for max2022

In my config xml I have:
<Value Name="MAXROOT" DataType="value">C:\3dsMax2022\</Value>
<Value Name="PLUGINS" DataType="value">C:\3dsMax2022\Plugins\</Value>

All paths, command line etc are good (deploy like this for ages, taken the latest vray5 doc for the config file)

But, both for vray5 and phoenix4, plugins are installed into:

C:\ProgramData\Autodesk\ApplicationPlugins\VRay3ds Max2022
C:\ProgramData\Autodesk\ApplicationPlugins\Phoenix 3dsMax2022

How can I got my plugins installed in my C:\3dsMax2022\Plugins\ ?

Thanks

[KiboOst]

Another thing,

phoenixfd.dlr file has not version set, was easy to check version installed to know if need to be updated or not.

[alexander.kazandzhiev]

Hi, from the 3ds Max 2022 on the plugins are packaged in a new format, more details can be found here:
https://help.autodesk.com/view/MAXDE...g_ins_packagin g_plugins_packaging_plugins_html
https://docs.chaosgroup.com/display/...cation+package

The V-Ray plugins now follow the 3ds Max plugins. There are several reasons for this as the one that they are mandatory for V-Ray GPU, VRayScene and VRayPluginNode; also there are some more details about loading plugins' dependencies when they are not besides the main process executable (3dsmax.exe); and finally all the essential V-Ray/V-Ray GPU files are now in one directory, so with the new format they could be moved to another machine fairly simple, but as a whole package.
One can try to put the files in a separate directory. The environment variables VRAY5_FOR_3DSMAX2022_MAIN and VRAY5_FOR_3DSMAX2022_PLUGINS should be set accordingly. Currently this is not well supported and some features may stop working.

On a side note: the installer now can choose between two predefined locations for the application plugins installation and the variable for the .xml is PKGROOT_SELECT with "0" for the all users location and "1" for the users private one.

Best regards,
Alexander

[KiboOst]

Ok, so I guess we have to deal with it and it's not an installer bug ...
Thanks for feedback