-
Notifications
You must be signed in to change notification settings - Fork 422
[UNSTABLE] Can't launch barotrauma. That's the bug. #16071
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
Comments
Fixed in https://github.com/FakeFishGames/Barotrauma-development/commit/89ac7272155ac4677883489d0a85b25e04a85d7a and updated the unstable build. Should still be tested on Mac and Linux. |
Tested on steam unstable branch, linux and mac No issues on linux Mac gives many errors that are similar, but doesn't cause a crash and was able to launch rounds in SP and MP
|
@Jasontti I'm interested in trying this out to figure out why that happens, as I haven't seen those errors myself – was this just from running the now current unstable, from Steam? |
@ilmarilahti Yes, just from steam. I have rider installed on that Mac and have successfully compiled DLC projects. Notes from testing: Updating dotnet to 9.0.5 did not resolve warnings. Steam uses Seems that workshop items are automatically stored in icloud. Making Disabling icloud syncing for documents folder fixed the issue. Could not find a way to exclude steams workshop folder from icloud, there might be a potential workaround with symlinking and having .nosync suffix in folders name
There still is one mystery why there is a warning for accessing I don't like disabling iCloud syncing on documents folder as a solution for this. |
Discussed in #16068
Originally posted by ubertpendragon May 13, 2025
Disclaimers
What happened?
I don't have a crash log or anything. It just doesn't launch
Reproduction steps
Bug prevalence
Just once
Single player or multiplayer?
Single player
-
No response
Version
v1.9.0.0 (Unstable)
-
No response
Which operating system did you encounter this bug on?
Windows
Relevant error messages and crash reports
No response
The text was updated successfully, but these errors were encountered: