I have followed all instructions from AVSIM and still getting CTD on long haul flights

[anthropos 0]

Hi folks, 

 

It's my first time here in the forum and I apologize if I'm not in the correct section.

 

I'm running P3D v3.4.14

 

I'm not able to perform any long haul flight with the PMDG 777.  

About 10 hours flying ( or less ) P3D simply shuts down.

 

I don't have any information about the crash in the APPCrash view neither in eventlog

 

Yesterday night before starting the simulator, I have followed all AVSIM CTD guide instructions:

 

- Deleted dll.XML

- Deleted exe.XML

- Deleted scenery.CFG

- Deleted all files inside Shaders folder

- Used Scenery config editor tool to disable all my addon scenery ( I kept only T2G Hong Kong and Aerosoft Rome )

- No overclock

- Reinstalled the latest satandalone Add-on Manager from Fsdreamteam

- I checked for any corrupt/missing files with SFC\scannow - everything OK

- All my drivers are updated

- I disabled startup programs

- Run the DirectX Diagnostic tool - everything OK

 

After that, I've reiniciated the PC and loaded P3D and took off with no problems.

I was running P3D, ASN and VRinside and AIMonitor  

 

Today's morning (19 December )  the aircraft was still on its route to LIRF when suddenly P3D shuted down (13:10 )

 

I went to AppCrashView and no inforation at all about the prepar3d

 

Todays is December 19 and the last entry I have in APPCrash view is form yesterday ( 18th )

 

Process File Event Name Event Time User Name Exception Code Exception Offset Fault Module Name Fault Module Version Process Path Report File Size Report File Path DpInstX64.exe No se pudo instalar el software de controlador. 18/12/2016 23:01:14 Bruno         C:\Program Files (x86)\IObit\Driver Booster\4.1.0\DrvInstall\DpInstX64.exe 2.594 C:\Users\Bruno\AppData\Local\Microsoft\Windows\WER\ReportArchive\NonCritical_x64_3798c4c3bd87e35cddb2a29cac3a3fb623767e1_1186c9de\Report.wer RemoteFlightServer.exe Dejó de funcionar 18/12/2016 12:09:59 Bruno         C:\Users\Bruno\Documents\RemoteFlightServer\RemoteFlightServer\RemoteFlightServer.exe 20.354 C:\Users\Bruno\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_RemoteFlightServ_dfaa3f9a4f275c52fd5ed95ddf874b9f4845ce_cab_15e43b88\Report.wer xRaidSetup.exe Error de compatibilidad de programas 17/12/2016 23:18:53 Bruno         C:\Windows\SysWOW64\xRaidSetup.exe 2.482 C:\Users\Bruno\AppData\Local\Microsoft\Windows\WER\ReportArchive\NonCritical_xRaidSetup.exe_6da15464a11913e0bdcd9f36697ab81e3ba1aa_1210abe8\Report.wer Prepar3D.exe Dejó de funcionar 17/12/2016 19:15:15 Bruno         C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe 41.334 C:\Users\Bruno\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_363282b13218c3e71586c25f46d1a9180422c2_10b36fcb\Report.wer Prepar3D.exe Dejó de funcionar 17/12/2016 8:38:32 Bruno         C:\Program Files (x86)\Lockheed Martin\Prepar3D v3\Prepar3D.exe 41.700 C:\Users\Bruno\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_Prepar3D.exe_88ff8629df2d9ea35bf35ff54f3841d98c704c_00702810\Report.wer

 

  On Windows eventlog, no information as well:

 

Información 19/12/2016 13:03:01  VSS  8224 Ninguno  -    The only event around 13:00

Información 19/12/2016 12:03:00 VSS 8224 Ninguno

Información 19/12/2016 11:03:00 VSS 8224 Ninguno

Información 19/12/2016 10:03:00 VSS 8224 Ninguno

Información 19/12/2016 9:03:00 VSS 8224 Ninguno

Información 19/12/2016 8:03:00 VSS 8224 Ninguno

Información 19/12/2016 7:03:00 VSS 8224 Ninguno

Información 19/12/2016 6:03:00 VSS 8224 Ninguno

Información 19/12/2016 5:03:00 VSS 8224 Ninguno

Información 19/12/2016 4:03:01 VSS 8224 Ninguno

Información 19/12/2016 3:51:44 Security-SPP 903 Ninguno

Información 19/12/2016 3:46:44 Security-SPP 902 Ninguno

Información 19/12/2016 3:46:44 Security-SPP 1003 Ninguno

Información 19/12/2016 3:46:44 Security-SPP 1066 Ninguno

Información 19/12/2016 3:46:43 Security-SPP 900 Ninguno

 

I have done almost everything I read on all internet forums to fix the problem but I'm right now completly lost :(

 

These are my specs:

 

- Inter core i7 CPU 950 @ 3.07 GHz  3.06 GHz

- RAM : 6.00 GB

- Windows 7 64 bits

- Nvidia GeForce GTX 960

 

I'm going to perform the same flight today with no AI traffic as my last try

 

Do you have any clue that could help me to find out where the problem is and how to fix it?

 

Any help is much appreciated

 

Best regards

 

Bruno

 

 

 

[simmerhead 885]

Do you have only 6 GB of RAM on your computer?

[winged532 7]

I am certainly not an expert, but if you can get that many hours of flying before it crashes you are doing great.  Some time ago I was getting random crashes without any apparent reason.  It turned out that I had a bad stick of memory.  Memory is quite cheap.  You might consider adding some new memory sticks.  That can be a very insideous problem in all our computers.  Not related to the programs at all.

[Woozie 732]

Ouch, those CTD/freezes towards the end of a long haul are certainly the most frustrating ones. What makes it even worse is the fact that such CTD's usually cannot be replicated by simply loading an mid-flight save as they only occur after a certain number of hours, and that makes troubleshooting even more tedious and frustrating than it already is. 

 

As you stated that P3D simply shuts down i assume that this is not a VAS/OOM issue, as this would usually result in an 'out of memory' error message. However, if the crashes always happen just about 20-30 minutes before landing it could be a VAS related issue as this is when the sim starts to load the destination scenery files into memory. Best is to keep an eye on your VAS usage during the flight. Easiest way to do this is to download 'procexp' from Microsoft which is kind of a task manager on steriods. Once open just add 'Virtual Size' column to your task view and it will show how much VAS has been used up by prepar3d.exe already. If its getting close to 4GB you are at the upper VAS limit. 

 

You didnt mention prepar3d.cfg in your list, i suggest to delete/rename this file as well to get it recreated during next launch. After the file has been recreated, make sure you only set the most basic options, no fancy graphics stuff for now. Next step would be to temporarily strip P3D from all addons by disabling them in your exe.xml/dll.xml. Be aware that you might have two of each xmls in different locations, make sure you disable your addons in both locations as P3D combines those xml files during startup. As far as i know, there are also entries for the PMDG, i'd leave them enabled for now, otherwise you will have to do the flight with a stock plane. 

 

Check these two folders for exe/dll xmls:

 

%PROGRAMDATA%\Lockheed Martin\Prepar3D v3

%APPDATA%\Lockheed Martin\Prepar3D v3

 

Also make sure you dont have any other addons running that do not have a xml entry but connect to the sim via simconnect or other interfaces. 

 

Now try to redo the same flight with no addons and only your departure and destination sceneries enabled. If it was successful your were either lucky this time or the CTD's are caused by a certain addon. Next step would be to enable one addon a time and see if you can still complete your flight successfully. 

 

BTW, your appcrash log shows remoteflight server, are you able to fly without this one or do you have a home cockpit setup? If not please disable this one as well for testing. 

 

I know from my own experience that these CTD's can take several weeks to troubleshoot and resolve. I had a similar issue (CTD after 6+ hours) and did EDDF-KMIA as a test flight about 25 times during troubleshooting, cant fly this route anymore now

 

Good luck

 

Regards

Lars

[Jim Young 2,356]

 

 

I have followed all AVSIM CTD guide instructions:

- Deleted dll.XML  Guide does not tell you to delete the dll.xml.  Just move to a temporary folder or rename it so that it will not load

- Deleted exe.XML  Guide does not tell you to delete the exe.xml.  Just move to a temporary folder or rename it so that it will not load

- Deleted scenery.CFG    When you delete the scenery.cfg, it is rebuilt with the default with no add-ons then you state below you used the scenery config editor tool to disable all of your add-on scenery.  This does not compute....

- Deleted all files inside Shaders folder

- Used Scenery config editor tool to disable all my addon scenery ( I kept only T2G Hong Kong and Aerosoft Rome )

 

See my comments in RED above in your quote.  If you deleted the dll.xml and exe.xml (and the AVSIM Guide did not tell you to do so), you now have no modules loading for your add-ons.  The dll.xml and exe.xml is needed to load modules developers created to make their products run properly.  If you downloaded and reinstalled the FSDT Standalone Addon Manager, that program will reinstall the proper entries in the dll.xml and exe.xml for FSDT products.  Sometimes developers that use the dll.xml to load their programs will create a backup dll.xml and exe.xml stating something like "dll.xml before AddonManager" or "dll-xml.ASbackup".  This could have your dll.xml before you deleted it but most likely you will have to reinstall all of those programs that used the dll.xml to load modules. 

 

Of course you can also try to do a restore prior to the date you deleted the dll.xml and exe.xml and perhaps a restore will bring it back where you can just move it or rename it so that it will not load when you startup P3D.

 

As woozie stated above, you did not indicate you deleted or renamed your P3D.cfg.  Deleting or renaming the P3D.cfg and letting it rebuild when you restart P3D fixes almost all crashes as users usually throw in a bad tweak or modified a parameter wrong.  When you settings are set too high or, if you have a bad tweak, it will take up a massive amount of resources and your computer will eventually crash.

 

Your "crash reports" are not really from AppCrashView (see page 7, AVSIM CTD Guide for an image of exactly what to copy and what the AppCrashView looks like).  Those are Event Viewer Reports and they are telling you there was a AppCrashReport in WindowsErrorReporting (.wer) which can be view when you download and run AppCrashView.  According to the AVSIM CTD Guide you must only open up Administrative Events in the Event Viewer (see page 8 of the AVSIM CTD Guide).  The guide also shows you that when you double-click an Event, a new window will open and in the bottom left corner it states "Copy".  You click on Copy and then come to your post and right click inside your post and click on Paste.  The Event is then shown.  (See the image on Page 9 of the AVSIM CTD Guide). You should only post events related to P3D or a P3D addon. 

 

 

 

I'm not able to perform any long haul flight with the PMDG 777.  About 10 hours flying ( or less ) P3D simply shuts down.

 

This is a common crash.  I actually do not know if your computer's CPU is staying cool enough during a long and intense flight like 10 hours.  There are a massive amount of resources placed on your CPU during those 10 hours!!  Your computer may not be capable of running that long.  Why not stay with flight 3-4 hours or less?  There are a lot of flightplans out there for that.  Pages 16/17 of the AVSIM CTD Guide provides detailed instructions on monitoring your Virtual Address Space (VAS).  When you run out of that, P3D will crash and that's caused by a combination of things (i.e., running P3D for 10 hours with high P3D and display driver settings, bad tweaks, lots of eye-candy scenery and aircraft that eat up resources fast).  If you install the FSUIPC.dll, you can monitor VAS and it will show you how much you have left after 10 hours of flying.  After the crash, you can open up the fsuipc.txt (a log file) and it will tell you how much you had at the beginning of the flight and how much when you ended the flight.

 

Many members have been able to fly for 10 or more hours of flight.  I just know in my experience that if I am flying the PMDG 777, with real world weather (AS16), from/to FSDT airports, over Orbx or Photoscenery, my VAS is dramatically low near the end of a 2.5 hour flight and it is nearly a slide show when landing.  However, with the latest version, they seem to handle VAS better and I have around 1GB of VAS remaining but the VAS jumps from 1GB down to 300MB's and then back up to 1GB during the approach phase (which is the most resource intense throughout the whole flight).

 

Hopefully you will get it figured out and back up and flying but I can pretty much assure you that it is not the fault of P3D that is causing your crashes, but how you have it configured and the length of the flight.

 

Best regards,

Jim

[anthropos 0]

Hi Jim, 

 

Thank you for your feedback. Really appreciated it.

 

I did not deleted dll.xml, exe.xml nor P3D.cfg. I just moved them to a temporary folder. Sorry for my bad explanation on my previous contact ;( 

 

I did rename P3D.cfg as well.

 

 

Yesterday I have increased my RAM from 6 to 12 GB, and did exactly the same flight from HKG to FCO, only having ASN connected and AI traffic slide around 60%. As I removed dll.XML to a temp folder, FSUIPC, SODE; AddonManager and FSpassengers were not on p3d addon tab.

 

This morning after 12:17 hrs flying the aircraft (PMDG 777 ) landed without any issue at FCO airport with a very good fps.

 

I'm now reistaling FSUIPC, SODE and AddonManager and will (try) to perform another long haul flight from VHHH to OTHH.

 

If i get a CTD, that means the problem should be in FSUIPC, SODE or AddonManager. Am I on the right way?

 

Here i'm sending you my P3D.cfg

 

 

[GRAPHICS]

SCREEN_CAPTURE_MAX_JOBS=10

VIDEO_CAPTURE_WIDTH=480

VIDEO_CAPTURE_HEIGHT=360

VIDEO_CAPTURE_FPS=30

VIDEO_CAPTURE_BIT_RATE=800000

VIDEO_CAPTURE_IS_THREADED=True

VIDEO_CAPTURE_INFO_SEND_RATE=20

VIDEO_CAPTURE_MAX_FRAME_SIZE=500000

VIDEO_CAPTURE_TTL=255

HDR_BRIGHTNESS=1.100000

HDR_BLOOM_THRESHOLD=3.000000

HDR_BLOOM_MAGNITUDE=1.000000

HDR_BLOOM_BLUR_SIGMA=0.800000

TONEMAP_DAY_EXPOSURE_KEY=0.280000

TONEMAP_NIGHT_EXPOSURE_KEY=0.130000

HDR_SATURATION=0.800000

ViewGroup_Number=-1

MIPMAP_VC_PANELS=1

TESSELLATION=1

TEXTURE_MAX_LOAD=1024

NUM_LIGHTS=4

COCKPIT_HIGH_LOD=1

AIRCRAFT_REFLECTIONS=1

LANDING_LIGHTS=1

DAWN_DUSK_SMOOTHING=1

LENSFLARE=0

HDR=0

DYNAMIC_REFLECTIONS=0

SHADOW_QUALITY=2

TERRAIN_SHADOW_CAST_DISTANCE=0

CLOUD_SHADOW_CAST_DISTANCE=0

OBJECT_SHADOW_CAST_DISTANCE=2

CONTENT_NO_SHADOW=0

INTERIOR_SHADOWS_CAST=0

EXTERIOR_SHADOWS_CAST=0

SIMOBJECT_SHADOWS_CAST=0

TERRAIN_SHADOWS_CAST=0

VEGETATION_SHADOWS_CAST=0

BUILDING_SHADOWS_CAST=0

CLOUD_SHADOWS_CAST=0

INTERIOR_SHADOWS_RECEIVE=0

EXTERIOR_SHADOWS_RECEIVE=0

SIMOBJECT_SHADOWS_RECEIVE=0

TERRAIN_SHADOWS_RECEIVE=0

VEGETATION_SHADOWS_RECEIVE=0

BUILDING_SHADOWS_RECEIVE=0

SHADOW_NUM_CASCADES_LOW=4

SHADOW_NUM_CASCADES_MID=5

SHADOW_NUM_CASCADES_HIGH=7

SHADOW_NUM_CASCADES_ULTRA=12

GROUND_SHADOW_TEXTURE_SIZE=2048

CLOUD_SHADOW_TEXTURE_SIZE=512

SHADOW_LOG_PARTITION_LOW=0.850000

SHADOW_LOG_PARTITION_MID=0.850000

SHADOW_LOG_PARTITION_HIGH=0.850000

SHADOW_LOG_PARTITION_ULTRA=0.850000

EFFECTS_QUALITY=0

EFFECTS_DISTANCE=0

TEXTURE_QUALITY=3

IMAGE_QUALITY=0

See_Self=1

Text_Scroll=1

[WEATHER]

CLOUD_FACING_MODE=0

WindshieldPrecipitationEffects=1

MinGustTime=10

MaxGustTime=500

MinGustRampSpeed=1

MaxGustRampSpeed=200

MinVarTime=5

MaxVarTime=50

MinVarRampSpeed=10

MaxVarRampSpeed=75

TurbulenceScale=1.000000

WeatherGraphDataInDialog=0

AdjustForMagVarInDialog=1

DynamicWeather=0

DownloadWindsAloft=0

DisableTurbulence=0

CLOUD_DRAW_DISTANCE=6

DETAILED_CLOUDS=1

OPTIMIZE_DENSE_CLOUDS=0

CLOUD_COVERAGE_DENSITY=7

THERMAL_VISUALS=0

VolumetricFog=0

[DISPLAY]

ChangeTime=4.000000

TransitionTime=4.000000

TEXTURE_FILTERING=16

MSAA=8

SSAA=0

VSYNC=0

FXAA=0

TRIPLE_BUFFER=0

ActiveWindowTitleTextColor=255,255,255

ActiveWindowTitleBackGroundColor=0,28,140,64

NonActiveWindowTitleTextColor=255,255,255

NonActiveWindowTitleBackGroundColor=24,33,87,64

InfoUpperLeftTextColorUser=255,0,0

InfoUpperLeftTextColorNonUser=255,127,0

InfoUpperLeftBackGroundColor=0,0,0,0

InfoUpperRightTextColor=255,0,0

InfoUpperRightBackGroundColor=0,0,0,0

InfoLowerLeftTextColor=255,255,255

InfoLowerLeftBackGroundColor=255,0,0,128

InfoLowerRightTextColor=255,255,255

InfoLowerRightBackGroundColor=255,0,0,128

InfoBrakesEnable=True

InfoParkingBrakesEnable=True

InfoPauseEnable=True

InfoSlewEnable=True

InfoStallEnable=True

InfoOverspeedEnable=True

InfoWeaponSystemEnable=True

InfoCountermeasureEnable=True

InfoUpperRightTextEnable=True

SKINNED_ANIMATIONS=1

TEXTURE_BANDWIDTH_MULT=30

UPPER_FRAMERATE_LIMIT=20

WideViewAspect=False

FullScreenBackground=True

FullScreenAutoFill=True

Fullscreen=False

[sCENERY]

MaxRegionsPurgePerFrame=16

POP_FREE_AUTOGEN=1

AUTOGEN_BATCH_LOD=2

AUTOGEN_TREE_MAX_DRAW_DISTANCE=9500.000000

AUTOGEN_TREE_MIN_DISTANCE_TO_LOD=2500.000000

IMAGE_COMPLEXITY=2

[MAIN]

User Objects=Airplane, Helicopter, Submersible, ExternalSim, Avatar

LabelsSupported=Airplane, Helicopter

Location=349,29,1677,835,\\.\DISPLAY1

Maximized=0

ShowInfoText=1

HideMenuNormal=0

HideMenuFullscreen=1

[PANELS]

IMAGE_QUALITY=1

SAVE_AND_LOAD_PANEL_STATE=0

PANEL_OPACITY=100

QUICKTIPS=0

PANEL_MASKING=1

PANEL_STRETCHING=1

UNITS_OF_MEASURE=0

PANELS_ALWAYS_ON_TOP=1

[CONTROLS]

Controls_Default=Standard

Controls_Current=Standard

KBDAIL=64

KBDELEV=64

KBDRUD=64

[TextInfo.1]

Latitude=1,1

Longitude=1,2

Altitude=1,3

Heading=1,4

AirSpeed=1,5

WindDirectionAndSpeed=1,6

[TextInfo.2]

FrameRate=1,1

LockedFrameRate=1,2

GForce=1,3

FuelPercentage=1,4

[TextInfo.3]

Latitude=1,1

Longitude=1,2

Altitude=1,3

Heading=1,4

AirSpeed=1,5

WindDirectionAndSpeed=1,6

FrameRate=2,1

LockedFrameRate=2,2

GForce=2,3

FuelPercentage=2,4

[slewTextInfo.1]

Latitude=1,1

Longitude=1,2

Altitude=1,3

Heading=1,4

AirSpeed=1,5

[slewTextInfo.2]

FrameRate=1,1

LockedFrameRate=1,2

[slewTextInfo.3]

Latitude=1,1

Longitude=1,2

Altitude=1,3

Heading=1,4

AirSpeed=1,5

FrameRate=2,1

LockedFrameRate=2,2

[Avatar]

DefaultAvatar=Airline Pilot Male with High Viz Jacket

AvatarModeEnabled=0

[DynamicHeadMovement]

LonAccelOnHeadLon=-0.020000

LonAccelOnHeadPitch=-0.010000

RollAccelOnHeadLat=0.010000

YawAccelOnHeadLat=-0.100000

RollAccelOnHeadRoll=0.100000

MaxHeadAngle=5.000000

MaxHeadOffset=0.300000

HeadMoveTimeConstant=1.000000

[VirtualCopilot]

VirtualCopilotActive=0

[DISPLAY.Device.NVIDIA GeForce GTX 960.0.0]

Mode=1920x1080x32

[uSERINTERFACE]

SHOW_SCENARIO_WINDOW=1

SHOW_MISSION_CAPTIONS=0

PAUSE_ON_LOST_FOCUS=0

PROMPT_ON_EXIT=1

RestoreTimeOnMove=1

ScreenshotImageFormat=0

Map_Orientation=2

[PointOfInterestSystem]

CycleSetting=0

[sOUND]

PrimaryPlaybackDevice={DEF00000-9C6D-47ED-AAF1-4DDA8F2B5C03}

VoicePlaybackDevice={DEF00002-9C6D-47ED-AAF1-4DDA8F2B5C03}

VoiceCaptureDevice={DEF00003-9C6D-47ED-AAF1-4DDA8F2B5C03}

SOUND=1

SOUND_QUALITY=2

SOUND_LOD=0

[TrafficManager]

AirlineDensity=60

GADensity=0

FreewayDensity=0

ShipsAndFerriesDensity=50

LeisureBoatsDensity=6

IFROnly=0

AIRPORT_SCENERY_DENSITY=0

[AContain]

ShowLabels=0

ShowUserLabel=0

ShowLabelManufacturer=1

ShowLabelModel=1

ShowLabelTailNumber=0

ShowLabelDistance=1

ShowLabelAltitude=1

ShowLabelAirline=0

ShowLabelAirlineAndFlightNumber=0

ShowLabelFlightPlan=0

ShowLabelContainerId=0

ShowLabelAirspeed=0

ShowLabelHeading=0

LabelDelay=1000

LabelColor=FFFF0000

EnableRibbonVisuals=0

ShowRibbonUser=0

ShowRibbonGroundAI=0

ShowRibbonAircraftAI=0

RibbonFidelity=5.000000

RibbonMaxDistance=3218.689941

[TERRAIN]

LOD_RADIUS=4.500000

TESSELLATION_FACTOR=85

MESH_RESOLUTION=21

TEXTURE_RESOLUTION=25

AUTOGEN_VEGETATION_DENSITY=1

AUTOGEN_BUILDING_DENSITY=1

DETAIL_TEXTURE=1

WATER_REFLECT_CLOUDS=0

WATER_REFLECT_USERAIRCRAFT=0

WATER_REFLECT_SIMOBJECTS=0

WATER_REFLECT_TERRAIN=0

WATER_REFLECT_AUTOGEN_VEGETATION=0

WATER_REFLECT_AUTOGEN_BUILDINGS=0

WATER_REFRACT_CLOUDS=0

WATER_REFRACT_USERAIRCRAFT=0

WATER_REFRACT_SIMOBJECTS=0

WATER_REFRACT_TERRAIN=0

WATER_REFRACT_AUTOGEN_VEGETATION=0

WATER_REFRACT_AUTOGEN_BUILDINGS=0

ENABLE_BATHYMETRY=0

WATER_CLARITY=30

WATER_DETAIL=1

UseGlobalTerrainView=False

[ATC]

AutoOpenAirTrafficWindow=0

UsePilotVoice=1

ShowATCText=1

PilotVoice=327680

COMM_MSG_AI_ATC_COLOR=0XFF8C00

COMM_MSG_ATC_AI_COLOR=0X00008B

COMM_MSG_ATC_USER_COLOR=0X006400

COMM_MSG_USER_ATC_COLOR=0XA52A2A

COMM_MSG_ATIS_COLOR=00000000

[iNTERNATIONAL]

ASLAT=2

ASLON=0

MEASURE=0

[REALISM]

PFactor=1.000000

Torque=1.000000

GyroEffect=1.000000

CrashTolerance=1.000000

General=1.000000

UnlimitedFuel=False

AllowEngineDamage=True

TrueAirspeed=False

AutoCoord=False

RealMixture=True

StressDamage=True

GEffect=True

ManualLights=True

GyroDrift=False

CrashWithDyn=True

CrashDetection=False

OnCrashAction=0

[ATTACHMENTS]

WeaponHighlight=False

HighlightDuration=1.000000

AutoWeaponSwitching=False

UnlimitedWeapons=False

UnlimitedCountermeasures=False

IgnoreAttachmentWeight=True

IgnoreAttachmentForces=True

[RECORDER]

RecordAITraffic=True

RecordAirportVehicles=True

RecordLeisureBoats=True

[sIM]

SYSCLOCK=0

OPTIMIZE_PARTS=1

[sTARTUP]

DEMO=0

STARTUP_DEMO=

LOAD_SCENARIO_TOOLS=1

LoadCorePlugins=1

LoadWindow=1

[FACILITIES]

COUNTRY=

STATE=

CITY=

GTL_BUTTON=4096

[MISC]

Com_Rate=7

[DEBUG]

ReportLoadErrors=0

[FlightPlanMap]

LineWidth=2

[MULTICHANNEL]

condAccountPassword=0

[MULTIPLAYER]

condAccountPassword=0

FrameSyncRate=0

 

Simmerhead & Wozie thank you too for your comments

 

Keep in touch

 

Best regards

 

 

[Jim Young 2,356]

 

 

Yesterday I have increased my RAM from 6 to 12 GB, and did exactly the same flight from HKG to FCO, only having ASN connected and AI traffic slide around 60%. As I removed dll.XML to a temp folder, FSUIPC, SODE; AddonManager and FSpassengers were not on p3d addon tab.

This morning after 12:17 hrs flying the aircraft (PMDG 777 ) landed without any issue at FCO airport with a very good fps.
I'm now reistaling FSUIPC, SODE and AddonManager and will (try) to perform another long haul flight from VHHH to OTHH.
If i get a CTD, that means the problem should be in FSUIPC, SODE or AddonManager. Am I on the right way?

 

Great investigating of YOUR crime scene!  I think you are on the right path. 

 

I took a quick look at your P3D.cfg and your settings are extremely low.  Not sure if you will be happy with the scenery.  You have 3 monitors and I know those are resource intensive.  You may want to try a flight with just the main monitor and see what difference it made.  I have two monitors but P3D runs on one monitor exclusively and the other one is used to open up programs like AS16, ProATC-X, etc.  But, if you have it spread across 3 screens, it will take up more system resources than normal. 

 

For checking our your P3D.cfg, I strongly recommend you look at the AVSIM P3D Guide which was recently released and published by an expert with Lockheed Martin as well as a Moderator here at AVSIM. 

 

Best regards,

Jim

[anthropos 0]

Thank you Jim

 

I will follow all your recomendations definitely.

 

At present I have only one monitor. One year ago I had VRinsight CDU ( using a small screen ) and another screenn ( total 3 ) but im not using them anymore ....a bit confused :(

 

Im going now to read AVSIM P3D guide and follow its recomendations

 

Thank you very much for your help mate 

 

Big hug

 

Bruno