Jump to content

You're browsing the 2004-2023 VATSIM Forums archive. All content is preserved in a read-only fashion.
For the latest forum posts, please visit https://forum.vatsim.net.

Need to find something? Use the Google search below.

Unable to save settings


Alessandro Brown
 Share

Recommended Posts

Alessandro Brown
Posted
Posted

I am unable to save changes to 1.3.10 preferences. I am trying to add the path to my CSL packages, but the changes are not saved once restarting the sim.

I am running Beta 9 with xPilot 1.3.10; the issue occurs with both OpenGL and Vulcan.

Link to comment
Share on other sites

Justin Shannon
Posted
Posted

Can you try adding your CSL path then close X-Plane and look in the xPilot plugin Resources folder (X-Plane\Resources\plugins\xPilot\Resources) and look to see if there is a Config.json file. If there is, open it with a text editor and check if your CSL path is defined. 

Controller (C3), Los Angeles ARTCC
Developer: xPilot, vATIS

Link to comment
Share on other sites

Alessandro Brown
Posted
Posted
17 minutes ago, Justin Shannon said:

Can you try adding your CSL path then close X-Plane and look in the xPilot plugin Resources folder (X-Plane\Resources\plugins\xPilot\Resources) and look to see if there is a Config.json file. If there is, open it with a text editor and check if your CSL path is defined. 

There is no .json file

Link to comment
Share on other sites

Justin Shannon
Posted
Posted
17 minutes ago, Alessandro Brown said:

There is no .json file

Sounds like something is blocking access to write the config file, could be a permissions issue. Can you upload the X-Plane log.txt to a file sharing website, such as Google Drive. 

Controller (C3), Los Angeles ARTCC
Developer: xPilot, vATIS

Link to comment
Share on other sites

Alessandro Brown
Posted
Posted
1 hour ago, Justin Shannon said:

Sounds like something is blocking access to write the config file, could be a permissions issue. Can you upload the X-Plane log.txt to a file sharing website, such as Google Drive. 

It was a permission issue, I got it sorted!

Link to comment
Share on other sites

 Share