https://i.imgur.com/fw3YKBH.jpg
Enhanced Sync don't work in Wolfenstein ll: The New Colossus when Vsync is off, you get tearing but with FreeSync the game is very smooth as butter. Enhanced Sync I see up 2.5x the frame rate but can't stand tearing.
Enhanced Sync don't work in Wolfenstein ll: The New Colossus when Vsync is off, you get tearing but with FreeSync the game is very smooth as butter. Enhanced Sync I see up 2.5x the frame rate but can't stand tearing.
AFAIK, Enhanced Sync doesn't remove 100% of the tearing--only as much as possible while still retaining ~90% of the vsync-off frame rate.
I managed to get a full hour of Overwatch without crashing (progress over .2 which crashed as soon as the match started) will play some more in the afternoon.5486651
I managed to get a full hour of Overwatch without crashing (progress over .2 which crashed as soon as the match started) will play some more in the afternoon.
Did you try deathmatch mode, I get crash there..
Quick and rank play no crash.
Wolfenstein TNC runs a tad bit better than 17.10.2
I can run a lot at medium and some high settings and maintain 60 fps in most situations but I know my vram is now holding me back which makes me sad, full vram usage and only 60% GPU usage .. no bottleneck as I have a 4790K cpu
resolution is 1050p
I managed to get a full hour of Overwatch without crashing (progress over .2 which crashed as soon as the match started) will play some more in the afternoon.
Keff91:
Did you try deathmatch mode, I get crash there..
Quick and rank play no crash.
In before Agonist goes like "WTF I don't get any crashes my friend on Fury X doesn't crash yet all nvidia cards crash, it's all Blizzard's fault."
Yet, AMD says:
Rambo:
Known Issues
OverWatch™ may experience a random or intermittent hang on some system configurations. Disabling Radeon ReLive as a temporary workaround may resolve the issue.
That intermittent hang issue has been mentioned on and off for about 3 months now if I haven't mistaken. Disabling ReLive means you're locked out of streaming or recording gameplay with an AMD card with AMD's official solutions that has negligible performance penalty. Pretty sure OverWatch™ is meant to be played against bots only, and not competitively where some people may find it necessary to stream and end up having to reboot their system mid game.
ISP was down for a few hours and while I checked the atiapfxx.blb file yesterday I didn't post about it but there's no real differences between 17.10.2 and 17.10.3 in there, version is mostly the only thing that changed.
Driver itself has two listed fixes for Vega GPU's in two games (Wolf2, Dest2) and that's about it, known issue list is the same as 17.10.2 too.
Could still be some minor tweaks to the driver file besides that though which I can't see and there's probably no-one but AMD who knows what changes in CNext / Crimson / Radeon Settings which is always updated though if it was important it would probably be listed. 🙂
[...]intermittent hang issue has been mentioned on and off for about 3 months now [...] disabling relive means you're locked out of streaming or recording gameplay with an AMD card with AMD's official solutions that has negligible performance penalty[...]
I've opt-out from ReLive because of the BSODs, but thankfully OBS does the work (without any issues) and I'm not going back until AMD release a properly tested WHQL driver.
I've opt-out from ReLive because of the BSODs, but thankfully OBS does the work (without any issues) and I'm not going back until AMD release a properly tested WHQL driver.
I have a R9 Fury 4GB HBM. I'm having a problem with enabling FreeSync with these latest drivers. Before the 17.10.2 drivers, FreeSync was working at a 60hz refresh rate. I even did a clean uninstall and reinstall with DDU because of the recent Windows 10 upgrade. I keep my Samsung monitor set to the Standard FreeSync, it works at a 72hz refresh, but not at 60hz and below. It now states that FreeSync is not supported, but I know something broke it.
The good thing about this driver is that the game detection is now working and I like how the GPU is being used for either graphics or compute.
Has anybody else experienced this issue? I may have to revert to the working driver.
I've opt-out from ReLive because of the BSODs, but thankfully OBS does the work (without any issues) and I'm not going back until AMD release a properly tested WHQL driver.
Honestly that has to be half of your issue with Overwatch. There is a relive bug with overwatch. Relive thankfully works without issue for me. Works even on my piddly HD 7850 1GB in my rfactor rig my friends uses. You shouldnt being getting a BSOD with a RX 580 man with relive. My buddys RX 480 4GB works just fine with Relive and twitch streaming. Are you on Win 10? If so what version? All machines of mine and friends are on the Win 10 FCU.
WHQL driver means squat for stability. Its gonna work perfect for someone else but not for another. Its not just gonna magically fix your issue just because its a WHQL driver.
In before Agonist goes like "WTF I don't get any crashes my friend on Fury X doesn't crash yet all nvidia cards crash, it's all Blizzard's fault."
Yet, AMD says:
That intermittent hang issue has been mentioned on and off for about 3 months now if I haven't mistaken. Disabling ReLive means you're locked out of streaming or recording gameplay with an AMD card with AMD's official solutions that has negligible performance penalty. Pretty sure OverWatch™ is meant to be played against bots only, and not competitively where some people may find it necessary to stream and end up having to reboot their system mid game.
Yet you cant even try to talk shit correctly. Try again. You cant even get anything correct I have previously said without looking foolish.
Maybe look at my previous post that. I even stated that to a member asking about Relive.
Yes I a mouthy blunt person, do I care, no.
[youtube=BX2IENd9hy8]
I'm very sorry for speaking out so soon (I know it was to early) it's as bad as the previous driver when it comes to Overwatch (only driver installed) already revert back to 17.10.1.
I made a video (starts at 2:40 due to me crashing on every match start...) as proof for those of you who think I'm making this stuff up and going back to 17.10.1 is the only way around it.
[youtube=BX2IENd9hy8]
I'm very sorry for speaking out so soon (I know it was to early) it's as bad as the previous driver when it comes to Overwatch (only driver installed) already revert back to 17.10.1.
I made a video (starts at 2:40 due to me crashing on every match start...) as proof for those of you who think I'm making this stuff up and going back to 17.10.1 is the only way around it.
I play OW quite a lot with the same card, and I am yet to crash even once. I'm either very lucky or this OW issue depends a lot on system spec.
I managed to get a full hour of Overwatch without crashing (progress over .2 which crashed as soon as the match started) will play some more in the afternoon.5486651