ipcReady not firing on 1.15.7/8.0

[pilotjohn]

I launch FSUPIC before the sim starts. With the latest update ipcReady never fires after loading into a flight and FSUIPC doesn't actually work (e.g. controls/events). I have to relaunch FSUIPC in order to regain functionality. Is this a known new bug?

 

FSUIPC7.zip

[John Dowson]

10 hours ago, pilotjohn said:

I launch FSUPIC before the sim starts. With the latest update ipcReady never fires after loading into a flight and FSUIPC doesn't actually work (e.g. controls/events). I have to relaunch FSUIPC in order to regain functionality. Is this a known new bug?

I have just tried this and it seems to still be working fine:

Quote

      422 34216 -------------------------------------------------------------------
      640 34216 ### Note: AI Traffic related facilities and data are inhibited!
      656 34216 LogOptions=60000000 00000011
     1390 34216 Using "D:\FSUIPC7\GFDEV64.DLL", version 2.2.8.0
     1390 34216 GoFlight GFP8 detected: 2 devices
     1390 34216 GoFlight GFT8 detected: 2 devices
     1390 34216 GoFlight GFRP48 detected: 2 devices
     1390 34216 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
    69250 34216 Simulator detected
   144968 34216   [INFO]: Connected to MSFS
   147031 34216 SimConnect_Open succeeded
   147031 34216 Running in "KittyHawk", Version: 11.0.282174.999 (SimConnect: 11.0.62651.3)
   147031 34216 MSFS version = 11.0.282174.999
   147031 34216 Generating controls file list: 'C:\Users\jldow\OneDrive\Documents\FSUIPC7\Controls List for MSFS Build 999.txt'
   147109 34216 Initialising SimConnect data requests now
   147109 35276 LUA.1: beginning "D:\FSUIPC7\ipcInit.lua"
   147234 34216 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y
   147234 34216 **** Empty name received in 'AircraftLoaded' state'
   147234 35276 LUA.1: ipcInit called: MaxSteeringSpeed set in offset 0x66C0 to 55
   147265 34216 **** Thread 23284 created for ScanButtons
   147265 34216 **** Thread 9100 created for ScanAxes
   188437 34216 User Aircraft ID not supplied -- trying default
   191750 34216 D:\MSFS2020\Community\A32NX\SimObjects\Airplanes\Asobo_A320_NEO\aircraft.CFG
   194703 34216 Aircraft loaded: running normally now ...
   194718 34216 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=Y
   194922 34216 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N
   195078 System time = 20/04/2021 11:27:46, Simulator time = 08:27:43 (09:27Z)
   195718 34216 Aircraft="Airbus A320 Neo Asobo"
   195812 34216 [Buttons] now profile-specific:
   195812 34216    2=P101,10,C68066,1
   195812 34216    3=P101,11,C68066,2
   195843 34216 [Buttons] now profile-specific:
   195843 34216    0=P101,8,CM3:2,1
   195843 34216    2=P101,10,C68066,1
   195843 34216    3=P101,11,C68066,2
   196000 34216 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N
   203687 34216 -------------------- Starting everything now ----------------------
   203750 25116 LUA.2: beginning "D:\FSUIPC7\ipcReady.lua"
   203765 25116 LUA.2: ipcReady ca;;ed: MaxSteeringSpeed set in offset 0x66C0 to 45
   207500 34216 *** EVENT: Cntrl= 67073 (0x00010601), Param= 6 (0x00000006) ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE
   207500 34216 *** EVENT: Cntrl= 66241 (0x000102c1), Param= 1 (0x00000001) TOGGLE_MASTER_BATTERY
   207500 34216 *** EVENT: Cntrl= 67073 (0x00010601), Param= 6 (0x00000006) ELECTRICAL_BUS_TO_BUS_CONNECTION_TOGGLE
   207500 34216 *** EVENT: Cntrl= 66241 (0x000102c1), Param= 2 (0x00000002) TOGGLE_MASTER_BATTERY
   207500 34216 *** EVENT: Cntrl= 67076 (0x00010604), Param= 2 (0x00000002) ELECTRICAL_BUS_TO_CIRCUIT_CONNECTION_TOGGLE
   207500 34216 *** EVENT: Cntrl= 67076 (0x00010604), Param= 2 (0x00000002) ELECTRICAL_BUS_TO_CIRCUIT_CONNECTION_TOGGLE
   207500 34216 *** EVENT: Cntrl= 67226 (0x0001069a), Param= 0 (0x00000000) WINDSHIELD_DEICE_OFF
 

The log you attached was cut short, and shows that FSUIPC7 did not reach the 'Starting everything now' stage. Did FSUIPC7 crash or did you manually kill it?
Is there anything in the event log?
Can you try again please, and if you still experience this issue attach your FSUIPC7.ini as well as the full log, and if FSUIPC7 did not close down correctly, please check the event log.

Also, you are using an old release, v7.0.9a - please update to the official release, v7.0.9 (or the v7.1.0f beta).

[pilotjohn]

Yes, I'm using the "old" release (where you added offsets for engine master). The log is complete, as in, that's all FSUIPC would show despite loading up a flight and being ready to go. Is there an official source for the latest greatest version (I'll search for these for now)?

[John Dowson]

Just now, pilotjohn said:

The log is complete, as in, that's all FSUIPC would show despite loading up a flight and being ready to go.

But the log does not show FSUIPC closing down - did you attach it before exiting FSUIPC7?

1 minute ago, pilotjohn said:

Is there an official source for the latest greatest version (I'll search for these for now)?

Usual places - on www.fsuipc.com or in the Updated Modules -> Download links section of this forum.

v7.0.9 is basically the same as v7.0.9a, but best to try with the supported version before I investigate, if needed. If the log you attached was the complete log, then FSUIPC7 crashed and I need to see the event log.

Anyway, download the latest version and try again. If you still get the same problem with v7.0.9, please also try with v7.1.0f.

Any issues, attach your log + ini + any info from the windows event viewer, if FSUIPC7 is indeed crashing.

[pilotjohn]

I'll try with the latest. No, the logs are before I quit FSUIPC to restart it, but was sitting on the ramp in the plane. I'll attach the full chain of events next time (if it still occurs).

[John Dowson]

1 minute ago, pilotjohn said:

No, the logs are before I quit FSUIPC to restart it, but was sitting on the ramp in the plane.

Ok, then that makes sense. But, always better to close down FSUIPC before attaching logs.
Did you have an FSUIPC assignments window open when the plane was loading by any chance? It looks like FSUIPC7 didn't even receive your aircraft name. so it never got to the 'ready-to-fly' state, which is strange...

 

[pilotjohn]

8 hours ago, John Dowson said:

Ok, then that makes sense. But, always better to close down FSUIPC before attaching logs.
Did you have an FSUIPC assignments window open when the plane was loading by any chance? It looks like FSUIPC7 didn't even receive your aircraft name. so it never got to the 'ready-to-fly' state, which is strange...

 

No I didn't have the assignment window open. The reinstall of 7.0.9 from April 14th seems to have "fixed" it.