6 Replies Latest reply on Nov 22, 2017 11:07 AM by amdmatt

    Guild Wars 2: Vega56 underperforming?


      Any thoughts of guidance on this would be helpful.


      On my old i5-2500k/GTX970 system my frames were consistently high and fluid, often running above 60 in the world on near max settings at 1440p/144hz. I was expecting my new AMD Ryzen 5 1600X/Vega56 system to perform much better than it is, and it's performing strangely.


      I did move up to a 4k/60 monitor, so I know that is more taxing. But, I'm hitting say 17-20 fps in Verdant Brink, and no matter what I do the frames don't really change. I can supersample, I can try to run the game at 1440p or 1080p but my frames remain the same. That doesn't seem right, yeah? Anyone experiencing anything similar? Silverwastes are also bad. Divinity's reach is maybe 20-30.


      My R5 is OCed to 4.0ghz locked, and my Vega56 is also overclocked (2.5% shader freq, +50% power limit, 975 mem freq, 1050/1075mv) , though running at stock clocks made no difference. When I play GPU activity is at 99% according to Wattman.


      I'm in a custom water loop, so all temps are good (CPU not over 70c, GPU not over 60c).


      The card runs as expected in single player DX9 games, but GW2 just doesn't seem to be getting the performance I'd expect. And I'm speaking about just regular world traversal, not even big events with lots of people which will always drop frames.


      Current in game settings have reflections off, shadows high, and player number/quality set to low.


      Anyone experiencing something similar, or can try and compare? This just doesn't seem to be working right to me. My frames should change at least if I change resolution, right?

        • Re: Guild Wars 2: Vega56 underperforming?

          Guild Wars 2 is based off of the 12 year old Guild Wars 1 engine. It is horridly optimized, and there is a known performance penalty with AMD product which they will not address, and their forums are full of threads about the "AMD performance penalty". It is not an AMD problem, it is an ANet problem.

          1 of 1 people found this helpful
          • Re: Guild Wars 2: Vega56 underperforming?

            Thread re-opened at the request of the OP.

            • Re: Guild Wars 2: Vega56 underperforming?

              Can we revisit this issue? I really need some people to test this themselves. This goes beyond any kind of "GW2 is old and doesn't favor AMD" situation.


              Whether I plug in a 4k monitor or a 1080p one, there is no change to my frames. At best +/- 5 fps. This isn't right.


              My RX 570 behaves as expected, doing excellently at 1080p, and struggling at 4k, while my Vega struggles regardless no matter the changes I make.


              I've brought this to the attention of Arena.net and I hope someone at AMD could please run some tests on this to see if the issue is a real bug somewhere, or if it's just me or my card.


              Heat isn't an issue, as I'm under water, and the card runs as expected in other games and benches.


              My RX 570 should not beat my Vega 56 at 1080p.


              Any help is most appreciated. Thanks!

                • Re: Guild Wars 2: Vega56 underperforming?

                  Welp, as with most things, the problem was my fault. The card was, in fact, in the wrong PCIE slot. It's a little concerning that GPU-Z didn't detect it as running at PCIE 2.0x4, but that is what it was running at. Here's how I found out.


                  In Radeon settings I noticed in the System > Hardware tab that the Current Bus Settings was at PCIE 2.0x16. That was odd, disagreed with GPU-Z, but was in line with some of the suggestions from other users that my card may be running at lower PCIE speeds.


                  I triple checked my ASRock AB350M Pro4 mobo map and saw where I got confused.


                  It lists the PCIE slots as PCIE1, PCIE2, PCIE3, not according to actual speed, but in order of top to bottom from the CPU. The speeds are actually PCIE 1.0, PCIE 3.0x16, PCIE 2.0x4. So the slot labeled PCIE2 is the PCIE 3.0 slot, and the slot labeled PCIE3 is the PCIE 2.0 slot. Awesome.


                  Well, I feel stupid, but at least it's fixed now. Thanks to everyone for their helpful suggestions which helped me eventually narrow it all down and fix the issue. I post this for anyone else who may be experiencing something similar, or may be also confused by this mobo labeling.

                  1 of 1 people found this helpful