etlegacy
etlegacy copied to clipboard
ET:L crashes 2 seconds after joining a server when using AMD drivers newer than 2022
Hi all,
I've already asked in discord, but no solution came up so far, other than using the old amd drivers: amd-software-pro-edition-22.q4-win10-win11-nov15.exe I'm using an Sapphire AMD Radeon Rx 5700 XT NITRO+, OS is Windows 10 22H2 (Build 19045.4291). And ET:L 2.81.1.0
Behaviour:
- When using most recent drivers (whql-amd-software-adrenalin-edition-24.3.1-win10-win11-mar20-rdna.exe) (or any newer than 2022)
- Starting ET:L directly with a connect line in the link: "E:\Spiele\Enemy Territory - Legacy\etl.exe" +connect to.bunker4fun.com (crash also occurs when usually starting ET:L, but sometimes I manage to connect manually, sometimes it crashes in menu/console)
- ET:L's loading screen shows graphic errors it doesn't show when using the 2022 pro edition (see image 1)
- After approximately 2 seconds rendering the game, it freezes, both monitors turn black, ET:L closes, they turn on again, AMD shows an error message (see image 2)
image 1
image 2
Do you have r_fastsky 1 and it still crashes?
Also try ETe.
Is adding
+seta r_fastsky "1"
or 0 to the lnk file a valid way to change it even if it is written as 0 in an etconfig.cfg file?
If it is so, then yes, it crashes for both, 0 and 1
Also try ETe.
It show's similar behaviours in ETe
Having the same problem with drivers 24.4.1 (I didn't try any others).
This is what shows on Event Viewer:
Faulting application name: etl.exe, version: 2.82.1.0, time stamp: 0x6622943f Faulting module name: atio6axx.dll, version: 31.0.24031.5001, time stamp: 0x6615ae2f Exception code: 0xc0000005 Fault offset: 0x0000000001cfde3b Faulting process id: 0x0x30AC Faulting application start time: 0x0x1DA9BEB7FDA20FE Faulting application path: C:\Games\ETLegacy\etl.exe Faulting module path: C:\Windows\System32\DriverStore\FileRepository\u0402338.inf_amd64_d4de815aa579b06a\B402197\atio6axx.dll Report Id: bf147e40-0e1e-4036-a91e-5cdafb5a5093 Faulting package full name: Faulting package-relative application ID:
Is adding
+seta r_fastsky "1"
or 0 to the lnk file a valid way to change it even if it is written as 0 in an etconfig.cfg file? If it is so, then yes, it crashes for both, 0 and 1
Maybe some config that loaded later overwrote r_fastsky, best to try setting it ingame in the console.