Hello, 

my try to find the G1000 javascript file within the fs2020 files - as written in our manual- was not successful. That means G1000 PFD/MFD have other solutions and it is not possible to use the same technique like CJ4 MDCU. 

Thx 

Reiner Müller 

 

 

 

 

Aren't those in here?
\Packages\Official\OneStore\asobo-vcockpits-instruments-navsystems\html_ui\Pages\VCockpit\Instruments\NavSystems\AS1000

No, you can't do this with just anything. Even if you find the location to place a hook, complex instruments have way too much data to stream their screen content to the outside with this technique. A big screen like the PFD creates around 200 individual file uploads, and you get a refresh rate of 0.25 FPS

That is what the Desktop/Web FIPs are for. There are two sample implementations available for download on the AAO website to help you make your own XML based instruments for any aircraft that you wish.

Edited February 21, 20224 yr by Lorby_SI

thank you found WEB FIPS and tested it. You have some documentation (Syntax e.g.)about this XML syntax , rules.

I could find the examples but no manual for this. 

Plan is to include some of these instruments in a copy of MS COMPAGNION APP to run all this on a tablet.

5 hours ago, ReiMuell said:

You have some documentation (Syntax e.g.)about this XML syntax , rules

This is not a custom dialect. For the most part, the AAO instruments follow the standard flightsim XML gauge syntax, that has been used in Microsoft flightsims for the last 25 years. Any resource online or in the SDK documentation(s) applies (but look more towards the simpler FS9 protocol than FSX/P3D).
The specialized AAO RPN commands that you can use on top are listed in the AAO manual.

The flight path display on the MFD (the magenta line) is a custom AAO thing though, and it is hard coded into the app. If you want that to look differently, you would have to contact me through the support channels.

Edited February 22, 20224 yr by Lorby_SI

HI there,

I'm trying something simiilar. I have it somehow up and running but it is a really ugly workaround, maybe you can guide me to improve it:

- I have a picture of the bottom part and the laterals. I treat each as an independent Gauge and map each button to its function.

- I manually detach the G1000 screen from the plant (alt-gr + click), move it to another screen and move and scale all 3 elements so that they fit.

 

My question: I only know to get the screen information out of MSFS doing this alt-gr. Is there any other way to get the screen out? I understand the hook technique for G1000 will not work properly. So any other idea there?

Thanks!