Skip to content
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

[Original UE Bug]: does not remember which tabs were open #103

Open
1 task done
JohnCorby opened this issue Feb 13, 2025 · 2 comments
Open
1 task done

[Original UE Bug]: does not remember which tabs were open #103

JohnCorby opened this issue Feb 13, 2025 · 2 comments
Labels
bug Something isn't working

Comments

@JohnCorby
Copy link

JohnCorby commented Feb 13, 2025

Are you on the latest version of CinematicUnityExplorer?

  • Yes, I'm on the latest version of CinematicUnityExplorer.

Which release are you using?

BepInEx IL2CPP

Which game did this occur on?

Outer Wilds, specifically using this fork (simple wrapper around standalone)

Describe the issue.

the original unity explorer used to remember which tabs were open and which were closed when restarting the game.
a few versions ago (again, in the original version), it stopped doing that, but only for logs and clipboard (they are always initially open).

i see data.cfg stores window positions and a boolean that i assume is "is this tab open?" but all of the booleans appear as False.

Relevant log output

no relevant stack traces or errors relating to unity explorer. UE logs just has normal startup logs, no exceptions. same with player log
@JohnCorby JohnCorby added the bug Something isn't working label Feb 13, 2025
@originalnicodr
Copy link
Owner

Mmm, this is odd. Is there a way you could try older releases of CUE to check if the problem was still present then?

My mind goes to code specific to the standalone version since I don't recall this being a problem in bepinex or melonloader? So maybe it is worth checking the code specific to that.

@JohnCorby
Copy link
Author

JohnCorby commented Feb 14, 2025

i remember this happening even in the original fork, before i switched to CUE, and yeah in the standalone version. dont specifically remember which version tho

i could try using the bep version of latest and see if it still happens

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants