Question / Help R9 Fury any capture methods extremely slow

[Pimpmuckl]

Edited the whole post because I had some time to debug:

Using the 15.11.1 CCC or Crimson drivers, any capture using the Fury is incredibly slow.

Test scene 1: Black screen
Test scene 2: Capturing a video in VLC via Window Capture
Test scene 3: Capturing Dota 2 via Game Capture.

Scene 1 has sub 5% frame drops when using preview without encoding anything.
Switching to Scene 2 makes GPU usage stay at 100% constantly in MSI Afterburner, Dota 2 frame rate (not captured) tanks from ~80-100fps to around 30.
Switching to Scene 3 has the exact same happening like Scene 2.

This behaviour does not happen in OBS MP if I set the renderer to Direct3D11 (it does happen if I use openGL though) however it still lacks Replaybuffer support so I can't just switch over even though the software is incredible.

I'll try to roll back to an older driver, I already tried to go back to Windows 8.1 (which I also currently use) from using Windows 10.

 

[Boildown]

We have nothing to go on here. Post a log file from your best attempt? And despite all you said, I'm still not sure what problem it is that you're having, you haven't actually said it.

 

[Pimpmuckl]

We have nothing to go on here. Post a log file from your best attempt? And despite all you said, I'm still not sure what problem it is that you're having, you haven't actually said it.

Sorry, I forgot to include the new logs after I reformatted the post and removed the windows 10 logs.

The problem is extreme fps drops and OBS not exactly dropping frames, but the frame counter in the bottom right corner is dropping just as much as the game or even the media player playing back a video file. Basically my GPU usage is consistently on 100% as long as I capture pretty much anything, be it Window- or Game Capture.

https://gist.github.com/636d6083a500a4e41a91

I would guess the line "video thread frame - [100%] [avg time: 17.552 ms]" points to this but I don't know enough about the workflow to understand what the exact problem is.

 

[dping]

Sorry, I forgot to include the new logs after I reformatted the post and removed the windows 10 logs.

The problem is extreme fps drops and OBS not exactly dropping frames, but the frame counter in the bottom right corner is dropping just as much as the game or even the media player playing back a video file. Basically my GPU usage is consistently on 100% as long as I capture pretty much anything, be it Window- or Game Capture.

https://gist.github.com/636d6083a500a4e41a91

I would guess the line "video thread frame - [100%] [avg time: 17.552 ms]" points to this but I don't know enough about the workflow to understand what the exact problem is.

Yeah the video thread frame means that there is something lagging with the scaler. in your case it could be that your monitor is set to 1440p yet you use 1600x900. have you tried setting the base to 1440p and downscaling to 1080p? hardware scalers are better quality and usually give better quality anyway.

Anyway, make sure hardware scaling is enabled in the AMD driver. I would actually say to prefer to use ccc over crimson for the time being but that is entirely up to you.

 

[Pimpmuckl]

Yeah the video thread frame means that there is something lagging with the scaler. in your case it could be that your monitor is set to 1440p yet you use 1600x900. have you tried setting the base to 1440p and downscaling to 1080p? hardware scalers are better quality and usually give better quality anyway.

Anyway, make sure hardware scaling is enabled in the AMD driver. I would actually say to prefer to use ccc over crimson for the time being but that is entirely up to you.

Thank you so much for that, I didn't try that on the 8.1 machine. I imagine by hardware scaling you mean the "GPU Scaling" which was called "Enable GPU scaling" in the CCC?

I might have a lead that some strange scenes of the CLR browser which are expected but missing and that might have been one of the issues, but this is some strange stuff.