STAR WARS: The Old Republic (1286830)

[okegima]

Compatibility Report

• Name of the game with compatibility issues: Star Wars The Old Republic (SWTOR)
• Steam AppID of the game: 1286830

System Information

• GPU: RX550
• Driver/LLVM version:
• Kernel version:
• Link to full system information report as Gist:

https://gist.github.com/okegima/6c5ff507e68d0701147d3c306afcea6c#file-gistfile1-txt

• Proton version:5.13-1

I confirm:

• [*] that I haven't found an existing compatibility report for this game.
• that I have checked whether there are updates for my system available.

Symptoms

Can't use ctrl c for copy and ctrl v to past in game chat or mail. ctrl a not working too. Not able to copy a word and past inside game and from outside (text editor) to inside game. It work's well on outside game (runing ubuntu 20.04.1 LTS

No issue when launching game one win 7.

Reproduction

Yes, did change keyboard, but nothing happen.

[droidoz]

I have the same problem with cut and paste in swtor chat. Using Proton 5.0-9 or 5.13-1 on Steam .Didn't have the problem using Lutris.

[ptkato]

I'm encountering a weird behaviour on the game part, some things straight out don't appear, for example the characters' portraits:

What is weird is that sometimes rarely, they do appear. This ain't exclusive to the portraits only, other times, though less often, the character models themselves don't appear, my companion goes invisible, and even scenery vanishing in a few cutscenes, just to appear again in the next one. I didn't have that jankiness when I installed the standalone client through Lutris.

[kisak-valve]

Hello @ptkato, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

[ptkato]

Here you go.

[TheDromundKaas]

For a few days now, I have the problem of the FPS of SWTOR often times dropping to single digits. It happens much more when moving. I've seen it on planets (wide open areas) as well as my personal starship (tiny closed off area). When using a full DXVK_HUD, I can see that the running equalizer goes into the red at that point. It almost looks like loading, but the assets of SWTOR are basically tiny and low resolution. I've also checked if it is shader compilation, but it doesn't seem to be, at least there's no message bottom left about compiling shaders when it happens.

As I am on a rolling release distribution, I could not specifically state if it started with any version of the proprietary NVidia driver, as it gets updated frequently. I was watching the issue to see if anybody else had the problem, but maybe the Linux population of that game is low.

A month ago I did not have that problem, everything in the game was silky smooth 200+ FPS.

My system information

[SveSop]

Updated proton to proton-6.3-5 today, and i have severe stutters when turning around.
This is due to dxvk being updated to 1.9 with proton-6.3-5.

Downgrading dxvk (replacing the d3d dlls in ~/.steam/steam/steamapps/common/Proton 6.3/dist/lib64/wine/dxvk and the 32-bit folder) with dxvk compiled from https://github.com/ValveSoftware/dxvk/tree/f8a4ca555a6e5d89f5162a042bbae550902f4e49 - dxvk-1.8.1 fixes the problem.

I did bisect this around april, but have since forgotten the commit ID. (But have an approximate if interested)

[kisak-valve]

Hello @SveSop, please copy your system information from Steam (Steam -> Help -> System Information) and put it in a gist, then include a link to the gist in this issue report.

It might be worthwhile to also mention the regression to upstream DXVK with what bisect info you have left.

[ptkato]

@SveSop, in the options, try disabling nameplate scaling. For some reason nameplate scaling destroys my FPS when moving the camera around.

[SveSop]

@ptkato

@SveSop, in the options, try disabling nameplate scaling. For some reason nameplate scaling destroys my FPS when moving the camera around.

Interesting! That did indeed help a lot with DXVK-1.9. I guess this "scaling function" is what bugs out then, cos i did not really have any issues with fps < DXVK-1.9.
Thanks :)

[ptkato]

I might be mistaken, but I think it has to do with the shader cache, every time something new appears, the thingy needs to compile the shaders, when the name renders, the game stutters, but then when you turn the camera, the name changes its size, then it needs to compile the shaders again, thus stuttering once more. I used to have a similar problem in Path of Exile, when dynamic resolution was enabled.

[SveSop]

@ptkato No problem seeing that being the case... Its just that this is not such an issue with DXVK-1.8.1, so atleast something did change there when it comes to this dynamic thing.
Working with upstream DXVK atm, so will see if they can figure something out :)

[SveSop]

@kisak-valve This has now been closed upstream by: doitsujin/dxvk#2126
And in the meantime, it is a viable fix to disable Scale Nameplates with Distance in the settings, as this seems to help a lot.

[ChaosBlades]

I got an update to Mesa 21.2.1 two days ago and since then I have had no crashes on Proton 6.16-GE-1. It appears the issue was a driver issue for my 6900xt. I have not tried Proton Experimental.

[ChaosBlades]

I did test Proton Experimental shortly after my last post and it was working flawlessly but now it looks like things have broken again. I am now getting the following error message on Proton Experimental and Proton-6.18-GE-2 immediately after the recent updates. All other games I have tried are still working.

I continue to have a stable experience on Proton 6.3-7 playing SWTOR.

Edit: ...and as soon as I report the issue it is resolved. This was a XanMod Kernel bug. I just got an update to 5.14.9-xanmod2. It seems kernel 5.14 was released the same day I updated to 6.18 GE and a Proton Experimental update released. It is odd that this kernel bug affected SWTOR specifically on Experimental and GE specifically.

Here were the changes in this kernel update for thoroughness.

• 1d25d6095fa0 Linux 5.14.9-xanmod2
• f164cc43ea1a zstd: fix fall-through warnings
• 90383d79db7c futex2: Add sysfs entry for syscall numbers
• 442d05a80b7e kernel: Enable waitpid() for futex2
• e5a1578d65ce docs: locking: futex2: Add documentation
• fa85b67049cc futex2: Add compatibility entry point for x86_x32 ABI
• 5f5c48319897 futex2: Implement requeue operation
• 9970c3df4edb futex2: Implement vectorized wait
• 1ee81ce10706 futex2: Add support for shared futexes
• ea14247af977 futex2: Implement wait and wake functions
• 6afbd4f8cd3c futex: Implement mechanism to wait on any of several futexes
• 12aea22c5b44 futex*: remove FUTEX_WAIT_MULTIPLE operation and futex2 patchset

[kisak-valve]

Hello @vasiliyaltunin, your log hints that you're using PROTON_USE_WINED3D=1 in the game's launch options. Can you double check if this is the case and remove it? This runtime option is not supported and could be directly related to the issue you're seeing.

[vasiliyaltunin]

Yes! Thank you this is solved problem! On experementall all works just fine!

[juliovco]

My system information
Proton version: 6.3
My launcher has a warning at the top "An error has ocurred. Please exit and restart the SWTOR Laucher." If I try to login, it hangs forever.
launcher log has "ERROR Steam DLL failed to load"
It used to work before. Played with no issues around the beginning of December.
launcher_20220106.log
steam-1286830.log

[kisak-valve]

Hello @juliovco, these look like the lines of interest from your log:

err:module:import_dll Library api-ms-win-crt-runtime-l1-1-0.dll (which is needed by L"C:\\windows\\system32\\VCRUNTIME140.dll") not found
err:module:import_dll Library api-ms-win-crt-heap-l1-1-0.dll (which is needed by L"C:\\windows\\system32\\VCRUNTIME140.dll") not found
err:module:import_dll Library api-ms-win-crt-string-l1-1-0.dll (which is needed by L"C:\\windows\\system32\\VCRUNTIME140.dll") not found
err:module:import_dll Library api-ms-win-crt-stdio-l1-1-0.dll (which is needed by L"C:\\windows\\system32\\VCRUNTIME140.dll") not found
err:module:import_dll Library api-ms-win-crt-convert-l1-1-0.dll (which is needed by L"C:\\windows\\system32\\VCRUNTIME140.dll") not found
err:module:import_dll Library VCRUNTIME140.dll (which is needed by L"Z:\\home\\fnord\\.steam\\steamapps\\common\\Star Wars - The Old Republic\\steam.dll") not found
err:module:import_dll Library api-ms-win-crt-stdio-l1-1-0.dll (which is needed by L"Z:\\home\\fnord\\.steam\\steamapps\\common\\Star Wars - The Old Republic\\steam.dll") not found
err:module:import_dll Library api-ms-win-crt-string-l1-1-0.dll (which is needed by L"Z:\\home\\fnord\\.steam\\steamapps\\common\\Star Wars - The Old Republic\\steam.dll") not found
err:module:import_dll Library api-ms-win-crt-heap-l1-1-0.dll (which is needed by L"Z:\\home\\fnord\\.steam\\steamapps\\common\\Star Wars - The Old Republic\\steam.dll") not found
err:module:import_dll Library api-ms-win-crt-convert-l1-1-0.dll (which is needed by L"Z:\\home\\fnord\\.steam\\steamapps\\common\\Star Wars - The Old Republic\\steam.dll") not found
err:module:import_dll Library api-ms-win-crt-runtime-l1-1-0.dll (which is needed by L"Z:\\home\\fnord\\.steam\\steamapps\\common\\Star Wars - The Old Republic\\steam.dll") not found
err:module:import_dll Library api-ms-win-crt-environment-l1-1-0.dll (which is needed by L"Z:\\home\\fnord\\.steam\\steamapps\\common\\Star Wars - The Old Republic\\steam.dll") not found

I read this as either Proton 6.3 on your system or the game's wineprefix is damaged or incomplete. I would first try to verify the integrity of Proton's files in Steam, and if that doesn't help, then move the game's wineprefix (/home/fnord/.steam/steamapps/compatdata/1286830) somewhere out of the way. It should be noted that removing the wineprefix might cause saves and settings to be lost, which is why I suggested moving instead of deleting the folder.

[ChaosBlades]

Launcher works for me on 6.3 and Experimental Bleeding Edge. Checked just now.

[juliovco]

Thank you both for the responses. I had already tried to verify integrity of both Swtor and Proton 6.3, but nothing changed. Also had tried uninstalling Swtor and installing again (I made a backup of the settings), nothing changed as well.
Now I tried playing another game (Aragami) which I also installed with Proton 6.3, and it played normally. But maybe this one doesn't use those ms-win-crt stuff, I don't know.
And now I tried changing Swtor to Proton 5.13 and it worked - so I'm happy, I can live with that. But then it seems there is something wrong with my Proton 6.3 installation. I tried uninstalling it through steam, but it failed with unexpected error. Is it because I have other games installed with this version? Do I have to change the proton version of those games to be able to uninstall it?

[kisak-valve]

As you expected, Proton is treated as a game dependency by Steam when games are configured to use it. (ValveSoftware/steam-for-linux#7407)

Maybe give #4269 (comment) a try?

[juliovco]

I tried the solution from the other thread you linked (removing the dist folder of 6.3), then changed Swtor back to 6.3 to try again. Then the launcher worked, but when I logged in, the game became a black screen. I verified integrity of both Swtor and 6.3 files but nothing changed. So I changed the games that were using 6.3, and also my Steam Play default setting (it was set to 6.3 as well), and managed to uninstall 6.3. Started the game again to reinstall 6.3. This time the launcher didn't open anymore (tried multiple times). So I tried uninstalling both 6.3 and Swtor, deleted what remained of the 6.3 folder, and reinstalled Swtor (and 6.3 automatically). Same result, the launcher doesn't open. I click Play, nothing happens and after a long time the button turns green again.
steam-1286830.log

[schwigi]

Thanks as well @alasky17. Will use an older Version as well, until it is time to get experimental again.

[alasky17]

@schwigi @GregDuhamel This regression should be fixed with the most recent experimental release (experimental-8.0-20230727). Please let me know if there is any lingering regressive behavior :)

[GregDuhamel]

@alasky17 Got another issue on two different card (6600XT & 7900XT) it seems with DXVK :

22:59:03 kernel: [drm] Skip scheduling IBs!
22:59:03 kernel: [drm] Skip scheduling IBs!
22:59:03 kernel: [drm] Skip scheduling IBs!
22:59:03 kernel: [drm] Skip scheduling IBs!
22:59:03 kernel: [drm] Skip scheduling IBs!
22:59:03 kernel: [drm] Skip scheduling IBs!
22:59:03 kernel: [drm] Skip scheduling IBs!
22:59:03 kernel: [drm] Skip scheduling IBs!
22:59:03 kernel: [drm] Skip scheduling IBs!
22:59:03 kernel: [drm] Skip scheduling IBs!
22:59:03 kernel: [drm] Skip scheduling IBs!
22:59:03 kernel: [drm] Skip scheduling IBs!
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow done
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: recover vram bo from shadow start
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: ring mes_kiq_3.1.0 uses VM inv eng 14 on hub 0
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: ring jpeg_dec uses VM inv eng 4 on hub 1
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_1 uses VM inv eng 1 on hub 1
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: ring vcn_unified_0 uses VM inv eng 0 on hub 1
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma1 uses VM inv eng 13 on hub 0
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: ring sdma0 uses VM inv eng 12 on hub 0
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 11 on hub 0
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 10 on hub 0
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 9 on hub 0
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 8 on hub 0
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 7 on hub 0
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 6 on hub 0
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: ring gfx_0.0.0 uses VM inv eng 0 on hub 0
22:59:03 kernel: amdgpu 0000:03:00.0: [drm:jpeg_v4_0_hw_init [amdgpu]] JPEG decode initialized successfully.
22:59:03 kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode).
22:59:03 kernel: [drm] kiq ring mec 3 pipe 1 q 0
22:59:03 kernel: [drm] DMUB hardware initialized: version=0x07001A00
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resumed successfully!
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: SMU driver if version not matched
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: smu driver if version = 0x00000037, smu fw if version = 0x0000003b, smu fw program = 0, smu fw version = 0x004e5500 (78.85.0)
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: SMU is resuming...
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: SECUREDISPLAY: securedisplay ta ucode is not available
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: RAP: optional rap ta ucode is not available
22:59:03 kernel: [drm] reserve 0x1300000 from 0x84fc000000 for PSP TMR
22:59:03 kernel: [drm] PSP is resuming...
22:59:03 kernel: [drm] VRAM is lost due to GPU reset!
22:59:03 kernel: [drm] PCIE GART of 512M enabled (table at 0x00000084FEB00000).
22:59:03 kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset succeeded, trying to resume
22:59:02 kernel: amdgpu 0000:03:00.0: amdgpu: GPU smu mode1 reset
22:59:02 kernel: amdgpu 0000:03:00.0: amdgpu: GPU mode1 reset
22:59:02 kernel: amdgpu 0000:03:00.0: amdgpu: MODE1 reset
22:59:02 kernel: [drm:gfx_v11_0_hw_fini [amdgpu]] *ERROR* failed to halt cp gfx
22:59:02 kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
22:59:02 kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
22:59:02 kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
22:59:02 kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
22:59:02 kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
22:59:02 kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
22:59:02 kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
22:59:02 kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
22:59:02 kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
22:59:02 kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
22:59:01 kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
22:59:01 kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
22:59:01 kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
22:59:01 kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
22:59:01 kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
22:59:01 kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
22:59:01 kernel: [drm:amdgpu_mes_unmap_legacy_queue [amdgpu]] *ERROR* failed to unmap legacy queue
22:59:01 kernel: [drm:mes_v11_0_submit_pkt_and_poll_completion.constprop.0 [amdgpu]] *ERROR* MES failed to response msg=3
22:59:01 kernel: amdgpu 0000:03:00.0: amdgpu: soft reset failed, will fallback to full reset!
22:59:01 kernel: Failed to wait all pipes clean
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x0
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x0
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x0
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CB/DB (0x0)
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          RW: 0x1
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          MAPPING_ERROR: 0x0
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          PERMISSION_FAULTS: 0x5
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          WALKER_ERROR: 0x0
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          MORE_FAULTS: 0x1
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:          Faulty UTCL2 client ID: CPC (0x5)
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00040A51
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:40 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
22:59:00 kernel: gmc_v11_0_process_interrupt: 55 callbacks suppressed
22:59:00 kernel: amdgpu 0000:03:00.0: amdgpu: IP block:gfx_v11_0 is hung!
22:58:59 kernel: amdgpu 0000:03:00.0: amdgpu: GPU reset begin!
22:58:59 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process swtor.exe pid 110324 thread dxvk-submit pid 110372
22:58:59 kernel: [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=98704404, emitted seq=98704406

Just to be sure any recent change on that side ?

[kisak-valve]

Hello @GregDuhamel, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the GPU reset, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put it in a gist, then include a link to the gist in this issue report.

[alasky17]

@GregDuhamel There are lots of changes in DXVK ... if you suspect a regression, it is fairly easy to confirm it is DXVK if you have a working Proton version to compare (eg 8.0-3).

1. Save a copy of these folders: ~/.steam/steam/steamapps/common/Proton - Experimental/files/lib/wine/dxvk and ~/.steam/steam/steamapps/common/Proton - Experimental/files/lib64/wine/dxvk.
2. cp ~/.steam/steam/steamapps/common/Proton 8.0/dist/lib/wine/dxvk/* ~/.steam/steam/steamapps/common/Proton - Experimental/files/wine/dxvk/. and same for lib64 folder.
3. After you are done, re-replace the dxvk contents in Experimental with the original dxvk folders that you saved, and the run "Verify Integrity of Files" on Proton - Experimental to confirm that everything is back to default.

Also, it helps to also describe the behavior you are seeing in addition to posting a log :)

[GregDuhamel]

Sorry guys it's taking longer to provide you with trace, unfortunately or fortunately, i was not able to reproduce the crash during the last two or three days.

[GregDuhamel]

Here we go @kisak-valve , hopes this will be enough.

Steam Runtime Diagnostics
steam-1286830.log.zip

[GregDuhamel]

@GregDuhamel There are lots of changes in DXVK ... if you suspect a regression, it is fairly easy to confirm it is DXVK if you have a working Proton version to compare (eg 8.0-3).

1. Save a copy of these folders: ~/.steam/steam/steamapps/common/Proton - Experimental/files/lib/wine/dxvk and ~/.steam/steam/steamapps/common/Proton - Experimental/files/lib64/wine/dxvk.

2. cp ~/.steam/steam/steamapps/common/Proton 8.0/dist/lib/wine/dxvk/* ~/.steam/steam/steamapps/common/Proton - Experimental/files/wine/dxvk/.  and same for lib64 folder.

3. After you are done, re-replace the dxvk contents in Experimental with the original dxvk folders that you saved, and the run "Verify Integrity of Files" on Proton - Experimental to confirm that everything is back to default.

Also, it helps to also describe the behavior you are seeing in addition to posting a log :)

Unfortunately 8.0-3 seems to have the same behavior for me.

It's hard to describe this issue, it's so random, i can do like 7 PVP match and have no issue and then out of nowhere, always at the beginning of the match, game froze, host is unresponsive and i have to do an hard reboot.

[ProjectSynchro]

I'm beginning to see intermittent gpu hangs again in this title, annoyingly I cannot consistently reproduce the issue, it seems to happen during dialog.

In X, my entire PC needs to reboot as the session cannot recover from a driver reset, whereas in Wayland the session does recover at least.

Relevant dmesg logs:

[ 4997.557010] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx_0.0.0 timeout, signaled seq=77966164, emitted seq=77966166
[ 4997.557219] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process swtor.exe pid 7391 thread dxvk-submit pid 7432
[ 4997.557401] amdgpu 0000:0d:00.0: amdgpu: GPU reset begin!
[ 4998.570991] amdgpu 0000:0d:00.0: amdgpu: IP block:gfx_v11_0 is hung!
[ 4998.571158] gmc_v11_0_process_interrupt: 47 callbacks suppressed
[ 4998.571161] amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:174 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[ 4998.571165] amdgpu 0000:0d:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
[ 4998.571167] amdgpu 0000:0d:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00040B5D
[ 4998.571169] amdgpu 0000:0d:00.0: amdgpu:      Faulty UTCL2 client ID: CPC (0x5)
[ 4998.571170] amdgpu 0000:0d:00.0: amdgpu:      MORE_FAULTS: 0x1
[ 4998.571172] amdgpu 0000:0d:00.0: amdgpu:      WALKER_ERROR: 0x6
[ 4998.571173] amdgpu 0000:0d:00.0: amdgpu:      PERMISSION_FAULTS: 0x5
[ 4998.571174] amdgpu 0000:0d:00.0: amdgpu:      MAPPING_ERROR: 0x1
[ 4998.571175] amdgpu 0000:0d:00.0: amdgpu:      RW: 0x1
[ 4998.571180] amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:174 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[ 4998.571183] amdgpu 0000:0d:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
[ 4998.571184] amdgpu 0000:0d:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 4998.571186] amdgpu 0000:0d:00.0: amdgpu:      Faulty UTCL2 client ID: CB/DB (0x0)
[ 4998.571187] amdgpu 0000:0d:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 4998.571188] amdgpu 0000:0d:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 4998.571189] amdgpu 0000:0d:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 4998.571190] amdgpu 0000:0d:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 4998.571191] amdgpu 0000:0d:00.0: amdgpu:      RW: 0x0
[ 4998.571196] amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:174 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[ 4998.571198] amdgpu 0000:0d:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
[ 4998.571200] amdgpu 0000:0d:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 4998.571201] amdgpu 0000:0d:00.0: amdgpu:      Faulty UTCL2 client ID: CB/DB (0x0)
[ 4998.571202] amdgpu 0000:0d:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 4998.571203] amdgpu 0000:0d:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 4998.571204] amdgpu 0000:0d:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 4998.571205] amdgpu 0000:0d:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 4998.571206] amdgpu 0000:0d:00.0: amdgpu:      RW: 0x0
[ 4998.571211] amdgpu 0000:0d:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:174 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[ 4998.571213] amdgpu 0000:0d:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
[ 4998.571215] amdgpu 0000:0d:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000000
[ 4998.571216] amdgpu 0000:0d:00.0: amdgpu:      Faulty UTCL2 client ID: CB/DB (0x0)
[ 4998.571217] amdgpu 0000:0d:00.0: amdgpu:      MORE_FAULTS: 0x0
[ 4998.571218] amdgpu 0000:0d:00.0: amdgpu:      WALKER_ERROR: 0x0
[ 4998.571219] amdgpu 0000:0d:00.0: amdgpu:      PERMISSION_FAULTS: 0x0
[ 4998.571220] amdgpu 0000:0d:00.0: amdgpu:      MAPPING_ERROR: 0x0
[ 4998.571221] amdgpu 0000:0d:00.0: amdgpu:      RW: 0x0

My current driver is built from mesa-git's HEAD

I am still running an AMD RX 7900XTX, (Kernel 6.5.1): https://gist.github.com/ProjectSynchro/f0d4e4f102ca29c71a683ea49dd4df7e

If I can catch this error again with PROTON_LOG=1 I will update this post.

[GregDuhamel]

@ProjectSynchro did you get rid of it ? I'm still having some issue for nearly each dialog i'm looking at. Very difficult to play ...

[Blisto91]

Thank you for the reports. I have created a mesa issue to track the, at least rdna3, hang problem. https://gitlab.freedesktop.org/mesa/mesa/-/issues/9878

[GregDuhamel]

Thanks so much for this @Blisto91 ! Your workaround is working perfectly too !

[Blisto91]

Proper fix have now been merged in mesa https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/25402

[ahjolinna]

does anyone else have flickering issue? especially if you play on "fullscreen (windowed)", in gameplay its not so bad but still noticeable/annoying compare to cinematic/conversation where it can be REALLY bad

Steam Runtime Diagnostics

log file (with experimental)

---

system spec:

Operating System: openSUSE MicroOS 20231226
KDE Plasma Version: 5.91.90
KDE Frameworks Version: 5.248.0
Qt Version: 6.6.1
Kernel Version: 6.6.7-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 5700G with Radeon Graphics
Memory: 46.8 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2
GPU Driver: v545.29.06

[Blisto91]

@ahjolinna Hi there. Are you able to provide a screenshot or video that shows the issue?

[ahjolinna]

@Blisto91 I wish I could do some video, but I use wayland (on nvidia) ...and proper screenshare/capture isn't there yet.

also its more of mix of stuttering & flickering

[ahjolinna]

@Blisto91 well I took a video with my phone. Here a new sith inq. characters first intro scene and you can see even from a phone recoding the issue...and this is even the mild version from what I have had :

20231230_000504.mp4

[ahjolinna]

oh and for some reason everytime I login I have to re-accept the end-user & licenses agreement and ToS ...dont know why it wont remember it.

also according to their latest email they have a new 64bit client, maybe thats why there are some new issues (dont know when this happened, I just started to replay)

[Blisto91]

@ahjolinna Taking a look with my AMD GPU i am not reproducing.
Looking at your driver version and that you are using Nvidia with Wayland i believe it could be this issue https://forums.developer.nvidia.com/t/545-29-02-ghosting-artifacting-stuttering-on-fullscreen-when-below-monitor-framerate/271853

As for the EULA appearing each time, which i am seeing too, i believe this might just be the game as i am seeing reports of it in general when doing a quick search. Though i will try to poke at it a bit and see.

[elinmyr]

EULA thing happens to me on steam version any time I validate files. Presumably would happen on a new install as well.

[ProjectSynchro]

The EULA bug is reproducible on windows as well.. seems like they have forgotten to ship a file on Steam..

If you want to fix it, there's a workaround on this forum thread: https://forums.swtor.com/topic/931246-eula-bug-fix/

I did this myself to see if I could get it fixed and it seems to work, according to: https://www.reddit.com/r/swtor/comments/l101al/eula_agreement_every_time_i_open_the_game/k9lbdji/, it looks like the file is the same for everyone (the one my vanilla launcher generated is the same as the one that user posted on Reddit).

I attached the missing EULA.settings file if anyone needs it, it should workaround the EULA prompt when launching (rename when using it): eula.settings.txt