Hans

What's the smallest save you have that triggers this issue reliably (after a short time)?

Thanks for providing the logs. It will probably take some time to analyze this issue. How big is your %appdata%\Avorion\galaxies\Andromeda folder?

Please attach the client log and the server log for one such error. To find the logs, read this post:

It looks like it could be an issue with initializing sounds. Can you try updating or reinstalling your audio drivers?

Beta Branch Note: These changes are currently available on the beta branch. The beta branch is for testing experimental changes and for finding and fixing errors. This is how you get access to the beta branch (USE AT YOUR OWN RISK): Right-Click on Avorion in your Steam list, Properties -> Betas -> Select branch 'Beta Branch - Newest Changes & Experimental Features'. UI Improved consistency of subsystem tooltip descriptions Bugfixes Fixed an issue where client and server disagreed about docking state This should resolve cases where the ship was shown as docked but various menus sent errors about not being docked Implemented a workaround for an AMD GPU driver issue Fixed an issue where ancient gates could be connected to world boss sectors Fixed an issue where it was possible to give orders meant for ships to stations Fixed a crash when a station was ordered to support a ship and the ship left the sector Fixed an issue where boss health bars were visible in build mode Fixed a crash related to destroyed entities in scrapyard sectors Fixed an issue where a tooltip obstructed the confirmation dialog when removing a subsystem with shift-click AMD situation Some users reported crashes with AMD cards when creating or loading a galaxy using AMD driver version 23.12.1 or 24.1.1. We have implemented a workaround that hopefully addresses this issue. If you had this issue, please report in the comments if this patch fixes the issue for you (on driver 24.1.1). If the problem still exists we recommend a downgrade to driver 23.11.1. Details Some background on the status of this issue, by one of our devs: "This problem is particularly difficult to debug. Originally none of our office PCs with AMD cards were affected. However, we managed to build a PC where we can reproduce the issue, but even with this PC, the crash doesn't happen reliably. On a technical level, the crash happens in a thread run by the AMD driver in the Avorion process. This should not be possible unless there is a bug in the driver. For those who don't know: a driver *must not crash*. We have verified multiple times that our code is correct and doesn't raise any errors. We've contacted AMD multiple times over different channels but have not received a helpful answer, yet. Warning, technical: To analyze the cause, we tried to disable various parts of the engine. When the crash disappeared we always had to test many times, as it wasn't 100% reliable. No crashes a few times in a row can just be plain (bad?) luck and lead down the wrong path. We finally found different, independent functions we could disable, that individually stopped the crash. None of them look like they made sense as a cause for a crash. Just leaving them disabled was no option either, we had to find a solution without impacting the content of the game. We settled on restructuring a small part of preparatory texture work so we give the driver less work while loading the game, and forced the driver to complete some of its work on our schedule instead of its own." We're very sorry for the inconvenience. We hope that the workaround we've screwed into our engine fixes the issue for you fine AMD folks, and we hope we can remove it once the driver crash was fixed by AMD.

Driver 24.1.1 seems to be affected as well.

You'll get a steam key when buying anything from our own shop! (The shop site now says "Steam key" as well).

There seems to be an issue with AMD GPU driver version 23.12.1. If you have an AMD card and your driver version is 23.12.1 and Avorion crashes when trying to enter a galaxy please try this: - search the Internet for "AMD {your GPU} previous drivers", for example "AMD RX 6700 XT previous drivers" - you should get a search result from the official AMD website - Download driver version 23.11.1 - Install it - Reboot - Try again if you can start Avorion and enter a single or multiplayer galaxy - Please report back here if this works for you or not, with the exact model name of your GPU.

We expect non-ASCII player names to work if both the server and the client are properly connected to steam. Was this really the full error message? Or did it contain "connection refused" as well? To help us diagnose why it does not work as expected we need as much context as possible. Is this single player or multi player? Can you provide log files?

What is the full error message? Is this an issue only when steam is in offline mode? Please test if it works when you first put steam in online mode and then start Avorion. If it is still an issue, please attach the client log and server log from a failed attempt. Log file locations are described here: https://forum.avorion.net/index.php?/topic/19-read-this-first/

Possible workaround: If you have an AMD card and your driver version is 23.12.1 and Avorion crashes when trying to enter a galaxy please try this: - search the Internet for "AMD {your GPU} previous drivers", for example "AMD RX 6700 XT previous drivers" - you should get a search result from the official AMD website (for example: Previous Drivers for RX 6700 XT) - Download driver version 23.11.1 - Install it - Reboot - Try again if you can start Avorion and enter a single or multiplayer galaxy - Please report back here if this works for you or not, with the exact model name of your GPU.

Your logs look like it could be a GPU driver related issue. You could test if the AMD Pro drivers https://www.amd.com/de/technologies/software-pro make a difference.

Does it behave the same or differently when you put Steam in offline mode (at least until the galaxy is loaded)?

The log files suggest there seems to be some networking issue and the machine can not communicate with 127.0.0.1 / localhost, which would mean it can't communicate with itself. Is there anything unusual about your networking setup? Do you use VPNs or some Hyper-V Virtualization features?

Have a look at %appdata%\Avorion\galaxies\GALAXYNAME\server.ini - readme.txt # (Windows) ~/.avorion/galaxies/GALAXYNAME/server.ini - readme.txt # (Linux) for any recently created or saved galaxy. Is that what you need?

The long-awaited Behemoth Events DLC has landed in the Avorion default branch with Patch 2.4.1! Encounter legendary behemoth ships, enhance your ship with new subsystems, and face epic challenges as they ruthlessly attack sectors in the galaxy. Key Features: - Fight against Behemoth ships that will attack different sectors in the galaxy. - Collect unique subsystems with special properties dropped by these colossal bosses. - Dive into a dynamic experience as behemoths destroy and salvage entire sectors if left undefeated. - Enable or disable behemoths at will, ensuring a customized gameplay experience. For more details on the other improvements and features coming with Update 2.4.1, check out the announcement here: https://store.steampowered.com/news/app/445220/view/3882728508900949686

Multiplayer & Security Updated Steam API to v 1.57, added authentication safety against man-in-the-middle attacks Bugfixes Fixed a crash on Linux related to recent Steam client updates affecting singleplayer and hosting multiplayer games Fixed an issue where the dedicated server settings were not fully visible in the ServerRunner window

The new beta branch patch hopefully addresses this issue. Does version 2.4.1 work for you?

Can you try the current beta branch version while the steam client is online?

Behemoth Events Increased number of bonus turret slots for Behemoth Combat/Civil Turret Control Systems Adjusted slightly misleading Behemoth Carrier Systems description Remote Ship Management Remote managing the selected ship now requires the player to hold "I" Briefly pressing "I" while having another ship selected now just opens your current ship's management window again Added visual clues to the remote manage window to make it more clear it is not your current ship's window Fleet Tab Improved compact view to take currently selected ship or station into account Ships that have yield ready to claim will now display an icon in compact view Misc Updated Credits Bugfixes Fixed a crash on Linux related to recent Steam client updates affecting singleplayer and hosting multiplayer games Fixed a crash when opening system tab in ship window while having a subsystem installed in a locked slot Fixed an issue where escorting ships prioritized gates over jumps even when target sector was in jump range They will still attempt to use gates if their hyperspace engine is on cooldown Fixed an issue where escorting ships did not immediately jump with the leader when possible Fixed an issue that caused error messages "You can't modify the component ControlUnit" Fixed an issue where player owned resource depots gave incorrect amounts of resources and money Fixed an issue where the filter for stolen goods overruled other cargo bay filter settings Fixed an issue where toggling compact view off and on resulted in the wrong row being expanded Fixed an issue where a Long-Distance-Trader subsystem's tooltip claimed to provide software for Transporter Blocks even when it didn't [edit 2023-12-07] Fixed an issue where duplicate mails were sent during the expedition to the center mission

Thanks everyone for providing the logs. We are working with high priority on this issue. In the meantime you can put your steam client into offline mode to play singleplayer mode.

Does it work when you put the steam client in offline mode?

This message suggests that the Avorion process and the Steam Client process are unable to interact with each other properly. Maybe some sandboxing or security feature of your OS is interfering, but I can only speculate. This new problem seems to be clearly outside of Avorion itself.

Thanks for providing the files. Sadly this time the server could not start for a different reason: 2023-10-20 09-37-02| ERROR accepting connections: bind: Address already in use (Either another AvorionServer was still running (or hanning) or you need a bit of pause after a previous attempt. If in doubt, you can try running pkill -9 AvorionServer before starting a new game.) Can you try again and get me two new files from one attempt where the serverlog contains a stacktrace?

Could you run this in a terminal: while ! pgrep AvorionServer ; do sleep 1 ; done ; cat /proc/$(pgrep AvorionServer)/maps > avorionserver-maps.txt and then try to start a game? Afterwards I would need the generated avorionserver-maps.txt and the matching server log from that attempt. (This essentially waits until an AvorionServer is running and then dumps its memory layout and loaded libraries. pgrep should be part of package procps-ng.)