Closed jm20122012 closed 10 months ago
Hey! First of all, thank you so much for providing all of the issue template information upfront. It saves a lot of time :D
Game crashes are almost always a game bug though, meaning there's nothing I can do to help you. I'd recommend seeing whether this is a common bug and/or try running the server outside of this Docker image. I strongly suspect that you'll find that it's a game bug unfortunately! I'd be happy to test this myself once I have some time.
As a workaround, see whether uploading a pre-existing save works?
Edit: one thing that became apparent when people encountered similar issues in the past was that using a generic KVM CPU definition triggered it for some reason. If possible, change your CPU definition to something less generic from your hypervisor.
Ah okay, I wasn't sure if it was a docker thing causing the issue or not. But yes, changing the CPU type in my virtual machine settings to match the host server CPU (Intel Xeon) worked. Thanks for the quick response! All is good now.
Describe the Bug After the server logs show telemetry instance started, I went into the client (Update 8) and went through the process of adding the server. Initially the connection seems to work just fine and I can create the server name, create an admin password and all that. I then went in to "Create Game" and selected the starting area, then named the session and clicked on "Create Game". As soon as I click on "Create Game" the container crashes. I've attached the full log as well as pasted the part showing the error below.
satisfactory-log-dump.txt
I did notice that if I restart the container without deleting the volume or anything, then it remembers my server and I can use the admin password previously defined to configure the server, but again after clicking "Create Game" it crashes again.
Your Runtime Command or Docker Compose File
System Specs (please complete the following information):
One thing to note is I'm trying to run this on an Ubuntu virtual machine running on the Proxmox hypervisor.
If you're on Linux, just paste the following block as a single command, and paste the output here.
Additional Context Log output: