Foreword
When you use RCS, you adjust and customize a lot of settings.
It might be helpful to know where it is saved in the following situations:
- deleting a corrupted file
- keep settings when upgrading to a new version
- moving settings to another computer / profile
- force settings through GPO
- ...
Solution
Every adjustment / setting made by the user is saved in the user's profile, in different places.
As files
The files are by default located in some specific folders:
- %APPDATA%\Strategies\<RCS_App_Name>\<Version>
- %LOCALAPPDATA%\Strategies\<RCS_App_Name>\<Version>
- <MyDocuments>\RCS Data
As registry
- HKEY_CURRENT_USER\Software\Strategies\<RCS_App_Name>\<Version>\...
- HKEY_LOCAL_MACHINE\Software\Strategies\<RCS_App_Name>\<Version>\...
When saved as a registry key, the final setting value is set using the following rule:
- If registry key exists in HKEY_CURRENT_USER, use this value
- Else if registry key exists in HKEY_LOCAL_MACHINE, use this value
- Otherwise, use default value
As some settings are used to specify some file / folder location, you should examine these values to have exhaustive knowledge of all the RCS settings locations.
Some examples
User workspace
| Topic | Folder / file location |
| Shortcut bar | %APPDATA%\Strategies\<RCS_App_Name>\<Version>\<xxx>_shortcuts.xml |
| Menu and toolbar definition | %APPDATA%\Strategies\<RCS_App_Name>\<Version>\desktop.ini |
| Keyboard shortcuts | %APPDATA%\Strategies\<RCS_App_Name>\<Version>\hot_key.xml |
Cutting
| Topic | Folder / file location |
| Tools configuration | <MyDocuments>\RCS Data\Config-<Version>\Cutting |
| Cutting filters / options / control colors | %APPDATA%\Strategies\<RCS_App_Name>\<Version>\rx_pre_decoupe_cfig.xml |
| Retroprojection calibration | %LOCALAPPDATA%\Strategies\RCSCUT\<Version>\sc_retro_calib.xml |
| Vision : digital acamera calibration | %LOCALAPPDATA%\Strategies\RCSCUT\<Version>\<Camera_Name>-<Camera_Number> |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article