Chaos
Published
spawning ships over 500k blocks crashes the game in ~5 minutes, servers too. Suspect its issue with the game, and not related to linux.
suspect the issues had were core game issues, not linux related. server crashes with large block counts
suspect the issues had were core game issues, not linux related. server crashes with large block counts
only issues appear to be the core game engine itself, not linux related. runs the same as windows.
missing textures after long times playing, probably some weird memory issues. Textures would be wrong,missing entirely, or flickering. Purely cosmetic, only happened after long sessions, fixed by a game restart.
rare crashes, seemed to be tied to multiplayer with windows clients, unloading areas people were in.
new launcher totally broken
disabling launcher will fix it, assuming you have an ini file to copy in. otherwise unplayable.
wine issues, if you use a device affected, took a week of digging to find the solution. This was absolute pain and most users wouldn't do it
Game doesnt support DirectInput, and wine (and thus proton) force unknown VID/PID devices to act as xinput instead of HID, breaking functionality of these devices in games not supporting DInput. Open control panel, controllers, and override the devices to act as DInput. You then open regedit and modify the following. (HKLM = HKEY_LOCAL_MACHINE) HKLM\System\CurrentControlSet\Services\winebus may need two DWRODs, "Enable SDL" = 0 and "Map Controllers" = 0 -delete every entry in HKLM\System\CurrentControlSet\Enum\WINEXINPUT -check ALL entries in HKLM\System\CurrentControlSet\Enum\WINEBUS for your devices VID:PID to match. if they have references to XINPUT you must change this to allow HID mode to operate correctly. use lsusb in terminal to find VID:PID for these entries, change: "Service" ->"winehid" "DeviceDesc" -> "Wine HID compatible device" "CompatiableIds" -> "WINEBUS\WINE_COMP_HID" - delete everything but this line for this you must do this for all entries for your VID:PID
Wine, and thus proton, treat any HID they dont explicity recognize by VID:PID as xinput, incorrectly, instead of treating them as HID. Normally, this can be worked around by using DInput, but in games that dont support DInput (like elite) this breaks functionality severely. Many regedits are required to fix the screwups of the default wine(and thus proton) behaviour.
Great if your devices are natively supported by wine/proton, otherwise it is painful, though this is WINE's fault, not the game.
for the wine team: Treating unknown HID's not as an HID, but instead as an xbox controller with max 10 buttons and 4 axis? It's in the name, guys. Words can't describe how dumb this is.
wine (and thus proton) detected my joysticks as xbox controllers, so when i bumped them, it would do all sorts of weird stuff until i unplugged them because it would switch to xbox controls. Fix was to override them in control panel to not act as xinput, or to unplug them.
mouse sensitivity in menus was unplayable in fullscreen
in fullscreen, mouse sensitivity was unplayable in menus. irrelelvent of fullscreen, mouse sensitivity was extremely high when controlling character, unplayably high.
stutters
mouse sensitivity was game breaking, might be worth trying without wayland.
EAC blocks users, devs say their too small of a team to click a checkbox to allow us in
boots to menu and lets you customize, cant even do the single player tutorial more than a minute before EAC boots you.
