PlayableShow Details
Unknown
Assigned middle mouse click on Back grip buttons
TDP limit to 10
Works great
No special treatment, install and hit play
QUBE2 settings:
Wine version: Proton - GE-Proton8-21
Select alternative EXE to run: QUBE2/QUBE/Binaries/Win64/QUBE-Win64-Shipping.exe
Running following command (replacing with QUBE2 Wine prefix path) in Terminal did not help in my case.
The installation of vcrun2019 was successful, but did not solve the Visual C++ runtime issue for me.
WINEPREFIX="PATH_TO_YOUR_WINE_PREFIX" winetricks vcrun2019
On first launch, a message appeared stating that Microsoft Visual C++ runtime is not installed.
Look up the path to the wine prefix in the settings of Qube 2 in Heroic and run the following command with your wine prefix path to install the missing runtime:
WINEPREFIX="PATH_TO_YOUR_WINE_PREFIX" winetricks vcrun2019
Does not work.
It complains about "Microsoft Visual C++ runtime" not being installed when trying to start the game. I tried lots of Proton versions. Made no difference. Does not work.
Works again out of the box
Works again out of the box.
The graphical degradation I noticed in my previous report was because now in Options > Video there's a "Reflections" setting which is set to low by default.
protontricks 359100 vcrun2019
I'm convinced the older version that still worked out of the box, also looked better
After 2013-08-25 update it stopped working.
It complains about no Microsoft Visual C++, and if installed with protontricks, then it complains abut the system not being DX12 compatible, even with the non-DX12 boot option. -dx11 also changes nothing, or using different proton versions (I tried Experimental, 8,7,6 and 5, and a couple of GE). Tried both in Deck and PC, both Borked
Идеально идет
Works perfectly with Proton 7 on SteamDeck with Heroic Games Launcher for Epic Games owners. Works perfectly too with the Steam version !
Had no issues.
enabled the right touchpad to do left mouse click upon being pressed
if the game had been booted up before on a different device with higher res. the same high res will be used to start the game. change the resulution back to 800p on the different device before playing.
I am running the game in DX12. and so far its running fine and I am 5 chapters in. launching the game will take a teensy bit before showing anything (about 1 to 2 min of steam loading screen thingy thing), have patience. it will boot!
I do recommend changing the control scheme a bit. the official one is good but lacks certain fine controls in my opinion.
don't forget to change the resolution back to 1280x800 if you have played this on a desktop/laptop/whatever with higher res. Else it would cause the game to boot up in same high res without scaling down.
Finished game with no issues
Between 120 and 144 fps in 1440p
Completed the entire game without any problems.
I used the default launch option (D3D11) instead of the secondary option to use D3D12. D3D12 also seems to work, although I only tested it very briefly.
144FPS worked through this tweak https://www.pcgamingwiki.com/wiki/Q.U.B.E._2#High_frame_rate but only in DX11 mode, DX12 still limited to 60FPS. As for the keyboard, it weirdly switched from AZERTY support to QWERTY in the DLCs. Which require to switch keyboard layout in order to function properly setxkbmap -layout fr
Cosmetic texture glitches aside, everything looked fine.
Some vertex fighting (Z fighting ?) with shadow textures applied on the sand in outdoor areas.
Screen tearing still appeared after activating V-Sync. However, I don't use a Freesync enabled screen, so that might be the issue.
Unknown(2+ hours with Proton)Runs very well, no problems while playing. But there is still the unreal engine error after quitting the game.
Unknown(2+ hours with Proton)Unknown(an hour with Proton)Runs perfectly without any problems. Just a few mouse-jerks that some else already reported happened to me (but rarely, maybe 3-4 times in about an hour playtime). Don't know if that's related to proton or the engine. Also there's the unreal engine error that appears after quitting the game, but that doesn't affect anything either.
Unknown(an hour with Proton)
Seems to run perfectly. The DX12 option didn't work for me but the generic unlabeled option worked fine. No issues, performance is very good.
Works Very Well. It's important to note that it's recommended to run this game under Proton version 3.16-6 or newer as older versions of Proton have issues with the game's audio.
Everything works, including Alt-Tabbing, fullscreen mode, etc. The game displays an Unreal Engine error after you quit it. Not really an issue. The single and only problem I had was with remapping some buttons - my input settings didn't save correctly. I think this probably is a problem when playing on Windows too though, so I'm not considering this a Proton issue. I solved it by reprogramming my keyboard, but you could probably use xdotool as well. Also if you're using a regular QWERTY keyboard you probably won't need to even think about it.
Runs out of the box, performance is good. Sometimes i get short, weird mouse-jerks, don't know if they are related to proton.
Unknown(< 1 hour with Proton)Sound effects are playing constantly when they shouldn't even when disabling some of the effects. Frame rate is choppy and does fluctuate extremely hard even on powerful hardware with reduced settings (30-120 fps).
Unknown(< 1 hour with Proton)
Sound is distorted, but winetricks xact helps. Afterwards works perfectly.
Unknown(< 15 minutes with Proton)Everything works without any tweaks, except binding extra mouse buttons (e.g. thumb buttons). The game crashes on exit, but that doesn't seem to affect anything.
Unknown(< 15 minutes with Proton)
mouse movement feels choppy, all the rest works fine and graphical performance is great
UnknownRequires xact (from winetricks) for proper sound. Error after closing, although it doesn't seem to affect anything.
Unknown
