${RANDOM_USER}
Published
Crashes after a short time, anything from a few seconds to a few minutes. Needs cleaning up with “killall -HUP Acconting.exe”.
Installed xact.
Not constant. Seems dependent on video settings.
Blue “unknown terrain” being extended to the edge of the window while panning. (No idea if this is DXVK-specific.)
“The action manifest for BAD DREAMS Demo was not found.”
⇒ No functional controls.
Unless you're using Vive controllers, you'll need to install the “windows_mixed_reality” beta (access code is “WMR4BatmanArkham”).
Fails with “Application load error V:0000065432”.
Also happens on Windows, according to https://steamcommunity.com/app/1016860/discussions/0/1744517115694947685/ -- so safe to say not Proton-specific.
Both mf-install and mf-installcab. I have not tested to see if only one is needed.
First start is fine, except for an empty box with an “okay” button upon reaching the main menu. No clue as to what text should be there.
Subsequent attempts to launch the game all fail with an error window showing text including
D3DCommandQueue->GetClockCalibration(&GPUTimestamp, &CPUTimestamp) failed
unless I select DX11. To do this, I edited …/compatdata/397540/pfx/drive_c/users/steamuser/My Documents/My Games/Borderlands 3/Saved/Config/WindowsNoEditor/GameUserSettings.ini, changing the value of key PreferredGraphicsAPI to DX11.
Launch command set to %command% -dx11
This game defaults to DX12. With that default, I find that it crashes on start-up.
VK_ICD_FILENAMES=/path/to/amdvlk/amd_icd64.json:/path/to/amdvlk/amd_icd32.json %command%
Needs amdvlk for high frame rates. With radv, I'm seeing typically 20-50fps.
Played the first few levels (up to the first boss). Seems that all is well with this one.
Short and simple.
Occasional stuttering or fade-out, most likely due to shaders being compiled or other resources being loaded.
protontricks 359320 dotnet40
The game needs to be launched once prior to installing: the launcher will run fine, and the game proper will crash on launch. This is expected.
The game sometimes hangs during startup, often when showing copyright info; it should also be showing the ED logo at that point.
In this situation, I forcibly kill the game: kill -HUP $(ps ax|grep '[CZ]:' | awk '{print $1}'). Without doing this, I find that the launcher won't start up (communication problems with Proton-handled ‘system’ processes?).
• Apart from those start-up hangs, it generally works fine, both flat and VR. However, you'll want to stick to one or the other or set up means to switch between two configurations as otherwise there is reconfiguration involved (due to game design choices).
• It's possible to set up switching between two graphics configurations (using symlinks, without affecting other settings) based on the presence of the /VR switch in the command line.
• The game should be able to use IPv6, but it completely fails to pick up on the assigned addresses. Looks like some misparsing, or possibly faulty presentation, going on.
Requires Proton 6.3 or later.
VR mode is currently broken. From the game window (on the desktop), it's clear that at least headset tracking is working; but there is only the default SteamVR “nothing running” scene shown by the headset. (Also, the game window regularly loses input focus (desktop is using focus-follows-mouse), so don't have exclusive full-screen mode selected.)
If I start without SteamVR running, I do not get the option of switching to VR mode. (This seems to be intended.)
Mostly fine. Some minor audio glitches, probably related to one CPU thread being fully used.
Be sure to open the Steam overlay if you want to move input focus to another window: if you don't, the game may start lagging in response to mouse movement.
SteamDeck=1 %command%
Some messages logged, with associated brief rendering freezes. Example:
[drm] Fence fallback timer expired on ring comp_1.3.0
Played part of the first level. No problems were noticed (with esync disabled).
protontricks 579110 xact -- required, else the game is silent.
The game apparently does not know about Index controllers, treating them as Vive controllers.
Stuttering related to mouse movement.
Whether this occurs depends on the mouse -- the problem occurs with my normal (gaming) mouse but not with a cheap mouse which I keep around as a spare.
protontricks 2071500 xact
Sound seems only to work on the first run after installing xact, and even then most likely not. All that I know is that the problem is somewhere between FMOD and ALSA.
If sound isn't working, there will be a lot of log spam (see Steam/steamapps/compatdata/2071500/pfx/drive_c/users/steamuser/AppData/Local/IslandsofInsight/Saved/Logs/).
Pointer may be moved to (0,0) during game initialisation.
The game appears to run without problems. The text is off-centre unless you install MS Gothic (see the pinned thread about this in the game's Steam discussion forum) -- run the game once, exit it, then download and install the font, putting it in “/path/to/Steam/SteamApps/compatdata/373770/pfx/drive_c/windows/Fonts/”.
The game sometimes fails to terminate properly and remains running on exit.
Briefly shows a black window then segfaults regardless of whether I use radv or amdvlk.
VKD3D_CONFIG=dxr11 PROTON_CONFIG=dxr11 VKD3D_FEATURE_LEVEL=12_1 RADV_PERFTEST=sam,rt %command%
Missing views through portals. Camera offset position (same as for Portal RTX).
It is necessary to append some settings to “Portal Prelude RTX/dxvk.conf” else the game will cause GPU hangs and (usually) resets.
rtx.raytraceModePreset = 0
rtx.renderPassGBufferRaytraceMode = 2
rtx.renderPassIntegrateIndirectRaytraceMode = 2
rtx.graphicsPreset = 4
Ray-tracing mode doesn't yet work via radv (I haven't tested amdvlk-open). I used the usual set of env vars to enable it, enabled it in-game and it just started eating RAM. (I killed the process, but the OOM killer would probably have done that after another few minutes anyway.)
This game works fine when seated using Vive controllers.
As a matter of convenience, I changed the launch command so that the HMD audio was used. (The details are, however, beyond the scope of this report.)
For multi-player, you must use Proton 5.13 or later. With 5.0, it will reliably hang when you enter the lobby.
Could not log in (hourglass) with newer versions of Proton.
Crashes within minutes with esync enabled.
Sound works. Video doesn't -- other than a menu bar, the window is entirely black.
Without this, all rendering is done in black on black, with black buttons to click on.
SDL_VIDEO_MINIMIZE_ON_FOCUS_LOSS=0 %command% --disable-gpu
protontricks 9900 d3dcompiler_47
Missing glyphs in a memory/symbol-match minigame, making it effectively impossible to complete that task. Missions containing this minigame have to be skipped.
Frequently crashes when starting up (initial progress bar still displayed). This appears to be related to the Steam overlay.
Occcasional glitches with item shapes, the occasional missing texture.
Game bug. I loaded one auto-save file and it promptly created another ‒ in the process, overwriting the one which I decided that I actually needed to load.
Mostly, problems are only occurring after an update.
Probably nothing which Windows users don't see. However:
- Occasionally, a door or other item is mispositioned, e.g. an airlock door is positioned as if part of another airlock immediately above.
- Glitches while base-building. I have a base where, when I moved a habitation unit, some of its content got left behind and get mispositioned again when I try to move them.
- One instance of my ship being embedded in a launch pad…
With current kernels (6.5.x, 6.4.x, older unknown), exiting the game causes a lot of warnings to be logged by amdgpu. A fix already exists for this but is not yet in release kernels.
Occasional glitches with item shapes (typically re. low-polygon versions of weapons), the occasional missing texture.
Game bug. I loaded one auto-save file and it promptly created another ‒ in the process, overwriting the one which I decided that I actually needed to load.
Occasional assertion failures (!status && "vkQueuePresentKHR"), usually occurring at start-up or when moving between locations.
None yet seen with Mesa 23.2.1, though.
Probably nothing which Windows users don't see. However:
- Occasionally, a door or other item is mispositioned, e.g. an airlock door is positioned as if part of another airlock immediately above.
- Glitches while base-building. I have a base where, when I moved a habitation unit, some of its content got left behind and get mispositioned again when I try to move them.
- One instance of my ship being embedded in a launch pad…
Notable improvement in frame rate with Mesa 23.2.1. Also using a recent kernel with this bug fix present.
protontricks 329380 dsound (else no sound)
The launcher is partially broken (all black). However, the game can be launched by clicking near the left, just below where the game name should be shown.
Otherwise, the game appears to run well, though silently unless -- as others have mentioned -- you use winetricks or protontricks to install ‘xact’.
The Repentance DLC is installed. As that is not available natively, Proton is required. I have no idea whether it ever will be available natively.
Gameplay is entirely mouse-driven.
Press A to pause or resume; press X to restart the current level.
Fails to start up about half of the time.
Gameplay is entirely mouse-driven; touchscreen works fine for it.
Press A to pause or resume; press X to restart the current level.
Some crackling, loss of audio (and duplicated audio) in the first cutscene. Probably due to background processing not completed; problems did not re-occur after restarting that scene.
Otherwise, only occasional minor glitches which seem related to system load or disk access.
Demo.
Caused a lot of GPU page faults (in batches) to be logged along with some gmc_v10_0_process_interrupt: 42 callbacks suppressed messages (for various values of 42, usually 3 digits). No GPU hang or reset, though.
RADV_PERFTEST=rt VKD3D_CONFIG=dxr11 %command%
Edited launcher-configuration.json so that the game falls back to DirectX 11.
With DX11, the game runs without problems.
With DX12, though:
- Proton 7.0-5 causes the game to crash almost immediately, briefly showing a black window; until a newer version is released, either Proton Hotfix or (I'm told) Proton Experimental is required.
- I've seen GPU hangs:
- without ray-tracing, after some time (probably related to this kernel bug report);
- with ray-tracing, immediately during actual gameplay (title screen's fine).
The launcher doesn't work here, for reasons unknown – it's as if I were using the --skip-launcher option.
Losing input focus will cause the game to stop responding. Minimising then restoring the game window is sufficient to restore normal behaviour.
Configuring your window manager or using another tool to automate this will help, e.g. with devilspie2:
-- ~/.config/devilspie2.lua
scripts_window_blur = {
'blur.lua'
}
-- ~/.config/devilspie2/blur.lua
if get_window_name() == "Titan Quest Anniversary Edition" then
minimize()
end
Occasionally stops, reporting a problem with the cursor. Also clearly a problem with error reporting, as the error code given is “Success” (errno=0).
I find that if this happens, it will then persistently hang on startup; there may be a file or two to delete in …/Steam/steamapps/compatdata/858260 but I don't yet know which. (I've been taking the sledgehammer approach of deleting it all.)
You will need to install the black-screen-fix branch. It appears that legacy reprojection is required for this game (best to select this quickly while the game is starting up for the first time).
