Open Timm638 opened 3 months ago
Try turning Radeon Enhanced Sync off?
I've had Enhanced Sync turned off already, but I've disabled FreeSync in my GPU drivers and the issues seems to be fixed? If it that happens again, I'll reopen the issue with updated logs.
Does it also happen without undervolting?
I have no info on that, since my PSU can't handle the full load. I haven't had otherwise any issues in other games.
It has happend again in a large match with long runtime, but this time Windows detected that the game froze and showed the "Window not responding" dialog box. Game version was 1.2988.0, with this time a non-undervolted AMD RX 5700 XT with Adrenalin 24.10.21. VSync in game was enabled, Radeon Enhanced Sync disabled.
Launcher Log spring-launcher-20240728T192528.log Uploaded log files from Launcher https://log.beyondallreason.dev/logs-20240728T2107-j7z6v1jQ.zip
Description
When playing matches with many players (~12+), my game freezes visually. Ingame sound can be still heard, including pausing and resuming the game. Clicking on buttons on the frozen windows plays a button click sound, but no further reaction visually.
There doesn't seem to be an existing issue.
1904 seems to be similiar and I tried the solution to set VSync to "Enabled", but that didn't resolve my issue. Compared to that issue, only BAR itself freezes, otherwise the PC is still running normally.
My GPU is a underclocked AMD RX 5700 XT with Adrenalin Drivers 24.3.1. Further information to the system are in the included DxDiag.txt. I've included two logs with the visual freezing. The second log was produced by rejoining the first match, after finishing the rejoin process, the game instantly freezed again.
Are the any further diagnosis tool I can use to collect further information?
Expected Behaviour
No Freezing of the Game
Actual Behaviour
Visual Freeze of the game, clicking on the frozen GUI still plays button sounds, other ingame sounds are still present.
Reproduction steps
Sadly no exact steps, long matches with high player counts and high runtime seem to trigger this issue. When the situation happens, it's reproducible by rejoining the match and rewinding until to the current game state.
Other
20240529235157_infolog.txt 20240529233748_infolog.txt DxDiag.txt