dave1812

I don't think I've ever played any version of FS on any computer that ever had FR as high in FS as in windowed mode.

update: no more fatal errors with uiautomation. I did get an error with the graphics driver, but I was doing a bunch of stuff with my computer at the time and believe that will not be an ongoing issue. I've flown several hours without incident!!

Finally fixed it. First of all, let me say that after unplugging the Logitech, and getting reverse thruster to work, dumb me realized that I had a CH Products Yoke sitting around. Plugged it in and went flying. RT worked like a champ. tinkerered around some more with the Logitech, installed a driver from their website, still no joy. Decided to cheat on the calibration. Voila! Success. By "cheating" during calibration of the throttle slider, I got the Logitech to work properly, because by not moving the slider all the way to idle while calibrating, the s/w compensated and that changed the output so that engines would go to full idle. If I calibrate it the way one is supposed to, it won't work. Whew!! I hope this helps someone having similar problems.

AHA!!! I just unplugged the joystick (Logitech Wingman Extreme) which has worked on all other versions of FS I've used it on, just fine. As soon as I unplugged it, I can now fully deploy reverse thrust, from the keyboard. I did this due to someone on another forum (been googling my fingers to the bone over this issue) complaining about reverse thrust not working and someone told them they had had that issue and it was due to interference from their joystick throttle (NOT a Wingman). So....now the question is how do I fix this incompatibility? I've already done several calibrations of the joystick (not that it ever seemed to need it), but I did it just to be sure.

Hi, i've got a Sager laptop with i7 2720QM, 8GB ram, Win 64, Nvidia GTX 650M. This problem has been ongoing since I installed FSX. just in case arming the spoilers (shift-fwd slash) is necessary for proper deployment of reverse thrust, I tried that too. still get half-assed reverse thrust with almost no braking effecting. the animation shows the engine cover barely retracting and it bounces between barely retracted and closed. this occurs on all jets. it's driving me nuts!

still not working! I changed airbus 321 to -.5 from default of -.25 min throttle limit, calibrated joystick and I still cant get a solid reverse thrust. instead, I get a sporadic, wimpy reverse thrust action and animation. #####??? oh, and I assigned a joystick button to throttle decrease along with repeat. I also tried to record what's happening with the video recorder but that doesn't seem to want to work properly. I've played FS since the back in the 80's and have never had trouble with reverse thrust before. anyone got any other ideas? After all those changes I even tried using both versions of DX--no difference between them for this issue.

I don't recall ever having issues with RT in FS9, but I can't get any of the heavies to do RT in FSX. When I hold F2 during landing, the engine sound doesn't change much, plane doesn't decelerate much, and the animation on the engines shows very little movement of the engine covers. Thinking maybe it was related to DX10 I switched to DX9. No joy. Can someone tell me what i've got to do to get RT to play nice on my system? googling didn't turn up this exact problem. mostly what I find is questions from people who don't know how to engage RT...

I did the things (choosing different views points) that caused the fatal error, and had no problem, once I removed the dll from the FSX folder. I think I'll just sim w/o that file. :) If I get more show stoppers, then I'll come back for more ideas.

just got another fatal error. after the error, I went ahead and renamed that dll file in my FSX folder so that it won't be used, and I'll see how FSX responds.

thanks. yup, that's the one I have (don't take my comment about trust too seriously! :) ) I'm just frustrated at a variation in what is the correct procedure for dealing with black screens or crashes) TIA

so u are saying that the explicit instructions in the other thread are wrong? who to trust? who to trust? LOL!! I need to go google how to unregister it. we'll see if that helps. thanks for the idea. EDIT: looks like "-u" command-line parameter does it. EDIT2: I got a error when trying to unregister it. Only thing I could think of was to register the dll that's in system32. then I renamed the one in the FSX folder pending any further action with that file if someone comes up with a better plan.

that's what I had done today, and less than an hour later, I got my first fatal error in FSX. :) and the error message mentioned that file. I only installed it (and registered it) because of a black screen I had gotten this afternoon--also a first. sigh.

thanks dave, I'll give that stuff a shot tomorrow morning.

ah, ok, thanks for getting back to me.

that I found from reading the forum. it occurred when I began to use spot plane during video replay mode after a lengthy flight. it was jerky, so as i did a right click to choose fixed spot, FSX crashed with the uiautomation.dll error. anyone know why? (http://forum.avsim.net/topic/340889-black-screen-after-long-flight/page__hl__black+screen__fromsearch__1 0) I hadn't had a fatal error in FSX before, on this roughly week long installation. Secondly, when i got to my destination (heathrow) progressive taxi didn't turn on when I selected it. ideas? btw I'm using DX10.

really? how about if i have a video card with 1536MB of memory. then is it still too high?

here's fsx.cfg: [sOUND]AmbientUIMusicVolume=-6.000000SOUND=1SOUND_QUALITY=2SOUND_LOD=0UISound=0AmbientUI=0PrimaryDevice={DEF00000-9C6D-47ED-AAF1-4DDA8F2B5C03}VoiceDevice={DEF00002-9C6D-47ED-AAF1-4DDA8F2B5C03}SOUND_FADER1=0.960000SOUND_FADER2=0.680000SOUND_FADER3=0.610000SOUND_FADER4=0.500000AmbientUIMusic=FSX01[Display]ChangeTime=4.000000TransitionTime=4.000000ActiveWindowTitleTextColor=255,255,255ActiveWindowTitleBackGroundColor=0,28,140,64NonActiveWindowTitleTextColor=255,255,255NonActiveWindowTitleBackGroundColor=24,33,87,64InfoUpperRightTextColor=255,0,0InfoUpperRightBackGroundColor=0,0,0,0InfoLowerLeftTextColor=255,255,255InfoLowerLeftBackGroundColor=255,0,0,128InfoLowerRightTextColor=255,255,255InfoLowerRightBackGroundColor=255,0,0,128InfoBrakesEnable=TrueInfoParkingBrakesEnable=TrueInfoPauseEnable=TrueInfoSlewEnable=TrueInfoStallEnable=TrueInfoOverspeedEnable=TrueBLOOM_EFFECTS=0SKINNED_ANIMATIONS=1TEXTURE_BANDWIDTH_MULT=40UPPER_FRAMERATE_LIMIT=40WideViewAspect=True[Main]//added for testing//FIBER_FRAME_TIME_FRACTION=0.2User Objects=Airplane, HelicopterSimObjectPaths.0=SimObjects\AirplanesSimObjectPaths.1=SimObjects\RotorcraftSimObjectPaths.2=SimObjects\GroundVehiclesSimObjectPaths.3=SimObjects\BoatsSimObjectPaths.4=SimObjects\AnimalsSimObjectPaths.5=SimObjects\MiscMaximized=0Location=439,145,1481,935,\\.\DISPLAY1HideMenuNormal=1HideMenuFullscreen=1ProcSpeed=6829PerfBucket=7[PANELS]IMAGE_QUALITY=1DEFAULT_VIEW=0QUICKTIPS=1PANEL_OPACITY=100PANEL_MASKING=1PANEL_STRETCHING=1UNITS_OF_MEASURE=0[Weather]WindshieldPrecipitationEffects=1MinGustTime=10MaxGustTime=500MinGustRampSpeed=1MaxGustRampSpeed=200MinVarTime=5MaxVarTime=50MinVarRampSpeed=10MaxVarRampSpeed=75TurbulenceScale=1.000000WeatherServerAddress=fs2k.zone.comWeatherServerPort=80WeatherGraphDataInDialog=0AdjustForMagVarInDialog=1DynamicWeather=2DownloadWindsAloft=0DisableTurbulence=0CLOUD_DRAW_DISTANCE=5DETAILED_CLOUDS=1CLOUD_COVERAGE_DENSITY=8THERMAL_VISUALS=1[DISPLAY.Device.NVIDIA GeForce GTX 560M.0]Mode=1920x1080x32Anisotropic=1AntiAlias=1[CONTROLS]Controls_Default=StandardControls_Current=StandardKBDAIL=64KBDELEV=64KBDRUD=64[TextInfo.1]Latitude=1,1Longitude=1,2Altitude=1,3Heading=1,4AirSpeed=1,5WindDirectionAndSpeed=1,6[TextInfo.2]FrameRate=1,1LockedFrameRate=1,2GForce=1,3FuelPercentage=1,4[TextInfo.3]Latitude=1,1Longitude=1,2Altitude=1,3Heading=1,4AirSpeed=1,5WindDirectionAndSpeed=1,6FrameRate=2,1LockedFrameRate=2,2GForce=2,3FuelPercentage=2,4[slewTextInfo.1]Latitude=1,1Longitude=1,2Altitude=1,3Heading=1,4AirSpeed=1,5[slewTextInfo.2]FrameRate=1,1LockedFrameRate=1,2[slewTextInfo.3]Latitude=1,1Longitude=1,2Altitude=1,3Heading=1,4AirSpeed=1,5FrameRate=2,1LockedFrameRate=2,2[DynamicHeadMovement]LonAccelOnHeadLon=-0.020000LonAccelOnHeadPitch=-0.010000RollAccelOnHeadLat=0.010000YawAccelOnHeadLat=-0.100000RollAccelOnHeadRoll=0.100000MaxHeadAngle=5.000000MaxHeadOffset=0.300000HeadMoveTimeConstant=1.000000[VirtualCopilot]VirtualCopilotActive=0[GRAPHICS]Highmemfix=1SHADER_CACHE_PRIMED=1693500672TEXTURE_MAX_LOAD=1024//default tml is 1024NUM_LIGHTS=8AIRCRAFT_SHADOWS=0AIRCRAFT_REFLECTIONS=1COCKPIT_HIGH_LOD=1LANDING_LIGHTS=1AC_SELF_SHADOW=0EFFECTS_QUALITY=1GROUND_SHADOWS=1TEXTURE_QUALITY=3IMAGE_QUALITY=0See_Self=1Text_Scroll=1SHADER_CACHE_PRIMED_10=1693500672D3D10=0[uSERINTERFACE]PageID=1ShowAllACPaintSchemes=0SelectAircraftManufacturer=AllSelectAircraftPublisher=AllSelectAircraftType=AllOpenATCOnCreate=0SHOW_MISSION_CAPTIONS=0PAUSE_ON_LOST_FOCUS=1PROMPT_ON_EXIT=1SITUATION=C:\Users\Dave\Documents\Flight Simulator X Files\orlyMap_Orientation=2DisplayFuelAsWeight=0[ATC]ShowATCText=1COMM_MSG_NONE_COLOR=FFFFFFFFCOMM_MSG_ATC_USER_COLOR=FFB6FFB6COMM_MSG_USER_ATC_COLOR=FFFFD21BCOMM_MSG_ATC_AI_COLOR=FF00FF00COMM_MSG_AI_ATC_COLOR=FFFF7840AutoOpenAirTrafficWindow=1UsePilotVoice=1PilotVoice=0[PointOfInterestSystem]CycleSetting=0[sCENERY]LENSFLARE=0DAWN_DUSK_SMOOTHING=1IMAGE_COMPLEXITY=3[TrafficManager]AirlineDensity=20GADensity=18FreewayDensity=15ShipsAndFerriesDensity=10LeisureBoatsDensity=14IFROnly=0AIRPORT_SCENERY_DENSITY=1[TERRAIN]LOD_RADIUS=4.500000MESH_COMPLEXITY=99MESH_RESOLUTION=25TEXTURE_RESOLUTION=29AUTOGEN_DENSITY=2DETAIL_TEXTURE=1WATER_EFFECTS=7[AContain]ShowLabels=1ShowUserLabel=0ShowLabelManufacturer=1ShowLabelModel=1ShowLabelTailNumber=0ShowLabelDistance=1ShowLabelAltitude=1ShowLabelAirline=0ShowLabelAirlineAndFlightNumber=0ShowLabelFlightPlan=0ShowLabelContainerId=0ShowLabelAirspeed=0ShowLabelHeading=0LabelDelay=1000LabelColor=FFFF0000[iNTERNATIONAL]ASLAT=2ASLON=0MEASURE=0[REALISM]PFactor=0.500000Torque=0.500000GyroEffect=0.500000CrashTolerance=0.500000General=0.500000UnlimitedFuel=FalseTrueAirspeed=FalseAutoCoord=FalseRealMixture=FalseStressDamage=TrueGEffect=TrueManualLights=FalseGyroDrift=FalseCrashWithDyn=TrueCrashDetection=TrueAutoTrim=FalseAllowEngineDamage=False[sIM]SYSCLOCK=1[sTARTUP]DEMO=0SHOW_OPENING_SCREEN=1STARTUP_DEMO=LoadWindow=1[FACILITIES]COUNTRY=STATE=CITY=GTL_BUTTON=1291[Misc]Com_Rate=7[AccelerationPack]ControlsFirstRun=0HomePageFirstRun=0[DISPLAY.Device.NVIDIA GeForce GTX 560M.0.0]Mode=1920x1080x32Anisotropic=1[JOBSCHEDULER]AffinityMask=12[Trusted]C:\FSX\GAUGES\Bendix_King_Radio.DLL.eotehuahrizwlceiaciwhnlweiwauheuariehene=2C:\FSX\GAUGES\Magnetic_Compass.DLL.hiiwceiotkbzutahorhctqchwubazenrboozoezl=2C:\FSX\GAUGES\Cessna.DLL.hqeciqnqwwztbbohcuonkliktrtauraiweheckoe=2C:\FSX\GAUGES\Cessna172.DLL.eoonobinaneeaorcahakitqlobaabaqzrhutukkz=2C:\FSX\GAUGES\Cessna182s.DLL.onbellqzotlkaktazqcnctkokwotrkrkiiaoquui=2C:\FSX\GAUGES\CessnaWAlpha.DLL.krqecreontuatlewobetwrckkwecluihuuqhzbia=2C:\FSX\GAUGES\Bell_206B.DLL.zrweneeziezthzkhlnwtozohetabrrituezbowlq=2C:\FSX\GAUGES\KingAir.DLL.zizakobwhoicbncztbbwaqiniuqzbbcbahcehkqu=2C:\FSX\GAUGES\KingAir_Radio.DLL.blwtnrbhtaobonzezbanrbwhttnrcalktctrqezi=2C:\FSX\GAUGES\BoeingGeneric.DLL.altncuqtrqhubeicqbhckouqehielbubzwhanhhw=2C:\FSX\GAUGES\fa-18.DLL.zzrunbrrnroktrqlqebzczrztklllaoqwowiihke=2[FlightPlanMap]LineWidth=2SHOW_AIRPORTS=1SHOW_VORS=1SHOW_NDBS=1SHOW_APPROACHES=1SHOW_INTERSECTIONS=1SHOW_VICTOR=0SHOW_JET=0SHOW_AIRSPACE=1SHOW_FLIGHTPLAN=1SHOW_WEATHERSTATIONS=1SHOW_WEATHERSYSTEMS=1SHOW_DATATAGS=1SHOW_TERRAIN=1show_waypoints=1show_airways=1show_markers=1show_volume_boundaries=1show_ac_twr=1[bufferPools]//PoolSize=5000000UsePools=1RejectThreshold=98304PoolSize=2097152[MULTIPLAYER]condAccoutPassword=0

thanks. that what I thought, but I'm still getting jaggies if i uncheck AA in FSX. does FSX require that DX9 be used in order for the card to control the AA? also, do we still need to set filtering, ie anisotropic, for good appearance. ie, is that completely independent of the card settings? i just switched to dx9 but still have the jaggies if AA isn't checked inside FSX, and still see the high rises in Paris flicker--black/normal, just like my complaint when I run dx10. i looked at your attachment and mine matches, yet jaggies still present if AA not checked. also, in either dx10 or dx9, I get momentary bright flashes. pretty often I seen the river turn white for a split second, or just get a random white flash randomly. it seems to be near the beginning of a flight, but not always. i see it either straight out the cockpit window during takeoff (but not every flight), or out the side window, down much of the length of the river.

service pack 3?? are u saying that MS is going to be issuing another SP? first of heard of it. i tried the limiter last night but afaik it only works with DX9.

I've got FSX running fairly smoothly on my i7 2720 with nvidia 560m. However, a couple of things still puzzle me. 1. landmark buildings (ie, not autogen) flash black quite often, sorta like the flashing going on on the runway where taxiways intersect them. I am using DX10. Not sure if these issues are related. I don't spend a lot of time on the runway, so I can live with the flashing there if it's not going to permeate the whole flying experience. 2. I see jaggies if I only enable AA in nvidiaInspector and uncheck AA inside FSX. Aren't we supposed to uncheck it inside FSX in order to keep the FR's up? Seems that I can only get FSX looking good (eliminating jaggies) by checking AA.

My new Sager runs FSX really well! :) (it has an Nvidia GTX 560m video card which I OC a bit)

I used to play FS2004 years ago and overclocking my old nvidia card using a utility that automatically determined the max oc parameters. Now I've got this new laptop and installed a oc utility called nvidiainspector. it's manual only and I've no idea how much I should push the settings. anyone know if there's another utility that properly manages that card automatically, to the best settings? someone on a Sager forum said NOT to us MSIafterburner with this particular card. no idea if they are right.

I am no expert at FSX, but have to say that for me, running FSX on an i7 (2720QM) with InfinityMask set to 12, rather than 14 was key to stopping all microstutters.

Today I'll be receiving a Sager 8130 laptop (same processor and memory as the DV6 I had, but comes with an Nvidia GTX 560m) from XoticPC. Wish me luck that it runs FSX even better than the first DV6 that I got from HP. FSX will be the first thing I load up on the Sager. It cost a lot more than the HP, but if it works well, I'll be a happy camper. Fingers crossed... oh, I went through my posting history here and copy/pasted all of the helpful hints you guys gave me a couple months ago, so I can apply them to the new installation. Just want to say thanks again to everyone that helped me!

No, HP has had no fix to date. Several forums discussing the issue are filling up more each day with complaints that the Radeon GPU doesn't kick in. This all began a few weeks ago, as people such as myself began taking delivery of the most recent version of the DV6/DV7 laptops (I heard it's also an issue on the Envy).