KSATRoadWarrior

Great news, thanks!!

:lol: :lol: :lol:

I have an AMD Radeon HD 7700 Series and just upgraded my driver to 13.152.0.0, which was recommended by CCC. I have the DX10 Scenery Fixer and have not noticed any problems. I have been running with this updated driver for 2 days. :unsure:

Wow, I guess as we get older "some times" we become a little more conservative. I have not spent nearly as much as the posters so far (as you can see from my configuration) but about $1,000 for hardware and about $300 on software, (it has only been a little over one year)!! :lol:

Really appreciate all the feedback. Interesting reading EVEN if I am still confused on the subject as much as ever. I will continue to experiment and keep in mind all of the valuable feedback from everyone. THANKS....

Thanks for the info so far. Just to clarify I was referring to the FSX built in limiter, not any associated directly with the video card. I am an ATI user and not even sure if there is an equivalent setting to the nVidia's. Is there a general belief that setting the FSX limit to 30 will reduce the amount of stutters?

Looking for technical reasons why choose FPS 30 vs. FPS Unlimited. It seems to me that if you set 30 then it will limit data going to either the CPU and/or GPU? Unlimited would not do the check for a limit and perhaps send more data (faster) to the CPU/GPU? What other factors need to be considered in choosing one over the other? ALL comments, ideas, suggestions or advice appreciated.

Well guys, I made it through the flight and landed at KBAD!! I did NOT make it with just the changes Jim had recommended, and did not hit 4 CTDs within an hour. I did reboot the system after the last CTD and removed the poolsize=0. I did not delete the shader cache but completed the flight. I am stumped as to what the real issue is, but it does seem like a combination of too high of settings and not having the System manage my virtual memory. Thanks again for your suggestions!!

Jim and FlyBoy: Thanks.....I think this is my scenario--------after installing the DX10 Scenery Fixer, performance was so good I slide ALL my sliders to the far right. I also discovered, thanks Jim, that my Virtual Memory was NOT being managed by the System (so I changed that). I am in the middle of the same CTD flight (and moving along OK). As soon as it is done I will go back and remove my Poolsize=0. Thanks to both and IF ( LOL) these changes don't work I guess I will be back. :lol:

OK, I am at a loss to determine what is causing this CTD with NTDLL always being the guilty party: Description Faulting Application Path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Problem signature Problem Event Name: APPCRASH Application Name: fsx.exe Application Version: 10.0.61637.0 Application Timestamp: 46fadb14 Fault Module Name: ntdll.dll Fault Module Version: 6.1.7601.18229 Fault Module Timestamp: 51fb1072 Exception Code: c0000005 Exception Offset: 0002e41b OS Version: 6.1.7601.2.1.0.768.3 Locale ID: 1033 Extra information about the problem LCID: 1033 It seems NTDLL was update on 9/11/13 and the only updates were the following Window updates: If anyone can give me a clue on what to look for it would be appreciated. At first I thought it was related to Simconnect but after deinstalling add-ons and reflying the same flight plan (different aircraft) and getting the same CTD I eliminated Simconnect as a problem. Could one of the Windows updates be causing many of us the same CTD with NTDLL.DLL? THANKS!!!!!!!!!

It sounds like Steve wants to make sure that there is no chance of another serious incident during installation or removal, as well as continue to work on cleaning up some things that have been brought to his attention the last few days. Per the following from FSS, the incident that caused the problem and delay was not Steve's fault: http://forum.avsim.net/topic/422092-man-am-i/page-2#entry2810800 Even some of the major developers have released products with problems. From what I have gained with this initial release I do not believe anyone will be disappointed if they wait a few days or a week to get a much better product. I can't believe the difference it has made it my FSX environment, but that may not hold true for everyone.

http://forum.avsim.net/topic/421399-dx10-fixer-released/page-20#entry2811919 See Steve's message and check his blog................. Also.....response from FlightSim Store: http://forum.avsim.net/topic/421399-dx10-fixer-released/page-20#entry2811652

Adrian, thanks for that update. We look forward to hearing from Steve that he is ready for an updated release.

That's when a group of volunteer pilots from the non-profit Warrior Flight Team (http://www.warrioraviation.org/) stepped in and agreed to fly in formation above the Arlington ceremony in their own planes, on their own dime. Eight civilian pilots honored the veterans, arranging permission from the Department of Homeland Security, Secret Service, and FAA with an aerial tribute above Washington. They even flew a Douglas A26 Invader - the same plane that the two friends from Georgia were flying when they were shot down 44 years ago. It was flanked by 2 P51 Mustangs.

"as another passenger rushed to help get the plane safely to the ground"...........there are VARIOUS stories out on the web. Better that we wait and here from FTSB and hopefully get the facts. I have read pilot, crew member, etc........sad event regardless for the families and a flight to remember for passengers.

United flight pilot suffers fatal heart attack on Seattle-bound flight; plane makes emergency landing http://www.foxnews.com/us/2013/09/27/united-plane-makes-emergency-landing-after-pilot-has-heart-attack/

WOW........nice having autonap (sorry auto pilot).................

Wow, another step forward with technolog.......................

Jim, I missed that and was wondering why some of my nav lights were not working......IF you set it correctly (disable display means it is ENABLED) it works GREAT..............THANKS Jim and another thanks to Steve..............

I did BEFORE I purchased DX10 Controller. I have sent the vendor an email suggesting that they add an option to know if someone is going to be using DX10 Controller. They then can calculate some higher settings than the ones used today without DX10 Controller. FSX Booster 2013 did make it easer for some of the tweaking (which can all be done without FSX Booster 2013). I am no longer using it since installing DX10 Controller.

I too no longer use FSX Booster 2013 since getting FSX Controller. If you do use it along side FSX Controller be cautious as I found it demotes some of your FSX settings where you may not get the full benefit of FSX Controller. At least that was my experience so far with it.

I have the DX10 Controller and the Aiport HD enhancer and have no problems with it. I did turn off airport signs otherwise I got duplicate signs.

I have the DX10 Controller and use MyTrafficX 5.4C and have no problem with AI nav and strobe lights........

A BIG thanks to Steve Parsons and his beta testers (Paul Johnson, Gerald Salden, Tomaz Drnovsek & Charles Earl) each of you have added to the enjoyment and longevity of FSX! Thank you, thank you.............job well done. I am sure that the weeks and months ahead will let us see additional improvements. :Applause: :drinks:

From Paul: The reason the rain is greyed out, is that you have the fix already there, so it doesn't replace it. If you want a complete new suite of the original ShadersHLSL code, just blow away the old HLSL folder, and replace it with your backed-up folder ( you DID back it up - right! :lol: ) and then reinstall the Fixer, and all boxes will then present themselves as original. Here's a Stock HLSL folder if you need it! Enjoy! All the Best!