Sign in to follow this  
flynman33

Mysterious CTD With P3 but Not FSX-SE

Recommended Posts

System Specs.

 

Intel I7 6700K 4.0

Evga 970 GPU

16gigs Ram

Asus Z170-P MOBO

Corsiar 750 watt PSU

HT OFF

 

So I have been trying to fly a flight longer than 4 hours with the PMDG 777 with P3D and so far I have not been able to complete one without a CTD. Error logs have done no good to resolve the issue.

 

I did a clean install of Windows 7 from Windows 10 to go back to an OS that was very dependable on my old system.

 

I installed FSX-SE back in to my system and loaded everything the same and in the past 34 hours I have completed a round the world flight with 4 stops KSEA/EHAM/OMDB/RSKI/KSEA and not one CTD.

 

My settings on FSX-SE were at 75% with 50% traffic locked at 40FPS. My P3 settings I went all the way down to and average of 25% on the scenery sliders and an unmodified CFG. I have looked at VAS and never used more than 60% or 2355. With P3 I was flying naked, nothing extra.

 

My thinking is it is either P3 or PMDG issue.  I would like to hear some discussions about this. I really like P3D but if I cant use it it has to leave my HD..

 

Thanks

 

Randy

 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

 

 


So I have been trying to fly a flight longer than 4 hours with the PMDG 777 with P3D and so far I have not been able to complete one without a CTD. Error logs have done no good to resolve the issue.

 

 

I have never been able to fly longer than 4 hours with the PMDG 777 in P3D.  I think it is impossible.  The flight from FSDT Chicago to FlightBeam's Wash Dulles is close to 3 hours.  When I'm coming in for a landing my VAS goes from just over 1GB to suddenly 500MB's and as I land I am hoping I don't get the dreaded OOM.  Sometimes I do, sometimes I can at least taxi to a gate.  I turned off cloud shadows and things are much better but I still run low on VAS. 

 

 

 


I have looked at VAS and never used more than 60% or 2355.

 

This is actually impossible.  Please do not make statements like this.  If you use the FSUIPC utility, you should set it up to log the amount of VAS usage during a flight.  It will look something like the following:

 

 

********* FSUIPC4, Version 4.955c (14th June 2016) by Pete Dowson *********
Windows version reported as 6.1.?.7601
Prepar3D.exe version = 3.3.5.17625
Reading options from "K:\Prepar3D_v3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 7
Module base=5CD10000
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
15 System time = 16/08/2016 18:53:25
15 FLT path = "C:\Users\JimY\Documents\Prepar3D v3 Files\"
15 ------ Module Version Check ------
15 acontain.dll: 3.3.5.17625
15 api.dll: 3.3.5.17625
15 controls.dll: 3.3.5.17625
15 fs-traffic.dll: 3.3.5.17625
15 G3D.dll: 3.3.5.17625
15 language.dll: 3.3.5.17625
15 sim1.dll: 3.3.5.17625
15 visualfx.dll: 3.3.5.17625
15 weather.dll: 3.3.5.17625
15 window.dll: 3.3.5.17625
15 ----------------------------------
15 Trying K:\Prepar3D_v3\Modules\SimConnectP3D3.dll
15 Found it: trying to connect
15 FS path = "K:\Prepar3D_v3\"
140 ---------------------- Joystick Device Scan -----------------------
140 Product= Cyborg X
140 Manufacturer= Saitek
140 Vendor=06A3, Product=0836 (Version 1.48)
156 Serial Number=
156 -------------------------------------------------------------------
156 LogOptions=00000000 00000001
156 -------------------------------------------------------------------
156 ------ Setting the hooks and direct calls into the simulator ------
156 --- CONTROLS timer memory location obtained ok
156 --- SIM1 Frictions access gained
156 --- FS Controls Table located ok
156 --- Installed Mouse Macro hooks ok.
156 --- Wind smoothing fix is installed
156 --- All links okay (except older global weather setting method)
156 -------------------------------------------------------------------
156 SimConnect_Open succeeded: waiting to check version okay
156 Trying to use SimConnect Prepar3D
29531 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.3.3.3 (SimConnect: 3.3.0.0)
29531 Initialising SimConnect data requests now
29531 FSUIPC Menu entry added
29546 C:\Users\JimY\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml
29546 K:\Prepar3D_v3\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
29796 Monitor IPC:024C (S32) = 3250680
39780 Monitor IPC:024C (S32) = 3097876
49764 Monitor IPC:024C (S32) = 3098388
59748 Monitor IPC:024C (S32) = 3097876
69982 Monitor IPC:024C (S32) = 3098900
89950 Monitor IPC:024C (S32) = 3098388
99934 Monitor IPC:024C (S32) = 3099412
120152 Monitor IPC:024C (S32) = 3098900
130136 Monitor IPC:024C (S32) = 3099412
140120 Monitor IPC:024C (S32) = 3099272
150354 Monitor IPC:024C (S32) = 3098792
160338 Monitor IPC:024C (S32) = 3099304
170322 Monitor IPC:024C (S32) = 3052520
180306 Monitor IPC:024C (S32) = 3053032
190539 Monitor IPC:024C (S32) = 3053544
210508 Monitor IPC:024C (S32) = 3054288
220492 Monitor IPC:024C (S32) = 3052584
230710 Monitor IPC:024C (S32) = 3049384
250678 Monitor IPC:024C (S32) = 3050920
260662 Monitor IPC:024C (S32) = 3047336
270771 Monitor IPC:024C (S32) = 3057996
280755 Monitor IPC:024C (S32) = 3058508
290770 Monitor IPC:024C (S32) = 3061004
295965 K:\Prepar3D_v3\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.air
318866 Monitor IPC:024C (S32) = 2674312
328600 Monitor IPC:024C (S32) = 2409184
338725 Monitor IPC:024C (S32) = 2237844
348678 Monitor IPC:024C (S32) = 1861088
348834 System time = 16/08/2016 18:59:14, Simulator time = 17:56:58 (22:56Z)
348834 Aircraft="PMDG 737-800NGX PMDG House Winglets"
350971 Weather Mode now = Theme
356291 Starting everything now ...
356384 ASN active function link set
356384 Ready for ASN WX radar

 

 

The AVSIM CTD Guide provides information on how to set up the FSUIPC to monitor the VAS and log it.  VAS will go up or down depending on the activity.  When you complete the flight it will show you exactly what your VAS usage was and the average FPS during the flight. 

 

Your AMD CPU is not very powerful and this may be a cause for issues with P3D.  P3D uses more resources than FSX and uses DX11 whereas FSX only has the ability to use DX10 Preview.  DX11 allows for more eye-candy rendering.  I have found that shadows are a killer in P3D and have turned them off.   I just have shadows for the aircraft and VC.  That works for me.  If I want to take a screenshot of my clouds and the shadows hitting the ground, I'll simply turn them on.  But I do not need them during flight. 

 

Best regards,

Share this post


Link to post
Share on other sites

Jim. My system I am using now is

 

Intel I7 6700K 4.0 CPU

Evga 970 GPU

16gig DDR4 2400 RAM

Windows 7

Corsair 750 PSU

 

I think I am going to install the simconnect on P3D and see if that solves this issue. My PMDG flys perfectly in FSX-SE now. I am on my last leg of my 2nd Round the Globe trip this weekend. So far I have kept aircraft in the air 65 hours of the last 72. I have 12 hours to finish RTW trip 2.

 

Randy


I have never been able to fly longer than 4 hours with the PMDG 777 in P3D.  I think it is impossible.  The flight from FSDT Chicago to FlightBeam's Wash Dulles is close to 3 hours.  When I'm coming in for a landing my VAS goes from just over 1GB to suddenly 500MB's and as I land I am hoping I don't get the dreaded OOM.  Sometimes I do, sometimes I can at least taxi to a gate.  I turned off cloud shadows and things are much better but I still run low on VAS. 

 

 

 

 

 

 

Jim. In the AMD system that is posted in my Avsim signature I was able to fly KSEA/RKSI OMDB/KSEA KSEA/EHAM with my PMDG 777 in P3D without any problem, this is why I am baffled that a far higher performing system does not handle P3 very well.  

 

Thanks, Randy

Share this post


Link to post
Share on other sites

Ah!  A new system!  I like it!  When one gets a new system, usually settings go much higher in the config and display driver settings (otherwise, why move up to a more powerful system?).  Unfortunately, you cannot buy a new system and move 'ALL' of the sliders up.  You just eat up VAS much faster with a newer system as you can render more textures faster.  Fortunately a newer system with the same settings as the old system will provide better performance and quicker rendering of textures and other neat stuff but not eliminate OOM's.  I have stated this in previous topics where we ran FSX on systems back in 2006/2007 that are not as powerful as today's systems and we rarely ran out of VAS because we kept our FPS slider to no higher than 30 and ran our systems with a max of 4.5 LOD Radius.  Many had to reluctantly lower the 4.5 LOD to a 3.5 LOD as they really had under-powered systems!! Then someone came up with a guide (not on AVSIM) where one could raise the LOD_Radius to 9.5 and came up with some tweaks that worked for some but mostly not all.  Then we had many who had OOM's and even the individual who came up with higher LOD_Radius settings said they were too high and he lowered them to only 7.5.  With settings like that you are just eating up VAS faster.  The max slider for LOD_Radius for P3D is 6.5 and I consider that very high for most if not all systems because your sim has to render more textures in a larger area.  Couple that with payware aircraft and scenery and you'll see OOM's much faster than in FSX.

 

Maybe I'm all wet but the way I see it.  If an application can go to 64 bits and you have an unlimited amount of VAS (well, almost), then maybe it will reduce the number of OOM's no matter what the settings.  But we are not there yet.

 

Hey!  I have some good news.  AVSIM will be releasing a P3D configuration guide soon (very soon).  Our resident expert, Rob Ainscough is almost finished.  Still it won't stop the OOM's but it will give you some good guidance.

 

Best regards,

Share this post


Link to post
Share on other sites

I think the point is that P3D 3.3.5, with similiar and/or significantly lower settings than FSX, will cause CTD. In my case fresh OS reinstall, newest P3D with medium or low settings and mimimum ammount of addons, still same crash happens. Reducing settings does not help. VAS is not the problem, never has been, even with FSX.

 

I'm changing back to FSX, for now.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this