Hello ! 
I have two tablets on my local network. I'd like to create gauges for each via WEBFIPS. How can I manage two different pages that work together? 
1 = MFD + PFD
2 = Flaps + Engine + Radio
I can't find a solution. 
Thank you.

You can only run one Layout at a time. But you can call individual FIPs on that layout - see AAO manual, chapter "WebFIPs", section "Accessing the WebFIPs"

So you would combine all required gauges into one Layout, then call the individual gauges either with separate browser windows - or you write a small HMTL page with iframes where each iframe calls a different FIP gauge. You could deploy those files on the AAO webserver or create local .html files on your devices. Whichever yields better performance.

Edited August 28, 2025Aug 28 by Lorby_SI

Thank you so much for your help. I managed to do what I wanted, but the ND doesn't display the route. I need to make a pop-up of my screens, but it consumes so many resources.
I'll eventually find something that meets my needs 😄. Thanks again.

Edited August 30, 2025Aug 30 by D1git4l

1 hour ago, D1git4l said:

but the ND doesn't display the route

You mean the default AAO ND gauge? That can only display the flight plan that you load into the sim itself, it doesn't have (can't have actually) a connection to whatever FMC the aircraft is using.

Load your route as a flight plan on the world map, and the AAO ND will display it.

Yes, I'm talking about the basic ND.
The problem is that when you have a flight plan change, you have to do it several times, just like during a live broadcast. Am I wrong?

On 8/30/2025 at 3:20 PM, Lorby_SI said:

You mean the default AAO ND gauge? That can only display the flight plan that you load into the sim itself, it doesn't have (can't have actually) a connection to whatever FMC the aircraft is using.

Load your route as a flight plan on the world map, and the AAO ND will display it.

Hi! I thought of something. It might be silly, but since it's not my area of expertise, I'm asking. You use pop-ups for FMCs and screen exports. Would it be technically possible to do the same thing for all the screens on an aircraft? PFD, ND, MFD, for example. So we could use the screens on your tablets via the web server, for example, in my case, opening two web pages for two screens, and not via external server applications to simulate screens that the PC also manages.

On 8/31/2025 at 5:06 PM, D1git4l said:

Yes, I'm talking about the basic ND.
The problem is that when you have a flight plan change, you have to do it several times, just like during a live broadcast. Am I wrong?

Unfortunately, the SimConnect API doesn't have a method to only save the current flight plan - you can only save the entire flight. Not sure if that is even possible in Carreer Mode. If you have a PLN file, you can load it with AAO - but again, I don't know if this works in that special mode. Tricky.

11 hours ago, D1git4l said:

Hi! I thought of something. It might be silly, but since it's not my area of expertise, I'm asking. You use pop-ups for FMCs and screen exports. Would it be technically possible to do the same thing for all the screens on an aircraft? PFD, ND, MFD, for example. So we could use the screens on your tablets via the web server, for example, in my case, opening two web pages for two screens, and not via external server applications to simulate screens that the PC also manages.

Yes, the (CAPTURETOFIP:) command can stream anything from your screen to a gauge or webpage. The problem will be performance, the lag will probably be too great and the refresh rate too low for a live instrument like a PFD. It might be good enough for the ND though.

The PFD is already working, no worries, the MFD or the ND no worries because of the framerate. So making it I could have all the instruments as I want. I will try to see how all this works. Take the time and learn :). Thanks again for taking the time to answer.

3 hours ago, D1git4l said:

The PFD is already working, no worries, the MFD or the ND no worries because of the framerate. So making it I could have all the instruments as I want. I will try to see how all this works. Take the time and learn :). Thanks again for taking the time to answer.

What aircraft do you want to do this with? I can write a demonstration ND gauge for you, that you can use to build others.

That's awesome! You really do a lot for us! Thank you so much. The easiest thing for you 🙂 I fly most often with the Ifly 737, the Fenix A320, and the RJ from Just Flight, and only on Msfs2024.

This is the code for a Web and Desktop-FIP that pops out the iFly 737 ND and then displays it. The only tricky bit is the part in "Initialize". It is pure convenience though, you could run the gauge without it. The "Initialize" will pop out the ND automatically when the gauge is first displayed, rename the popout-window, and then it will move it off-screen. The actual capture is done in the "Update" part, and the "Image" displays the captured image.

Personally, I don't like this solution. I think that a web page is the better way to go, less moving parts, and better options to clean up afterwards. I will create one of those too.

<?xml version="1.0" encoding="utf-8"?>
<Gauge Name="iFly 737 ND" Version="1.0">
<Position X="0" Y="0"/>
<Image Name="(L:ndscreen, String)" ImageSizes="1024,1024,1024,1024"/>
<Initialize>
  <Frequency>0</Frequency>
  <Script>
    'flightsimulator' procexist if{ (WINDOWPOSITIONGET:flightSimulator|fsx|fsy|fsw|fsh) } 'flightsimulator2024' procexist if{ (WINDOWPOSITIONGET:flightSimulator2024|fsx|fsy|fsw|fsh) }
    (WINDOWCLOSE:ND) 2 (>A:CAMERA STATE, Enum) 2 (>A:CAMERA VIEW TYPE AND INDEX:0, Enum) 0 (>A:CAMERA VIEW TYPE AND INDEX:1, Enum) 
    (SPLIT:2000) 'flightsimulator' procexist if{ (FOCUS:flightsimulator) } 'flightsimulator2024' procexist if{ (FOCUS:flightsimulator2024) } (SPLIT:200) 
    (L:fsw) 3840 / 2600 * flr (L:fsx) + (L:fsh) 2160 / 1200 * flr (L:fsy) + (VMOXY:%1|%2) (SPLIT:100) (VMOMV:10|10) (SPLIT:100) (VMOMV:-10|-10) 
    (SPLIT:100) (VKD:541-669-162) (VKD:56-184-165-1) (SPLIT:300) (VMOBD:Left) (SPLIT:100) (VMOBU:Left) (SPLIT:300) (VKU:56-184-165-1) (VKU:541-669-162) (SPLIT:3000) 
    (WINDOWTITLESET:WASMINSTRUMENT~0|ND) (SPLIT:1000) (WINDOWPOSITIONSET:ND|10000|10000|1024|1024) 
    (SPLIT:200) 2 (>A:CAMERA STATE, Enum) 1 (>A:CAMERA VIEW TYPE AND INDEX:0, Enum) 1 (>A:CAMERA ACTION COCKPIT VIEW RESET, Bool)
  </Script>
</Initialize>
<Update>
  <Frequency>5</Frequency>
  <Script>
    (CAPTURETOFIP:ND|ndscreen|FULL)
  </Script>
</Update>
</Gauge>

 

Edited September 3, 2025Sep 3 by Lorby_SI

12 hours ago, D1git4l said:

That's awesome! You really do a lot for us! Thank you so much. The easiest thing for you 🙂 I fly most often with the Ifly 737, the Fenix A320, and the RJ from Just Flight, and only on Msfs2024.

So here is a WebPages package. It works the same way as the WebFMCs, using the popout feature.

https://www.dropbox.com/scl/fi/5u2040bucatukuk5sl8yr/nds.zip?rlkey=e2q00u3peydk7ww0g9gjfa5of&dl=0

readme.txt is in the ZIP

Oh all this work! It's incredible! Thank you! I'll take the time tomorrow night after work to install and get everything working properly. It's really crazy! Thanks again

Hello, I finally managed to take the time to test the scripts, and they work perfectly. It's exactly what I needed. Ideally, now I need to learn how to add the PFD. I'll look into that. Thanks again. AAO is truly awesome!