June 7, 201411 yr Hi, since I use the NGX I've a problem with this plane. After one minute flying this aircraft the FSX freeze 5 - 10 seconds. After that the FSX runs another minute and then the same.... THe Problem appears only with the NGX. Do you have a solution ?
June 7, 201411 yr Hi, since I use the NGX I've a problem with this plane. After one minute flying this aircraft the FSX freeze 5 - 10 seconds. After that the FSX runs another minute and then the same.... THe Problem appears only with the NGX. Do you have a solution ? PC Specs? FSX.CFG? NI settings? Ric Elmore
June 8, 201411 yr Author Hi, my PC Specs: AMD FX 8320 3,5 GHz 8 GB DDR3 Radeon HD 6850 the FSX.cfg [AccelerationPack]ControlsFirstRun=0HomePageFirstRun=0[AContain]LabelColor=FFFF0000LabelDelay=1000ShowLabelAirline=0ShowLabelAirlineAndFlightNumber=0ShowLabelAirspeed=0ShowLabelAltitude=1ShowLabelContainerId=0ShowLabelDistance=1ShowLabelFlightPlan=0ShowLabelHeading=0ShowLabelManufacturer=1ShowLabelModel=1ShowLabels=1ShowLabelTailNumber=0ShowUserLabel=0[ATC]AutoOpenAirTrafficWindow=1COMM_MSG_AI_ATC_COLOR=FFFF7840COMM_MSG_ATC_AI_COLOR=FF00FF00COMM_MSG_ATC_USER_COLOR=FFB6FFB6COMM_MSG_NONE_COLOR=FFFFFFFFCOMM_MSG_USER_ATC_COLOR=FFFFD21BPilotVoice=0ShowATCText=1UsePilotVoice=1[CONTROLS]Controls_Current=StandardControls_Default=StandardKBDAIL=64KBDELEV=64KBDRUD=64JOYSTICKS=1[Display]ActiveWindowTitleBackGroundColor=0,28,140,64ActiveWindowTitleTextColor=255,255,255BLOOM_EFFECTS=0ChangeTime=4.000000InfoBrakesEnable=TrueInfoLowerLeftBackGroundColor=255,0,0,128InfoLowerLeftTextColor=255,255,255InfoLowerRightBackGroundColor=255,0,0,128InfoLowerRightTextColor=255,255,255InfoOverspeedEnable=TrueInfoParkingBrakesEnable=TrueInfoPauseEnable=TrueInfoSlewEnable=TrueInfoStallEnable=TrueInfoUpperRightBackGroundColor=0,0,0,0InfoUpperRightTextColor=255,0,0NonActiveWindowTitleBackGroundColor=24,33,87,64NonActiveWindowTitleTextColor=255,255,255SKINNED_ANIMATIONS=1TEXTURE_BANDWIDTH_MULT=40TransitionTime=4.000000UPPER_FRAMERATE_LIMIT=31WideViewAspect=False[DISPLAY.Device.AMD Radeon HD 6800 Series.0]Mode=1920x1080x32AntiAlias=1[DynamicHeadMovement]HeadMoveTimeConstant=1.000000LonAccelOnHeadLon=-0.020000LonAccelOnHeadPitch=-0.010000MaxHeadAngle=5.000000MaxHeadOffset=0.300000RollAccelOnHeadLat=0.010000RollAccelOnHeadRoll=0.100000YawAccelOnHeadLat=-0.100000[FACILITIES]CITY=COUNTRY=GTL_BUTTON=1392STATE=[GRAPHICS]AC_SELF_SHADOW=1AIRCRAFT_REFLECTIONS=1AIRCRAFT_SHADOWS=1COCKPIT_HIGH_LOD=1EFFECTS_QUALITY=2GROUND_SHADOWS=0HIGHMEMFIX=1IMAGE_QUALITY=0LANDING_LIGHTS=1NUM_LIGHTS=8See_Self=1SHADER_CACHE_PRIMED=1693500672SHADER_CACHE_PRIMED_10=1693500672TEXTURE_MAX_LOAD=1024TEXTURE_QUALITY=3Text_Scroll=1D3D10=0[iNTERNATIONAL]ASLAT=2ASLON=0MEASURE=2[Main]FIBER_FRAME_TIME_FRACTION=0.33HideMenuFullscreen=1HideMenuNormal=0PerfBucket=7ProcSpeed=6486SimObjectPaths.0=SimObjects\AirplanesSimObjectPaths.1=SimObjects\RotorcraftSimObjectPaths.2=SimObjects\GroundVehiclesSimObjectPaths.3=SimObjects\BoatsSimObjectPaths.4=SimObjects\AnimalsSimObjectPaths.5=SimObjects\MiscSimObjectPaths.6=SimObjects\IVAO_MTLTEXTURE_BANDWIDTH_MULT=90User Objects=Airplane, HelicopterLocation=488,0,1906,1040,\\.\DISPLAY1Maximized=0[Misc]Com_Rate=7[PANELS]IMAGE_QUALITY=1PANEL_MASKING=1PANEL_OPACITY=100PANEL_STRETCHING=1QUICKTIPS=1UNITS_OF_MEASURE=1DEFAULT_VIEW=0[PointOfInterestSystem]CycleSetting=0[REALISM]AllowEngineDamage=FalseAutoCoord=FalseAutoTrim=FalseCrashDetection=FalseCrashTolerance=0.000000CrashWithDyn=FalseGEffect=FalseGeneral=0.000000GyroDrift=FalseGyroEffect=0.000000ManualLights=FalsePFactor=0.000000RealMixture=FalseStressDamage=FalseTorque=0.000000TrueAirspeed=FalseUnlimitedFuel=True[sCENERY]DAWN_DUSK_SMOOTHING=1IMAGE_COMPLEXITY=2LENSFLARE=1[sIM]SYSCLOCK=1[slewTextInfo.1]AirSpeed=1,5Altitude=1,3Heading=1,4Latitude=1,1Longitude=1,2[slewTextInfo.2]FrameRate=1,1LockedFrameRate=1,2[slewTextInfo.3]AirSpeed=1,5Altitude=1,3FrameRate=2,1Heading=1,4Latitude=1,1LockedFrameRate=2,2Longitude=1,2[sOUND]AmbientUI=0AmbientUIMusicVolume=-6.000000PrimaryDevice={DEF00000-9C6D-47ED-AAF1-4DDA8F2B5C03}SOUND=1SOUND_LOD=0SOUND_QUALITY=2UISound=1VoiceDevice={DEF00002-9C6D-47ED-AAF1-4DDA8F2B5C03}[sTARTUP]DEMO=0LoadWindow=1SHOW_OPENING_SCREEN=1STARTUP_DEMO=[TERRAIN]AUTOGEN_DENSITY=2DETAIL_TEXTURE=1LOD_RADIUS=3.500000MESH_COMPLEXITY=70MESH_RESOLUTION=19TEXTURE_RESOLUTION=24WATER_EFFECTS=3[TextInfo.1]AirSpeed=1,5Altitude=1,3Heading=1,4Latitude=1,1Longitude=1,2WindDirectionAndSpeed=1,6[TextInfo.2]FrameRate=1,1FuelPercentage=1,4GForce=1,3LockedFrameRate=1,2[TextInfo.3]AirSpeed=1,5Altitude=1,3FrameRate=2,1FuelPercentage=2,4GForce=2,3Heading=1,4Latitude=1,1LockedFrameRate=2,2Longitude=1,2WindDirectionAndSpeed=1,6[TrafficManager]AirlineDensity=0AIRPORT_SCENERY_DENSITY=1FreewayDensity=0GADensity=0IFROnly=0LeisureBoatsDensity=15ShipsAndFerriesDensity=15[uSERINTERFACE]Map_Orientation=2OpenATCOnCreate=0PageID=1PAUSE_ON_LOST_FOCUS=0PROMPT_ON_EXIT=1SHOW_MISSION_CAPTIONS=0SITUATION=FLIGHTS\OTHER\FLTSIMShowAllACPaintSchemes=1SelectAircraftManufacturer=AirbusSelectAircraftPublisher=AlleSelectAircraftType=AlleDisplayFuelAsWeight=1[VirtualCopilot]VirtualCopilotActive=1[Weather]AdjustForMagVarInDialog=1CLOUD_COVERAGE_DENSITY=6CLOUD_DRAW_DISTANCE=3DETAILED_CLOUDS=1DisableTurbulence=0DownloadWindsAloft=0DynamicWeather=0MaxGustRampSpeed=200MaxGustTime=500MaxVarRampSpeed=75MaxVarTime=50MinGustRampSpeed=1MinGustTime=10MinVarRampSpeed=10MinVarTime=5THERMAL_VISUALS=0TurbulenceScale=1.000000WeatherGraphDataInDialog=0WeatherServerAddress=fs2k.zone.comWeatherServerPort=80WindshieldPrecipitationEffects=1[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[MULTIPLAYER]condAccoutPassword=0 What do you mean with NI settings?
June 8, 201411 yr Hi indeopax, first off, as a policy, always put your name whenever you write a post. I had a look at your cfg. file, one thing I would do, is disable AntiAlias, as you have it if I am correct. Try Trilinear instead, and do a couple of flights. If that does not help, I suggest you read the following: http://forum.avsim.net/topic/428129-avsim-fsxp3dfs9-crash-to-desktop-guide/ and then post your results in the Crash to Desktop section of AVSIM. Enrico NI= Nvidia Inspector settings Never mind the Nvidia Inspector, he's got a Radeon GPU, Enrico
June 8, 201411 yr Author Hi Enrico, thanks for the tip, but I have the same effect with trilinear. The FSX does not crash to the desktop, i've only the problem with the short freezes. Any other tips ? Nico
June 8, 201411 yr Hi Nico, just by looking at the cfg. file, there is no way of knowing what process might be hanging when FSX freezes. The link I sent you also deals with freezes, same for the Crash to Desktop forum. Just look at it, there is an application that you can run when you are ready to takeoff, and that reads every process that is running, and if something hangs, and you have a freeze, it will tell you what it is. You'll find the instructions in that section, Enrico
June 8, 201411 yr Never mind the Nvidia Inspector, he's got a Radeon GPU, But we did not know it at the time, did we? So I was responding to the OP's ask. Rick Almeida
June 8, 201411 yr Whenever you get a freeze or a long pause in FSX, you should run Process Monitor and set it up to only log FSX. Here's how I suggest doing it:Setting up the Process Monitor for FSX – Another investigative tool used to pin down a situation where FSX freezes, crashes, or stutters/pauses during a flight is to run a utility called Process Monitor - http://technet.microsoft.com/en-us/sysinternals/bb896645. During your flight, this utility monitors activity such as calling textures, AI aircraft schedules, ATC, weather updates, and scenery loading. When FSX/P3D stutters or FPS drop dramatically you simply write down the time it occurred. This is important as thousands of entries are made every minute, every second. Continue doing this throughout the flight. Of course, if it freezes, you will know what was going on before the sim froze. This utility will not show you a definitive cause of your issue but it will show you what add-ons were being loaded about when you received the stutter, the long pause(s), and the freeze and you can further investigate by disabling that scenery, that aircraft, or whatever might have caused the event. One member used this utility to determine that My Traffic X, version 5.4c was the cause of a BEX/StackHash/NTDLL.dll crash he was getting. It was easy to disable My Traffic X in the Scenery Library and find that FSX no longer crashed. AVSIM recommends you do not run a flight any longer than 60 minutes as the Process Monitor log becomes quite large. For a 60 minutes flight, expect the file to be at least as large as 8GB’s or tens of millions of captured events. Make sure you delete the log or move it to another drive after you have finished your testing to free up HDD space. Another recommended tip is to make sure you use system time to mark the time of each event and do not use an external clock unless they are sync’d. Going through one minute of a glitch is a massive amount of data needed to be reviewed (it goes fast as thousands of entries just show a scenery being loaded). To run this utility properly, you need to capture only FSX events. It would be nearly impossible to find a possible glitch if Windows events or other system activities were being logged too. AVSIM recommends opening of the Process Monitor when you are on the active runway and preparing to takeoff to save space on your HDD: Open Process Monitor. Click on the Filter tab and then Filter…. Display entries matching these conditions: Where it says Architecture, click on that and select “Process Name”Go next to the blank box and click on that and select FSX.exe and make sure “Include” is shown (FSX must be running when you do this!!). Once completed, click on Add and then click OK at the bottom of the form and Go Fly.You can use the utility while in Full Screen mode or Windowed Mode. In Windowed Mode you can monitor what is happening instantly but it is best to run Process Monitor in Full Screen (unless you are seeing freezes in Windowed Mode).When the flight is finished, immediately go to the Process Monitor application and hit Ctrl+E on your keyboard to capture the events (event logging will continue until you do this). Shutdown FSX and begin your investigating! Hope this helps. Best regards, Jim Young | AVSIM Online! - Simming's Premier Resource! Member, AVSIM Board of Directors - Serving AVSIM since 2001 Submit News to AVSIMImportant other links: Basic FSX Configuration Guide | AVSIM CTD Guide | AVSIM Prepar3D Guide | Help with AVSIM Site | Signature Rules | Screen Shot Rule | AVSIM Terms of Service (ToS) I7 8086K 5.0GHz | GTX 1080 TI OC Edition | Dell 34" and 24" Monitors | ASUS Maximus X Hero MB Z370 | Samsung M.2 NVMe 500GB and 1TB | Samsung SSD 500GB x2 | Toshiba HDD 1TB | WDC HDD 1TB | Corsair H115i Pro | 16GB DDR4 3600C17 | Windows 10
June 8, 201411 yr Thanks for that, Jim, as I occasionally get long freezes but that happens when I have a lot of apps running in the background such a Microsoft Office, Firefox, etc and when that happens I just go to Task Manager and bring the Not responding FSX to the front. In a fashion after repeated stabs at it, it eventually re-starts, But your detailed way of dealing with it is much better. I do have ProcMon already. Going to follow this. Rick Almeida
June 8, 201411 yr But we did not know it at the time, did we? So I was responding to the OP's ask. Sure we did, just read the cfg. file.... Enrico
June 8, 201411 yr Sure we did, just read the cfg. file.... Enrico Fact is, you were not the one asking what NI was, irrespective of what was in the .cfg file or not, and the response was to HIS question. Rick Almeida
June 9, 201411 yr You could always try looking at Windows's event monitor. I used to have the same problem. Game would hang for around a minute, then pick right back again as if nothing happened. The HDD led would be constantly lit during this. I checked the event logger and it showed me an atapi error at the same time the freezes were occurring. This I traced to the HDD controller on my motherboard. I changed the SATA cable to another connector and I never had that problem again. Cristi Neagu
June 9, 201411 yr Author Hey guys, the autosave at FSUIPC was the problem. But I'm confused . The Airbus X or other Add On doesn't have this problem. Thank's for help.
Create an account or sign in to comment