ATI 6870 not overclocking (Low FPS)

[LeLv8_Archi]

Originally Posted by gabuzomeu

ATI tray tools, 870MHz on 4890 fixed everything: enjoyable (patched) game, 50fps over sea, 25 over land, everything high in 1680x1050, no AA yet.
Looking at beta patch thread, most if not all ATI owners are disappointed, Nvidia see improvement -> points to GPU speed being the limiting problem on ati cards ...

Hi,

I have also 4890 and trying to get the max out of it so could you post some (AtiTrayTools) setup specs since it crashes my computer every time I try to set it up...

Thanks

[Ataros]

Stock speed of my 4890 is 850:975. It crashes if I overclock it usually.

Try making a profile for ATT for this speed.

[LeLv8_Archi]

It's no go with the ATT profile-thing pc freezez when launching the profile.

[JG301_HaJa]

My HD6870 now clocks up properly but the GPU sits as 100% or almost 100% all the time.

Also the CPU is at 26% load.

[Flanker35M]

S!

Ran AMD resource monitor during free flight over France. GPU load was 45-61% all the time, GPU clocks were at 3D speeds etc. CPU utilization was mere 23-27% on average, varied between cores.

GPU load seemed to increase when nothing was visible, like sea or sky. But when looked down on ground etc. it decreased. CPU utilization was pretty constant through the test.

[JG301_HaJa]

Did a new test with completely different results?!

I have set W7 performance to "adjust for best performance" or whatever it's called in the English version of OS. I have downloaded and used "Gamebooster 2" from IOBit and then I ran it again.

The 1 core is at about 40% to 60% all the time and the other flutter from 0% to 30%
The GPU load is around 50% after an initial 100% for about 20 seconds.

I havn't checked the FPS but it feels very playable atm. Have to fly some and see if it feels nice. All setting are at high except buildings and trees that are very low and also no grass.

[Phazon]

Hey guys, I was reading some of the Russian Clod forums and apparently the game still doesn't use a proper full-screen mode. It was still buggy and didn't make the patch. I think having a proper full-screen mode will fix the issue as it is unorthodox to have a intensive 3D program run in a window. The drivers are optimised to run in full-screen mode.