bonkmaykr/firestar
bonkmaykr/firestar
2
1
Fork 0
Code Issues 3 Pull Requests Packages Releases 6 Wiki Activity
Page: Troubleshooting
Pages
Creating Mods Decrypting Original PSARC Files Home How to Use Firestar Installing Mods to Decrypted Game Folder Manually Repacking a PSARC Setting Up Repatch Reloaded Troubleshooting Using FScript
14 Troubleshooting
Downforce Agent edited this page 2024-10-03 19:23:21 -04:00
Table of Contents

WipEout crashes at a certain spot repeatedly

This usually indicates that your original PSARCs were not dumped correctly, and as a result, there are important files missing from the PSARC generated by Firestar.
Please see: Decrypting Original PSARC files

"psarc error: Invalid header (bad magic number)"

This error message means that your original PSARCs were not dumped correctly. If you try to install mods this way, your game will break.
Make sure you decrypted your game before giving it to Firestar. Please see: Decrypting Original PSARC files

"The file is corrupted" when trying to launch WipEout

You aren't supposed to replace the original files, that method will only work on the Vita3K emulator. PSVita games are encrypted and writing over them directly will corrupt them.
Use the Repatch Reloaded plugin to load your mods. Please see: Setting up Repatch Reloaded and then How to Use Firestar

Oh, and make sure to backup your save file and then reinstall your game, since you did just completely cook the PFS partition this is the only way to fix it. Be more careful next time! ;)

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.

"CRITICAL FAILURE" at the very end of the Deploy process

Make sure you have write permissions on the folder you export your mods to.
If it is on an external drive, make sure it is mounted and it is not read-only.

"The BROWSE action is not supported on the current platform" when using the Help menu

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 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

Home