RadeonPro BETA (Automating 3D Settings) #2

How are you confirming your FQS? My real time FQS testing (MadVR DX11) shows the FQS changes made my RadeonPro and direct reg edit intervention show no change to the FQS. I think the FQS can only be changed for DX9 titles. The rest are locked out (hard coded).

 

FQS for csgo? whats is better for play? crimson 15.12

 

How to get Dynamic Vsync to work? Always on works, but Dynamic does not. Tested on Far Cry 3 and Unigine Heaven

AMD Crimson drivers.

Dynamic Vsync is one thing I envy nVidia users

Edit: works now. Had to disable game overlay in UPlay settings Unigine DX11 also works, my mistake was testing in DX9 windowed mode. In fullscreen or DX11 Dynamic VSync works.

 

+1 wondering same

 

Anyone have problems with AC:Syndicate?, it starts fine and shows the fps counter but crashes after "press any key to continue".

 

Does anyone know why AC Syndicate version 1.31 is crashing with RadeonPro?

Ive killed afterburner and RTSS and it still crashes. Even with no settings enabled in RP, it still crashes.

Weird. Is there a setting somewhere im missing?

 

sometimes you have to disable some of API's to work in RP.
eg. DX9/10/OGL for AC:S

 

I've readed few pages back that this problem is caused because the pagefile is deactivated. Is this your case?

 

Nope. Page File is active but small. I have 16Gb so no need for a large one i presume.

 

by limiting the size of your page file, you are limiting the total commit charge.

once the paging memory fills up, you will slow to a crawl.

you should always let windows handle it, or set it to 1.5x physical ram at a minimum.

ALL these people that seem to think disabling their paging file speeds things up are in their own little world.

Windows memory management REQUIRES a paging file for the most part to be the most efficient.

 

I agree with that. Disabling page file on the system give more problems than benefits.

 

I couldn't make vsync work in Alan Wake with D3DOverrider... but RadionPro worked perfectly, nice program I haven't really used it before, it has some nice features.

 

some stuff is outdated, but it mostly works well.

 

Despite working on previous Crimson drivers a couple days ago, RP kinda died after upgrading to 16.4.1, as trying to start it gives me a .Net error

i.imgur.com/fftw9mo.png

pastebin.com/NQqeMbEu

And if I choose to continue, I can get it to start to an extent, but trying to access any of the settings gives me another .Net error

pastebin.com/C15JQcfc

I went back to 16.3.2 and it works, so I'm assuming it's something in 16.4.1 it doesn't like. Card is a Fury, if that matters

 

Is this still worth using with radeon settings? I reformatted recently and I noticed I quit using it since FPS cap was added to the driver period. Now AMD does things like flipque and such based on their own database of what is best per game or something.

So is this worth using still?

 

works fine for me on 16.4.1..

im using Triple buffering DFC, and onscreen FPS counter

the FPS counter on raptr is messed up, its reporting 62 fps on FO4..

 

I remember I read somewhere, probably this very thread, that RadeonPro does not at all work with Fury cards, but it seems it works for you. Anyway, it also works fine for me on 16.4.1.

I still find it as the most convenient way to force SMAA/FXAA, Triple Buffering in DX applications, and monitor refresh rate (I use a different refresh rate for desktop and games).

 

Hey cool, so RadeonPro DOES still work with Furies on 16.4.1 then?

Hmmm, I'll keep that in mind when I'm upgrading. Still not sure if I should go green or stay red.

I'll probably just wait for the next generation of hardware anyway. Where is it?!?!?

 

I decided to start using this again but it comes up with "invalid video adapter: AMD Radeon 200 series". Should I ignore it?


Oh I see, we have a new installer I didn't see listed in the thread. GG, fixed it.

 

june, for both.

Polaris will most likely be a 390/x replacement however.