Upvote Upvoted 20 Downvote Downvoted
Massive FPS Boost for AMD Catalyst Users
posted in Customization
1
#1
0 Frags +

NOTE: Only boosts FPS on DX8

I disabled the Catalyst AI (basically for Crossfire, useless for people with 1 GFX Card) and now I'm able to smoothly play with Comanglia's Movie CFG in filled-up pubs. I consider the performance increase to be about equivalent of the performance increase with Timer Resolution/Core Unparking, which is honestly pretty big.

How to do it:

1. Go to C:\Users\(insert username here)\AppData\”. Click on "Local", then click on "ATI", and finally click on "ACE".

2. Open the file Profiles.xml with Notepad++. Ctrl + F to find CatalystAI. Go to the line that has a value of "Enable". Change "Enable" to “Disable”. Save the file, and in the folder, right click it, go into properties, and make it Read-Only.

3. Finally, go where your ATI folder is in Program Files (for 64-bit users, it would be under Program Files (x86)). Open the folder ATI.ACE, and then open the folder called Core Static. Find MOM.exe, and launch it. If nothing shows up after you click on it, you did it right.

[b][u]NOTE: Only boosts FPS on DX8[/u][/b]

[b]I disabled the Catalyst AI (basically for Crossfire, useless for people with 1 GFX Card) and now I'm able to smoothly play with Comanglia's Movie CFG in filled-up pubs. I consider the performance increase to be about equivalent of the performance increase with Timer Resolution/Core Unparking, which is honestly pretty big.[/b]

How to do it:

1. Go to C:\Users\(insert username here)\AppData\”. Click on "Local", then click on "ATI", and finally click on "ACE".

2. Open the file Profiles.xml with Notepad++. Ctrl + F to find CatalystAI. Go to the line that has a value of "Enable". Change "Enable" to “Disable”. Save the file, and in the folder, right click it, go into properties, and make it Read-Only.

3. Finally, go where your ATI folder is in Program Files (for 64-bit users, it would be under Program Files (x86)). Open the folder ATI.ACE, and then open the folder called Core Static. Find MOM.exe, and launch it. If nothing shows up after you click on it, you did it right.
2
#2
2 Frags +

idk, can't find appdata this way using win 10, any help? (could locate it before on 8.1 but not now)

idk, can't find appdata this way using win 10, any help? (could locate it before on 8.1 but not now)
3
#3
3 Frags +
MGEMikeidk, can't find appdata this way using win 10, any help? (could locate it before on 8.1 but not now)

the folder is invisible, type \AppData in at the top to access it

[quote=MGEMike]idk, can't find appdata this way using win 10, any help? (could locate it before on 8.1 but not now)[/quote]

the folder is invisible, type \AppData in at the top to access it
4
#4
5 Frags +
MGEMikeidk, can't find appdata this way using win 10, any help? (could locate it before on 8.1 but not now)

Win + r and then enter %appdata%

[quote=MGEMike]idk, can't find appdata this way using win 10, any help? (could locate it before on 8.1 but not now)[/quote]

Win + r and then enter %appdata%
5
#5
3 Frags +

As soon as I left notepad++ the thing would automatically get enabled again, so I couldn't make it read-only before it got changed. As shitty workaround I made a copy of the file, put it in a different location, renamed to Profiles.xml there and edited the file. Then I made it read-only there, and copy-pasted it to the appdata directory. Most people running into the same thing could probably figure this out themselves, but just in case some people wouldn't think of it I put it here.

Before:
2639 frames 29.690 seconds 88.88 fps (11.25 ms/f) 9.131 fps variability

After:
2639 frames 27.673 seconds 95.36 fps (10.49 ms/f) 6.989 fps variability

Thanks for this! Hadn't heard of 'Timer Resolution/Core Unparking' before either, so going to check those out as well.

As soon as I left notepad++ the thing would automatically get enabled again, so I couldn't make it read-only before it got changed. As shitty workaround I made a copy of the file, put it in a different location, renamed to Profiles.xml there and edited the file. Then I made it read-only there, and copy-pasted it to the appdata directory. Most people running into the same thing could probably figure this out themselves, but just in case some people wouldn't think of it I put it here.

Before:
2639 frames 29.690 seconds 88.88 fps (11.25 ms/f) 9.131 fps variability

After:
2639 frames 27.673 seconds 95.36 fps (10.49 ms/f) 6.989 fps variability

Thanks for this! Hadn't heard of 'Timer Resolution/Core Unparking' before either, so going to check those out as well.
6
#6
1 Frags +
Forty-TwoAs soon as I left notepad++ the thing would automatically get enabled again, so I couldn't make it read-only before it got changed. As shitty workaround I made a copy of the file, put it in a different location, renamed to Profiles.xml there and edited the file. Then I made it read-only there, and copy-pasted it to the appdata directory. Most people running into the same thing could probably figure this out themselves, but just in case some people wouldn't think of it I put it here.

Before:
2639 frames 29.690 seconds 88.88 fps (11.25 ms/f) 9.131 fps variability

After:
2639 frames 27.673 seconds 95.36 fps (10.49 ms/f) 6.989 fps variability

Thanks for this! Hadn't heard of 'Timer Resolution/Core Unparking' before either, so going to check those out as well.

Thanks for doing the benchmarks man, because I'm way too lazy to. :)
enjoy ur frames

You can get the premium timer resolution from Danpixed's MaxFPS Compilation: (http://www.teamfortress.tv/27801/danpixeds-maxfps-compilation)
Open the program, click 'Maximum', and then minimize the program and forget about it.
I recommend keeping it in your startup folder.

And the Core Unparker is here (You can try V2 if you want to, I used V1 and it was fine):
(http://coderbag.com/Programming-C/Disable-CPU-Core-Parking-Utility)
Just click Unpark all once you get in the program, and you're all set.

The correct download link on Coderbag looks like this:
http://i.imgur.com/NFdPLwX.png

[quote=Forty-Two]As soon as I left notepad++ the thing would automatically get enabled again, so I couldn't make it read-only before it got changed. As shitty workaround I made a copy of the file, put it in a different location, renamed to Profiles.xml there and edited the file. Then I made it read-only there, and copy-pasted it to the appdata directory. Most people running into the same thing could probably figure this out themselves, but just in case some people wouldn't think of it I put it here.

Before:
2639 frames 29.690 seconds 88.88 fps (11.25 ms/f) 9.131 fps variability

After:
2639 frames 27.673 seconds 95.36 fps (10.49 ms/f) 6.989 fps variability

Thanks for this! Hadn't heard of 'Timer Resolution/Core Unparking' before either, so going to check those out as well.[/quote]

Thanks for doing the benchmarks man, because I'm way too lazy to. :)
enjoy ur frames

You can get the premium timer resolution from Danpixed's MaxFPS Compilation: (http://www.teamfortress.tv/27801/danpixeds-maxfps-compilation)
Open the program, click 'Maximum', and then minimize the program and forget about it.
I recommend keeping it in your startup folder.

And the Core Unparker is here (You can try V2 if you want to, I used V1 and it was fine):
(http://coderbag.com/Programming-C/Disable-CPU-Core-Parking-Utility)
Just click Unpark all once you get in the program, and you're all set.

The correct download link on Coderbag looks like this:
http://i.imgur.com/NFdPLwX.png
7
#7
3 Frags +

Theres nothing in my Core Static file where MOM.exe should be?

EDIT: Nvm found it,it was in AMD/ATI.ACE

Theres nothing in my Core Static file where MOM.exe should be?

EDIT: Nvm found it,it was in AMD/ATI.ACE
8
#8
3 Frags +

What are the potential downsides to doing this?

Rather, what am I actually turning off by doing this?

What are the potential downsides to doing this?

Rather, what am I actually turning off by doing this?
9
#9
3 Frags +

theres absolutely nothing in my ACE folder in appdata

theres absolutely nothing in my ACE folder in appdata
10
#10
1 Frags +
TwistedWhat are the potential downsides to doing this?

Rather, what am I actually turning off by doing this?

Might actually be detrimental for performance in some games, I don't know about windows but on Linux but heres some fps tests on linux to give you an idea (just scroll to the graphs), also i'm fairly sure its required for crossfire.
http://www.phoronix.com/scan.php?page=news_item&px=MTA1Nzc
http://www.phoronix.com/scan.php?page=news_item&px=MTgxNjA
http://www.phoronix.com/scan.php?page=news_item&px=MTI1ODM

I got no fps change from doing this btw.

[quote=Twisted]What are the potential downsides to doing this?

Rather, what am I actually turning off by doing this?[/quote]

Might actually be detrimental for performance in some games, I don't know about windows but on Linux but heres some fps tests on linux to give you an idea (just scroll to the graphs), also i'm fairly sure its required for crossfire.
http://www.phoronix.com/scan.php?page=news_item&px=MTA1Nzc
http://www.phoronix.com/scan.php?page=news_item&px=MTgxNjA
http://www.phoronix.com/scan.php?page=news_item&px=MTI1ODM

I got no fps change from doing this btw.
11
#11
2 Frags +
TwistedRather, what am I actually turning off by doing this?

Crossfire. You should be fine unless you're running two AMD Cards, and if you happen to be running two cards it's just as simple as going into properties, un-enabling read-me, and then switching that 'Disable' back to 'Enable' again.

NinjaDCMight actually be detrimental for performance in some games, I don't know about windows but on Linux but heres some fps tests on linux to give you an idea (just scroll to the graphs), also i'm fairly sure its required for crossfire.

I got no fps change from doing this btw.

Idk man, I think its just Linux since AMD doesn't really care about its Linux drivers.

[quote=Twisted]Rather, what am I actually turning off by doing this?[/quote]
Crossfire. You should be fine unless you're running two AMD Cards, and if you happen to be running two cards it's just as simple as going into properties, un-enabling read-me, and then switching that 'Disable' back to 'Enable' again.

[quote=NinjaDC]
Might actually be detrimental for performance in some games, I don't know about windows but on Linux but heres some fps tests on linux to give you an idea (just scroll to the graphs), also i'm fairly sure its required for crossfire.

I got no fps change from doing this btw.[/quote]
Idk man, I think its just Linux since AMD doesn't really care about its Linux drivers.
12
#12
3 Frags +

Last time I did a benchmark before this I got 195 fps, after following this I got 220.

Last time I did a benchmark before this I got 195 fps, after following this I got 220.
13
#13
2 Frags +

Recorded a demo of 2 lives of pubbing on pl_upward, today.
Comanglia's FPS config, dx8, Radeon HD 7950 + i5 3570k @ 4 GHz
Catalyst AI Enabled (before):

14551 frames 76.670 seconds 189.79 fps ( 5.27 ms/f) 16.541 fps variability

Catalyst AI Disabled (after):

14551 frames 73.397 seconds 198.25 fps ( 5.04 ms/f) 18.702 fps variability

Looks like it works well for TF2. Not sure about any other game, but hey, good find. I'm going to run this test again in a bit with higher settings to see if that matters at all.

DX9, Catalyst AI Enabled (before):

14551 frames 81.055 seconds 179.52 fps ( 5.57 ms/f) 15.652 fps variability

DX9, Catalyst AI Disabled (after):

14551 frames 81.726 seconds 178.05 fps ( 5.62 ms/f) 16.336 fps variability

Less impact in dx9. Weird.

Recorded a demo of 2 lives of pubbing on pl_upward, today.
Comanglia's FPS config, dx8, Radeon HD 7950 + i5 3570k @ 4 GHz
Catalyst AI Enabled (before):
[code]14551 frames 76.670 seconds 189.79 fps ( 5.27 ms/f) 16.541 fps variability
[/code]

Catalyst AI Disabled (after):
[code]14551 frames 73.397 seconds 198.25 fps ( 5.04 ms/f) 18.702 fps variability
[/code]

Looks like it works well for TF2. Not sure about any other game, but hey, good find. I'm going to run this test again in a bit with higher settings to see if that matters at all.



DX9, Catalyst AI Enabled (before):
[code]14551 frames 81.055 seconds 179.52 fps ( 5.57 ms/f) 15.652 fps variability[/code]
DX9, Catalyst AI Disabled (after):
[code]14551 frames 81.726 seconds 178.05 fps ( 5.62 ms/f) 16.336 fps variability
[/code]

Less impact in dx9. Weird.
14
#14
3 Frags +

Enabled:

2639 frames 12.849 seconds 205.39 fps ( 4.87 ms/f) 13.553 fps variability

Disabled:

2639 frames 12.846 seconds 205.43 fps ( 4.87 ms/f) 13.608 fps variability
Enabled:

[code]2639 frames 12.849 seconds 205.39 fps ( 4.87 ms/f) 13.553 fps variability[/code]

Disabled:

[code]2639 frames 12.846 seconds 205.43 fps ( 4.87 ms/f) 13.608 fps variability[/code]
15
#15
3 Frags +

does anyone know of a nvidia equivalent of this?

does anyone know of a nvidia equivalent of this?
16
#16
2 Frags +

soz for bump, but like w stated above, is there anything equivalent to this for nvidia users?

soz for bump, but like w stated above, is there anything equivalent to this for nvidia users?
17
#17
0 Frags +
torrittheres absolutely nothing in my ACE folder in appdata

i also experience this

[quote=torrit]theres absolutely nothing in my ACE folder in appdata[/quote]

i also experience this
Please sign in through STEAM to post a comment.