neutrinomuxer
Published
Works great out of the box with Proton 5.0-10
In certain occasions I witnessed the game crashing when attempting to save. When that happens the save file does get created, but attempting to load it will always fail. If that happens to you though there is no need to panic, as it is actually possible to recover the save file. If you browse the local files of the game you should be able to see a directory named savegame which contains all the save files. In the event that the game crashed during saving, there should be there two files with the name you gave for the save file. One with an .svx extension and one with a .tmp. Simply delete the file with the .svx extension and rename the other from .tmp to .svx.
There were some strange frame drops but only during the tutorial. Apart from that though, I have everything maxed out and get constant 60 FPS.
The game fails to start with Proton 5.13-4 but it everything appears to be working fine with 5.0-10, apart from the save game issue described above.
Works out of the box.
Minor audio crackling mostly noticeable in the main menu.
I'm on Debian Buster with Gnome and for some reason the game fails to launch under Wayland, if however I select the "Gnome on Xorg" option and then login to the desktop everything is perfectly fine. Apart from that the game runs flawlessly out of the box without the need for any workarounds. With VSync enabled and my graphics settings tuned just right, I get constant 60 FPS most of the time without any issues.
Doesn't start, tried the workaround with preferences.ini but without success.
For anyone who also wants to give this a try, the preferences.ini doesn't exist from the start but can be created by running configure.exe with wine as follows, "wine /.steam/steam/steamapps/common/The\ Longest\ Journey/configure.exe". Just note that the file should appear at "/.wine/drive_c/users/manolis/Application Data/The Longest Journey Demo/preferences.ini", so you need to copy it to the right directory afterwards and then make the changes.
Works perfectly well as long as I disable vsync in the game settings. If vsync is enabled though I get a black screen every time I try to launch the game and it just never starts no matter how much time I wait, so I have to forcefully kill it.
With vsync disabled though I had to lower my settings just enough in order to make sure I always get a bit over 60 FPS, so I could then set a 60 FPS frame limit and this way get constant 60 FPS most of the time. This is necessary because without vsync even if I get 59 FPS instead of 60, it results to horrible stuttering due to the mismatch between the frame rate I receive in the game and the refresh rate of my monitor which as you may have guessed is 60 Hz.
I tried enabling vsync many times so far in the hope that something might have changed, but every time I do the game just refuses to start and I have then to manually modify the user.settings file in order to disable it. Also, attempting to enable vsync while the game is running will cause it to freeze.
Finally, I should mention that if I disable DXVK using "PROTON_USE_WINED3D=1 %command%" in the launch options, then having vsync enabled doesn't appear to cause any issues. Of course that's not really a solution since doing so will result to a huge performance impact. To be more specific, with DXVK disabled I can barely get 25 FPS at low settings. I just thought it would be a good idea to mention it, as many people here seem to suggest it as a possible solution, while I belive the real problem is related to vsync which is in fact enabled by default if I recall correctly.
Crashes with the latest Proton version when entering a battle, but with version 4.11-13 everything works perfectly.
The native version of the game doesn't work properly with ultrawide aspect ratios. Instead of displaying black bars on the sides, it stretches the image causing some pretty terrible distortion. And that happens even if the resolution is set properly and the widescreen option is enabled. I guess this shouldn't be a huge issue for people with regular monitors, but I have an 31:9 Dell UltraSharp U4919DW and no matter what I tried I just couldn't make the game to stop stretching the image. However, when I tried the Proton version everything appeared to be working properly, and since there was virtually no difference in performance I haven't attempted again to use the native version.
