Closed baldandbearded93 closed 1 year ago
I'm assuming this is the burst compiler in Unity, but naturally we don't know what exactly the developers use the burst compiler for as it's usually only enabled for specific kind of logic.
That said, I'm still slightly worried that by renaming it we are effectively breaking it, and the all the attached logic along with it. Unless of course Unity is smart enough to have a built-in fallback option in situations like these.
I am not 100% sure what happens, as I am not familiar with Unity. This was found as a fix for the Windows users and is now the recommended (pinned) solution in the server-hosting threat on Discord. So, I figured to add it as a possible work-around until the developers either make AVX/burst optional or another solution has been found, so people could keep using the container.
Now updated by adding +@sSteamCmdForcePlatformType windows
to the steamcmd to stop it from crashing. There are still plenty of errors, but for now it works.
Now updated by adding
+@sSteamCmdForcePlatformType windows
to the steamcmd to stop it from crashing. There are still plenty of errors, but for now it works.
Thanks! Can you add this to your derivative repo? Your last update saved my server
Now updated by adding
+@sSteamCmdForcePlatformType windows
to the steamcmd to stop it from crashing. There are still plenty of errors, but for now it works.Thanks! Can you add this to your derivative repo? Your last update saved my server
Should be there now :)
Now updated by adding
+@sSteamCmdForcePlatformType windows
to the steamcmd to stop it from crashing. There are still plenty of errors, but for now it works.Thanks! Can you add this to your derivative repo? Your last update saved my server
Should be there now :)
Thanks I tried but still no dice using a docker-compose up with that image. Did you apply that update to your docker image as well?
I can verify that this is functional
@sjdodge123 I had problems aswell last night. Fixed it by deleting the vrising server folder and recreating the docker.
@sjdodge123 I had problems aswell last night. Fixed it by deleting the vrising server folder and recreating the docker.
Thanks for the tip, unfortunately I tried that as well still no luck
Merged into main. Rebuilding the container right now.
In a recent hotfix, the VRisingServer requires AVX support (according to the Discord) and older (or virtualized) CPUs do not support this, resulting in an error regarding the file
VRisingServer_Data\Plugins\x86_64\lib_burst_generated.dll
. This modification adds a check to see if the CPU supports it, and if not, renames the offending file to file.bak.