-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
shaber ipa patch fails #5
Comments
This seems to be caused outside of ShellSaber, and could be to do with BSIPA-Linux. Could you please send what you have in your ShellSaber config file, and a list of the contents of |
ShellSaber config:
Here's the contents of the directory:
Also, if the issue is in BSIPA-Linux, what would be the next step to finding a solution? Thanks for replying so fast! |
As a final check, please could you copy |
Yep, same error. Thanks for the help, I'll post an issue over there. |
Hold on, you need to set up a config file -- you sent me the default |
Copy the default config file to |
That actually is the correct directory, when I installed my OS i linked |
Ah that makes sense then. Please do go ahead and file an issue at geefr's repo! I'll keep this one open in case it is my fault :) |
As a quick note, @businessfish, just run |
Reopening because it seems something weird is happening with enabling BSIPA... |
Looks like you say my post on the other issue. After downloading/updating BSIPA with shaber, attempting to do the patch fails like so:
I watched the my beat saber folder while it ran, and it successfully created the IPA directory but failed after, I guess. |
Along with sending the logs for |
I don't need the patch log, since that isn't the problem. |
|
You need to run |
|
Was never properly installed so it is unhappy. Run |
Looks like that might have done it |
That's all gone well now! I'm very confused as to how it ended up broken in the first place... Perhaps you had the directory incorrectly set the first time around? There's not really anything more I can do to prevent this, since we don't know how to reproduce it. You should have a fully patched Beat Saber install now :) Please make sure to post a new issue if you encounter any more bugs. I'm also frequently updating ShellSaber, so make sure to watch this repo or regularly check back for updates! |
Thank you! I'm pretty sure that I'm just an idiot and deleted that directory at some point in an effort to reinstall it from a clean slate. So maybe not a bug but more of an idiot-proofing issue |
Haha! I will be working out how to make the script handle that sort of issue when removing and disabling so as to not error out, but I can't really do much to stop people from deleting their Beat Saber directory... |
Describe the bug
shaber ipa patch seems to be expecting the unity data patch and engine files to be in a different location.
Steps to reproduce the behavior:
run shaber ipa patch
Expected behavior:
should properly find the unity files its looking for
Logs:
System info:
Distro: 5.4.89-1-MANJARO
Beat Saber version:1.13.2
Additional context:
I tried to go into the script and manually change where it expects those files/directories to be, but it seems like that action takes place in the IPA-Minimal binary, called on line 675:
"$ipa_native_dir/IPA-Minimal" "Beat Saber.exe" -n -f --relativeToPwd
It looks like the directory with that engine file in it is
/data/fish/.local/share/Steam/steamapps/common/Beat Saber/Beat Saber_Data/
on my machine and not what it expects.The text was updated successfully, but these errors were encountered: