-
Notifications
You must be signed in to change notification settings - Fork 9
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
[Bug]: libunity.so stripping breaking games #8
Comments
the same issue happens with Gods of gravity on the quest 2 on and before v51, these logs are a bit old becuase i've deleted my newer ones but its still the same issue. I'll upload newer logs when i get the chance |
this does work on versions of the game that were compilied with no stripping though |
@TrevTV |
I haven't messed with Unity-project-side stuff too much with this, but I believe disabling Strip Engine Code would fix it. |
having the same issue in Dictators: No Peace :^(
|
@amir16yp That doesn't look like a stripping issue, that looks like the initial issue that Muse Dash had. If you replace the If it crashes after that, it's likely actually the stripping issue. |
now i get the different error and the game crashes before getting into the main menu
|
I've never actually seen that before, but I'd assume it's crashing if it doesn't support that Unity version, like the error says. |
Any progress made on this or is it just an “I have no idea where to begin” issue? |
All of the following criteria must be met
Latest.log
file included. If no file exists then leave this unchecked and state so.All of the following are optional to answer
Describe the issue.
Replacing libunity.so with the one from the Unity deps repo can sometimes lead to stripping errors that break the game. Not replacing the file leads to constant errors.
Honestly, I have no idea how this part works and what I would need to do to solve it, so I wouldn't expect anything anytime soon.
Known Effected Games:
Did you attach your log file?
/storage/emulated/0/Android/data/<package name>/files/melonloader/etc/Latest.log
The text was updated successfully, but these errors were encountered: