Black Ops 1 suffering driver timeouts on AMD graphics cards.

[Dovahnaut]

What happened?

This occurs in both SP & MP games, including zombies, and even on LAN.
When playing on an AMD graphics card (my system uses an RX 9070 but there are reports of it happening on an RX 590 as well) the game will, at some random point, freeze up for several seconds, even a minute, as the graphics card suffers a driver timeout. The game will resume afterward, but will suffer more and more driver timeouts as time goes on.
It's worth noting that WAW and Black Ops 2 do not suffer this issue, only Black Ops 1.
This seems to happen regardless of driver version.

Expected result

I'm really not sure what to put here. I guess I expected the game not to suffer driver timeouts.

Steps to reproduce

1. Use an AMD graphics card.
2. Play Black Ops 1.
3. Wait until a driver timeout occurs.

Affected game(s)

BO1 Multiplayer (T5MP)

Affected component(s)

Client (game)

Plutonium version

r5246

Relevant logs

No response

Additional information

There is a compatibility fix made by an "EvelynYuki" on Gitlab, which claims the issue is due to Plutonium's executable name being different than the executable name AMD drivers expect for Black Ops 1.
Unfortunately, as far as I'm aware this compatibility fix only works on LAN, and doesn't allow for MP at all.
Maybe it'd be helpful to the devs.

Operating system

Windows 10 Home 22H2

Plutonium profile

https://forum.plutonium.pw/user/dovahnaut

Discord username

No response

[ineedbots]

This is because the plutonium-bootstrapper-win32.exe isn't marked by your driver as a 'game'. The reason it doesn't happen on steam is because it uses the 'BlackOps.exe', which AMD can recognize as a game. I don't own any amd hardware, so I wouldn't be able to test, but I think there is a way of adding an exe to the list of 'game' exes.

Doing a google search about the issue yields the same issue across many different games.

[Dovahnaut]

Right, I mentioned the exe name mismatch myself.
Adding the exe to a "game list" is news to me though, especially considering the Gitlab fix I linked states that the driver issue is hardcoded, but if you can find out more about that then I'd be happy to hear about it, I couldn't turn anything up in searches personally.

Truthfully, while any temporary fixes would still be appreciated, I opened this issue more for the Plutonium devs to try incorporating a fix into the launcher itself.