FSUIPC Loads But In-sim Window Does Not Open

[Sumits81]

Pete,

Need your assistance once more. I've managed to overcome the initial crash by re-installing FSUIPC and P3D launches OK. I can also see FSUIPC in the addon menu but clicking on it does not open the FSUIPC options menu (note this is in P3D windowed mode so I would know if it's behind the actual sim window). You have the FSUIPC.log already (sent via email earlier).

Thoughts?

Thanks

[Sumits81]

Disabling FSUIPC in the DLL.xml enables other addons to load and launch in-sim normally.

[Pete Dowson]

49 minutes ago, Sumits81 said:

I can also see FSUIPC in the addon menu but clicking on it does not open the FSUIPC options menu (note this is in P3D windowed mode so I would know if it's behind the actual sim window). You have the FSUIPC.log already (sent via email earlier).

Yes, and it showed no problems.

Can you tell me EXACTLY what other add-ons or add-ins are running? Have you tried eliminating any?

As a first step I need some more logging.  Something seems to be stopping the message from SimConnect telling FSUIPC that the menu option has been clicked.

Add 

Debug=Yes
LogExtras=x8000

This just adds some logging to the menu process. Do that and then try to get the FSUIPC options showing. Do it just twice, with a minute or two between, then show me the log.

I'll be back in a few hours.

Pete

 

[Pete Dowson]

3 minutes ago, Sumits81 said:

Disabling FSUIPC in the DLL.xml enables other addons to load and launch in-sim normally.

Sorry, what have other addons got to do with it. Your report makes no mention of any problem other that the fact that the FSUIPC options screen won't appear.

FSUIPC cannot affect any other add-on, except those which interface to it, of course. If that's happening you have a serious corrupted installation.

Pete

 

[Sumits81]

Pete,

I couldn't get the FSUIPC to open in P3D but the logs show something interesting:

********* FSUIPC4, Version 4.961a (6th February 2017) by Pete Dowson *********
Windows 10 Enterprise N 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0)
Prepar3D.exe version = 3.4.18.19475
Reading options from "E:\P3D\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 10
Module base=527B0000
User Name=removed
User Addr=removed
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
        0 System time = 06/02/2017 20:51:11
        0 FLT path = "C:\Users\user\Documents\Prepar3D v3 Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 3.4.18.19475
        0             api.dll: 3.4.18.19475
        0        controls.dll: 3.4.18.19475
        0      fs-traffic.dll: 3.4.18.19475
        0             G3D.dll: 3.4.18.19475
        0        language.dll: 3.4.18.19475
        0            sim1.dll: 3.4.18.19475
        0        visualfx.dll: 3.4.18.19475
        0         weather.dll: 3.4.18.19475
        0          window.dll: 3.4.18.19475
        0 ----------------------------------
        0 Trying E:\P3D\Modules\SimConnectP3D3.dll
        0 Found it: trying to connect
        0 FS path = "E:\P3D\"
       94 ---------------------- Joystick Device Scan -----------------------
       94 Product= Saitek X52 Pro Flight Control System
       94    Manufacturer= Saitek
       94    Vendor=06A3, Product=0762 (Version 1.35)
       94    Serial Number= 
       94 -------------------------------------------------------------------
       94 LogOptions=00000000 00080011
       94 -------------------------------------------------------------------
       94 ------ Setting the hooks and direct calls into the simulator ------
       94 --- CONTROLS timer memory location obtained ok
       94 --- SIM1 Frictions access gained
       94 --- FS Controls Table located ok
       94 --- Installed Mouse Macro hooks ok.
       94 --- Wind smoothing fix is installed
       94 --- SimConnect intercept for texts and menus option is off
       94 --- All links okay (except older global weather setting method)
       94 -------------------------------------------------------------------
      109 SimConnect_Open succeeded: waiting to check version okay
      109 Trying to use SimConnect Prepar3D
      109 Opened separate AI Traffic client okay
    10453 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
    11219 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.18.19475 (SimConnect: 3.4.0.0)
    11219 Initialising SimConnect data requests now
    11219 FSUIPC Menu entry added
    11250 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
    11250 C:\Users\user\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml
    11250 E:\P3D\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
    31797 E:\P3D\SimObjects\Airplanes\Piper_J3Cub\Piper_J3Cub.air
    47312 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
    47328 User Aircraft ID 2 supplied, now being used
    47906 System time = 06/02/2017 20:51:59, Simulator time = 20:51:42 (20:51Z)
    47906 Aircraft="Piper Cub"
    51844 Weather Mode now = Theme
    57906 Starting everything now ...
    57906 Note: "E:\P3D\Modules\PFCFSX.DLL", Error 126 (The specified module could not be found. )
    57906 Note: "E:\P3D\Modules\EPICINFO5.DLL", Error 126 (The specified module could not be found. )
    57906 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
    57922 ASN active function link set
    57922 Ready for ASN WX radar
    63406 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
    65031 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
    77000 ### MENU: EV_MENU [15] received: dwMenuEvent=0, fInScanJoy=0, fInOptions=0
    80656 ### MENU: EV_MENU [15] received: dwMenuEvent=15, fInScanJoy=0, fInOptions=0
    80922 ### MENU: Error: failed to receive DLGMODE notification! Aborting menu!
    83531 Deactivated: culprit unknown
    83531 Focus lost: culprit unknown
    92078 Deactivated for PID=4072, "explorer.exe"
    92078 Lost focus to PID=4072, "explorer.exe"
    94047 Deactivated for PID=8752, "AS16.exe"
    94047 Lost focus to PID=8752, "AS16.exe"
    98047 ### MENU: EV_MENU [15] received: dwMenuEvent=0, fInScanJoy=0, fInOptions=0
    99875 ### MENU: EV_MENU [15] received: dwMenuEvent=15, fInScanJoy=0, fInOptions=0
   100812 Deactivated: culprit unknown
   100812 Focus lost: culprit unknown
   101922 ### MENU: Error: failed to receive DLGMODE notification! Aborting menu!
   104625 ### MENU: EV_MENU [15] received: dwMenuEvent=0, fInScanJoy=0, fInOptions=0
   107922 ### MENU: Error: failed to receive DLGMODE notification! Aborting menu!
   108328 Deactivated for PID=4072, "explorer.exe"
   108328 Lost focus to PID=4072, "explorer.exe"
   129547 ### MENU: EV_MENU [15] received: dwMenuEvent=0, fInScanJoy=0, fInOptions=0
   131141 ### MENU: EV_MENU [15] received: dwMenuEvent=15, fInScanJoy=0, fInOptions=0
   132906 ### MENU: Error: failed to receive DLGMODE notification! Aborting menu!
   260953 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
   260953 Sim stopped: average frame rate for last 196 secs = 30.2 fps
   260953    Max AI traffic was 0 aircraft
   264797 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
   273203 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
   292703 Deactivated for PID=1064, "dwm.exe"
   292703 Deactivated for PID=1064, "dwm.exe"
   292703 Lost focus to PID=1064, "dwm.exe"
   292719 Lost focus to PID=1064, "dwm.exe"
   292734 Deactivated for PID=1064, "dwm.exe"
   292734 Lost focus to PID=1064, "dwm.exe"
   292781 E:\P3D\SimObjects\Airplanes\FSLabs A320 IAE\A320.air
   293125 Aircraft="FSLabs A320-X United Airlines"
   293547 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
   332187 ### MENU: EV_MENU [15] received: dwMenuEvent=0, fInScanJoy=0, fInOptions=0
   335125 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
   335125 Sim stopped: average frame rate for last 42 secs = 30.0 fps
   335125    Max AI traffic was 0 aircraft
   374078 === Calling SimConnect_Close ...
   374281 === SimConnect_Close done!
   375281 System time = 06/02/2017 20:57:27, Simulator time = 20:55:51 (20:55Z)
   375281 *** FSUIPC log file being closed
Minimum frame rate was 28.4 fps, Maximum was 44.4 fps
Minimum available memory recorded was 32768Mb
Average frame rate for running time of 262 secs = 30.1 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 5 Allocs, 4 Freed
********* FSUIPC Log file closed ***********
 

[Sumits81]

Update: this is weird.

When I load up the PMDG 747 v3 on the default runway (Eglin AFB) FSUIPC (v.4961) works fine (logs below). When I load her up (or the Piper Cub in the logs above) at UK2000 EGLL FSUIPC doesnt load at all.

********* FSUIPC4, Version 4.961 (1st February 2017) by Pete Dowson *********
Windows 10 Enterprise N 64 Bit reported as Build 14393, Release ID: 1607 (OS 10.0)
Prepar3D.exe version = 3.4.18.19475
Reading options from "E:\P3D\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 10
Module base=530D0000
User Name=
User Addr=
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
       15 System time = 06/02/2017 21:52:09
       15 FLT path = "C:\Users\user\Documents\Prepar3D v3 Files\"
       15 ------ Module Version Check ------
       15        acontain.dll: 3.4.18.19475
       15             api.dll: 3.4.18.19475
       15        controls.dll: 3.4.18.19475
       15      fs-traffic.dll: 3.4.18.19475
       15             G3D.dll: 3.4.18.19475
       15        language.dll: 3.4.18.19475
       15            sim1.dll: 3.4.18.19475
       15        visualfx.dll: 3.4.18.19475
       15         weather.dll: 3.4.18.19475
       15          window.dll: 3.4.18.19475
       15 ----------------------------------
       15 Trying E:\P3D\Modules\SimConnectP3D3.dll
       15 Found it: trying to connect
       31 FS path = "E:\P3D\"
      125 ---------------------- Joystick Device Scan -----------------------
      125 Product= Saitek X52 Pro Flight Control System
      125    Manufacturer= Saitek
      125    Vendor=06A3, Product=0762 (Version 1.35)
      125    Serial Number= 
      125 -------------------------------------------------------------------
      140 LogOptions=00000000 00080011
      140 -------------------------------------------------------------------
      140 ------ Setting the hooks and direct calls into the simulator ------
      140 --- CONTROLS timer memory location obtained ok
      140 --- SIM1 Frictions access gained
      140 --- FS Controls Table located ok
      140 --- Installed Mouse Macro hooks ok.
      140 --- Wind smoothing fix is installed
      140 --- SimConnect intercept for texts and menus option is off
      140 --- All links okay (except older global weather setting method)
      140 -------------------------------------------------------------------
      140 SimConnect_Open succeeded: waiting to check version okay
      140 Trying to use SimConnect Prepar3D
      140 Opened separate AI Traffic client okay
    12765 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.4.18.19475 (SimConnect: 3.4.0.0)
    12765 Initialising SimConnect data requests now
    12765 FSUIPC Menu entry added
    12797 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
    12797 C:\Users\user\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml
    12797 E:\P3D\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
    36719 E:\P3D\SimObjects\Airplanes\PMDG 747-400\B747-400_RR.air
    54078 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
    54094 User Aircraft ID 2 supplied, now being used
    55094 System time = 06/02/2017 21:53:04, Simulator time = 08:00:01 (13:00Z)
    55094 Aircraft="PMDG 747-436 British Airways (G-CIVI | 2016)"
    58281 Weather Mode now = Theme
    60109 Starting everything now ...
    60109 Note: "E:\P3D\Modules\PFCFSX.DLL", Error 126 (The specified module could not be found. )
    60109 Note: "E:\P3D\Modules\EPICINFO5.DLL", Error 126 (The specified module could not be found. )
    60125 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
    60156 ASN active function link set
    60156 Ready for ASN WX radar
    60781 Advanced Weather Interface Enabled
    87328 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
    87328 Sim stopped: average frame rate for last 33 secs = 28.8 fps
    87328    Max AI traffic was 0 aircraft
    92594 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
    95031 ### MENU: EV_MENU [15] received: dwMenuEvent=0, fInScanJoy=0, fInOptions=0
    95031 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
    95031 ### MENU: ST_DLGMODE received, stt->dwInteger=1, dwMenuEvent=15
    95031 ### MENU: ST_DLGMODE: fInScanJoy=0, fInOptions=0
   113531 ### MENU: PropertySheet call returned 1
   113531 ### MENU: ST_DLGMODE: ending dialog mode
   113625 ### MENU: Error: failed to receive DLGMODE notification! Aborting menu!
   113859 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
   143219 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y
   143219 Sim stopped: average frame rate for last 29 secs = 30.0 fps
   143219    Max AI traffic was 0 aircraft
   177359 === Calling SimConnect_Close ...
   177562 === SimConnect_Close done!
   178562 System time = 06/02/2017 21:55:07, Simulator time = 08:01:05 (13:01Z)
   178562 *** FSUIPC log file being closed
Minimum frame rate was 29.9 fps, Maximum was 33.0 fps
Minimum available memory recorded was 32768Mb
Average frame rate for running time of 65 secs = 29.4 fps
Maximum AI traffic for session was 0 aircraft
Memory managed: 64 Allocs, 63 Freed
********* FSUIPC Log file closed ***********
 

[Sumits81]

Update- I **may** have fixed this. I think when P3D crashes upon being shutdown it somehow corrupts the dll.xml. I opened the file in Notepad++ and selected the option that says- 'encode in ANSI'. This somehow revives the dll.xml to function normally.

More tests to follow.

[Sumits81]

OK, so the theory checks out. I think I may have fixed this! BLIMEY!

[Pete Dowson]

2 hours ago, Sumits81 said:

I think when P3D crashes upon being shutdown it somehow corrupts the dll.xml. I opened the file in Notepad++ and selected the option that says- 'encode in ANSI'. This somehow revives the dll.xml to function normally.

I can understand a corrupt DLL.XML file causing FSUIPC not to be loaded -- it would have no menu entry then -- but I still don't understand how a loaded FSUIPC doesn't respond when its menu entry is selected. In the log earlier where there was no menu, this sequence:

    77000 ### MENU: EV_MENU [15] received: dwMenuEvent=0, fInScanJoy=0, fInOptions=0
    80656 ### MENU: EV_MENU [15] received: dwMenuEvent=15, fInScanJoy=0, fInOptions=0
    80922 ### MENU: Error: failed to receive DLGMODE notification! Aborting menu!

  shows that you clicked on the selection twice, presumably because it was slow to respond.  the "=15 in the second is the 'memory' of the first, showing my code that it was already trying to get into dialog mode. the notification of the menu selection worked, but then SimConnect wouldn't go into dialog mode. The correct sequence is:

   778305 ### MENU: EV_MENU [15] received: dwMenuEvent=0, fInScanJoy=0, fInOptions=0
   778305 ### MENU: ST_DLGMODE received, stt->dwInteger=1, dwMenuEvent=15
   778305 ### MENU: ST_DLGMODE: fInScanJoy=0, fInOptions=0

Then, on exit from the options screen:

   784857 ### MENU: PropertySheet call returned 1
   784981 ### MENU: ST_DLGMODE: ending dialog mode

I also get this 'error', later:

   785668 ### MENU: Error: failed to receive DLGMODE notification! Aborting menu!

That's just a safety measure, to stop the "MenuEvent" memory I mentioned preventing further attempts to enter dialog mode.

The last time I saw anything like this it was down to another add-on somehow preventing dialog mode from being used. I'm afraifd I don't remember which add-on. This must be about 6 or 7 years ago, at least!

Pete

 

[Sumits81]

Baffling but my P3D seems stable for now. I can explain why FSUIPC would load in other airports and not UK2000's EGLL- had to delete the wx file that brought that back to life too. It all kicked off when I upgraded GSX, addonmanager and FSUIPC late last week. During the height of the issue I even removed addonmanager completely but it still wouldn't play ball. Wasn't until I looked at the xml.dll from just after upgrading AS16 last week and found the formatting (in Notepad++) slightly different- the indentation got me thinking. So I proceeded to delete the partially rebuilt dll and renamed the pre-AS16 and it ran OK. Looked up the properties of the file and realised it was encoded in ANSI...

[Sumits81]

Let me know if there's any added value in running 4.961a instead of the current 4.961.

Thanks

[Pete Dowson]

13 minutes ago, Sumits81 said:

Let me know if there's any added value in running 4.961a instead of the current 4.961.

Not really. I'm only moving things around to see what changes. And I don't think the changes are relevant to your problems. And anyway, I'm up to 4.961b now.

Pete

 

[Sumits81]

Roger.