Hi team,
I know that RV stores configuration information in the preference file located in the user’s home directory.
We are currently using RV2023.0.2 internally and are in the process of updating to RV2024.2.0.
We would like to use a separate RV.ini file for the RV2024 version, rather than the RV.ini file used in the RV2023 version.
I know that the RV_PREFS_OVERRIDE_PATH environment variable can be used to provide default values for RV preferences, but since the values set by the user already exist on the user’s machine, those values are used instead.
In conclusion, what I want is for each user to have a separate RV.ini file depending on the RV version.
RV2023 → %APPDATA%/TweakSoftware/RV2023.ini
RV2024 → %APPDATA%/TweakSoftware/RV2024.ini
Is there a way to achieve this?
I also tested using the RV_PREFS_CLOBBER_PATH environment variable, but it did not work in my case.
Is there a way to set this in the RVpush command, rather than the RV command?
There does not seem to be any information for this in the rvpush arguments.
Actually, what I am looking for is a way to set the “user preferences file path” such as the RV_PREFS_OVERRIDE_PATH and RV_PREFS_CLOBBER_PATH environment variables.
Looking at this page, it seems that user preferences file path is fixed, but I am wondering if there is a way to set it in the environment variable.
SG uses a custom uri protocol called rvpush://.
Each OS handles this differently, I will take windows as example but the docs do show how to do this on MacOS and Linux too.
By default RV’s installation setup registers the custom URI protocol and points it to a file in the RV installation folder (maybe even just RV.exe).
To change the behaviour you need to point the rvpush uri protocol to a python file on your network or make sure the same file exists on all machines.
In that file you can run your logic to detect what show the RV Launch command is sent from (it’s basically going to get the same info as an AMI, a GET request if you will).
Then your python script will set the correct environment and then launch RV.
I am wondering if it is possible to update it to be set as an environment variable, such as RV_PREFS_OVERRIDE_PATH and RV_PREFS_CLOBBER_PATH.
Implementing the method you suggested would require modifying and updating the protocol on all users’ machines that use RV, which is somewhat complex.
So, I believe that if there was an environment variable with the same role as the -prefsPath parameter, it could be used in a simpler and more intuitive manner.
No the custom browser protocol would point to a script that will then run whatever logic you want.
If you are on a Windows domain network this is prety easy to do via Group Policy, ask your IT department.