OnCourse Software

I run P3dv5.4 on one PC and PF3 3.21 on a second PC from within the Wide Client folder. This system has served me very well for a long time; until early October of 2023. That is when the 'app hangs' started. Maybe an hour or two into a flight P3d hangs. No stutters, good frame rates and basically flawless operation until the 'hang'.

On the second PC running PF3, nothing happens except the red notice saying that PF3 was disconnected appears.

So I've been checking the error logs after each 'hang and this caught my eye:
Notice that the log from the PF3 PC has an error time about a minute BEFORE the 'hang' time shown in the P3D PC error log.

Every time I've checked the P3D PC App logs for a P3d 'hang' I've found an error in the PF3 PC App logs about a minute BEFORE.

Also, I've run the exact same flights with PF3 and without using PF3 and the only time P3D hangs is when using PF3.

I've run <sfc /scannow> to try to fix a possible bad ntdll.dll; no joy.

I'm attaching the old debug monitor log from time of last hang.
Any assist would be appreciated
Thanks,
max

What am I doing wrong with these attachments????

What am I doing wrong with these attachments????

Apparently... nothing.

The faulting application is logged as WideClient and here's the entries in the PF3 debug log

1/22/2024 12:43:48 PM: 300 - Problem reading FS_Alive offset
1/22/2024 12:45:08 PM: 840 - FS cannot be detected!
1/22/2024 12:45:08 PM: 840 - Connection OFF! #1
1/22/2024 12:45:10 PM: 900 - END of LOOP......
1/22/2024 12:45:11 PM: 930 - PF Loop Exited due to FS Disconnected!
1/22/2024 12:45:11 PM: 930 - ****** PF3 Disconnected from FS

So as far as PF3 was concerned it could no longer see FS

We read FSUIPC offset 0x337E and this is what is described in the SDK

Quote:

FSUIPC activity count. Simply a number that is
incremented every time FSUIPC receives a call or message
from Flight Simulator. This can be used through WideFS to
check if FS is still active, for example. Note that when FS is
loading aircraft or scenery/textures, this value may not
change for many seconds as FSUIPC is then not getting
any processor time at all.

If PF3 detects this value is not incrementing then we keep trying for however many seconds you have the FS Inactive time set in PF3 options, in your case it is 90 seconds. You could try setting this to a higher value to see if it helps. Other than that there's not much I can do to help unfortunately. You may wish to report this to John Dowson to see what his take is on the situation... he would probably want to see the WideClient log.

Hope this helps

Thanks, Dave for taking the time to answer.
max