Jump to content

chrisol

Members
  • Posts

    10
  • Joined

  • Last visited

Reputation Activity

  1. Like
    chrisol reacted to Jiggathebauce in AMD 22.8 series breaks game again   
    In addition to out of memory, is anyone else hitting save or next turn and the game just closing itself? No crash notification, just closes.
  2. Like
    chrisol reacted to Bufo in AMD 22.8 series breaks game again   
    I confirm, white flashes are gone with 23.4.2.
    Finally 😀
  3. Like
    chrisol reacted to LeBlaque in AMD 22.8 series breaks game again   
    Anybody brave enough to see if the most recent drivers 23.4.2 fixed the issue? (e.g. @Jiggathebauce @Bufo
  4. Like
    chrisol reacted to nox_plague in AMD 22.8 series breaks game again   
    Yes folks here is the official AMD thread would be great if they let us Beta test it to make sure it's really fixed.
     
    https://community.amd.com/t5/drivers-software/amd-driver-issues-with-opengl-in-combat-mission-games/td-p/587742
  5. Like
    chrisol reacted to Jiggathebauce in AMD 22.8 series breaks game again   
    Apparently AMD is implementing the fix! Just asked on their forum when it will hit for users, wether in a new update or something. Really looking forward to the performance improvements with no Flashes!!!! Can't wait to play the new cold war module when it hits as long as the game works well
  6. Like
    chrisol reacted to Jiggathebauce in AMD 22.8 series breaks game again   
    Response from AMD:  fix is currently available in the internal driver builds only. The fix is likely to get promoted to the public driver soon. However, at this moment, I can't provide an ETA for this fix.
    I'm thinking next driver update should have it implemented based on that. 
  7. Like
    chrisol reacted to Codreanu in AMD 22.8 series breaks game again   
    Awesome, I've been taking a break from CM since the drivers started breaking things so it'll be great to get back into it again. Big thanks to everyone who helped out by reporting the issue so we could get it fixed!
  8. Like
    chrisol reacted to Jiggathebauce in AMD 22.8 series breaks game again   
    Hmm ... I'm not thrilled that for half a year at least, AMD card owners have been unable to play CM2 titles except as flashbang to the face simulator.  Here's what I'm going to do:
    I'm going to signal boost on AMDs forum, another user has already posted there, but i think another thread specifically calling out CM and multiple driver updates screwing it up is warranted.
    Also, I have a steamdeck, bought CMCW on bf website and i believe we have access to steam key correct? If so, I will see if steam deck doesn't have this issue
    I will add that this solution is highly impractical, it's basically a console and it will be extremely weird to play CM with a gamepad setup and potentially on my television screen.
    I am not pleased at the moment with AMD.
     
     
  9. Like
    chrisol reacted to Schrullenhaft in AMD 22.8 series breaks game again   
    Battlefront is aware of this issue and are looking at it. However this issue is more likely in AMD's court. The 22.7.1 drivers brought in a bunch of OpenGL optimizations and it is one (or several) of those optimized routines for implementing OpenGL that has caused these problems.
    These optimizations have brought some welcome speed improvements to CM for Radeon users. CM loads multiple times faster than it did before. However they have also caused problems that everyone in this thread is aware of now. I don't know how hard it would be for Battlefront to reprogram some of the visual affects in CM that are affected by these optimizations. Using different calls/methods to reproduce some of the effects may be complex enough to almost not be worth the effort. At its simplest it may result in an option to turn off certain effects for compatibility purposes.
    If AMD were to address this issue there could be a couple of possibilities:
    AMD figures out that some of the optimizations need refining and are able to find a fix and maintain the speed improvements.
    or
    AMD realizes that the optimizations are incompatible with certain OpenGL calls. This results in a decision to:
    1) Consider the incompatible calls as deprecated in their OpenGL implementation - this can be a likely scenario if the calls are older and there are others that are considered suitable replacements (however harder they might be for programmers to implement). The optimizations all remain in place and potentially benefit the majority of OpenGL programs, but CM suffers.
    or
    2) Possibly reverse/sacrifice some of the optimizations in order to make CM work with their current OpenGL implementation. This would result in a driver that wasn't as fast in all respects as the current ones, but it may still be an improvement speed-wise over earlier drivers. Depending on what programs were affected by the optimizations this could take several possible paths.
               a) If several significant programs were affected and only a few changes are necessary (and thus most speed improvements remain), this could be the driver base for OpenGL going forward. Future drivers will have these fixes and CM will continue to work with newer drivers.
               or
               b) If only a few programs are affected and/or many optimizations have to be dropped or engineered in a manner that significantly reduces the performance benefit the optimizations originally provided. Then AMD could release (if it found that the effort has significant enough demand) a 'beta' driver that may be a 'dead end'. Future updates would NOT utilize this as a base for OpenGL, but instead implement the full OpenGL optimizations of the previous driver. This 'beta driver' would have some speed improvements and compatibility with the latest Radeons, but this would potentially be the last driver supporting certain OpenGL calls in a manner compatible with CM.
    I have seen in the past when AMD has reached out to Battlefront to get more info on certain bugs in their drivers. However even with the intense initial interest in fixing the problem it took 9 months to get a driver release that fixed the problem (which was more significant in its effect than the problems experienced here).
×
×
  • Create New...