Still no fix for my screen tearing issues I'm seeing in Civilization: Beyond Earth - Rising Tide while using Mantle on 2 R9 290X crossfired. The problem does not occur with Direct X11. Have been posting this issues for the last 4 beta drivers and haven't heard a word from either AMD or Firaxis. Hilarious as this is a AMD sponsored game using and AMD API.
You're going to be waiting a while as Mantle development/drivers are no longer supported by AMD. AMD has opted to support Vulkan and DX12 going forward. Mantle is supposedly being utilized internally as some sort of test platform, but that's about it.
I understand that, but it was still a flagship title and I switched into the AMD ecosystem (2 crossfire flagship cards and a free sync monitor) just for the game. It feels like a huge let down.
If the problem doesn't exist in Dx11... what's holding you from doing so? I'm pretty sure that your system can handle Civ:BE without the need of Mantle.
It really does have a change. Civ:BE supports Mantle SFR Dual Graphics. It is the only title that support this.We all know that Civ consume graphic memory a lot and this tech really help since normal dx11 crossfire do not add up two card's memory.
Mantle has been abandoned, it is becoming the Vulcan API, IIRC. Use Direct X, AMD had made no secret that they are not worrying fixing minor Mantle bugs.
Um, have you not been reading AMD's financials? They need to be tight. This is the correct type of driver release for games that are selling now. I use Beta drivers all the time on AMD and they're fine. I do buy based on performance and how the company handles software updates over the life of the card. Nvidia does a good job on this, so AMD just needs to bring parity for supporting new titles.
For those of you running multiple cards. We are in a minority and it doesn't always work 100%. You'll need to determine, which support route you need to go whether it is game developer support or graphics card manufacturer. I opt for a working game over all out performance, so if there is a setting that works - roll with it.
Because it would be a complete waste of time and money. Exactly what benefit does getting them WHQL certified bring for game specific beta drivers? The only reason for WHQL certification are major updates that bring broad fixes that need to go out to everyone.
Uh, no. Omega was just the branded name for a specific series of drivers, nothing to do with certifications status. Catalyst 14.12 Omega, for example, was WHQL certified.
These drivers actually have regressed. I updated the previous beta because the driver that Windows 10 installs on top of whatever driver you had carefully chosen runs into parts of Visual Studio 2015 not redrawing. I just got used to whenever there was an Insider update that I'd need to go get the latest beta to avoid the issue. I just installed this new beta this morning and the icons in my button bar have vanished and when I publish to the web server half the screen doesn't redraw. Guess I'll track down the previous beta and hope to hell this beta isn't on a fast track.
That's a Visual Studio thing. I had a similar same problem on my laptop with its intel graphics (also with VS15) and Windows 10 Insider Preview something (may have been RTM at that point, not sure). Never fixed it, just removed VS15 (only needed it to create a fix for a project while on the go)... I don't like typing on laptops anyway.
We’ve updated our terms. By continuing to use the site and/or by logging into your account, you agree to the Site’s updated Terms of Use and Privacy Policy.
Facebook
Twitter
RSS
19 Comments
Back to Article
Galatian - Tuesday, November 17, 2015 - link
Still no fix for my screen tearing issues I'm seeing in Civilization: Beyond Earth - Rising Tide while using Mantle on 2 R9 290X crossfired. The problem does not occur with Direct X11. Have been posting this issues for the last 4 beta drivers and haven't heard a word from either AMD or Firaxis. Hilarious as this is a AMD sponsored game using and AMD API.mrdude - Tuesday, November 17, 2015 - link
You're going to be waiting a while as Mantle development/drivers are no longer supported by AMD. AMD has opted to support Vulkan and DX12 going forward. Mantle is supposedly being utilized internally as some sort of test platform, but that's about it.Galatian - Tuesday, November 17, 2015 - link
I understand that, but it was still a flagship title and I switched into the AMD ecosystem (2 crossfire flagship cards and a free sync monitor) just for the game. It feels like a huge let down.milli - Tuesday, November 17, 2015 - link
Just use DX11. Mantle is worth nothing in this game.The 290X has excellent performance under DX11 in this game.
www.anandtech.com/show/8640/benchmarked-civilization-beyond-earth/2
heffeque - Tuesday, November 17, 2015 - link
If the problem doesn't exist in Dx11... what's holding you from doing so? I'm pretty sure that your system can handle Civ:BE without the need of Mantle.mikeztm - Tuesday, November 17, 2015 - link
It really does have a change.Civ:BE supports Mantle SFR Dual Graphics. It is the only title that support this.We all know that Civ consume graphic memory a lot and this tech really help since normal dx11 crossfire do not add up two card's memory.
looncraz - Tuesday, November 17, 2015 - link
Mantle has been abandoned, it is becoming the Vulcan API, IIRC. Use Direct X, AMD had made no secret that they are not worrying fixing minor Mantle bugs.tamalero - Tuesday, November 24, 2015 - link
isnt Direct X12 based on mantle anyway?bizude - Tuesday, November 17, 2015 - link
Enable V-Sync. Problem solved.Morawka - Tuesday, November 17, 2015 - link
Man why won't AMD get this drivers certified? are they that freaking tight?looncraz - Tuesday, November 17, 2015 - link
Why would they certify a beta driver? It's not like it's a ten minute process... or free.Morawka - Thursday, November 19, 2015 - link
the whole reason it's called "beta" is because it's not certified. you dont know that?All beta drives are "not whql certified.
if they got it certified, they could remove the "beta" tag.
eanazag - Tuesday, November 17, 2015 - link
Um, have you not been reading AMD's financials? They need to be tight. This is the correct type of driver release for games that are selling now. I use Beta drivers all the time on AMD and they're fine. I do buy based on performance and how the company handles software updates over the life of the card. Nvidia does a good job on this, so AMD just needs to bring parity for supporting new titles.For those of you running multiple cards. We are in a minority and it doesn't always work 100%. You'll need to determine, which support route you need to go whether it is game developer support or graphics card manufacturer. I opt for a working game over all out performance, so if there is a setting that works - roll with it.
freeskier93 - Tuesday, November 17, 2015 - link
Because it would be a complete waste of time and money. Exactly what benefit does getting them WHQL certified bring for game specific beta drivers? The only reason for WHQL certification are major updates that bring broad fixes that need to go out to everyone.D. Lister - Thursday, November 19, 2015 - link
AMD often doesn't splurge for WHQL certification. Even when they finalize a driver they designate it as "Omega".freeskier93 - Thursday, November 19, 2015 - link
Uh, no. Omega was just the branded name for a specific series of drivers, nothing to do with certifications status. Catalyst 14.12 Omega, for example, was WHQL certified.NXTwoThou - Tuesday, November 17, 2015 - link
These drivers actually have regressed. I updated the previous beta because the driver that Windows 10 installs on top of whatever driver you had carefully chosen runs into parts of Visual Studio 2015 not redrawing. I just got used to whenever there was an Insider update that I'd need to go get the latest beta to avoid the issue. I just installed this new beta this morning and the icons in my button bar have vanished and when I publish to the web server half the screen doesn't redraw. Guess I'll track down the previous beta and hope to hell this beta isn't on a fast track.looncraz - Tuesday, November 17, 2015 - link
That's a Visual Studio thing. I had a similar same problem on my laptop with its intel graphics (also with VS15) and Windows 10 Insider Preview something (may have been RTM at that point, not sure). Never fixed it, just removed VS15 (only needed it to create a fix for a project while on the go)... I don't like typing on laptops anyway.AS118 - Tuesday, November 17, 2015 - link
Sounds good, downloading the drivers now. Hopefully I'll be able to bump up a setting or two in Fallout 4.