PC Graphics

[RogueStriker]

Hello,

Myself and a large number of users with AMD cards have been having OpenGL related crashes in the game Beyond All Reason. The stacktrace for the games crash refers to atio6axx.dll which is used for OpenGL games. The only fix right now seems to be rolling back  to a driver from late last year which does not work well for those of us who are playing other games that benefit from newer drivers. I have made multiple attempts with recent drivers, using the AMD clean up utility each time and it does not fix the issue. Below I can provide a link to the crash logs from the game. The most recent crash was on 4/23 at 7:30PM. 

https://log.beyondallreason.dev/logs-20250424T0309-rzueltKz.zip 

[Voytsje]

I'm also experiencing crashes when playing Beyond All Reason with Adrenalin 25.3.1, 25.3.2 and 25.4.1.

I don't experience any crashes in Adrenalin 25.2.1 and older, it seems like something was changed in 25.3.1 that is causing these crashes.

[Neoony]

Same here on 7900 XTX Nitro+
Filed AMD bug report from the crash few days ago

This game is gaining popularity fast and it seems broken for AMD users.
https://www.beyondallreason.info/

Devs pointing to AMD (seems Nvidia does not have such crashes)

[Voytsje]

It is the latest AMD drivers that are the problem. Upgrading or reinstalling the newest drivers doesn't help when it is the newest drivers that are broken.

You have to downgrade your drivers to work around this issue.

[AMD-baozhlu]

@RogueStriker could you provide a fastest/easiest way to reproduce this issue ?

[RogueStriker]

@AMD-baozhlu Yes most of the time it will crash within the first 20 to 30 minutes of a match. The game will hang and go to a black screen with music still playing for a few seconds then I will get a notification from the driver that it detected a driver timeout.  

[Neoony]

7900 XTX Nitro+
25.4.1

Start the game and start skirmish.
Do a 4vs4
Map Center Command BAR

Then crash within the first few minutes of the match....or within first half hour (but mostly crashed within just first few minutes)
You can also just leave it without selecting your commander position and it will crash after a while.

Crashes on many maps, but on that one I consistently crashed within the first few minutes.
Only once it took around half hour on that map.
I could never finish a match on that map yet

(it seems like some maps crash more than others)

[Neoony]

I can also confirm again that 24.12.1 is working fine
3 matches, no crashes
But I would rather not use old version

[AMD-baozhlu]

Thanks Neoony for providing such a simple and quick way to reproduce this issue, I clicked on skirmish but I only see 1v1/2v2/3v3, didn't see 4v4, I don't understand these map very well, I picked a map at random and played around with this for a few minutes and was not able to reproduce this issue. maybe I  overlook any steps ?

Can you help to capture a trace using apitrace ? So that I can debug directly using the trace.

It would be even better if you could also record a video showing the steps to reproduce.

[Voytsje]

When setting up a skirmish, you need to click on the advanced button and the game allows you to pick any map and add any number of AI opponents to the game that you want.

I was able to capture a trace using apitrace. The file is pretty big, 13GB I've shared it through my dropbox account.

https://www.dropbox.com/scl/fi/md44mjv6h3mlk1cawk0ut/bar2.trace?rlkey=f0zfojwv2ml0r5xszt71jvty2&st=x...

[AMD-baozhlu]

Hi, Voytsje, can you help capture a trace on Nvidia GPU, I need a trace which can run to the end in Nvidia but will crash midway on AMD GPU (same reason as crash when running the app directly on AMD GPU). 

[Voytsje]

I have an old PC with a GTX 1060, but it isn't set up for gaming right now. I guess I can get Windows and BAR set up on it and try it out.

If you need to compare a trace of the game crashing on an AMD GPU against it not crashing, maybe a trace of the game running with Adrenalin 24.12.1 could help you in figuring out what the problem is? It is also a lot easier for me to make a trace using an older driver than it is to get everything set up on the PC with the Nvidia GPU.

BAR doesn't crash with Adrenalin 24.12.1 and it is the version that the BAR developers are currently recommending until this issue is resolved.

That said, I'm not sure by what you mean a trace running to the end? The is no limit to how long a match in BAR can be, should I run the game for the same amount of time as the trace with the GPU timeout? Or should I run it longer?

edit - My current GPU is a 7900 GRE, I also have an old 5700 XT that I can try, would that be interesting?

[AMD-baozhlu]

Yes, you are right, using Adrenalin 24.12.1 is a better idea than using Nvidia. The current issue is that I ran the trace, but I am not sure if this trace can reproduce the issue because when we use the wrong driver to capture a trace, the trace does not record the OpenGL calls after the crash. Therefore, when the trace replay ends, we don't know if it is caused by the trace ending or a crash. besides, Besides, when I replay the trace, I cannot see the game screen after loading the match on both Nvidia and AMD, you can try to replay your trace on your machine.

[AMD-baozhlu]

@Voytsje @Neoony 

I start skirmish -> Do a 4vs4 -> Map Center Command BAR, this game has been running for more than 30minutes but still no crashing, can anyone help to record a video showing the steps to reproduce?

besides, have you changed the game and Radeon setting? or is it reproducible with default setting?

[Voytsje]

I'm just using the default performance settings in the Adrenalin software, I have not enabled any of the advanced features (No framegeneration or anything like that). I have disabled the Radeon overlay. (The crashes happen no matter if the overlay is turned on or off)

I don't have much time to troubleshoot right now, I'll try and see if I can get a recording of the game crashing later.

Graphics quality in game is set to ultra.

So far the only way I know of how to reproduce the issue is to just load into a match and then wait for the game to crash. I don't think anyone has been able to identify any specific in-game event that triggers the crashes, they seem to just happen randomly although they do appear to happen more frequently on some maps compared to others.

Center Command BAR is a map that crashes very frequently for me, but I don't know what exactly it is about that map that causes it to crash so often.

[AMD-baozhlu]

Video link:  Beyond-All-Reason-Spring-video

I recorded a video, Neoony said "we can also just leave it without selecting your commander position and it will crash after a while", so I just select a commander position but didn't actively play it, yet I didn't observe crash after 30 minutes, trying many times, can you see if my operation is correct? 

[Neoony]

I guess I cant watch the video "You do not have sufficient privileges for this resource or its parent to perform this action."

I would usually crash the most with these skirmish settings: https://imgur.com/n5MrHzq 
Most of the time just within few minutes.

I installed the 25.4.1 again and tried to record a video, but of course I didnt crash this time.
I could only do around 20 minutes and then I had to go. Not enough time.

I also used Ultra graphics settings. (I saw that someone in the discord tested lower graphics and no change with crashing, so I never tried going lower)

I dont have any AMD settings set for the game, everything is off except Freesync on AMD optimized and Tesselation also on AMD optimized.
While I do use Virtual Super Resolution 4k on 1440p monitor, but surely not all others crashing use it.
I have however also tried to play with Freesync off, and OpenGL tripple buffering on and also tried to force vsync, but none of that helped or affected it.
I also did send the AMD Bug report once from the crash, linked to the game and explaining it there.

When I first started the game, I could play few matches fine. Then had a crash here and there and then I tried the Center Command BAR and just kept crashing within the first few minutes, while I could only manage 1 time to get to around half hour. And then I also kept crashing on few other maps I tried.

I will keep trying to get a video of the game settings and crash, if I find some time.

I have to also note that while using the 24.12.1 which does not crash, I have noticed that around the time that I would crash on 25.4.1, I would get a huge stutter, very similar to when the crash happens, however it recovers and game continues without issues and it never freezes like that again in that match.
I saw that on the Center Command BAR map and also on the scavengers scenario and the default map thats selected.
Again this would happen either just few minutes after match start, or later maybe half hour into the match. Seems very similar, but it recovers.

When the crash happens on 25.4.1, the game freezes, but the mouse moves for few seconds, until the whole PC completely freezes for 1/few minutes and then it crashes and AMD Bug report pops up.
(I remembered that I do also have the TdrDelay thingy set in registry for other reasons which might probably make the freeze longer until the GPU crash, I guess)

And when on 24.12.1 it freezes around that same time, also the game is frozen but mouse moves. It just does that one big stutter for around 1-3 seconds and then the game continues, instead of the whole PC freezing like on 25.4.1

[AMD-baozhlu]

you can download the video here to see if my operation is correct

Video link:  Beyond-All-Reason-Spring-video

[AMD-baozhlu]

Video link:  Beyond-All-Reason-Spring-video

[RogueStriker]

Here is a crash apitrace for me. 

https://drive.google.com/file/d/13yruFoESVKRQFt9VwpbRRb1IuXvpWmLa/view?usp=sharing

For whatever reason the apitrace running with the game seems to prolong the eventual crashing. I got massive freezes though that were similar to what happens when the game crashes but it would recover. Eventually though it finally crashed. I created a 6v6 game and just spectated it.

[Neoony]

Also discord thread on the topic on BAR Discord
Has many AMD people describing their experience
https://discord.com/channels/549281623154229250/1357160016767090709

[AMD-baozhlu]

Can anyone help to capture a trace using apitrace on Nvidia GPU? I need a trace which can run to the end in Nvidia but will crash midway on AMD GPU (same reason as crash when running the app directly on AMD GPU). 

So that I can debug directly using the trace. need crash within the first few minutes, othewise the trace file will be very large.