How to launch SpaceClaim using a specific user settings file (.config)
I tried launching SpaceClaim/Speos in batch mode using the option /DefaultUserSettingsFile
"C:\Program Files\ANSYS Inc\v221\scdm\SpaceClaim.exe" /AddInManifestFile="C:\Program Files\ANSYS Inc\v221\Optical Products\SPEOS\Bin\SpeosSC.Manifest.xml" /DefaultUserSettingsFile="C:\Users\gmoysan\OneDrive - ANSYS, Inc\Support\userGMN.config"
However, my settings are not taken into account:
I expect SpaceClaim to be launched with the option "Axes" unticked as specified in my userGMN.config file:
<ImportProcessing> ... <ImportObjectNames>true</ImportObjectNames> <ImportPoints>true</ImportPoints> <ImportPlanes>true</ImportPlanes> <ImportAxes>false</ImportAxes> <ImportCoordinateSystems>true</ImportCoordinateSystems>
But "Axes" is still ticked in the SpaceClaim Options > File Options > General > Import Options:
What am I doing wrong ?
Answers
-
@Gwenaël Moysan can you also share what's in userGMN.config ?
0 -
@Charly Meyer Line 952 in the config file false (I exported the settings from the SpaceClaim Options > Advanced > Export User Settings
4 -
@Charly Meyer Here is the config file I used: userGMN.config
0 -
You can create an environment variable called
SpaceClaim_ADMIN_CONFIG
It should point to the fully qualified file name, in your case
SpaceClaim_ADMIN_CONFIG = "C:\Users\gmoysan\OneDrive - ANSYS, Inc\Support\userGMN.config"
It also can be a network path.
But you have to delete under %APPDATA%/Local/SpaceClaim all settings that it will be used. Then, you can add changes to you own preferences. Maybe this is also the problem why your current configuration/test is not working. I never used the way which you suggested, but I used successfully the environment variable.
See
https://ansyshelp.ansys.com/account/secured?returnurl=/Views/Secured/corp/v221/en/spaceclaim/Discovery/user_manual/advanced_options.html?q=SpaceClaim_ADMIN_CONFIG
section: How to create a universal user settings file2