RadeonPro BETA (Automating 3D Settings)

cnckane · Nov 13, 2012

After a few launch doesn't shows the FPS and don't apply the VSYNC settings.
I trtied with Mass Effect 3 first time worked perfectly but now I can do anything don't want to show FPS.

The Mac · Nov 13, 2012

Valken said: ↑

I just installed the latest RP build and SweetFX configuration screen is blank for me? There is nothing to set? I don't have injectors in those game profiles.

I am using 12.4 with 12.10 caps1
Click to expand...

you need to set the sweetfx directory in settings.

Valken · Nov 13, 2012

The Mac said: ↑

you need to set the sweetfx directory in settings.
Click to expand...

Thank you!

Edit - I think some of the settings are inverted.

EG:

If I use splitscreen shader, with the injector, the RIGHT half would show SweetFX settings.

If I enable splitscreen with RP, the LEFT half would show SweetFX settings.

Good news - SMAA is working better under RP than with the injector since RP applies SMAA as the LAST shader effect. The injector would have loaded SMAA, then AA would break if lumasharpen or other effects were also used.

I need to test with enbseries!!

|ALE| · Nov 13, 2012

Japamd i tried video recording in real time.

bf3, very gpu and cpu intensive works very smooth, no impact in framerate or smoothness of image.

fifa 13, where my gpu works less than 45%, when video recording is active, my framerate goes down to about 45fps and gives me some stuttering of image.

do you know if this problem is caused by the engine of the game or may be it could be fixed trough radeonpro?

the only difference between fifa and bf3, the first is played with vsync and tb on, 60fps, the second is played with dynamic framerate limiter to 57fps. I tried to switch the video recording speed from 50 to 60 fps, but no results... it's "strange" that the video recorded from fifa shows the smoothness of 60fps when played with media player classic...

edit:

resolved disabling fifa 13 vsync and triplebuffer, now i'm testing

edit 2:

without vsync and triple buffer in fifa 13 video recording doesn't affect the framerate, but there is tearing (in bf3 no). Tried with dynamic framerate limiter to 57/58/9 fps, with framerate locker at monitor refresh rate (60hz), with the framerate limiter built in game, trying to set flip queue to 0 or 1... but withous results, tearing a gogo.

Derko1 · Nov 13, 2012

Tried the new version and it installed and runs. But it still does not detect my cards. This is what I get still...
Code:
Graphics Card:	
[Unknown]:	
Video Adapter:	
Bios Version:	
Chip Identifier:	
DAC Type:	
Memory Size:	
Registry Location:	System\CurrentControlSet\Control\Video\{40EC01EF-ADEA-4F73-8A9B-B22FC9060749}\0000
Driver Caps:	010000001000000000000
Main Device:	\\.\DISPLAY1
Total GPU count:	2
Installed Drivers:	aticfx64,aticfx64,aticfx64,aticfx32,aticfx32,aticfx32,atiumd64,atidxx64,atidxx64,atiumdag,atidxx32,atidxx32,atiumdva,atiumd6a,atitmm64
PNP Device ID:	PCI\VEN_1002&DEV_6798&SUBSYS_0B001002&REV_00\4&1CDA0A78&0&0008
I still can not apply AA mode and it shows up as adaptive(quality) and supersampling when only a single card is enabled. :wanker:

FRN2003ita · Nov 13, 2012

it is normal that with this latest version of RP not working for me override? that is, it works but I can not raise the frequencies, just change the fan speed. was perfect with the other versions ......

japamd · Nov 14, 2012

GregP said: ↑

Thanks for these suggestions -- although they themselves didn't fix my problem, going through that process fixed it. The only change in my DCS profile was turning the OSD on, showing temp, utilization, and fan percentage. For some reason, having all of these selected right from the beginning was crashing DCS. When I turned them all off, and then turned them back on one at a time, and ran DCS between each addition of an OSD element -- RP worked fine. I've now got it working in DCS. AND SweetFX is working with SoftTH -- incredible!!!!

One last problem remains, though: only 1 of my 2 GPUs is showing in the OSD. In the previous preview version, in the OSD settings it listed 3 GPUs, which wasn't correct as I only have 2. Now it's only showing 1. I think this is probably related my system still not having the AMD ADL thing working correctly. I know japamd said he added a new backup method of detecting the GPUs, so I imagine it is a limitation of this backup method that it can only see 1 GPU?
Click to expand...

Cool, I'm glad you have it sorted out.

CFX detection code is a bit broken, works for me and a few people but not for everybody. I'll make some tool to help me diagnose what is going on.

AntiAlias said: ↑

Does `Games for Windows – LIVE` corrupt the movie-record feature?
Recording fallout3 results in a blackscreen-movie. Record skyrim (without LIVE) for instance is working correct.
Click to expand...

Should not but I just tried Fallout NV (which uses the same graphics engine) and the movie was all black, got only audio recorded. I'll have a look into that issue now.

Mikedogg said: ↑

Any changes made to SweetFx has the ability to change in-game settings in real-time.

Will the next update to RP include this function?
Click to expand...

Maybe... stay tuned

cnckane said: ↑

After a few launch doesn't shows the FPS and don't apply the VSYNC settings.
I trtied with Mass Effect 3 first time worked perfectly but now I can do anything don't want to show FPS.
Click to expand...

That happens when you have some other hooking program like Xbox360 CE which uses a custom xinput_3.dll. That DLL breaks RP at random.

Valken said: ↑

Thank you!

Edit - I think some of the settings are inverted.

EG:

If I use splitscreen shader, with the injector, the RIGHT half would show SweetFX settings.

If I enable splitscreen with RP, the LEFT half would show SweetFX settings.

Good news - SMAA is working better under RP than with the injector since RP applies SMAA as the LAST shader effect. The injector would have loaded SMAA, then AA would break if lumasharpen or other effects were also used.

I need to test with enbseries!!
Click to expand...

Other effects are ok?

About SMAA, RadeonPro applies post processing in the following order:

1- FXAA
2- SMAA
3- SweetFX

|ALE| said: ↑

Japamd i tried video recording in real time.

bf3, very gpu and cpu intensive works very smooth, no impact in framerate or smoothness of image.

fifa 13, where my gpu works less than 45%, when video recording is active, my framerate goes down to about 45fps and gives me some stuttering of image.

do you know if this problem is caused by the engine of the game or may be it could be fixed trough radeonpro?

the only difference between fifa and bf3, the first is played with vsync and tb on, 60fps, the second is played with dynamic framerate limiter to 57fps. I tried to switch the video recording speed from 50 to 60 fps, but no results... it's "strange" that the video recorded from fifa shows the smoothness of 60fps when played with media player classic...

edit:

resolved disabling fifa 13 vsync and triplebuffer, now i'm testing

edit 2:

without vsync and triple buffer in fifa 13 video recording doesn't affect the framerate, but there is tearing (in bf3 no). Tried with dynamic framerate limiter to 57/58/9 fps, with framerate locker at monitor refresh rate (60hz), with the framerate limiter built in game, trying to set flip queue to 0 or 1... but withous results, tearing a gogo.
Click to expand...

Cool, thanks for the heads up. I guess we can live with a little tearing while recording a movie.

DX9 is more "slow" than DXGI (DX10 and above) at frame capture time, so DX9 games will have a bigger performance hit than DXGI counterparts. For instance, I can record Crysis Warhead at about 45~60 FPS in DX10, but in DX9 I get only about 30~40 FPS.

FRN2003ita said: ↑

it is normal that with this latest version of RP not working for me override? that is, it works but I can not raise the frequencies, just change the fan speed. was perfect with the other versions ......
Click to expand...

Should be working with installer published today, have you tried it?

Mikedogg · Nov 14, 2012

japamd said: ↑

Maybe... stay tuned
Click to expand...

Aw sweet! For the sake of simplicity and accuracy, are you considering changing SweetFx values into a slider design? Or does it work better the way it is?:infinity:

Derko1 · Nov 14, 2012

So I'm debating going back to Windows 7 to see if the issues are resolved. Japamd do you think the CF issues are fixable? Are they related to the new drivers or even Windows 8?

zooyork19 · Nov 14, 2012

Hello, thanks for the newest update, it works great except for one thing.

After I installed, all 64bit programs refused to run, in the error the file AppProfiles64.dll kept coming up. After closing all the applications that were using the file I managed to delete it out of the RP directory and everything works now.

Zyrusticae · Nov 14, 2012

japamd said: ↑

I know, when I decided to support SweetFX in RadeonPro I was just thinking of an easy way to use current implementation, so you don't need to change your code at all. I made a small effect file that wraps API differences so SweetFX's effects can be compiled transparently and without user intervention.

ENB does SSAO but in a very limited set of games, AFAIK. NVIDIA SSAO doesn't work for all games as well.

You don't need to change your focus, put it simple nothing changes besides the fact RadeonPro users will have a bit more advantage over other users (they'll be able to use SweetFX on 64-bit games and have more control over settings without having to deal with text files)
Click to expand...

I should note that this isn't the only reason to use it. It's also great for getting around games with overzealous anti-cheat detection tools (and also the only reason I'm posting in this thread, heh). If it's at all possible, it'd be great to see an equivalent for Nvidia users. The whole thing with Gameguard's been driving me mad, quite frankly...

japamd · Nov 14, 2012

Mikedogg said: ↑

Aw sweet! For the sake of simplicity and accuracy, are you considering changing SweetFx values into a slider design? Or does it work better the way it is?:infinity:
Click to expand...

My working build show each field description and a numeric up/down control is being implemented, I just need to get around some grid view limitations.

Derko1 said: ↑

So I'm debating going back to Windows 7 to see if the issues are resolved. Japamd do you think the CF issues are fixable? Are they related to the new drivers or even Windows 8?
Click to expand...

I think you should wait just a bit 'till I can figure out why CFX detection isn't working in some cases.

zooyork19 said: ↑

Hello, thanks for the newest update, it works great except for one thing.

After I installed, all 64bit programs refused to run, in the error the file AppProfiles64.dll kept coming up. After closing all the applications that were using the file I managed to delete it out of the RP directory and everything works now.
Click to expand...

Thanks, but which error message? Can you, please, be more specific? Deleting AppProfiles64.dll will break 64-bit features of RadeonPro, you could just disable 64-bit if you don't need it.

Zyrusticae said: ↑

I should note that this isn't the only reason to use it. It's also great for getting around games with overzealous anti-cheat detection tools (and also the only reason I'm posting in this thread, heh). If it's at all possible, it'd be great to see an equivalent for Nvidia users. The whole thing with Gameguard's been driving me mad, quite frankly...
Click to expand...

Hmm, so the Gameguard thing doesn't block RadeonPro but blocks other injectors?

Zyrusticae · Nov 14, 2012

japamd said: ↑

Hmm, so the Gameguard thing doesn't block RadeonPro but blocks other injectors?
Click to expand...

Correct. That's because Gameguard only checks for injection in the game executable, which RP does not touch. And there are some games that just outright block all DLL injection (Aion comes to mind here), even without cheat detection tools.

Plus it guarantees peace of mind when playing other games that allow DLL injection but run cheat detection tools like Punkbuster (BF3, for example). I think you've got a really good thing going here.

japamd · Nov 14, 2012

Installer updated with cosmetic improvements to SweetFX tab

[IMG]

There's also some code to help me out on CFX detection issue. For people using CFX, please click at AMD Radeon logo at RadeonPro's window, then click at Dump video entries button to generate a list of video cards information, right click the list, choose Copy all and post the text here.

[IMG]

It will look like this:

Code:

Main display:
AMD Radeon HD 7900 Series
\\.\DISPLAY1
System\CurrentControlSet\Control\Video\{72FBECAC-4F4C-4DD1-A0DC-38FA1D97E8E8}\0000
================
AdapterIndex=0
AdapterName=AMD Radeon HD 7900 Series
BusNumber=2
DisplayName=\\.\DISPLAY1
DriverNumber=0
DriverPath=\Registry\Machine\System\CurrentControlSet\Control\Video\{72FBECAC-4F4C-4DD1-A0DC-38FA1D97E8E8}\0000
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0003
Exist=1
FunctionNumber=0
OSDisplayIndex=0
PNPString=PCI\VEN_1002&DEV_6798&SUBSYS_30001002&REV_00\4&1AA6ED88&0&0009
Present=1
UDID=PCI_VEN_1002&DEV_6798&SUBSYS_30001002&REV_00_4&1AA6ED88&0&0009A
Vendor ID: 1002
==================
AdapterIndex=1
AdapterName=AMD Radeon HD 7900 Series
BusNumber=2
DisplayName=\\.\DISPLAY2
DriverNumber=0
DriverPath=\Registry\Machine\System\CurrentControlSet\Control\Video\{72FBECAC-4F4C-4DD1-A0DC-38FA1D97E8E8}\0001
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0003
Exist=1
FunctionNumber=0
OSDisplayIndex=1
PNPString=PCI\VEN_1002&DEV_6798&SUBSYS_30001002&REV_00\4&1AA6ED88&0&0009&02
Present=1
UDID=PCI_VEN_1002&DEV_6798&SUBSYS_30001002&REV_00_4&1AA6ED88&0&0009&02A
Vendor ID: 1002
==================
AdapterIndex=2
AdapterName=AMD Radeon HD 7900 Series
BusNumber=2
DisplayName=\\.\DISPLAY3
DriverNumber=0
DriverPath=\Registry\Machine\System\CurrentControlSet\Control\Video\{72FBECAC-4F4C-4DD1-A0DC-38FA1D97E8E8}\0002
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0003
Exist=1
FunctionNumber=0
OSDisplayIndex=2
PNPString=PCI\VEN_1002&DEV_6798&SUBSYS_30001002&REV_00\4&1AA6ED88&0&0009&03
Present=1
UDID=PCI_VEN_1002&DEV_6798&SUBSYS_30001002&REV_00_4&1AA6ED88&0&0009&03A
Vendor ID: 1002
==================
AdapterIndex=3
AdapterName=AMD Radeon HD 7900 Series
BusNumber=2
DisplayName=\\.\DISPLAY4
DriverNumber=0
DriverPath=\Registry\Machine\System\CurrentControlSet\Control\Video\{72FBECAC-4F4C-4DD1-A0DC-38FA1D97E8E8}\0003
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0003
Exist=1
FunctionNumber=0
OSDisplayIndex=3
PNPString=PCI\VEN_1002&DEV_6798&SUBSYS_30001002&REV_00\4&1AA6ED88&0&0009&04
Present=1
UDID=PCI_VEN_1002&DEV_6798&SUBSYS_30001002&REV_00_4&1AA6ED88&0&0009&04A
Vendor ID: 1002
==================
AdapterIndex=4
AdapterName=AMD Radeon HD 7900 Series
BusNumber=2
DisplayName=\\.\DISPLAY5
DriverNumber=0
DriverPath=\Registry\Machine\System\CurrentControlSet\Control\Video\{72FBECAC-4F4C-4DD1-A0DC-38FA1D97E8E8}\0004
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0003
Exist=1
FunctionNumber=0
OSDisplayIndex=4
PNPString=PCI\VEN_1002&DEV_6798&SUBSYS_30001002&REV_00\4&1AA6ED88&0&0009&05
Present=1
UDID=PCI_VEN_1002&DEV_6798&SUBSYS_30001002&REV_00_4&1AA6ED88&0&0009&05A
Vendor ID: 1002
==================
AdapterIndex=5
AdapterName=AMD Radeon HD 7900 Series
BusNumber=2
DisplayName=\\.\DISPLAY6
DriverNumber=0
DriverPath=\Registry\Machine\System\CurrentControlSet\Control\Video\{72FBECAC-4F4C-4DD1-A0DC-38FA1D97E8E8}\0005
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0003
Exist=1
FunctionNumber=0
OSDisplayIndex=5
PNPString=PCI\VEN_1002&DEV_6798&SUBSYS_30001002&REV_00\4&1AA6ED88&0&0009&06
Present=1
UDID=PCI_VEN_1002&DEV_6798&SUBSYS_30001002&REV_00_4&1AA6ED88&0&0009&06A
Vendor ID: 1002
==================
AdapterIndex=6
AdapterName=AMD Radeon HD 7900 Series
BusNumber=1
DisplayName=
DriverNumber=0
DriverPath={230D7F4E-F61B-4654-BF1B-A3C4293C03F4}
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0004
Exist=1
FunctionNumber=0
OSDisplayIndex=0
PNPString=PCI\VEN_1002&DEV_679A&SUBSYS_32201682&REV_00\4&2D68EC9A&0&0008
Present=0
UDID=PCI_VEN_1002&DEV_679A&SUBSYS_32201682&REV_00_4&2D68EC9A&0&0008A
Vendor ID: 1002
==================
AdapterIndex=7
AdapterName=AMD Radeon HD 7900 Series
BusNumber=1
DisplayName=
DriverNumber=0
DriverPath={230D7F4E-F61B-4654-BF1B-A3C4293C03F4}
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0004
Exist=1
FunctionNumber=0
OSDisplayIndex=0
PNPString=PCI\VEN_1002&DEV_679A&SUBSYS_32201682&REV_00\4&2D68EC9A&0&0008&02
Present=0
UDID=PCI_VEN_1002&DEV_679A&SUBSYS_32201682&REV_00_4&2D68EC9A&0&0008&02A
Vendor ID: 1002
==================
AdapterIndex=8
AdapterName=AMD Radeon HD 7900 Series
BusNumber=1
DisplayName=
DriverNumber=0
DriverPath={230D7F4E-F61B-4654-BF1B-A3C4293C03F4}
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0004
Exist=1
FunctionNumber=0
OSDisplayIndex=0
PNPString=PCI\VEN_1002&DEV_679A&SUBSYS_32201682&REV_00\4&2D68EC9A&0&0008&03
Present=0
UDID=PCI_VEN_1002&DEV_679A&SUBSYS_32201682&REV_00_4&2D68EC9A&0&0008&03A
Vendor ID: 1002
==================
AdapterIndex=9
AdapterName=AMD Radeon HD 7900 Series
BusNumber=1
DisplayName=
DriverNumber=0
DriverPath={230D7F4E-F61B-4654-BF1B-A3C4293C03F4}
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0004
Exist=1
FunctionNumber=0
OSDisplayIndex=0
PNPString=PCI\VEN_1002&DEV_679A&SUBSYS_32201682&REV_00\4&2D68EC9A&0&0008&04
Present=0
UDID=PCI_VEN_1002&DEV_679A&SUBSYS_32201682&REV_00_4&2D68EC9A&0&0008&04A
Vendor ID: 1002
==================
AdapterIndex=10
AdapterName=AMD Radeon HD 7900 Series
BusNumber=1
DisplayName=
DriverNumber=0
DriverPath={230D7F4E-F61B-4654-BF1B-A3C4293C03F4}
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0004
Exist=1
FunctionNumber=0
OSDisplayIndex=0
PNPString=PCI\VEN_1002&DEV_679A&SUBSYS_32201682&REV_00\4&2D68EC9A&0&0008&05
Present=0
UDID=PCI_VEN_1002&DEV_679A&SUBSYS_32201682&REV_00_4&2D68EC9A&0&0008&05A
Vendor ID: 1002
==================
AdapterIndex=11
AdapterName=AMD Radeon HD 7900 Series
BusNumber=1
DisplayName=
DriverNumber=0
DriverPath={230D7F4E-F61B-4654-BF1B-A3C4293C03F4}
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0004
Exist=1
FunctionNumber=0
OSDisplayIndex=0
PNPString=PCI\VEN_1002&DEV_679A&SUBSYS_32201682&REV_00\4&2D68EC9A&0&0008&06
Present=0
UDID=PCI_VEN_1002&DEV_679A&SUBSYS_32201682&REV_00_4&2D68EC9A&0&0008&06A
Vendor ID: 1002
==================
AdapterIndex=12
AdapterName=Intel(R) HD Graphics Family
BusNumber=0
DisplayName=\\.\DISPLAY7
DriverNumber=2
DriverPath=\Registry\Machine\System\CurrentControlSet\Control\Video\{EEBE370F-32C5-4FA0-91F1-B65C4D133F02}\0000
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0001
Exist=1
FunctionNumber=0
OSDisplayIndex=6
PNPString=PCI\VEN_8086&DEV_0122&SUBSYS_D0001458&REV_09\3&13C0B0C5&0&10
Present=1
UDID=PCI_VEN_8086&DEV_0122&SUBSYS_D0001458&REV_09_3&13C0B0C5&0&10A
Vendor ID: 8086
==================
AdapterIndex=13
AdapterName=Intel(R) HD Graphics Family
BusNumber=0
DisplayName=\\.\DISPLAY8
DriverNumber=2
DriverPath=\Registry\Machine\System\CurrentControlSet\Control\Video\{EEBE370F-32C5-4FA0-91F1-B65C4D133F02}\0001
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0001
Exist=1
FunctionNumber=0
OSDisplayIndex=7
PNPString=PCI\VEN_8086&DEV_0122&SUBSYS_D0001458&REV_09\3&13C0B0C5&0&10&02
Present=1
UDID=PCI_VEN_8086&DEV_0122&SUBSYS_D0001458&REV_09_3&13C0B0C5&0&10&02A
Vendor ID: 8086
==================
Adapter 0 status=1
ADL_Adapter_ID_Get (0)=19AD300
Add iAdaptLink[6]=6
ADL_Adapter_ID_Get (0)
================
Adapter 1 status=0
ADL_Adapter_ID_Get (1)=19AD300
Add iAdaptLink[0]=0
ADL_Adapter_ID_Get (1)
Add iAdaptLink[6]=6
ADL_Adapter_ID_Get (1)
================
Adapter 2 status=0
ADL_Adapter_ID_Get (2)=19AD300
Add iAdaptLink[0]=0
ADL_Adapter_ID_Get (2)
Add iAdaptLink[6]=6
ADL_Adapter_ID_Get (2)
================
Adapter 3 status=0
ADL_Adapter_ID_Get (3)=19AD300
Add iAdaptLink[0]=0
ADL_Adapter_ID_Get (3)
Add iAdaptLink[6]=6
ADL_Adapter_ID_Get (3)
================
Adapter 4 status=0
ADL_Adapter_ID_Get (4)=19AD300
Add iAdaptLink[0]=0
ADL_Adapter_ID_Get (4)
Add iAdaptLink[6]=6
ADL_Adapter_ID_Get (4)
================
Adapter 5 status=0
ADL_Adapter_ID_Get (5)=19AD300
Add iAdaptLink[0]=0
ADL_Adapter_ID_Get (5)
Add iAdaptLink[6]=6
ADL_Adapter_ID_Get (5)
================
Adapter 6 status=0
ADL_Adapter_ID_Get (6)=1E25040
Add iAdaptLink[0]=0
ADL_Adapter_ID_Get (6)
================
Adapter 7 status=0
ADL_Adapter_ID_Get (7)=1E25040
Add iAdaptLink[0]=0
ADL_Adapter_ID_Get (7)
Add iAdaptLink[6]=6
ADL_Adapter_ID_Get (7)
================
Adapter 8 status=0
ADL_Adapter_ID_Get (8)=1E25040
Add iAdaptLink[0]=0
ADL_Adapter_ID_Get (8)
Add iAdaptLink[6]=6
ADL_Adapter_ID_Get (8)
================
Adapter 9 status=0
ADL_Adapter_ID_Get (9)=1E25040
Add iAdaptLink[0]=0
ADL_Adapter_ID_Get (9)
Add iAdaptLink[6]=6
ADL_Adapter_ID_Get (9)
================
Adapter 10 status=0
ADL_Adapter_ID_Get (10)=1E25040
Add iAdaptLink[0]=0
ADL_Adapter_ID_Get (10)
Add iAdaptLink[6]=6
ADL_Adapter_ID_Get (10)
================
Adapter 11 status=0
ADL_Adapter_ID_Get (11)=1E25040
Add iAdaptLink[0]=0
ADL_Adapter_ID_Get (11)
Add iAdaptLink[6]=6
ADL_Adapter_ID_Get (11)
================

But RP actually injects itself into game code and, AFAIK, Punkbuster doesn't like it.

Valken · Nov 14, 2012

Other effects seems to be working but I will do an injector vs RP comparison soon. The most noticeable was the split shader.

I think the way you have programmed RP, the first shaders in will be prioritized whereas the injector would prioritize the other shaders.

SMAA breaking was most noticeable with LumaSharpen enabled concurrently via injection. I will test it with RP vs injector method.

Here is what my setup says - using modded 12.4 drivers with 12.10 cap1

Code:

Main display:
7900 MOD - AMD Radeon HD 6900 Series
\\.\DISPLAY1
System\CurrentControlSet\Control\Video\{E28D080D-DB37-4BEB-9E3D-F3BE0A995BAF}\0000
================
AdapterIndex=0
AdapterName=7900 MOD - AMD Radeon HD 6900 Series
BusNumber=1
DisplayName=\\.\DISPLAY1
DriverNumber=0
DriverPath=\Registry\Machine\System\CurrentControlSet\Control\Video\{E28D080D-DB37-4BEB-9E3D-F3BE0A995BAF}\0000
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0003
Exist=1
FunctionNumber=0
OSDisplayIndex=0
PNPString=PCI\VEN_1002&DEV_6719&SUBSYS_0B001002&REV_00\4&113C73B2&0&0018
Present=1
UDID=PCI_VEN_1002&DEV_6719&SUBSYS_0B001002&REV_00_4&113C73B2&0&0018A
Vendor ID: 1002
==================
AdapterIndex=1
AdapterName=7900 MOD - AMD Radeon HD 6900 Series
BusNumber=1
DisplayName=\\.\DISPLAY2
DriverNumber=0
DriverPath=\Registry\Machine\System\CurrentControlSet\Control\Video\{E28D080D-DB37-4BEB-9E3D-F3BE0A995BAF}\0001
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0003
Exist=1
FunctionNumber=0
OSDisplayIndex=1
PNPString=PCI\VEN_1002&DEV_6719&SUBSYS_0B001002&REV_00\4&113C73B2&0&0018&02
Present=1
UDID=PCI_VEN_1002&DEV_6719&SUBSYS_0B001002&REV_00_4&113C73B2&0&0018&02A
Vendor ID: 1002
==================
AdapterIndex=2
AdapterName=7900 MOD - AMD Radeon HD 6900 Series
BusNumber=1
DisplayName=\\.\DISPLAY3
DriverNumber=0
DriverPath=\Registry\Machine\System\CurrentControlSet\Control\Video\{E28D080D-DB37-4BEB-9E3D-F3BE0A995BAF}\0002
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0003
Exist=1
FunctionNumber=0
OSDisplayIndex=2
PNPString=PCI\VEN_1002&DEV_6719&SUBSYS_0B001002&REV_00\4&113C73B2&0&0018&03
Present=1
UDID=PCI_VEN_1002&DEV_6719&SUBSYS_0B001002&REV_00_4&113C73B2&0&0018&03A
Vendor ID: 1002
==================
AdapterIndex=3
AdapterName=7900 MOD - AMD Radeon HD 6900 Series
BusNumber=1
DisplayName=\\.\DISPLAY4
DriverNumber=0
DriverPath=\Registry\Machine\System\CurrentControlSet\Control\Video\{E28D080D-DB37-4BEB-9E3D-F3BE0A995BAF}\0003
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0003
Exist=1
FunctionNumber=0
OSDisplayIndex=3
PNPString=PCI\VEN_1002&DEV_6719&SUBSYS_0B001002&REV_00\4&113C73B2&0&0018&04
Present=1
UDID=PCI_VEN_1002&DEV_6719&SUBSYS_0B001002&REV_00_4&113C73B2&0&0018&04A
Vendor ID: 1002
==================
AdapterIndex=4
AdapterName=7900 MOD - AMD Radeon HD 6900 Series
BusNumber=1
DisplayName=\\.\DISPLAY5
DriverNumber=0
DriverPath=\Registry\Machine\System\CurrentControlSet\Control\Video\{E28D080D-DB37-4BEB-9E3D-F3BE0A995BAF}\0004
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0003
Exist=1
FunctionNumber=0
OSDisplayIndex=4
PNPString=PCI\VEN_1002&DEV_6719&SUBSYS_0B001002&REV_00\4&113C73B2&0&0018&05
Present=1
UDID=PCI_VEN_1002&DEV_6719&SUBSYS_0B001002&REV_00_4&113C73B2&0&0018&05A
Vendor ID: 1002
==================
AdapterIndex=5
AdapterName=7900 MOD - AMD Radeon HD 6900 Series
BusNumber=1
DisplayName=\\.\DISPLAY6
DriverNumber=0
DriverPath=\Registry\Machine\System\CurrentControlSet\Control\Video\{E28D080D-DB37-4BEB-9E3D-F3BE0A995BAF}\0005
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0003
Exist=1
FunctionNumber=0
OSDisplayIndex=5
PNPString=PCI\VEN_1002&DEV_6719&SUBSYS_0B001002&REV_00\4&113C73B2&0&0018&06
Present=1
UDID=PCI_VEN_1002&DEV_6719&SUBSYS_0B001002&REV_00_4&113C73B2&0&0018&06A
Vendor ID: 1002
==================
AdapterIndex=6
AdapterName=7900 MOD - AMD Radeon HD 6900 Series
BusNumber=2
DisplayName=
DriverNumber=0
DriverPath={08413FAA-D00D-4CC6-8D64-EB756490875B}
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0000
Exist=1
FunctionNumber=0
OSDisplayIndex=0
PNPString=PCI\VEN_1002&DEV_6719&SUBSYS_0B001002&REV_00\4&896556D&0&0028
Present=0
UDID=PCI_VEN_1002&DEV_6719&SUBSYS_0B001002&REV_00_4&896556D&0&0028A
Vendor ID: 1002
==================
AdapterIndex=7
AdapterName=7900 MOD - AMD Radeon HD 6900 Series
BusNumber=2
DisplayName=
DriverNumber=0
DriverPath={08413FAA-D00D-4CC6-8D64-EB756490875B}
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0000
Exist=1
FunctionNumber=0
OSDisplayIndex=0
PNPString=PCI\VEN_1002&DEV_6719&SUBSYS_0B001002&REV_00\4&896556D&0&0028&02
Present=0
UDID=PCI_VEN_1002&DEV_6719&SUBSYS_0B001002&REV_00_4&896556D&0&0028&02A
Vendor ID: 1002
==================
AdapterIndex=8
AdapterName=NVIDIA GeForce GTX 465
BusNumber=7
DisplayName=\\.\DISPLAY7
DriverNumber=0
DriverPath=\Registry\Machine\System\CurrentControlSet\Control\Video\{B74460F9-2BCF-4BAD-8A6F-BD84CED992A1}\0000
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0002
Exist=1
FunctionNumber=0
OSDisplayIndex=6
PNPString=PCI\VEN_10DE&DEV_06C4&SUBSYS_00007377&REV_A3\4&5C759D9&0&00E0
Present=1
UDID=PCI_VEN_10DE&DEV_06C4&SUBSYS_00007377&REV_A3_4&5C759D9&0&00E0A
Vendor ID: 10
==================
AdapterIndex=9
AdapterName=NVIDIA GeForce GTX 465
BusNumber=7
DisplayName=\\.\DISPLAY8
DriverNumber=0
DriverPath=\Registry\Machine\System\CurrentControlSet\Control\Video\{B74460F9-2BCF-4BAD-8A6F-BD84CED992A1}\0001
DriverPathExt={4d36e968-e325-11ce-bfc1-08002be10318}\0002
Exist=1
FunctionNumber=0
OSDisplayIndex=7
PNPString=PCI\VEN_10DE&DEV_06C4&SUBSYS_00007377&REV_A3\4&5C759D9&0&00E0&02
Present=1
UDID=PCI_VEN_10DE&DEV_06C4&SUBSYS_00007377&REV_A3_4&5C759D9&0&00E0&02A
Vendor ID: 10
==================
Adapter 0 status=1
ADL_Adapter_ID_Get (0)=2057480
Add iAdaptLink[6]=6
ADL_Adapter_ID_Get (0)
================
Adapter 1 status=0
ADL_Adapter_ID_Get (1)=2057480
Add iAdaptLink[0]=0
ADL_Adapter_ID_Get (1)
Add iAdaptLink[6]=6
ADL_Adapter_ID_Get (1)
================
Adapter 2 status=0
ADL_Adapter_ID_Get (2)=2057480
Add iAdaptLink[0]=0
ADL_Adapter_ID_Get (2)
Add iAdaptLink[6]=6
ADL_Adapter_ID_Get (2)
================
Adapter 3 status=0
ADL_Adapter_ID_Get (3)=2057480
Add iAdaptLink[0]=0
ADL_Adapter_ID_Get (3)
Add iAdaptLink[6]=6
ADL_Adapter_ID_Get (3)
================
Adapter 4 status=0
ADL_Adapter_ID_Get (4)=2057480
Add iAdaptLink[0]=0
ADL_Adapter_ID_Get (4)
Add iAdaptLink[6]=6
ADL_Adapter_ID_Get (4)
================
Adapter 5 status=0
ADL_Adapter_ID_Get (5)=2057480
Add iAdaptLink[0]=0
ADL_Adapter_ID_Get (5)
Add iAdaptLink[6]=6
ADL_Adapter_ID_Get (5)
================
Adapter 6 status=0
ADL_Adapter_ID_Get (6)=2479040
Add iAdaptLink[0]=0
ADL_Adapter_ID_Get (6)
================
Adapter 7 status=0
ADL_Adapter_ID_Get (7)=2479040
Add iAdaptLink[0]=0
ADL_Adapter_ID_Get (7)
Add iAdaptLink[6]=6
ADL_Adapter_ID_Get (7)
================

Edit - I got Splinter Cell 1 to work with RP and SweetFX!

Just copy enbseries dx8 to dx9 convertor dll into the "Splinter Cell\system" folder. Do not force any AA (it works but also breaks the game geometry so parts of the game world walls would go missing or turn invisible - wallhack like). Then use SMAA, FXAA, or MLAA and any SweetFX setting!

This trick might work for any other DX8 game.

FRN2003ita · Nov 14, 2012

japamd said: ↑

Should be working with installer published today, have you tried it?
Click to expand...

no one today I have not tried! I'll let you know

Caleb171 · Nov 14, 2012

The defaults value settings in SweetFX in this new build seems wrong. Ex: sharp strengh (0.10 to 3.00) is set to 60,00. It's happens in almost effects.

MeMeMe · Nov 14, 2012

I have a crossfire setup, but I haven't installed the radeonPro beta. Can you make the crossfire detection tool a separate tool, so those of us who dont want to install the beta can send you with our crossfire info?

captforest · Nov 14, 2012

Hi I am new to this forum
I still have problem to get radeon pro working. I have the same problem as in posts above, icon is only shown for a few second and then disappears ...:/ Previous preview build worked without any problems. I would like to try posted solutions but I dont even have config.xml file...any suggestions?

japamd · Nov 14, 2012

Valken said: ↑

Other effects seems to be working but I will do an injector vs RP comparison soon. The most noticeable was the split shader.

I think the way you have programmed RP, the first shaders in will be prioritized whereas the injector would prioritize the other shaders.

SMAA breaking was most noticeable with LumaSharpen enabled concurrently via injection. I will test it with RP vs injector method.

Here is what my setup says - using modded 12.4 drivers with 12.10 cap1

Edit - I got Splinter Cell 1 to work with RP and SweetFX!

Just copy enbseries dx8 to dx9 convertor dll into the "Splinter Cell\system" folder. Do not force any AA (it works but also breaks the game geometry so parts of the game world walls would go missing or turn invisible - wallhack like). Then use SMAA, FXAA, or MLAA and any SweetFX setting!

This trick might work for any other DX8 game.
Click to expand...

Is RP detecting your CFX correctly?

Caleb171 said: ↑

The defaults value settings in SweetFX in this new build seems wrong. Ex: sharp strengh (0.10 to 3.00) is set to 60,00. It's happens in almost effects.
Click to expand...

I forgot to honor localization settings thus 0.6 turned into 6 after number conversion. It should be fixed now.

MeMeMe said: ↑

I have a crossfire setup, but I haven't installed the radeonPro beta. Can you make the crossfire detection tool a separate tool, so those of us who dont want to install the beta can send you with our crossfire info?
Click to expand...

Don't worry, people running the beta and with CFX detection issues will help.

You can help too, just install, run, do the detection steps, close RP and uninstall it. It won't bite nor take a piece of your system if you just do that.

Log in or Sign up

RadeonPro BETA (Automating 3D Settings)

cnckane Guest

The Mac Guest

Valken Ancient Guru

|ALE| Guest

Derko1 Guest

FRN2003ita Guest

japamd Ancient Guru

Mikedogg Guest

Derko1 Guest

zooyork19 Guest

Zyrusticae Guest

japamd Ancient Guru

Zyrusticae Guest

japamd Ancient Guru

Valken Ancient Guru

FRN2003ita Guest

Caleb171 Member

MeMeMe Guest

captforest Guest

japamd Ancient Guru

Share This Page