OnCourse Software

Good afternoon, I hope everyone is well.

I have tried to do the same flight on two separate occasions from BIKF-LSZH and FS9 has CTD in exactly the same spot, at the same time after being asked to change frequencies. Thanks in advance for any help or advice.

Cheers,
Nathan

This is a strange one; it seems unlikely that this is being caused by PF3, but Dave may correct me on this.
I've seen similar things in the past while running with high scenery density; FS2004 is a 32-bit program so has limited address space to use for everything.

What do you have your scenery density set to (Settings/Display/Scenery tab).
Perhaps you could try the same flight, with a reduced scenery density?

Hope this helps,
Martin

Thank you for your reply, the scenery densities are set to high in my settings so could be something to look at. The first time I flew the flight I hadn’t turned off any of the addon airports in the scenery.cfg so I thought that it may have been that. When I flew the fligh for the second time, I only had BIKF and LSZH selected out of my addon airports. The aircraft I was flying was an HJG DC-8 so very low VAS model.

The thing that got me thinking is that it crashed both times at the same place after PF3 asked for a frequency change and the VCP was changing the frequency. I’m wondering if it was directing FSUIPC to select an illegal frequency or something? I didn’t catch the freq as VCP was doing it so I unfortunately can’t tell you what that freq was. Hoping that the debug_monitor will show something.

Cheers

It could be coincidence. It could be just that the PF3 channel change point coincides with your coming within range of a faulty scenery* or AI aircraft but there is only one way I can think of to eliminate that possibility. Which is to (SHOCK HORROR!) carry out the same flight using the FS default traffic control rather than PF3.

* - I appreciate you tried to eliminate add-on sceneries but occasionally some such files are placed in the main FS scenery directories.

Another thing you might do is to see what caused the crash by looking it up in Event Monitor: https://www.windowscentral.com/how-use- ... windows-10. It is a valuable tool! Other methods apply on earlier Windows systems.

John

That’s a great idea, unfortunately I probably won’t have the opportunity to fly for a few days yet.

Good afternoon, I hope everyone has had a good weekend.
I have just completed the same flight using default ATC, the same aircraft, no changes to my scenery setup, same sim time/date and historical weather and no CTD. I got all the way through to Zurich. Just wondering if the Debug_Monitor from my previous flight shows anything as this one has me stumped.

Cheers,
N

PF3 couldn't cause FS to CTD as it doesn't interact with it directly. All read/writes are done via fsuipc and I doubt that is the culprit either. Unfortunately I'm not sure that version of fsuipc is still supported. If it is you could try sending the fsuipc log to their support to see if they have any ideas. We'd certainly be interested to be kept in the loop

Thank you for your reply Dave and I will see if I can follow it up as you suggested. Um, can I ask one thing if you’re not too busy, in the debug_monitor log, what was the last frequency that PF3 requested the VCP to change to before the FS9 crash? It might help, but only if you have the spare time.

Cheers and thanks again to everyone who has tried to help,
N

The frequency was 128.30 and FS had disappeared before PF3 gave up

Note the first message about the avionics master switch being off.... that was the first point at which PF3 detected something was not right and FS had probably crashed by then

Quote:

27/01/2023 12:39:34 PM: 020 - *** Avionics Master switch is OFF - TRX Skipped *** !!!
27/01/2023 12:39:37 PM: 370 - Problem reading hotkey data! (dwResult=11)
27/01/2023 12:39:37 PM: 370 - Attempting a retry...
27/01/2023 12:39:37 PM: 370 - Wait 10 seconds...
27/01/2023 12:39:47 PM: 380 - Retrying now...
27/01/2023 12:39:48 PM: 490 - Problem reading hotkey data! (dwResult=11)
27/01/2023 12:39:49 PM: 610 - Problem resetting hotkey data!

Thank you Dave