femboy lenhador
Published
Some floor textures flickering. Really small details and I only noticed them around two times in a 2+ hour long game setion.
Don't actually know how these reports work (if the most recent will overwrite the previous one) so, if they don't overwrite, do not consider the previous one. It turns out that I did the dumb and reported that the mouse didn't automatically hide itself when using a controller but what happened was that I didn't had the game window selected...
Too much flickering assets. The characters and monster still appear as normal, but everything else keeps flickering, including the ground.
Lots of flickering assets, including ground areas.
Had to disable Steam Imputs for the controller to be detected.
At first, the game did not opened even tho Steam said it was running, so I had to close it through the "stop" button and re-open it.
Couldn't open the game through Proton Hotfix and Proton GE opened the game but have me a black window.
Colisions still work as intende, so the game is still playable if you really want too, but the ground flickering is too much for me.
When using two monitors, the setting to choose in which monitor to display the game did'nt do anything, so I had to go windowed mode, drag the game to my main monitor and then put it back again in fullscreen mode.
Apparently, the game have one save file for Windows and another for Linux so when I booted the game for the first time I was back at the level 1. So backup your game from a Windows instalation before migrating for Linux. After that, go to the save file folder, paste your save and rename it from "saveXXX.sav" to "linux_saveXXX.sav". Make sure to do that for every file (I had a "save001.sav" and a "save098.sav" and had to rename both of them for the game to be able to read them).
I got some constant frame drops but it got solved by itself by closing the game and openning it again.
The occasional Payday 2 crashes, which are not a Linux problem but a game problem. Once in a while your game can crash and the amount of crashes will get higher for each additional mod you or the host have.
Since it's P2P, lag and connectivity errors are based on your and the other player's Internet connection, but I was able to play with the whole America without any major issues.
You can still play the game with Proton Experimental but there will be no multiplayer (I do believe the multiplayer could exist but only with Linux players, as someone else said, but I did not test that).
Also, I had to redownload the game when I changed from the Proton Experimental to Proton GE, since I still don't know if that's normal behaviour, I'm putting this in here (I also saw some people saying that they didn't needed to redownload it and some saying that they did need to redownload it, so I would say it's better to download it with the Proton GE settings already enabled, unless you want to do some testing in the other version or if you want to play only the offline mode, which works just fine in the Proton Experimental version).
Got the "vk::PhysicalDevice::createDeviceUnique: ErrorFeatureNotPresent" message when booting the game.
Tried switching between standard proton version, experimental, GE-Proton9-22 and 8.0-5 as well as changing the launcher options as Sunscorcher, ĸsiążęce and Kraetos10 said but nothing changed.
Also tried what wigglyDon, BetaVersionBY (https://www.reddit.com/r/linux_gaming/comments/1ed0dbg/poe/) and jprofesorek#1652 (https://www.pathofexile.com/forum/view-thread/3445835/page/5) said but the problem persisted.
Also also tried what Crabiolo said (https://www.reddit.com/r/linux_gaming/comments/1ejg5nx/path_of_exile_vulkan_error/) but couldn't even find the file they're mentioning (I supposed that it would be created when the game properly launched, which didn't happened with me).
Too much connection issues resulting in absurd amount of lag.
Alt-Tabing during login screen or character selection screen would give a black screen on the immediate next loading screen, going to Haven. Alt-Tabing at any other moment doesn't seem to give any problem.
Had to disable Steam Inputs for it to recognize my controller. When playing on fullscreen, the mouse cursor would ramein invisible, making it hard to navigate through the menus since this task can't be done by the controller.
Sometimes the game would just not start, requiring it to be reinstalled. Seems to happen when the game gets closed for losing connection with the servers.
The connection with the servers can get really bad even when playing solo.
Some manual changes in the game files may be needed and, even with the changes, it could impact first time players' experience.
The character's dialogue audio file didn't played, requiring it to be re-encoded.
The file in question, for the english language, is "00144.dat", in ~/Games/Heroic/X2 - The Threat/mov (for a GOG version installed through Heroic Games Launcher). I did the process though Sound Converter.
Open the file in the program and convert it to ".wav". After it, rename the file from "00144.wav" to "00144.dat" and copy it to the mov folder, replacing the original file. The audio file becomes almost 2GB big, so I recommend using a software for the conversion, instead of doing it through an online service.
The video file with the character's models communicating through the comms system didn't played.
The file in question is "00001.dat", in ~/Games/Heroic/X2 - The Threat/mov (for a GOG version installed through Heroic Games Launcher) and I believe the "00003" file too.
All this stuff "qasf quartz amstream devenum wmp11" as winetricks solved the problem, but then made loading/saving times extremely long (sometimes not even completing then). Tried different combinations without success: if the video problem gets fixed, the loading problem would appear. Also tried the 6.10-GE-1 ProtonGE version, as someone else suggested, but the game wouldn't open.
To be honest, not having the videos during comms won't impact much of the game. You'll have some trouble during the story missions identifying who's talking to you, but that's all, and since 99% of the game isn't the story... The biggest problem is a short freeze before the comms open, which can be annoying during dogfights.
Alt-tabbing during loading screens would make the game crash. At any other moment I couldn't identify this problem.
If I press "shift + o" to go to the options menu and then select the "savegame" option (or press "shift + s", the command to savegame) I get the message "savegame only possible inside stations or with salvage insurance" even tho I'm inside a station.
So, to save the game it is required to first open the station menu by hiting "enter" and then go to the player tab, select options and save the game. You could also hit "enter > shift + o > savegame", or even "enter > shift +s" to save the game.
Not really a problem, but a detail to look for (the need to first open the station menu to be able to save the game, you can't just straight hit "shift + s" to save it, even while inside a station). And since I smashed my head against a wall trying to figure this out, here it is in the report.
