OnCourse Software
http://www.ocs-support.co.uk/forums/

Could it be a PF3 induced CTD?
http://www.ocs-support.co.uk/forums/viewtopic.php?t=3258		 Page 1 of 1
Author:  Kingfosco [ Sat May 23, 2020 3:34 am ]
Post subject:  Could it be a PF3 induced CTD?
Hello,

first of all congratulations for this great piece of software.

I have a problem with P3D crashing more or less at the same location (got three CTDs, it quits immediately without alert and event viewer shows ntdll.dll as the problematic module).
Could you please compare these two logs and tell me if the problem is the waypoint "XXX" between waypoints "BATAR" and "OGAKO"?

Thank you in advance.


Alessandro Panzacchi
Author:  Dan77 [ Sat May 23, 2020 3:57 pm ]
Post subject:  Re: Could it be a PF3 induced CTD?
It looks like PF3 crashed because FS crashed and I'm not sure why. One thing I would try is repeating the flight using Original Control Sectors rather than Extended. On the page where you select the flight plan to load, select Original Control Sectors at lower right. I'm not sure this is the problem but I have had similar crashes at a particular point in a flight and using Original sectors has sometimes fixed it.
Author:  Kingfosco [ Sat May 23, 2020 4:57 pm ]
Post subject:  Re: Could it be a PF3 induced CTD?
Thank you Dan77. I'm currently flying the same route without ATC hoping to reach my destination. I'll update you about the outcome.

Alessandro
Author:  Dave March [ Sun May 24, 2020 11:30 am ]
Post subject:  Re: Could it be a PF3 induced CTD?
Just a small correction to Dan's comments. :o PF3 did NOT crash on either occasion. :D FS either crashed or you shut it down without first disconnecting PF3(same thing to PF3). The first time PF3 displayed a nice error window and invited you to send in the relevant logs. This was due to FS presumably hanging and PF3 was unable to read the data it needed at that particular time. The second time FS simply disappeared so PF3 did not report an error as such but just said, oh well, FS has gone so I'm shutting down. PF3 logs were updated accordingly both times before it shut down itself.

Now, I would never say it's impossible, but I would say it's really, really, really, very unlikely that PF3 could cause FS to crash. We do not interact with FS directly and only do so via FSUIPC, using the various published memory offsets available.
Author:  Kingfosco [ Sun May 24, 2020 12:01 pm ]
Post subject:  Re: Could it be a PF3 induced CTD?
Hello Dave, thank you for the clarification. I used PF3 for more than 2,000 hours and this is the first time I had to fly without it to complete a flight. Can't say if I've been lucky or it was indeed that frequency change that triggered the ntdll.dll crash, but I can say that PF3 is surely a great way to fly 8-) .
Speaking about control sectors, may I ask you if it's safer to set "Original" instead of "Extended"?

Many thanks.

Alessandro
Author:  Dave March [ Sun May 24, 2020 12:42 pm ]
Post subject:  Re: Could it be a PF3 induced CTD?
Kingfosco wrote: *  Sun May 24, 2020 12:01 pm
Speaking about control sectors, may I ask you if it's safer to set "Original" instead of "Extended"?
I don't believe one is safer than the other. The "Extended' ones haven't been in use as long as the originals so there's always a chance they may be some irregularities.
Author:  Kingfosco [ Thu May 28, 2020 10:56 pm ]
Post subject:  Re: Could it be a PF3 induced CTD?
Roger, thank you.
Keep up the great work!

Alessandro
Page 1 of 1 All times are UTC+01:00
Powered by phpBB® Forum Software © phpBB Limited