PoorPocketsMcNewHold
Published
Outside that, works wonderfully.
Intro video can’t be watched, can surely be fixed with a MF fix.
C'est leeeeent. Utilise tout mon GPU pour ~30 fps. Jouable cependant.
Seems overly great, outside during the time when trying to close the game, force killing the process seems to be the only issue.
No issues, working as expected.
You need to launch the game in Windowed for the first time, before being able to use it in fullscreen after that.
As previously stated, We need to rename the launcher and the game executable to switch their name between each others. Once it´s done, It´s run pretty well as we would expect it. One issue that i´ve found out was that alt+tabbing resulted into a resolution reset, so we´ve had to reconfigure the correct resolution from it. But outisde that, everything works great !
Freeze during the early seconds of the first in-game cinematic. Regardless of the DX11/12 played version.
Recommend playing the non-DX12 version for graphical artifacts. You are only missing TAA with it, as both doesn't have RTX support working, despite their previous benchmark version allowing vkd3d to make it work.
Took a long time to install its repositories, but in the end, no issues has been found. (Outside of the ordinary game, like the poor adaptation of the Widescreen screen ration for my case.)
Outside the obvious game issues that he had in itself, the game seems to work flawlessly.
Everything is running superb, including the anti-cheat which isn’t working half of the time like other games using it.
No idea if it’s an issue with slowly loading game assets or Proton, but the game tends to be extra slow loading HQ assets (Texture/models and all)(Around ~20s freeze for an 85/75Mo/s on a read/write). Either strongly recommend installing on an SSD or lowering those. Often create stalling freezes at the start of each matches.
Atleast, It is in a playable state right now, will surely require some tinkering to minimize the reported stuttering issues.
Tested on KDE Plasma with Lightdm, you can alt-tab it, but it has issues reverting to the game window.
Expect to have some stuttering during gameplay. Important ones at the beginning of any match, and a few during gameplay. By the look of it, seems to be related to the texture loading, installing the game on something like a faster HDD or an SSD could potentially reduce it.
LD_PRELOAD=/lib/libtcmalloc_minimal.so.4 %command%
Classic libmalloc Source issue. Use that launch command and gperftools-libs.i686 installed on Fedora to make the native version work.
Neither the proton version, or the native version works. They simply launch the process but does nothing else.
After having issues with both native and Protonfied, I´ve managed to make it work flawlessly. Surely due to my Keyboard with controller input (Wooting One), It was causing issue with the game. -nojoy launch setting fixed that issue directly.
Works almost as native, even with the Steam controller.
Highly recommend to check for the FPS cap tweak, and the ultra widescreen patched executable. Both work trough Proton.
If it's just shader caching, then we just need to wait a couple of days. If it's Proton, then surely a week or two.
The sound took the incorrect default output for some reason. Thankfully, the game allow to manually change the audio output and input manually in the in-game settings.
I suspect it's just the necessary shader caching issues that come with a new game, but the game freeze for ~1 second every time you shoot or take a shot, pretty difficult to play decently even at lower difficulties.
Still would have to fix those two issues if they are affected by it. Otherwise, it's fine.
The sound took the incorrect default output for some reason. Thankfully, the game allow to manually change the audio output and input manually in the in-game settings.
With my steering wheel plug at all time, it caused ~1 second of freezing every time you shoot or take a shot, pretty difficult to play decently even at lower difficulties. Regardless if it was used, of course. Unplug everything or wait for a patch to fix, or allow to disable vibrations or controllers.
Work natively, even when handling the useless launcher.
Might be caused by the game port, but some game lag can be experienced when ¨dropping¨ on the map, due to loading all the assets in higher quality. Strange for the Disk and hardware configuration I have compared to the destined smartphones platform.
The Bethesda.net login (And, as such, the integrated mod browser) isn't working. The same goes for the achievements.
It's a bit confusing how it name the “controller” thing, but basically, if you want the first player to use the KB+/M then choose the controller for player 2.
Use a source-port either way. Luxtorpeda allows you to automatically set up any of your choosing over it.
Completlyt absent. The sound works from the fixed intro videos via Proton, but that's it.
Issues with video loading (that can be fixed via Proton), and incorrect rendering of the already hard to read font in the game settings.
Crash around 30 seconds in.
Using either Steam Native runtimes (1.0 and 3.0) didn't change anything. Would suggest running the Windows version via Proton.
Crash around 30 seconds in.
Using either Steam Native runtimes (1.0 and 3.0) didn't change anything. Would suggest running the Windows version via Proton.
Well, It’s been a while since I’ve been waiting to be able to play GTA IV, with the Complete Edition, it is finally possible.
After around 30 minutes of play, some slowness is expected perceived as a sort of ¨lag¨ despite being played in single-player.
You would need a bit more than just proton to compile all of it into a working game. Take a look at the main game, instead at his source code.
https://github.com/ValveSoftware/halflife/issues/3158
Had an issue with sysmalloc assertion. Had to compile a new filesystem_stdio.so file via https://github.com/dreamstalker/rehlds, as described in the issue. I also included my compiled binary in the issue for those who don't want to compile and trust me enough.
This reverse-enginered port isn't binary-compatible due to using newer compiler versions, so some specific engine plugins doesn't work. The repo has a server list using this version of the engine http://www.gametracker.com/search/?search_by=server_variable&search_by2=sv_version
If only Valve gave something about their title compatibility issues...
Random fatal error. Absolutely no way to just launch the game.
Il est possible qu'avant, le jeu fonctionnait convenablement sous Linux, mais ce n'est plus le cas actuellement.
DXVK_ASYNC=1 gamemoderun %command%
Quelques ralentissements toutes les ~5mn, jusqu'a un arrêt complet à force d'utiliser trop de mémoire (Malgré mes 32GB & 16GB en mémoire graphique). L'hypothèse d'une fuite de mémoire est possible. Comme indiqué sur le ticket de support Proton de ce jeu. https://github.com/ValveSoftware/Proton/issues/2907#issuecomment-1366206426
En addition, le mode en ligne et les succès sont toujours non supportés sous Proton.
Did the .reg tweak as previously mentioned. The game doesn’t suffer from any slowness and run pretty well out of the bunch.
Doesn’t work with 5.11_GE_3_MF-1 with a :
hdInit: failed````error.
Contrary to what other people were reporting, and my experience with the dev previous native ports, Isonzo runs better on native.
Contrary to what other people were reporting, and my experience with the dev previous native ports, Isonzo runs better on native.
Just does not launch, and silently fail within a few seconds.
Crash at launch.
Start a command-line window, and then shortly crash. Trying to run it from the executable doesn't fix it either.
Use the beta code `livelongandprosper` to get access to this 2018 updated build of the native port of the game.
Occasionally, Explosion sounds aren't heard, even when in plain view. Seems to happen with explosions at a certain distance, notably in strongholds. Nothing game-breaking.
Some occasional FPS drop to around 40FPS. Seems perhaps just due to some auto-saving issue which happen on the Windows build as well.
Feral still did a decent job with the Linux build, and still suggest trying it out.
Same state as the Italian, or universal English release. Seems to work out of the box.
LD_PRELOAD=$LD_PRELOAD:/usr/lib/libtcmalloc_minimal.so.4 %command%
The usual LibMalloc issue also plaguing older Source games like Team Fortress 2. For my case, on Fedora, that the correct path with gperftools-devel.i686 installed. But it will differ for other Linux distributions.
Fonctionne comme natif, via SteamVR natif. Je n'ai pas testé sous SteamVR en mode Proton, et cela ne fonctionne évidemment pas avec Monado.
Works perfectly out of the box.
The Steam Controller works natively on this game. Due to the specific nature of the game, it does need a custom config however. I’ve added one I’ve done myself thankfully.
After you fix those two issues, and accept that at the current state of the game, It is pretty janky. Then, I suppose it should be fine,
You need to do protontricks 707030 win7 to fix the sounds issue. mf-install is still required for video cutscenes to work. The latest can be substituted with the latest version of proton-ge.
That's early Access for you. Still think it runs a tad bit worse than on Windows native.
Running, pretty much as janky as Windows.
Expected from an Early Access Unreal 4 title. Happen on Windows builds as well. RWS are still working on it. I’m helping them as a GNU/Linux QA tester, and work on improving the game compatibility and performance via Proton, until a native Linux port is made.
Some important framerate loss can happen, when loading saves. The reason is still relatively unknown, and seems to be related to game cached loaded levels not unloading the previous one. Restarting, or just going back to the menu to reload the save fix it.
As reported in QA, The 0.3.1.1 update is borked, and they haven’t answered.
I have been accepted in RWS private QA testing as the only GNU/Linux tester, to test its compatibility with it. Despite reporting the worked update being borked due to an unskippable UE4 redistributable installer, they did nothing for it. More detail on the P4 Proton Github Issue page.
Glad to have POSTAL 4 working again on Linux. Still working on covering it's support for future game versions.
Workaround for the UE4 redistributable installer found by Justin. https://steamcommunity.com/app/707030/discussions/0/3080998989603834402/ More details here but in a nutshell, you need to replace the UE4 redistributable installer by a VC+ redist 2015 x86 installer, so it tricks the UE4 check to install it instead and pass the installation.
Very minor performance difference on the current build, compared to running it on Windows on the same Hard-drive and rig. Only really a difference of 1~2 frames and a generally slower loading of textures and models.
Tested it on a pre-release development build. I feel confident myself already stating that the game run well out of the box.
Video doesn’t work, but that something that can be fixed with the MF fixes.
Streaming Steam Movie, Despite having to use the crappy Steam Video Player, everything works !
Issue with the steam video player scaling. Not dependent of the movie in itself.
Just a tech demo, which shows that the future will be full of noisy visual in an inconsistent slideshow framerate.
gamemoderun mangohud vk_pro %command%
As expected, it runs poorly. 6 FPS with the default configuration at Ultra/High. ~25fps if you reduce everything and lower the rendering at 1/10 via the configuration file. As shown, the AMDGPUPRO Vulkan driver is needed, as mesa doesn't natively support RT yet (Without some arguments that i haven't used).
Works now on the latest Proton versions. I do recommend it to actually properly activate it (Steps on PCGamingWiki) instead of us the NoDRM.
No need to use older Proton versions now, to play your favorite bad game! I regret nothing.
gamemoderun %command%
A bit slow to cache shaders but that's normal DXVK behavior, same with the async patch. Also some freeze when opening the options but it's fine overall.
Haven't managed to make it work in Proton, as pointed out by the GitHub report and the others ProtonDB reports.
Crackling during video cutscenes AND real-time gameplay. Not in the menu. Forcing the game to run in “Steam Linux Runtime” seems to have fixed it.
Just a little note, and perhaps also on the other platforms. The intro cutscene was cut into a small window at the center of the screen, despite having the game in full screen with a correct set resolution. Other cutscenes showed fine (But with black bars on my 21:9 monitor)
Haven't managed to make it work in Proton, as pointed out by the GitHub report and the others ProtonDB reports.
Crackling during video cutscenes AND real-time gameplay. Not in the menu.
Just a little note, and perhaps also on the other platforms. The intro cutscene was cut into a small window at the center of the screen, despite having the game in full screen with a correct set resolution. Other cutscenes showed fine.
Run perfectly, as it was native.
The Vulkan executable renaming process, is still needed however.
Generally, perform better than the native one, but especially, doesn't have the OpenGL transparency rendering issues it suffers.
Despite my current rig, the game wasn't able to substain a stable 75 FPS at ANY quality settings. mesa_glthread=true helped, but only -force-d3d9 fixed it, throwing away DirectX11.
I would recommend it, only when forcing DirectX9.
Supprimer le fichier libstdc++.so.6 dans le dossier du jeu/bin
Marche parfaitement. Les deux versions se valent.
Même chose que le rapport de ${RANDOM_USER} : https://www.protondb.com/app/292030#D9QWokpSZN
gamemoderun RADV_PERFTEST=rt VKD3D_CONFIG=dxr11 mangohud %command% --skip-launcher
Sous AMD, activer les options de ray-tracing dans le jeu, fait crasher celui-ci. Cependant, le reste du jeu sous DX12 et tout à fait jouable avec le reste des options disponibles, donc je vous conseillerais en dépit, de jouer sans pour le moment. Et, au pire, la version précédente en DX11 est toujours accessible.
I have been testing it quite extensively these last days, but, nothing found about the game running in Proton.
Instant silent crash
The Unity ¨loading screen¨ appears shortly, and then crash silently.
Currently, unplayable. That's a shame to know for a cool game, who have translations for my non-billingual friends.
As said, the videos of the Sub the titles contains important high-pitched distorted audio glitches.
Unplayable videos. Proton-ge only cause for the actual videos of the Sub The Title to appears glitched, distorted and with audio artifacts, and the install script didn’t changed anything.
Marche parfaitement et sans modifications. En incluant le mode VR sous Valve Index pour ma part.
Has previously stated, the game is able to launch without any issues, you can do everything you want in the menus, but once you launch a game, it lost the connection to the host everytime. The first time, it has been able to load to the map screen while loading the game sounds in the background (meaning that it did load the current game, atleast partially), but before i can select any thing, it redirect me back to the menu with a host connection lost error message. If you aren´t that lucky, it might even just redirect you back without even seeing the map screen. Tested aswell to connect using the server browser, exact same issue.
Was at least able to launch into the menu, and managed to even load into a map and play alone during the waiting times, but now, you are directly stuck into the menu, with an EAC error, due to apparently, not launching the game with the launcher. Still blocked by the Anti-cheat.
Veteran Closed Beta. Install the MY.GAMES launcher correctly, and works perfectly. Everything works perfectly in-game.
CBT Beta. MY.GAMES launcher. Unable to launch the game due to a generic error with the game executable. No support about it.
In addition, confirmation of use of MRAC anticheat. No Linux support then, unplayable :c
