I had and have alot of pain switching from HD5870 to a 7970 3Gb ghz. Did not believe that in the first place but here i am tryiing to find the best driver experience outhere. The new betadrivers does not work and my ccc still cant open in Windows 7 64bit regardless all the fix out there.

Does Radeonpro replace the functions of ccc? For now i can change settings in the windows taskbar by rightclicking ccc.

 

Thanks Michael

I had and have alot of pain switching from HD5870 to a 7970 3Gb ghz. Did not believe that in the first place but here i am tryiing to find the best driver experience outhere. The new betadrivers does not work and my ccc still cant open in Windows 7 64bit regardless all the fix out there.

Does Radeonpro replace the functions of ccc? For now i can change settings in the windows taskbar by rightclicking ccc.

 

Thanks Michael

 

OK firstly...

 

One problem that could be killing you I think is .NET if it is not running right, CCC will fail. It is not AMD issue it is a Win7 issue and if it never got installed and patched right on day one? It will haunt you forever.

 

http://support.amd.com/us/kbarticles/Pages/AMDCatalyst13-4WINReleaseNotes.aspx

 

.NET 4.0 SP1 should be installed prior to the driver. Uninstall the driver... Install this .NET 4.0 SP1 and reinstall the driver!

 

http://www.microsoft.com/en-ca/download/details.aspx?id=17718

 

As for best driver and CCC and all that. I have switched 4 cards (one NVidia in the middle) in 12 months same build of Windows 7 64 and not one single issue. I went from ATI 6950 to GTX660ti to ATI 7950 to ATI 7950 Ghz and at least 3 driver revisions since. I do not use any driver cleaner or any of that other stuff. I simply used the "AMD Catalyst Install Manager" in the Programs and Features area of Control Panel. I do not know why you are having problems. But lets look at things...

 

I have a fully working CCC and I can switch between using CCC and RadeonPro at will without a single issue. Although I strongly recommend Radeonpro app (no need to remove CCC) for a few reasons... DFC (Dynamic Framerate control) enabled at 30 fps and Vsync forced on but FSX fps set to unlimited (smoother and better fps in dense regions). In DX10 mode you cannot get vsync to work in FSX with ATI without RadeonPro also so you know in case you want to try DX10 preview.

 

Current Catalyst is 13.4 and that is what I am using. I guess I could but I will wait for the next version to be official I think. Last few drivers have been rock solid and great performance in FSX for me since the 6950.

 

My advise is simply....

 

1. Uninstall from Control Panel in Win7 Programs and Features using the Catalyst Install Manager using the EXPRESS UNINSTALL ALL AMD SOFTWARE option.

2. Then reboot

3. Install the current Catalyst 13.4 driver package COMPLETE including CCC.

4. reboot

5. PREP FSX for the new card! This is imperative no matter the brand card you have.

• Flush Shader Cache http://fsxtimes.wordpress.com/2011/07/11/clean-up-shader-cache/
• Delete FSX.CFG covered here in first two steps ---> http://fsxtimes.wordpress.com/2011/08/29/part-1/\

6. Add the following and ONLY the following to FSX.CFG (ATI does not need the majority of the NVidia centric balancing tweaks). Some of the tweaks I have played with harm performance on ATI cards. For the ATI friendly ones, these are the MUST HAVES....

 

[GRAPHICS]

HIGHMEMFIX=1 <----- add this line!

ForceFullScreenVSync=1 <---- and this line if using CCC otherwise Radeon Pro can force vsync for you as well. Add the line anyway!

 

http://fsxtimes.wordpress.com/2011/08/14/fsx-cfg-verticalsync/

 

[Display]

WideViewAspect=True (Make true as default is False)

 

Optional ... ATI is notoriously good at using this last tweak for some reason. Try it. If you don't like it take it out.

http://www.fsdeveloper.com/forum/showthread.php?t=19460

 

[bufferPools]

UsePools=0

 

QUOTE -> the ATI's are FANTASTIC reading the command buffer faster than ANY card on the planet so with an ATI you could practically have FSX nirvana if FSX were to send all draw instructions to the command buffer bypassing the BufferPools.. however, THERE IS A CATCH. Since ATI's have more shader processors, they need to run 'slower' (they run at 700Mhz) same as the core clock. so, complex scenery, clouds, add-on aircraft will considerably LOWER your total average FPS. so, again, its up to you to decide...

 

Please note that the 79XX series is a lot more powerful than the 5870 so some of this is no longer an issue in terms of "losing fps". My 7970 flying around CYVR PNW scenery from ORBX in C377 I get aprox 15 - 20% better fps (benching in unlocked mode) with UsePools=0 But every 5 - 10 minutes I might get a flicker of a patch on the ground. Rarely though.

 

Current AMD 79XX driver... Win7 64 http://support.amd.com/us/gpudownload/windows/Pages/radeonaiw_win8-64.aspx

 

Charles.

All that said... I did do a guide for DX10 in FSX with ATI...

 

http://www.orbxsystems.com/forum/topic/60367-dx10-guide-for-atiamd-users-with-ssaavsync-enabled/

Thanks for the advice in which i allready had done besides the reinstall SP1. NET. Will try that.

 

Could it be the directx11 who has failures? Cant reinstall as Windows says allready up to date

Thanks for the advice in which i allready had done besides the reinstall SP1. NET. Will try that.

 

Could it be the directx11 who has failures? Cant reinstall as Windows says allready up to date

What exactly is not working? Or failing?

What exactly is not working? Or failing?

 

CCC is closing when trying to open the program . Using CCC via taskbar with your right mouse is working. I can live with that. I am  not alone with this issue but the fixes from other sites and methods to reinstall only CCC does not work on my system. (cleaning files ACES in the regedit and in appdata/roaming etc etc.)

 

I7-4770K and Asus Z87-Pro just ordered btw :-)

 

Michael moe

OK so you can get it to open but not with a double click but with a right click.

 

Weird. That CPU is going to rock! So you going to reinstall windows with the new motherboard?

 

C.

Yes maybe but the problem is that i cant recall all the small fixes maid to FSX over 2-3 years. Some is deleting files in scenerys etc etc but i will try a image backup first.

 

Michael Moe

HI,

 

@cvearl, thanks for your guide.

I've got some pb: if you could put an eye on these please, it would be an honor!

Thank you.

Reinstalled and is now still installing all weekend and using 13.4 but found the problem is. Net 4.5. Just uninstalling and everything is fine again. Testing the Haswell and FTX global. With a maxed fsx system without aitraffic i get 60-80 fps with beechcraft in Aerosoft ENVA with default CPU settings. Nice. The haswell will load into Windows 7 and fsx at 4.8 ghz at 1.25v but still no stable there so default it is for now

Reinstalled and is now still installing all weekend and using 13.4 but found the problem is. Net 4.5. Just uninstalling and everything is fine again. Testing rhe Haswell and FTX global. With a maxed fsx system without aitraffic i get 60-80 fps with beechcraft in Aerosoft ENVA with default CPU settings. Nice. The haswell will load into Windows 7 abd fsx at 4.8 ghz at 1.25v but still no stable there so default it is for now

I thought most people could only hit 4.4 or so on Has well aand that is better than 5.0 sandy?

This chip must be a good one. 36 fps idle at [email protected] but very very hot in prime95. Hitting 100c and bsod. This is still new to me so will try lowering til i get a stable system. My RAM is also only 1600mhz at 1.65v. Might be a problem

The reason for the CCC program to close on you like this is due to UIAutomationCore.dll...CCC needs that to do it's job.  I found that putting the UIAutomationCore.dll fixed on in FSX folder while leaving the on in the Windows directory alone allows CCC to work while having no crashes ever in FSX...hope this helps!

 

I am 100% sure that is why your CCC randmoly closes at startup.  I singled it out by adding UIAutomationCore.dll back to the windows directory then running CCC just fine, then immediately removing the DLL and trying CCC again, and the window closed up on me, put it back in, and all is good. 

These are the default version for Windows 7, (version in bold) and should be installed in these folders:-

 

C:\Windows\winsxs\amd64_microsoft-windows-uiautomationcore_31bf3856ad364e35_6.1.7600.16385_none_0c0d85465bcceb37\

 

C:\Windows\winsxs\wow64_microsoft-windows-uiautomationcore_31bf3856ad364e35_6.1.7600.16385_none_16622f98902dad32\

 

C:\Windows\System32\       Same version in these two folders.

 

C:\Windows\SysWOW64\

 

These files should not ever be removed or copied elsewhere - as programmes written to use them may or will crash if/when they cannot be found.

 

The version which FSX needs is 6.0.5840.16386, (no other) and this should be placed in the root folder of FSX. 

This version should not ever be removed or copied elsewhere, as programmes written to use the Windows 7 version - like CCC - may or will crash if/when they cannot be found.

 

It should also absolutely NOT be registered.

 

OK?  :smile:

Paul, can confirm! I tried that once with bad results.  You HAVE to use that particular uiautomationcore version that Paul mentioned in FSX or badness happens....