How does fsuipc read aircraft.cfg information in msfs2024.

[ljk811]

Our quality monitoring software wants to differentiate between aircraft models, such as 332 and 333.
I found that fsuipc can read the information of aircraft.cfg. How is it done? Can my software also identify the sub-model of the aircraft through fsuipc?

c:\users\3829\appdata\roaming\microsoft flight simulator 2024\streamedpackages\microsoft-aircraft-a330\content\simobjects\airplanes\microsoft-a330\presets\inibuilds\a330-200 (rr)\config\aircraft.cfg

[John Dowson]

  On 11/22/2024 at 6:53 AM, ljk811 said:

I found that fsuipc can read the information of aircraft.cfg. How is it done? Can my software also identify the sub-model of the aircraft through fsuipc?

c:\users\3829\appdata\roaming\microsoft flight simulator 2024\streamedpackages\microsoft-aircraft-a330\content\simobjects\airplanes\microsoft-a330\presets\inibuilds\a330-200 (rr)\config\aircraft.cfg

Expand  

FSUIPC tries to read the icao_type_designator, icao_manufacturer, icao_model & icao_airline from the reported location of the aircraft.cfg file. However, it can only do this if the file is readable and not encrypted. Are you sure FSUIPC is reading this? Check offsets 0x0618, 0x09D2 and 0x0B26 and you will probably see that they are empty, which means that the aircraft.cfg can't be read.

[ljk811]

  On 11/22/2024 at 9:24 AM, John Dowson said:

FSUIPC tries to read the icao_type_designator, icao_manufacturer, icao_model & icao_airline from the reported location of the aircraft.cfg file. However, it can only do this if the file is readable and not encrypted. Are you sure FSUIPC is reading this? Check offsets 0x0618, 0x09D2 and 0x0B26 and you will probably see that they are empty, which means that the aircraft.cfg can't be read.

Expand  

The path seems to be read in fsuipc.log. So I want to ask how to identify this path.

In fact, I don’t need to read the information in aircraft.cfg. I only need to read the folders that I can’t see to distinguish the type of 330.

[John Dowson]

  On 11/22/2024 at 9:57 AM, ljk811 said:

The path seems to be read in fsuipc.log. So I want to ask how to identify this path.

Expand  

The path is available at offset 0x3C00. FSUIPC gets this from the AircraftLoaded event.

 

[ljk811]

  On 11/22/2024 at 10:07 AM, John Dowson said:

The path is available at offset 0x3C00. FSUIPC gets this from the AircraftLoaded event.

 

Expand  

thank you very much. I'll try.

[John Dowson]

I don't think you can open that file in MSFS2024....if you succeed, let me know!

[ljk811]

  On 11/22/2024 at 10:25 AM, John Dowson said:

I don't think you can open that file in MSFS2024....if you succeed, let me know!

Expand  

No, I don’t need to open this folder, I need to read the name of the folder to identify the aircraft type, such as a330-300(rr) or a330-200 (rr)

[John Dowson]

  On 11/22/2024 at 10:28 AM, ljk811 said:

I need to read the name of the folder to identify the aircraft type, such as a330-300(rr) or a330-200 (rr)

Expand  

Ah, ok.

[ljk811]

  On 11/22/2024 at 10:33 AM, John Dowson said:

Ah, ok.

Expand  

I also discovered a problem. The "fsuipc-lvar-module" generated by fsuipc in the wasm folder is placed in MSFS2020. Is this a small flaw?

[John Dowson]

  On 11/22/2024 at 1:11 PM, ljk811 said:

The "fsuipc-lvar-module" generated by fsuipc in the wasm folder is placed in MSFS2020. Is this a small flaw?

Expand  

No, that is not the WASM module, it is the persistent storage area for the WASM, which in MSFS2020 was under 
    C:\Users\[USERNAME]\AppData\Roaming\Microsoft Flight Simulator\Packages\fsuipc-lvar-module

If using FSUIPC7 with MSFS2024. please use the latest beta, available here: 

All questions / comments / requests on using FSUIPC7 with MSFS2024 should be posted in that topic for the time being. I am closing / locking this topic now.

John