Skip to content

Commit 779fdfb

Browse files
authored
Update README.md
Clean up the readme
1 parent 18ab41b commit 779fdfb

1 file changed

Lines changed: 2 additions & 5 deletions

File tree

README.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,8 @@ Troubleshooting
6060
To get the highest chance of success, you should always run the patch on a clean install of Unity. If that doesn't work, you can try:
6161

6262
* Resetting your user preferences either manually or by calling [`EditorPrefs.DeleteAll()`](https://github.com/aevitas/unity-patch/issues/17#issuecomment-592070343)
63+
* On MacOS Unity might be displaying a mix of Dark and Light Themes after patching. This can be resolved by restarting Unity. After restarting Unity the Theme should display correctly.
64+
* If you get `command not found`, try changing permissions for the file by running `chmod +x Patcher`. If running the patcher again gives you the following error `Can not patch the specified file - it is marked as read only!` then you need to check Unity to ensure you have write permissions for the `Unity.app` file as well.
6365

6466
Issues
6567
======
@@ -81,8 +83,3 @@ For example, on Linux you would run:
8183
or on Mac:
8284

8385
`sudo ./osx-64/Patcher -e=/Applications/Unity/Hub/Editor/<VERSION>/Unity.app/Contents/MacOS/Unity --mac --t=dark`
84-
85-
**NOTE:**
86-
On MacOS Unity might be displaying a mix of Dark and Light Themes after patching. This can be resolved by restarting Unity. After restarting Unity the Theme should display correctly.
87-
88-
If you get `command not found`, try changing permissions for the file by running `chmod +x Patcher`. If running the patcher again gives you the following error `Can not patch the specified file - it is marked as read only!` then you need to check Unity to ensure you have write permissions for the `Unity.app` file as well.

0 commit comments

Comments
 (0)