• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

The AMD Driver Thread

Sh4rkie said:
I'll have to revisit this but i'm sure when i ran Dirt Rally VS + FS with no FRTC i got tearing. With FS and FRTC and no VS it cleared up.

Since then i've always run FS + FRTC and no VS on everything, can't say it felt or looked 'bad' as a result.
Click to expand...

In my case it has nothing to do with tearing or Freesyncing looking "bad". Simply that before in some games Freesync would not activate itself even though settings wise everything was in order. Since I've followed that recommendation (so not using Fressync and FRTC together) I don't have that problem anymore.

Now whether that's because of what Robert is explaining or actually the result of a driver/software bug in the Freesync implementation I can't really comment.
 
nashathedog said:
What AMD Gaming evolved's limiter?

That's what I've been using, Are they saying there own software can't play nice with freesync?

If I'm not meant to use FRTC where do I turn v-sync on? In game?
Click to expand...

It's not gaming evolved, it's part of the Crimson driver.
Freesync works fine here with both vsync and FRTC.. What vsync does do better is works with LFC Low Framerate Compensation when the frame rate drops below the freesync range.
I think this is what Robert is getting at, if you never drop below just use FRTC to keep the frame rate inside the freesync range.
This what I doing and had no issues
 
16.10.2 out now:

Radeon Software Crimson Edition 16.10.2 Highlights
Support For:
Battlefield 1™
Sid Meier's Civilization® VI
Titanfall 2™
Serious Sam™ VR Early Access
Eagle Flight VR™
New AMD CrossFire profile added for DirectX® 11:
Sid Meier's Civilization® VI

Fixed Issues
Fan speed may sometimes remain elevated on select Radeon RX 400 series graphics products even when an application has been exited.
Eyefinity group settings may not be retained after driver upgrade when using AMD CrossFire configurations.
Gears of War™ 4 may experience an application hang when using select high resolution and quality configurations in some specific game maps.
DirectX®12 content may be unable to launch on some older CPUs that do not support popcnt instruction.
Battlefield 1™ AMD CrossFire profile updates for game launch.

Known Issues
A few game titles may fail to launch, experience performance issues or crash if the third party application "Raptr" has its game overlay enabled. A workaround is to disable the overlay if this is experienced.
H.264 content playback may experience playback issues on internet browsers with hardware acceleration when also running gaming applications or content.
The Division™ may experience checkered corruption when using character model overlays or the game menu.
Some users without the Radeon WattMan feature may experience a Radeon Software popup error regarding Radeon WattMan.
FIFA 17™ may experience an application hang or black screen on launch for some select Hybrid Graphics or AMD PowerXpress mobile configurations.
H.264 content may experience blocky corruption when streaming using P2P content players on some Radeon RX 400 series graphics products.
 
Does crossfire still work in the latest drivers?
I used to get a little crossfire symbol in the top right show up when I launched a game and that doesn't happen anymore and there doesn't appear to be a setting in crimson to apply crossfire at all?
 
p5ychonaut said:
@spoony77 I don't run Crossfire any more but I believe the on/off toggle and "AMD Crossfire Logo" option were moved to the Crimson "Global Settings" under the "Gaming" tab.

This is a useful document from the GPUOpen.com website - though it still shows the enable/disable option in the old location:

http://gpuopen-librariesandsdks.github.io/doc/AMD-CrossFire-guide-for-Direct3D11-applications.pdf
Click to expand...

Thanks for that p5ychonaut found them....why are they always moving settings around!!
 
Chewie said:
Also, for those of who of you who might have problem with Freesyncs I think the explanation (from an AMD guy) below will be useful:

[–]AMD_RobertTechnical Marketing 4 points 1 month ago*

OP, I see you're using FreeSync and FRTC together. Don't. The FRTC algorithms that analyze frames to reject useless ones can interfere with the rolling frame time analysis performed by FreeSync to synchronize the display with the GPU. If you are using FreeSync, your FPS is being capped anyways because you have vsync enabled alongside it to pull the FPS back down when it exceeds the DRR range supported by the display. And if you didn't want vsync enabled to contain the framerate to the DRR range of the display, because you cared about the lowest possible input latency, then you wouldn't be using FRTC.

//edit for clarity: If an app's FPS is within the DRR range of a monitor, then the FPS vs. Hz will be synced 1:1. The vsync setting matters for what happens outside of the DRR range. If vsync is on, then the GPU will simply reject frames to keep you within the DRR range of the display if the FPS tries to go above the range. If vsync is off, then the FPS can go however high it wants and you will get input latency benefit at the expense of marginal tearing. FreeSync will resume activity if the FPS falls to the DRR range again. Below the DRR range of the display, LFC is active if the monitor supports.

In both cases, FRTC is undesirable and unnecessary in the presence of FreeSync.

https://www.reddit.com/r/Amd/comments/4z2spv/fix_freesync/?st=iuicx2mf&sh=ed9bcd66

I personally used to have issues with Freesync not working on some games when I was using it with FRTC, since following the recommendation above I no longer have any problems (R9 Fury + Asus MG279Q).
Click to expand...

Iiiiiiiiiiiiiiiiiiiiiinteresting... I will try this in Mafia 3 then. Fingers crossed!
 
Ok well disabling FRTC didn't help freesync in mafia 3. It's ok though.

16.10.2 is HORRIBLE for BF1. Crashing and locking up every 10 minutes in to the game or so. Went back to 16.10.1 and bf1 runs like a dream.

Did two re-installs of the latest driver too to see if that was the issue. Already found others reporting same thing. ughhhhhhh
 
shankly1985 said:
It's not gaming evolved, it's part of the Crimson driver.
Click to expand...
That's what I meant sorry.
shankly1985 said:
Freesync works fine here with both vsync and FRTC.. What vsync does do better is works with LFC Low Framerate Compensation when the frame rate drops below the freesync range.
I think this is what Robert is getting at, if you never drop below just use FRTC to keep the frame rate inside the freesync range.
This what I doing and had no issues
Click to expand...

Same here I've had no issue so until I do I'll continue as is, I haven't had freesync that long though so I'll see how it goes.
 
TonyTurbo78 said:
no Battlefield 1 crossfire driver but a Civ6 one? Or was there a BF1 crossfire driver in an earlier driver version?
Click to expand...

The latest (16.10.2) release notes:
http://support.amd.com/en-us/kb-art...re-Crimson-Edition-16-10-2-Release-Notes.aspx
Show Battlefield 1 Crossfire under the "Fixed issues" section, so it looks like earlier versions had Crossfire support for the game already, but the latest works for the game's release version.

Haven't got the game yet (will do when it's cheaper) so can't test it myself.
 
TonyTurbo78 said:
no Battlefield 1 crossfire driver but a Civ6 one? Or was there a BF1 crossfire driver in an earlier driver version?
Click to expand...

It does list a fixed issue
"Battlefield 1™ AMD CrossFire profile updates for game launch."

That implies the profile is already there from an earlier release. I'll try it in a bit.
 
You must log in or register to reply here.
Back
Top Bottom