LeBlaque

HOOOOKAY!! Here we are! THREE months later. And what do we hear from BF and AMD? (crickets) (crickets) (crickets) Uh, gentlemen... it is STILL broken. ...and most egregious? I read the year 2024 things to come thread and not ONE reference to AMD issues. That is right, not ONE. But us "complainers" were referred to copiously in the second thread!

@Grey_Fox Appreciate your post. For the life of me I cannot FIND the notification on BFC that products do not work on "certain AMD cards." I may have missed it, but it is certainly not prevalent on the BFC website. And to be clear, it does not work properly on ALL AMD graphics cards unless legacy drivers are used and certainly doesn't work at all on those cards that cannot roll back. Your observations are spot on. I have come to the conclusion that perhaps as disappointing as anything is the continued silence by BFC on this issue. I did not expect this of this company given prior "transparency" experience. Communication behaviors seem more like those small companies that after taking your money on Steam in an Early Access environment wave their middle-finger at you while silently claiming "sucker" and then disappearing into the ether, never to address their game's issues and remaining in an Early Access unfinished state.

Follow-up from my AMD posting: yesterday from Dipak Hi @leblaque , As I have been informed, the OpenGL QA team already filed a ticket for the "out-of-memory" issue with larger maps. The dev team is looking into it. Thanks.

Okay, okay, so let me just summarize some things here: - AMD cards have been notoriously fickle with CM-- products for years. They've been largely BUSTED since early Spring '22 until the most recent version: except they are busted in large battles (I have confirmed working/not working as described) -AMD 7000+ users cannot roll-back drivers, so they are SOL until a "full fix." - Nvidia cards (I just recently found out) are also kinda busted on large battles, with 'deteriorating' drivers relative to OpenGL. -Rumor from other members is OpenGL programming from BF is "less than ideal?" potentially contributing to these issues. So in summary, how is this okay? How is it that regardless of numerous posts to both AMD and BF no one is really willing to offer an explanation, a full solution, hope for the future, etc? I'm tired of the excuse of "niche product" --- I get it -- but 18 MONTHS without a solution for games that are still being SOLD on multiple sites? This is NOT a legacy product!! If the game is not working on AMD, Nvidia, etc. SOMETHING NEEDS TO BE DONE TO PERMANENTLY RESOLVE THIS!! And... why is it I have never seen any post from BF on the AMD site regarding these issues? If they are using a "back door" they are not being successful, and I'm surprised that Dipak over at AMD (who I've bitched loud and long to) has never said anything regarding a BF inquiry to resolve this. As Sgt. Rock says, 'nuff said.

Reconfirmed-- AMD most recent drivers BUSTED on larger engagements (CMRT cat and mouse). Works on smaller, tho.... got the CM executable out of memory error at about 49% progress.... UN-F-BELIEVABLE.

Believe it or not, I've had some luck with a "fix" on the drivers released early December! Have it working on CMRT, CMBS, and CMFI... having said this, these are NOT larger battles. Nevertheless, finally some progress from AMD! per post here. https://community.amd.com/t5/opengl-vulkan/combat-mission-series-games-23-4-2-driver-fixes-quot-white-flash/m-p/650762#M5078

No, fixing the drivers myself is not "fun." And how many of us really run Linux for F- sake??? Here is my fed-up response today to AMD after another loyal CM purchaser can't get their AMD 7000 card to work... Broken drivers... apparently broken companies.... The unresolvable remains unresolvable with continued excuse-making that it is "fixed" in an internal build with an actual released driver that repairs CTDs and "white flashes" essentially vaporware. Shame on AMD and Battlefront for allowing this MULTI-YEAR issue to continue to exist. AMD 7000 users are out of luck as they can't roll-back drivers effectively, and BF continues to sell these products at full price on Steam with no warning the game is essentially broken with updated drivers. Frankly horrific customer services from both companies. Too bad this wasn't Call of Duty-- would've been fixed near immediately.... Here is a link to some more history for those that wish to keep up with this miserable issue "resolution." https://community.amd.com/t5/opengl-vulkan/combat-mission-series-games-23-4-2-driver-fixes-quot-whit... 0 Likes REPLY

@Jiggathebauce, @nathangun, @Grey_Fox As noted by Jigga... this issue remains unresolved. There is allegedly some hope, however-- see this AMD link. You may wish to consider posting yourself. https://community.amd.com/t5/opengl-vulkan/combat-mission-series-games-23-4-2-driver-fixes-quot-white-flash/td-p/607289 I am becoming very disenchanted with both Battlefront and AMD. I understand AMD has no strong desire to address an issue associated with a niche product. As such, this issue is largely in Battlefront's court as they sell multiple products at full price that are effectively broken with AMD graphics products. The BF "fanboys" claim we should not expect a small team to come to AMD's rescue. Well, if we keep passing the buck, who is going to solve the problem?? If you sell a product, unless it is legacy, you are obligated to support it. Get on the stick, BF! I tire of constant reporting to BF and AMD on the same issue over and over again. If I were not such a fan of the games, I'd be posting negative reviews on Steam, and putting-to-rest all my BF products. And.... next time.... Nvidia....

@Redwolfhere you go https://community.amd.com/t5/drivers-software/amd-driver-issues-with-opengl-in-combat-mission-games/m-p/640670#M182980

I have tried HARD for months to get this issue resolved with either AMD or BF. At the risk of sounding like either a naysayer or fanboy, I will just concur completely with @Grey_Fox. CM games are essentially broken on AMD cards unless legacy drivers are used-- which should not be expected for any game that is still being sold for any reasonable price on Steam, Slitherine, etc. You cannot get a REFUND on Steam after 2 hours use-- that is NOT a solution or "customer friendly." Continued sales does not seem ethical without Fox's "warning." P.S. I posted AGAIN today to AMD as apparently the "white flashes" are back with the newest driver.

Agreed that the 22 series of drivers noted works as stated. The remaining elephant-in-the-room issue is that updated drivers designed to improve many other games cannot be installed. This is a fourteen month issue still unresolved by AMD and Battlefront despite numerous trouble tickets to both. In fact, things seem to be going backwards as the most recent 23.7.2 drivers are CTD on "medium-sized" battles (less than battalion and smaller maps) in CMRT and CMBS.

I have no link for the BF troubleticket to AMD-- was just told it occurred by staff. Here is the link to my AMD ticket: https://community.amd.com/t5/opengl-vulkan/combat-mission-series-games-23-4-2-driver-fixes-quot-white-flash/m-p/607289

I posted a trouble ticket at AMD on this crashing out-of-memory issue. Apparently BF has done so as well as a result of my internal trouble ticket. Yesterday I got an email from AMD saying "they are tracking it." Should be another nine months before a fix....

I have an open trouble ticket that has been confirmed by BF and one of their beta testers RE: Out-of-Memory bug on the newest 23 drivers. It appears it happens on the largest battle maps as dependent on folks' AMD systems, smaller maps can be run w/o issue (including my own). Having said this, the beta tester's crash with 12 GB VRAM is certainly cause for concern. AND, CMBS Steam version is more problematic compared to BF direct purchase (unfortunately).

@Jiggathebauce no multiplayer needed. Just try single player with the largest CMBS file and see if it crashes. And if you want to try a multi-player game, just give me a email-- leblaque@hotmail.com

If I could appeal to this AMD community for some help-- while we collectively helped fix the "flashbang" the out-of-memory issue is also a game-killer. I am working with John at BF on a trouble-ticket but some extra "data" would help solve the problem. What would be helpful is try loading the LARGEST CM (Black Sea is a culprit, others) and see if the scenario crashes the game. My buddy and I have the exact same AMD card with 8GB or VRAM, but different levels of RAM (He 32 me 16). My mid-size email game crashes CMBS with 23-series drivers-- though not tiny scenarios-- while his system does not crash. BUT, the biggest CMBS files crash both our systems. Any feedback from the community would help resolve this continuing driver issue.... Let's get this problem knocked out, too! @Jiggathebauce @nox_plague @lerxster @BFCElvis @Bufo @Codreanu et. al.

I did now, Elvis, thanks.

@JoMac Thank you for the attempt! Unfortunately no luck after downloading/installing the three noted files. Still CMBS still crashes to desktop after one rotation of the camera. Astonishingly, this does not happen with CMRT. You made an excellent point which led to my observation: CMRT is a direct purchase from BF, while CMBS is a Steam (Slitherine) version. There has to be something up with THIS. Hoping @BFCElvis and @Battlefront respond to this-- should not be dealing with crashes as a long-standing issue area. Are you saying you are operating on the most recent 23-series AMD drivers???

A copy/paste from a prior thread given this is a separate issues unrelated to the "flash-bang" screen issue that has been resolved. Frankly, kinda disturbing as apparently a long-term unaddressed problem? *********************** @Myles Keogh @Battlefront.com Unlike Myles, I do need updated drivers (ideally) for other games. 23.4.2 is still bugged, and apparently, this is a long-standing issue per above post. This is infuriating in a way, as I am playing an email game in CMRT flawlessly (no flashbang, etc.) but a game in CMBS got the following error, then afterwards crashes to desktop when I rotate the view (my card is an RX 6600XT w. 8GB). I have attached relevant pics/dropbox links for BF (and others) to check on their AMD systems. All I can say is, https://www.dropbox.com/s/l25g01e0okcrrb5/Rollin' On The River 105.ema?dl=0 (CMBS PW: od) https://www.dropbox.com/s/0t049ub1b2xbdur/Retaking of Koshtovnist 153.ema?dl=0 (CMRT PW: od)

@BFCElvis @Myles Keogh @Battlefront.com Unlike Myles, I do need updated drivers (ideally) for other games. 23.4.2 is still bugged, and apparently, this is a long-standing issue per above post. This is infuriating in a way, as I am playing an email game in CMRT flawlessly (no flashbang, etc.) but a game in CMBS got the following error, then afterwards crashes to desktop when I rotate the view (my card is an RX 6600XT w. 8MB). I have attached relevant pics/dropbox links for BF (and others) to check on their AMD systems. All I can say is, WTF.... https://www.dropbox.com/s/l25g01e0okcrrb5/Rollin' On The River 105.ema?dl=0 (CMBS PW: od) https://www.dropbox.com/s/0t049ub1b2xbdur/Retaking of Koshtovnist 153.ema?dl=0 (CMRT PW: od)

@Battlefront.com, et. al. Thanks for the test and great feedback. The out-of-memory error seems like a "driver-killer" as I experienced this as well on a large CMRT e-mail battle with drivers after 22.5.2. Despite the flashbang being resolved in newest, if the game crashes that is a fatal flaw. Do we all need to do ANOTHER separate trouble ticket for BF and AMD??

Anybody brave enough to see if the most recent drivers 23.4.2 fixed the issue? (e.g. @Jiggathebauce @Bufo

@Bufo, @Jane's @Steve - that is fascinating-- why with MODS would the flash be eliminated on the steam version? Does this imply that with the same mods a non-Steam version of CMBN would be repaired? I can't test as I don't own this particular game. The original author claims it is the Steam version itself that solves the problem so this implies its MODS? This should be updated to AMD by Battlefront if replicated as it just makes driver resolution (IMHO) more confounding?

Thank you, Steve, good to hear. I will speak for the rest of us and be hopeful that AMD won't wait ANOTHER nine months to address these issues. The last version that worked for CM was released June '22.... (and BTW I remember that 'mouse click' issue )

Well, this seems to have pretty far-reaching implications. Steve are you suggesting that if AMD does NOT fix their "broken" OpenGL API calls as a consequence of their OpenGL "upgrades" that all AMD users of Battlefront CM games are therefore stuck on legacy drivers? Beyond the flash-bang issue, per my earlier post I received an out-of-memory error on CMBS after an email turn completed its 60 second cycle making that game "fully broken." Since it sounds like all Engine4 CM games are suffering from this (I can confirm on CMBS and CMRT-- oddly no out-of-memory on the latter), I can't see both parties ignoring this issue indefinitely-- and frankly, AMD might end of "just not caring" about a comparatively smaller user base. Its not like this is happening in Call of Duty....