You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently there is a new bug on Unix builds that is blocking out users from launching or logging into a game server.
A little bit of background information: Some users Wine Prefix installs caused the launcher to report not enough disk space even though their system had the required storage space. A notable example would be the Steam Deck (Using Lutris), where the Root of the Drive is reporting a different available storage size while the Folder of where the Launcher installation resides reports a different amount of available storage space.
With the release of 2.2.0.2 we attempted to use a command to get the storage space on Unix, but due to how Wine handles Linux commands only, so we are unable to read its value. Release version 2.2.0.4, a check that was used to bypass the issue on Unix was removed due to the Error handling that took place to fix the game download bug. Unfortunately, a quick fix would be to revert the change, but some users will bump into the aforementioned issue and would not be able play the game.
Solution? Well the easiest would be to stick with version 2.2.0.2, however, if your planning to play on game servers that require the latest build, then unfortunately there is currently no resolution.
So any help or ideas to resolve the issue is welcomed since the launcher team has explored various methods to retrieve the correct information.
Here is a few ideas that was explored from our end:
Recursing the Drive
Not ideal for performance and wait times
Recursing the Installation Folder
Only gives us used space
While this is used currently, its only used to verify the folder size if its under the expected install size
df command
Only works if running an app with SuperUser and even then it has a chance to fail
DriveInfo
We tried to use a specific path as the root drive
Causes a invalid drive error when being emulated through wine
Thanks from Launcher Division
The text was updated successfully, but these errors were encountered:
Since the release of 2.2.0.0 the launcher has had a console which is aimed to include commands that doesn't meet/or fit the criteria of getting a UI element. Spoiler Alert; there isn't a lot of commands for now, but in the near future it will be include commands to quickly change a setting, but that's for another day.
You can either do the following (each method have the same commands):
Now typing in help in the launcher console will list of commands available, However, there are commands that is not listed (Slight oversight on my part).
The following commands are only available on 2.2.0.6 or newer:
Currently there is a new bug on Unix builds that is blocking out users from launching or logging into a game server.
A little bit of background information: Some users Wine Prefix installs caused the launcher to report not enough disk space even though their system had the required storage space. A notable example would be the Steam Deck (Using Lutris), where the Root of the Drive is reporting a different available storage size while the Folder of where the Launcher installation resides reports a different amount of available storage space.
With the release of 2.2.0.2 we attempted to use a command to get the storage space on Unix, but due to how Wine handles Linux commands only, so we are unable to read its value. Release version 2.2.0.4, a check that was used to bypass the issue on Unix was removed due to the Error handling that took place to fix the game download bug. Unfortunately, a quick fix would be to revert the change, but some users will bump into the aforementioned issue and would not be able play the game.
Solution? Well the easiest would be to stick with version 2.2.0.2, however, if your planning to play on game servers that require the latest build, then unfortunately there is currently no resolution.
So any help or ideas to resolve the issue is welcomed since the launcher team has explored various methods to retrieve the correct information.
Here is a few ideas that was explored from our end:
df
commandThanks from Launcher Division
The text was updated successfully, but these errors were encountered: