timamsk/OpenCore-Legacy-Patcher
1
0
Fork 0
mirror of https://github.com/dortania/OpenCore-Legacy-Patcher.git synced 2026-06-20 22:20:53 +10:00
Code Issues Packages Projects Releases Wiki Activity

Slight rewording

Browse Source
This commit is contained in:
neon ball
2024-11-02 11:35:59 +02:00
committed by GitHub
parent 7ac83d8dd6
commit ed0e3ff66a
1 changed files with 6 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/FAQ.md
+6 -2
View File
@@ -32,11 +32,15 @@ Refer to [Updating OpenCore and patches](https://dortania.github.io/OpenCore-Leg
## Why are the settings "not saving"? ## Why are the settings "not saving"?
Starting with OpenCore Legacy Patcher 2.1.0, settings will now be saved under ```/Users/Shared/.com.dortania.opencore-legacy-patcher.plist```. The application will utilize this file to keep track of settings, no longer requiring a reconfiguring after each update. The user interface will reset if any model other than "Host Model" is selected, as building for a different model will require different settings. Starting with OpenCore Legacy Patcher 2.1.0, the status of settings in the GUI will now be saved under ```/Users/Shared/.com.dortania.opencore-legacy-patcher.plist```. The application will utilize this file to keep track of settings, no longer requiring a reconfiguring after each update. The user interface will reset if any model other than "Host Model" is selected, as building for a different model will require different settings.
In case of issues, delete the file to revert the GUI to default settings. In case of issues, delete the file to revert the GUI to default settings.
* Note: Only settings made within OCLP are accounted for, modifications made directly into the ```config.plist``` file outside of OCLP **will continue to reset**. ::: warning
Only settings made within OCLP are accounted for, modifications made directly into the ```config.plist``` file outside of OCLP **will continue to reset**. Additionally, modifying ```config.plist``` manually may lead to a state where settings showed in the GUI are not in sync compared to settings in use, due to the application not knowing whether the file has been manually modified.
:::
::: details Explainer for older versions (click to expand) ::: details Explainer for older versions (click to expand)