Screen flickering, no metal spots and no starting locations on AMD RX480 driver 16.7.3

Discussion in 'Support!' started by Azer1652, July 30, 2016.

  1. Azer1652

    Azer1652 New Member

    Messages:
    2
    Likes Received:
    1
    As of AMD driver 16.7.3 I have no metal spots, the starting locations are not indicated and some planets are making the entire screen flicker severely when in view. I do not know what is wrong. I have attached the dxdiag file and the log.

    Any help would be greatly appreciated since the game is unplayable in its current state.

    I did not launch with --nomods because I couldn't create a game when I did. I did have all community mods disabled.

    Attached Files:

  2. pbm42

    pbm42 New Member

    Messages:
    1
    Likes Received:
    0
    Same issue here... (AMD R9 290X - 16.7.3)
  3. Bostonjunk

    Bostonjunk New Member

    Messages:
    9
    Likes Received:
    11
    Can confirm. R9 390 on 16.7.3 and having the same issue.
  4. SpaceRiceBowl

    SpaceRiceBowl New Member

    Messages:
    1
    Likes Received:
    0
    Can confirm, an AMD Drivers 16.7.3, the game is completely broken for me every time I try and play a match.
  5. Bostonjunk

    Bostonjunk New Member

    Messages:
    9
    Likes Received:
    11
    Workaround for the time being:
    • Go to https : / / mega . nz / #F!8tlAhDyQ!2AkAQukJKAYuIWEzDTGtFA (Sorry, I can't post links) and go to the OpenGL/Vulkan folder and download the DLLs for 16.7.2
    • Put them in %STEAMDIR%\SteamApps\common\Planetary Annihilation Titans\bin_x64
    • Start game from Steam as normal
    • You might need to log in again when you start it up
    stuart98, tunsel11, pbm42 and 2 others like this.
  6. cdrkf

    cdrkf Post Master General

    Messages:
    5,720
    Likes Received:
    4,793
    Aren't the 16.7.3 drivers beta at the moment? Hopefully something that will get fixed before they go live. Someone should probably submit this to AMD as a bug report and link back here so everyone with the issue can upvote... I haven't tried the beta drivers yet but can do to help confirm the issue.
  7. Azer1652

    Azer1652 New Member

    Messages:
    2
    Likes Received:
    1
    The 16.7.3 drivers went live on the 28th.
    cdrkf likes this.
  8. cdrkf

    cdrkf Post Master General

    Messages:
    5,720
    Likes Received:
    4,793
    Ah OK, hadn't realised, thanks.
  9. tripper

    tripper Active Member

    Messages:
    135
    Likes Received:
    48
    Confirming, so broken. :(
  10. cdrkf

    cdrkf Post Master General

    Messages:
    5,720
    Likes Received:
    4,793
    To confirm, the previous stable drivers - 16.3.2 work fine with PA. I'd advise everyone with older graphics cards to stick with those drivers if possible.

    I'm posting a topic on the AMD support forum, maybe get someone to look into what's happened...

    Edit: Link to topic (please add comments there if you get chance):
    https://community.amd.com/message/2740585
    Last edited: August 7, 2016
    DeathByDenim likes this.
  11. Bostonjunk

    Bostonjunk New Member

    Messages:
    9
    Likes Received:
    11
    Anyone tried with 16.8.1 or 16.8.2 ?

    EDIT: Quick test and 16.8.2 still showing same symptoms. :(
    Last edited: August 13, 2016
  12. mwreynolds

    mwreynolds Well-Known Member

    Messages:
    470
    Likes Received:
    292
    Whats up with AMD...

    Maybe if more people posted about the issue like cdrkf did, they may take more notice.
    cdrkf likes this.
  13. cdrkf

    cdrkf Post Master General

    Messages:
    5,720
    Likes Received:
    4,793
    Yeah if people could add to the forum thread I created over at AMD that would help. They get a lot of support cases so need to highlight it, otherwise the thread will simply get buried....
    Nicb1 and mwreynolds like this.
  14. mwreynolds

    mwreynolds Well-Known Member

    Messages:
    470
    Likes Received:
    292
  15. wizboyd

    wizboyd New Member

    Messages:
    1
    Likes Received:
    0
    so is there any way as to fix this problem because i tried doing this for 16.8.2 but it did not work unfortunately so would anyone be able to tell me how to fix this for problem for 16.8.2
  16. mwreynolds

    mwreynolds Well-Known Member

    Messages:
    470
    Likes Received:
    292
    You need to use the dll files for version 16.7.2
  17. stormtrooper058

    stormtrooper058 New Member

    Messages:
    2
    Likes Received:
    0
    Im missing things like metal deposits and such, is there any hard fix yet?
  18. DeathByDenim

    DeathByDenim Post Master General

    Messages:
    4,326
    Likes Received:
    2,118
    Hard fix would have to come from AMD. In the meantime you'll have to use the workaround, I'm afraid.
  19. lostmekka

    lostmekka Member

    Messages:
    69
    Likes Received:
    96
    I had the problem too, with a Radeon R9 390 and driver version 16.7.3 as well as 16.8.2.
    The funny thing was, that this behaviour was starting while the game was open: From one GW game to the next. So the driver worked correctly for at least 2 games until the bug showed up.

    Downgrading to 16.7.2 did help though :) Hope AMD fixes this soon.

    Edit: I'm not a big fan of manual dll juggling. I'm afraid this could have very bizarre side effects if the driver is replaced only partially ^^
  20. Gutsdozer

    Gutsdozer New Member

    Messages:
    1
    Likes Received:
    0
    Same problem with an R9 270x. Only started happening within the last week.

Share This Page