MSI Afterburner still a problem?

Take command of air and naval assets from post-WW2 to the near future in tactical and operational scale, complete with historical and hypothetical scenarios and an integrated scenario editor.

Moderator: MOD_Command

Post Reply
Dimitris
Posts: 15480
Joined: Sun Jul 31, 2005 10:29 am
Contact:

MSI Afterburner still a problem?

Post by Dimitris »

Hi all,

One of the oldest graphics-related issues we've had is that running MSI's Afterburner utility alongside CMANO/CMO would result in red-X or a hard crash.

In v1.04 we have fixed a major cause of the red-X issue, and we are curious if the fix also affects compatibility with Afterburner. We would therefore appreciate feedback from anyone who uses this utility regularly.

Thanks.
thewood1
Posts: 10259
Joined: Sun Nov 27, 2005 6:24 pm
Location: Boston

RE: MSI Afterburner still a problem?

Post by thewood1 »

I run MSI AB on my big laptop and have had no issues with CMO. I'll double check.

Edit: MSI AB 4.6.4 beta 3 running with CMO 1.04 with no issues. Slight overclocking on the 2080.
Twistedpretzel
Posts: 69
Joined: Sun Sep 06, 2020 2:31 pm

RE: MSI Afterburner still a problem?

Post by Twistedpretzel »

I have had no issues using MSI Afterburner, but if I use rivatuner and turn the On Screen Display (OSD) on to show performance of GPU and CPU I still get the red X when a scenario loads. 1.04.114733
LMychajluk
Posts: 126
Joined: Sun Oct 08, 2017 10:25 am

RE: MSI Afterburner still a problem?

Post by LMychajluk »

ORIGINAL: Twistedpretzel

I have had no issues using MSI Afterburner, but if I use rivatuner and turn the On Screen Display (OSD) on to show performance of GPU and CPU I still get the red X when a scenario loads. 1.04.114733

Same. If I turn off the 'On-screen Display Support' option in rivatuner, I don't have the map problems.
KnightHawk75
Posts: 1850
Joined: Thu Nov 15, 2018 7:24 pm

RE: MSI Afterburner still a problem?

Post by KnightHawk75 »

I've been using Afterburner the entire time I've owned cmo (and cmano before it). I only turn it off when debugging issues to eliminate it as an issue before reporting anything, and I've never run into issues with having AB 4.5 running. That said all I use it for is to watch temps in my taskbar, I don't use any of the overlay osd\stuff same as others have said, which I image is where display interaction was causing issues at some point for some folks. So glad to hear about the locking\resume\display driver reset- red x thing being addressed though.


Post Reply

Return to “Command: Modern Operations series”