search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
23.71k stars 1.03k forks source link

STAR WARS: The Old Republic (1286830) #4326

Open okegima opened 3 years ago

okegima commented 3 years ago

Compatibility Report

System Information

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

I confirm:

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.

GregDuhamel commented 1 year ago

Hello,

same here, i had to switch back to Proton 8.0-2 I'm using Steam through Flatpak

Steam Runtime : https://gist.github.com/GregDuhamel/722edd6fb9faeebc1e628c5a34373d9d

System Information ``` ```
alasky17 commented 1 year ago

@schwigi @GregDuhamel Thank you so much for the reports! You have indeed found a regression with one of the experimental patchsets that is currently a work in progress (hence the name "Proton Experimental" :D). I have passed along the information so that the patchset can be refined and improved. In the meantime, please continue to use Proton 8.0-2 for this title as this patchset will not be included in a stable release until we have squashed such regressions.

GregDuhamel commented 1 year ago

Thanks @alasky17 for your quick answer.

schwigi commented 1 year ago

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

ProjectSynchro commented 1 year ago

Hello, I am seeing a GPU hang when completing quests in both Proton 8.0-2 and Experimental (bleeding-edge).

It typically is reproducible when the 'quest reward' page is supposed to open. Instead of opening, the GPU hangs, and X crashes. A reboot is necessary to recover from this.

If you want to attempt to reproduce, try finishing any quest that has a reward.

I have attached a log from a run that crashed: steam-1286830.zip

I am running an AMD RX 7900XTX with Mesa 23.2.0 (it's built from git, cannot recall which commit specifically) System Information: https://gist.github.com/ProjectSynchro/f0d4e4f102ca29c71a683ea49dd4df7e

Blisto91 commented 1 year ago

@ProjectSynchro Hello there. I haven't been able to reproduce with the same GPU with either radv 23.2.0-rc1 or latest git. I tried completing a couple of quests on each with a rewards screen and also 1 quest before updating my git version. Might be interesting if you could try a stable driver or newer git version.

ProjectSynchro commented 1 year ago

@ProjectSynchro Hello there. I haven't been able to reproduce with the same GPU with either radv 23.2.0-rc1 or latest git. I tried completing a couple of quests on each with a rewards screen and also 1 quest before updating my git version. Might be interesting if you could try a stable driver or newer git version.

I was also beginning to suspect it's due to a faulty build of Mesa, especially once issues in other Vulkan applications started to manifest.

After a fresh rebuild from latest git, the issue seems to have disappeared..

If it starts happening again, I'll attempt to debug the issue and open a report upstream.

alasky17 commented 1 year ago

@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 commented 12 months ago
@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 commented 12 months ago

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 commented 12 months ago

@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 commented 12 months ago

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 commented 11 months ago

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

Steam Runtime Diagnostics steam-1286830.log.zip

GregDuhamel commented 11 months ago

@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 commented 11 months ago

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 commented 11 months ago

@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 commented 11 months ago

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 commented 11 months ago

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

Blisto91 commented 11 months ago

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

ahjolinna commented 7 months ago

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 commented 7 months ago

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

ahjolinna commented 7 months ago

@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 commented 7 months ago

@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 :

https://github.com/ValveSoftware/Proton/assets/6993072/922cbe0d-4d94-460d-8d23-f4e862cd9db2

ahjolinna commented 7 months ago

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)

image

Blisto91 commented 7 months ago

@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 commented 7 months ago

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

ProjectSynchro commented 7 months ago

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