From a36bb1704dd9616266290640c72e0d38ca407d7c Mon Sep 17 00:00:00 2001 From: Downforce Agent Date: Sat, 22 Feb 2025 12:43:37 -0500 Subject: [PATCH] Update Troubleshooting --- Troubleshooting.md | 24 +++++++++++------------- 1 file changed, 11 insertions(+), 13 deletions(-) diff --git a/Troubleshooting.md b/Troubleshooting.md index 5707b44..cf149fb 100644 --- a/Troubleshooting.md +++ b/Troubleshooting.md @@ -15,10 +15,6 @@ Oh, and make sure to backup your save file and then reinstall your game, since y ### The game loads correctly but my mods don't work Make sure your mods were not disabled in Firestar when you deployed them, your Repatch_ex kernel plugin is loaded, and that the path to the file is correct. If you just installed Repatch, your Vita may need to be rebooted. -### I can't find the exported PSARC file / The exported PSARC file has a strange name -Ensure that the export destination you typed out has a slash at the end. -This quirk will be fixed in Release 1.3. - ### Linux: Firestar is stuck on "extracting data.psarc..." WINE probably opened a dialog in the background asking you to install the Mono runtime, dismiss it and everything should continue as normal. @@ -32,13 +28,15 @@ This is an issue with your Java Runtime. Try upgrading to a newer Java version. ### My source PSARC is missing from ~/.firestar/ after using the auto-downloader Make sure you have the [Visual C++ 2012 libraries](http://www.microsoft.com/en-au/download/confirmation.aspx?id=30679) installed. -### The team select screen looks funny! -This is caused by a rare combination of conflicting files plus missing one or two PSARCs, especially if you have the base PSARC dumped but not any patches. Notably, if you are missing data1.psarc but have all of the others. - -For Firestar version 1.2 and older, where protections against this sort of thing don't exist, your best bet is to either remove extra PSARCs you aren't using or to add all 5 of them. Either method will make sure that none of your files revert to their launch day variants. - -### My mods keep moving themselves around in the priority list! -This is a bug in Firestar 1.2 and older, which is caused by bad alphanumerical sorting of the index file when the size of the list exceeds 10 mods. We didn't notice the issue until 1.3 because at the time there simply weren't that many WipEout mods in existence. Upgrade to 1.3 to solve this problem. - ### Linux: Fonts look ugly -This is a conflict with some X11 window managers due to the Java framework we use for UI rendering. We don't know what causes it. If you find out what the issue is, please post it here: #10 \ No newline at end of file +This is a conflict with some X11 window managers due to the Java framework we use for UI rendering. We don't know what causes it. If you find out what the issue is, please post it here: #10 + +### (Legacy) I can't find the exported PSARC file / The exported PSARC file has a strange name +Ensure that the export destination you typed out has a slash at the end. +This is only an issue for Firestar 1.2 or older. Please update to the newest version. + +### (Legacy) The team select screen looks funny! +This is caused by a rare combination of conflicting files plus missing one or two PSARCs, especially if you have the base PSARC dumped but not any patches. Notably, if you are missing data1.psarc but have all of the others. For Firestar version 1.2 and older, where protections against this sort of thing don't exist, your best bet is to either remove extra PSARCs you aren't using or to add all 5 of them. Either method will make sure that none of your files revert to their launch day variants. + +### (Legacy) My mods keep moving themselves around in the priority list! +This is a bug in Firestar 1.2 and older, which is caused by bad alphanumerical sorting of the index file when the size of the list exceeds 10 mods. We didn't notice the issue until 1.3 because at the time there simply weren't that many WipEout mods in existence. Upgrade to 1.3 to solve this problem. \ No newline at end of file