OnCourse Software

A few days ago I had a CTD from P3Dv5 which was attributed to G2D.dll. Based on what I've read, that dll controls the various text such as "brakes", etc. and menu items. Is there any possibility this could have been aggravated by PF3's "in-sim" text windows?

I ask because I don't recall ever having a CTD due to that dll, including over 600 flights using PF3 in P3Dv4 and v5 using Remote Text on a 2nd monitor. I have most of the on-screen texts disabled (except "pause"), and only recently - say the previous 4-5 flights - tried using the in-sim text display. I'm only suspecting PF3 may have been a cause based on the usual logic of "it worked fine until you changed something, so what did you change?"

Since then I've run a couple flights using Remote Text and PF3 Web Display and no issues yet.

Not necessarily requesting support, nor do I know for sure that PF3 was or wasn't the cause, but figured I would ask. P3D seems to have had its share of issues with text windows, so perhaps this was just an unrelated one-off incident.

Thanks!

I would very much doubt this had anything to do with PF3. We don't use that DLL directly, but that's not to say it doesn't get used indirectly at some point. However, the last communication transcript from PF3 was at 21:49:00, when you contacted Memphis Center. At that point the in-sim Captions window was used.

PF3 then went through 22 cycles without any issues, which was just over 3 minutes, and then was unable to access the sim, which as you say CTD'd

I didn't think so either, but like I said, just posting to add to the knowledge base, just in case...

I had been away from the PC for several minutes when it crashed and only knew something happened because I didn't hear it anymore. So unless a more defined cause reveals itself I'll just blame the VCP.

While I did like the ability to show the active hotkeys, I did find that the Web Display utility actually suits my setup a little better. So not all is bad - necessity being the mother of invention...