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

Multiple branches conflict with each other #2294

Closed
ywgATustcbbs opened this issue Mar 6, 2025 · 4 comments
Closed

Multiple branches conflict with each other #2294

ywgATustcbbs opened this issue Mar 6, 2025 · 4 comments
Labels
Status: to verify Issue is currently not verified by trusted user Type: bug

Comments

@ywgATustcbbs
Copy link

ywgATustcbbs commented Mar 6, 2025

Are you on the latest version of Nitrox?

Yes, I'm on the latest release of Nitrox.

Which OS are you playing on?

Windows

On which platform did you buy Subnautica?

Steam

Describe the issue.

  1. build master, run
  2. build another branch, run
  3. one of them fails to luanch multiplayer game (stuck at the warnning screen)
    See video proof

https://1drv.ms/v/c/435ac0427bc6e131/EUYhonxzlAxNghjuVlRRRX0BYJfyXDd4-6NMFA8VvyXeUg?e=KrOxak

Describe the steps you took to encounter the bug.

No response

Relevant log output

No response

@ywgATustcbbs ywgATustcbbs added Status: to verify Issue is currently not verified by trusted user Type: bug labels Mar 6, 2025
@oliver408i
Copy link

I don't see why any end user would be doing this. I find that you typically need to clear your subnautica_data's Managed folder when changing Nitrox versions or back to singleplayer.

@ywgATustcbbs
Copy link
Author

ywgATustcbbs commented Mar 6, 2025

There is a case where an end user might want to build a latest commit containing major bug fixes rather than waiting months or years for the next release, like me, since downloading vs and repo and build it is just a few clicks (while unfamiliar with how the project is organized).

@OhmV-IR
Copy link
Contributor

OhmV-IR commented Mar 6, 2025

There is a case where an end user might want to build a latest commit containing major bug fixes rather than waiting months or years for the next release, like me, since downloading vs and repo and build it is just a few clicks (while unfamiliar with how the project is organized).

The github versions of the mod are NOT supported under any circumstances, we don't provide support for these versions because they are not considered end-user ready. I would recommend following the usual steps of verifying game files, cleaning the build and then rebuilding but if that doesn't work, please just use the tested 1.7.1.0 version of the mod from the normal website, yes it has a lot of bugs but at least they're known and there are a variety of workarounds available in the discord.

@Jannify
Copy link
Member

Jannify commented Mar 7, 2025

since downloading vs and repo and build it is just a few clicks (while unfamiliar with how the project is organized).

Since all devs (and testing staff) don't really encounter this bug, I think this is a problem on your end/setup. From experience: having to clean the project dir or subnautica's managed folder is normal from time to time.
While we encourage issue reporting and helping from people outside the dev team (see #2278), we can't provide extensive support for people wo don't know how to use these tools

@Jannify Jannify closed this as not planned Won't fix, can't repro, duplicate, stale Mar 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: to verify Issue is currently not verified by trusted user Type: bug
Projects
None yet
Development

No branches or pull requests

4 participants