cvearl

That is what happens if you zoom all the way out on the planet. /shrug.

13.9 is current 13.4 is previous and is stable in both DX10 and DX9. Most ATI users are using it with FSX. 13.10 and 13.11 are BETA's currently. Problem is 13.9, BETA 13.10 and 13.11 crash if you fly in DX9 mode. Charles. Google this... "FSX, OOM and Addon VAS Usage" and there is a blog from xxxxx that covers this well enough. But the jist is this... Large LOD radius and big airport addons with PMDG planes = OOM probability. Every time you pass near a payware airport or scenery, VAS (Virtual Address Space) increases and once you get close to 4GB... Boom. C.

Spoke too soon. Second flight when I try to change planes or exit FSX I still get the FATAL Error on Driver version 13.11. Well see what the next version brings. Nothing wrong with 13.4. It's been solid in DX10 and DX9 FSX and any games I have played but with Battle Field 4 coming I will need to upgrade. I might have to leave FSX in DX10 mode by the looks of it if I want to move forward with driver versions. ATI has been made aware through the driver team and well see if it gets resolved in the next release. I know there is the work around for DX9 mode by using the atiumdag.dll file from 13.4 in the FSX root folder. I was just hoping that I could go without yet another work around. Just like we all do with UIAutomationcore.dll to prevent menu crash bug in FSX. Charles.

You still use RadeonPro for vsync though or are you using something else? C.

Might be straws here but... Shut down. Unplug. Open Case and remove card and reseat card in slot and ensure it's plugged in well. Re-seat the RAM. Close it up and try to start it again. No go? Boot and enter the BIOS. Reset your BIOS to standard factory defaults and then try again. Back when I had my GTX660Ti and I was switching ATI for NVidia and back a few times I had this happen once. If multi screen go back to single and try again with only one screen hanging. Not telling you what to do but these are my desperation steps. Wife's calling. Gotta jet. Saying a little prayer for you. This is a good guide if this is a Windows 7 issue you are experiencing. http://www.sevenforums.com/tutorials/219533-troubleshooting-windows-7-failure-boot.html Charles.

Don't install Catalyst? I personally would not follow that advice. I am an ATI user from way back (VGA Wonder Days) and used to be in the driver BETA's back in the day ATI. I know you get some people believing CCC is bloat ware but then in NVidia land (I have had dozens of these as well) we have their control panel and all that stuff. Then we run MSI Afterburner and so on. What's the diff? Personally I do not have problems with CCC ever. The AMD Catalyst Install Manager has never failed me. But I always follow this simple rule. So this might be why? #1. Before uninstall I reboot to release any locked files. I ensure RadeonPro or other VGA Utilities are also not loaded. #2. I use the Catalyst Install Manager to do the "Express Uninstall All AMD Software" Option and at the end it asks if you want Catalyst Install Manager removed as well and I say yes. #3. Then I reboot. #4. I find any AMD folders on C: and delete them. #4. Install the complete driver of my choice. ALL of it. Yes I do Express because I want all of it installed. #5. Reboot again even though it does not ask. I, and anyone I support this way, never have a problem. However. Now that I have said that, Murphy's law.... My computer will blue screen as soon as I start FSX and not come back up. LOL I hope he gets sorted either way. Charles.

I always find these kinds of posts confusing. I just built my 6th AMD Video card based simulator (I do this for other people wanting a home sim for training *single screen only so far*) and I have tested like 4 AMD cards and 2 NVidia in my current build and have been flipping drivers back and forth for years and never had this. But I definitely feel for you. It can be confusing and painful when this happens. Can you at least start in safe mode? Did you, or, have you ever run driver cleaner and CC cleaner? I don't recommend that. I never do. I have seen critical files nuked by the process. Did you or do you ever use restore points and restore to a previous time ever? I never do that. It leaves traces that can conflict. Charles.

If you lock frame rates in FSX menu and then try to lock frame rates within Radeon Pro you will get stutter. With FSX sent to unlimited and Radeon pro locked at 30 I get super glass smooth not even a MicroStutter. But we all don't have the same add-ons I guess. In dx10, I know of no other way to force Vsync without Radeon Pro. C.

Uninstall the current driver. Do it through programs in the control panel in Windows 7 using the Catalyst Install Manager do a full complete uninstall and reboot the computer.

OK DX9 and 13.11 seem to work with my 7970 without crashing. And the performance seems awesome. I would like someone else to test though. I wondered if the UIAutomationcore.DLL that we all put in the root of FSX folder was a problem with one of the ATI files. I have renamed it and I have done several flights in several planes using the menu in FSX extensively as I go and NO CRASHES or FATAL ERRORS. Even when ending the flight. Can someone else test? Beta 13.11 is here -> http://support.amd.com/en-us/download Please fully uninstall using the "AMD Catalyst Install Manager" in "Programs and Features" in the control panel and reboot and then install the new BETA and reboot. Then test. The UIAutomation.DLL file (if you used it like all the old guides said to) is here. You can see how I renamed it.

Well I have had a number of hours at 8xSSAA with medium clouds and not a single spike. Hmmm... C.

No spikes? BTW... In DX10 how are you forcing vSync? I am using RadionPro C.

I'm not using that setting in DirectX 10 currently since my last post my sim is glass smooth. I only use it in Directx 9. My config file is virgin.

Not ATI's fault. 7 year old engine. Unfinished DX10 mode with re-jigged shaders. Issue effecting a very niche market. Doubt they would bother even looking at that. However... I have had 6 hours of flights in A2A 172 and Duke Piston B60 V2 around CYVR and KSEA with Building Storms theme. Not one single spike. Where previously, using the 13.4 driver for my 7970 and the initial release of Steve's fixer, I could not go 15 minutes without being surrounded by spikes and big sheets of textures shooting out of the ground. I will post my stuff in a bit but I am using a virgin FSX.CFG with wideviewaspect=true and highmemfix in it and that's all. Even using my regular settings in FSX. Off the top of my head... Water Low 2x, Scenery and AG Very Dense and Dense. Clouds at 100% density. I reloaded my REX theme with the DX10 stuff all enabled in the options. Used the Medium Computer Spec (Was using High) so now my textures are all 1024 I think. DXT5 and all that. Then for the theme I took "Reality" and changed the water to "Use This". Then... I was testing 4xAA set in the tool. Water Shader disabled (unchecked) in the tool. SuperSample enabled in RadeonPro (or CCC). 16xAF Quality. Vsync forced in RadeonPro. But after about 4 hours of flying like that I re-enabled Water Shaders in the tool and bumped to 8xAA in the tool. Aside from the obvious side effect of a few stutters if I put a 3000 foot thick overcast deck 2000 feet above the ground, I got not a single spike. I think I saw one and only one flash of a white square on the ground for a split second in a flight that was over an hour. I am on a new version of DX10 Fixer for testing (but I doubt that has anything to do with it) and I am running the new 13.11 BETA 1 driver from AMD. http://support.amd.com/en-us/download If you are going to run this driver. Please please please... No driver cleaners and stuff. Just use the Catalyst Install Manager in Programs in the Win7 Control Panel to do a complete uninstall of all AMD drivers and programs and say yes to remove it all and reboot when asked. Then install the BETA 13.11 (Express) and reboot again. And in the fixer, set 4xAA for now. Disable the water shader and make your first flight and see. No spikes? Enabled Water Shader and fly around again. No spikes? Try 8xAA. As per usual. Bad weather+dense AG+8xAA+high settings in FSX = stutters and lower fps. Same as nVidia using 8xAA+8xSGSS. One catch. WHQL 13.9, Beta 13.10 and 13.11 will all FATAL ERROR CTD FSX in DX9 mode when manipulating the menu (I think Auautomationcore.dll in the fsx root has something to do with that?). If you want DX9 mode you have to go back to 13.4. ATI has been told about this error by several of us. Current Status: I don't know what fixed what. New Tool from Steve for testing. New Driver from AMD. Reset my REX theme with more moderate settings (no 2048 stuff). A virgin FSX.CFG. Or just the simple act of disabling the Cloud and Water Shader for a few flights and then turning them back on shook something loose (But I dont normally subscribe to chance voodoo happenings like that). Using a tool to watch GPU usage and I can see with 4xAA+SuperSample set the GPU usage barely reaches 65% even in cloud. Go to 8xAA+Supersample with clouds and the usage heads up into 90%+ range. I know eventually I will have issues on longer flights sustaining nearly maxed GPU usage and the only cure is not using unlimited in FSX and setting 30 fps and turning off the external limiter. But then it is not as smooth in demanding situations. The price of perfect AA. Charles.

Looks like ORBX has some competition if they were looking at going to XP10. Comparing to ORBX, same quality. http://fullterrain.com/product_czst.html

I understand completely. I am a graphics ###### from way back and as a previous nVidia 660Ti owner, I understand the use (and effect) of SGSS 100%. I also understand how all the AA modes work and the overall effect they have on edge based shimmer as you fly. Especially bitmap GPS screens and the lines and fonts. So... I can only conclude that you were simply unseccuessful at getting it to work. But as long as you are happy with whatever you have going now, that is all that matters but I assure you. I have 95% shimmer free razor sharp as you see in my screenshots. I use TrackIR and when I pan my virew and fly past 3d objects or approach them from far away, I have nearly perfect shimmer free geometry. Charles.

Your willing to live with Shimmering just to have Sweetfx? Not this cowboy. I mean. Are you saying you blur the writing with Sweetfx? C. 4xSSAA in DX9 is perfect for the GPS/FMS/MFD's 4xSSAA in DX10 is nearly perfect for them as well. Almost no shimmering. 95% shimmer free. 8xSSAA in DX10 is 100% perfect for them. But then overcast clouds become a problem with framerates. No SweetFX needed. Have you tried Enabling supersample in ATI CCC or Radeon Pro with AA set in Steve's tool? Just an FYI...In the driver for ATI (through CCC or RadeonPro) if you use adaptive AA or Morphological AA, you get horrid shimmer. I hope that's not what you have set. Also. If it is set in CCC and not in RadeonPro, it will be set still. If using RadeonPro (have to for vsync) you must have CCC set to DEFAULT in the 3D Applications page. Charles.

7970 here. BETA 13.11 worked a treat in DX10 last night. I already know it will CTD in DX9. Have not tried the old atiumdag.dll file yet with DX9. I am sure it will work because it is a fix people have used in the past in other games that crashed with that file. I would like to know since this is a menu crash we get in DX9 if the uiautomationcore.dll file we all hacked into FSX has anything to do with it. Can someone rename it uiautomationcore.old for now and see if the crashing stops in DX9 with 13.10 or 11 ? I will later but off to work I go. Charles.

SGSS is NVidia for sure. It's MSAA (Multisample) combined with (SSAA) SuperSample for transparent textures like Gauges and exterior paints line edges. 2xSGSS = 4xMSAA+2xSSAA So with ATI... Not SGSS but SSAA like so -> Same order as the screenshots... Option 1: through Radeon Pro Option 2: through CCC 3rd shot is only 4xSSAA. 4th shot is only 8xSSAA. <--- (8xAA+4xSGSS) but expect the same performance in clouds.

not sure which model of graphics card you have as I'm reading this from my phone. But I think you may have missed a step. With DirectX 10 if you enable super sample in the ATI CCC Control Panel or with radeonpro and you have the DirectX 10 fixer set to 4x AA, it should be crystal clear in the cockpit and almost no shimmering whatsoever. C. whoops I did not see that you're using sweetfx. are you saying that now that you disable sweet FX it's looking sharp now cuz I also found running sweetfx I did not like the result at all. but to be completely fair I did not try a lot of things. C.

I tested both 13.10 and 13.11 in DirectX 10 mode using Steve's directx10 fixer. no issues. however I confirmed again 13.10 and 13.11 will get a fatal error with FSX when manipulating the menu for trying to exit FSX when using DirectX 9.this perhaps be linked to the UI Automation core DLL that we all place in our FSX root? I have not tested that yet.

13.9 is the current WHQL driver from AMD. It is crashing DirectX 9 mode FSX with fatal errors and this is a known issue and discussed in another thread. 13.4 is working fine in DirectX 9. the current betas are 13.10 and 13.11 both of these are also crashing in DirectX 9 mode with FSX however in DirectX 10 they appear to be working but I am testing further this is also covered in another thread. These issues have been reported to ATI by me in a few other people as well with FSX it's hard to say whether or not they will be able to resolve them. In the other thread there are workarounds for this by copying one of the files from an older driver I'm not sure if that's a good idea but some of reported that that works fine as well. sorry I do not have the link to those threads right now.

Either disable the shader in the tool or go back to DX9 or go nVidia. You will need a GTX770 or better to match what you have. Three test flights with Water at 2xLow is fine with Water Shader disabled in the tool. NOT using BP=0 in DX10. Actually no tweaks in DX10. Just Highmemfix, wideviewaspect. Everything else virgin. Really I am thinking that it is something to do with the tool's Water Shader. But I could be wrong. Charles. 13.10 is fine in DX10... ATIUMDAG.DLL FATAL ERRORS FSX in DX9 mode. I have put 2 reports into ATI on this as it happens with WHQL 13.9 and both BETA's 13.10 and 13.11 Testing 13.11 in DX10 currently with the Water Shader disabled in the Fixer. Charles.

Nothing wrong with uninstalling a driver by the book and rebooting and installing another one. Works 100% perfect. Last few years at least and I look after thousands of computers with Altiris and other end point management tools. I never recommend system restore except as a last resort. It is not as safe as we sometimes make out. I have seen it bugger an OS or two in my time. But we have all had different experiences and I respect that. BETA 1 13.11 is out. Any takers? LOL I will try it. 1. Full uninstall all AMD drivers via Win7 CP Programs 2. Reboot. 3. installl beta. If fail... Repeat but install 13.4 Charles.

Fltplan mobile for Android and iPad is free and includes all plates approaches arrivals and departures for free.but currently only covers Canada the United States and Alaska. You just have to set up a free account on their website. C.