I got the webfmc working, but would like to recover the hidden window (the as530 window).  I can't find it, and even when I pop the window out without AAO running I cannot find it.

Is there a way to recover it?

The popout has been moved off screen, it's not really hidden. Are you saying that the sim remebers that? That's bad. 

I will take a look at the code tonight and let you know how to get it back into the default location.

Yeah, looks like it doesn't come back.   Thanks!

50 minutes ago, dc9116 said:

Yeah, looks like it doesn't come back.   Thanks!

When the web page is open and shows the 530, Issue this script command in the AAO script editor:

(WINDOWPOSITIONSET:AS530|0|0|512|512)

This should bring the screen back to the main monitors' top left corner. Do not close it! End your flight in the sim by going back to the main menu. When I do it this way, the sim remembers the last location and size of the pop out.

Sorry for that, this was unexpected. MSFS is sometimes a bit weird in its ways.

Edited May 30, 20251 yr by Lorby_SI

OK, so here is what I found out: when a pop out window is closed (manually or automatically by AAO) then the sim doesn't remember it's last location. It will still be off screen.

I made a new version of the WebFMCs real quick, where the window is only relocated back to the main screen, but not closed. Do not close it manually either - instead end your flight in the sim by going back to the main menu. When I do this, the position and size of the pop out is remembered, and will be the same when you pop out the instrument manually again.

thanks for the response.  I issued the command and it got the window back.  I did download and run the new fmc.  Will continue to play with it.  Also, I assume I can copy your code and use it for another airplane.  I have the justflight arrow package and it names the window A530_1.   

I do want to thank you for a great product.  There have been a few purchase that didn't pan out the way I expected.  This is not one of them.

I don't use this product to its fullest extent, but MSFS would not be the same for me without it.

7 hours ago, dc9116 said:

Also, I assume I can copy your code and use it for another airplane.

Yes, sure. 

Hey, wanted to give this also a try and did it with the A2A Comanche and the GNS530 Popout Window, but whenever i click on Asobo GNS530 on the Webpage and the GNS Interface opens the SIM Freezes 😞

With Cessna 172SP it works, so i guess its something with A2A Comanche

7 minutes ago, Bam2000 said:

Hey, wanted to give this also a try and did it with the A2A Comanche and the GNS530 Popout Window, but whenever i click on Asobo GNS530 on the Webpage and the GNS Interface opens the SIM Freezes 😞

With Cessna 172SP it works, so i guess its something with A2A Comanche

The sim freezing when you pop out things is not unheard of. I have a tester who cannot pop out anything in any aircraft - the sim always freezes. To my best knowledge neither cause nor cure are known yet.

40 minutes ago, Lorby_SI said:

The sim freezing when you pop out things is not unheard of. I have a tester who cannot pop out anything in any aircraft - the sim always freezes. To my best knowledge neither cause nor cure are known yet.

Yes super weird, only happening with the a2a Comanche , using the gns530 in Cessna 172 works like a charm and when I popout the gns530 it’s shown on the webpage. Weird I don’t even get to pop out the gns530 in the Comanche, it freezes as soon as the gns530 webpage opens

41 minutes ago, Bam2000 said:

Yes super weird, only happening with the a2a Comanche , using the gns530 in Cessna 172 works like a charm and when I popout the gns530 it’s shown on the webpage. Weird I don’t even get to pop out the gns530 in the Comanche, it freezes as soon as the gns530 webpage opens

I think that this is caused by one of the C++ modules in that plane. The freeze also happens when AAO just queries the current windows while the A2A is on screen. I've seen this before, some programs don't like it when another process asks for the title of their own process window(s) (even hidden ones). Must be one of those.

Edited May 31, 20251 yr by Lorby_SI

15 hours ago, Bam2000 said:

Yes super weird, only happening with the a2a Comanche , using the gns530 in Cessna 172 works like a charm and when I popout the gns530 it’s shown on the webpage. Weird I don’t even get to pop out the gns530 in the Comanche, it freezes as soon as the gns530 webpage opens

It is working for me when I do things the other way round. Pop out the 530 first from the A2A Comanche, then go to the AAO web page. The web page then grabs the GNS screen and the simulator continues to work. When your flight is finished, remember to go back to the FMC selection page in your browser (this brings back the GNS on your main screen) and in the sim then go back to the world menu, so the sim closes the popout. Otherwise the sim apparently remembers the off-screen position.

Edited June 1, 20251 yr by Lorby_SI

Hi Lorby!

On the P180, I think the aspect ratio of the screen in the sim is slightly wider than the frame used in the web page, so it's cropping part of the text, particularly the bottom line and some of the right. Although the cdu.png image file itself looks correct, so maybe it's the pixel dimensions in index.html or config.js?

10 hours ago, aaronpriest said:

Hi Lorby!

On the P180, I think the aspect ratio of the screen in the sim is slightly wider than the frame used in the web page, so it's cropping part of the text, particularly the bottom line and some of the right. Although the cdu.png image file itself looks correct, so maybe it's the pixel dimensions in index.html or config.js?

This can also happen when your monitor setup has a slightly different idea about the pixel-level resolution of off-screen assets. That's the reason why I made a separate config file, so you can adapt it to your display(s). So config.js would be the one to change.

Overall, I'm really happy with these new WebFMCs, they really work much better than I would have expected and have a lot of potential uses. Thanks!

 

For the P180, this change to the config.js fixed the clipping at the bottom and right and gets the text aligned correctly with the buttons for me:

const screenXY = "left:25px; top:62px;";
const screenWidthHeight = "width:660px; height:440px;";

Also, for the P180, the buttons in the index.html had white outlines, those should be made transparent like the others.

 

For the AS530, this worked for me to fit the window correctly:

const screenXY = "left:129px; top:47px;";
const screenWidthHeight = "width:538px; height:404px;";