Hi, is it possible to popout the PFD and ND instruments as it is possible in the A321?

Hi @julian2

In FS2020 this could be done by holding 'RIGHT ALT' key + left clicking on the displays.
However at the moment this does not appear to be possible in FS2024.

Thanks!

That would be quite dissapointing. Will this also be on the A350 like this? The popups are working on the A321 and also on the Asobo 737 for example. 

Apologies, it seems the key required to do this was unbound on my end. However I can confirm the issue now on A330s.
Reported to the team. Thanks!

Also have this issue. Works on the A400, but not on A330.

 

Hi, yep. We've noted this. Looking into it for a future update! 🙂 

Any estimate when the popouts will be added? I would love to use this aircraft. 

Any ideas when this will be fixed?

When is this going to be fixed? Thanks!

Sorry to ask again. Is this fixed by now? Or will it ever be fixed? Best regards.

I would also need this functionality implemented ASAP. I normally undock the PFD / ND and Engine Display to 3 seperate square HDMI screens for better immersion. It doesn't work for inibuilds A330.

Any update on this? It’s been 3 months. There’s no way to use my home cockpit Airbus displays as of now 

Edited February 24, 20251 yr by nathan3219

I noticed this thread and am particularly worried that it could also be an issue with the forthcoming A350, redering my home cockpit unworkable, that would be a show stopper for me, heavily invested.  #innibuilds

When can we expect to be able to pop-out the displays in the MSFS2024 inibuilds A330?

@iniBuilds: Please fix this issue. Can you confirm that it will be fixed in SU1? Thank you.

I confirm that POP OUT is NOT ACTIVE in  A330 - A330 Beluga. FS2024. PLEASE UPGRADE IT !!!!!! C MON !!!!

On 3/2/2025 at 1:32 AM, Splinter said:

@iniBuilds: Please fix this issue. Can you confirm that it will be fixed in SU1? Thank you.

I also made a post about this, yet they won’t reply to mine either. Support seems nonexistent for this bug for some reason. A shame…

Not fixed in SU1. Come on iniBuilds, it was reported very early.

 

Please fix this in SU2!   

Inibuilds team! why does this still not work!!!!

Just tried loading the A350, popping out the screens then reloading with the A330 and it works. So this functionality does exsist, it seems to be an issue where while in the A330 its not picking up that you are keying the Right ALT button to launch the popout. This definitly needs to be fixed. I tried it with the A350, and can get almost all the screens to display popped out in the A330, however missing a few such as lower/upper ecam, and MCDU. Tried with the A310, same thing works, just not the right screens. Tried with the INI A320 as the screens in theory would be the same but this does not work, it expands/chops up the PFD accross all the popouts. You need to fix this

Why does INI refuse to respond to this post here or threads about the same issue in discord?

We have not refused to answer anything. The most up-to-date information regarding this report is seen scrolling up on this very post. Myself and Rich have told you all that we know about the issue and have logged it internally. We cannot speak on any timeline. Hopefully it'll roll out with a patch in the near future. 

Thank you for your patience! 

How about my report?

https://forum.inibuilds.com/topic/26144-fma-bug-athr-not-in-white-box-after-levers-set-to-clb/

On 3/19/2025 at 9:00 PM, Eddie said:

We have not refused to answer anything. The most up-to-date information regarding this report is seen scrolling up on this very post. Myself and Rich have told you all that we know about the issue and have logged it internally. We cannot speak on any timeline. Hopefully it'll roll out with a patch in the near future. 

Thank you for your patience! 

 

Hello,

Here is a workaround.

1. Load A310
2. Pop out PFD
3. Pop out ECAM (on FO side) - this will be ND on A330
4. End the flight.
5. Load A330

For FO side pop out Vertical speed&TCAS on CPT side (will be ND on A330) and an Engine gauge (will be PFD).

Cheers.

@support: The workarounds work so it is a bug in the coding. Could you pls let your users know when this bug is being fixed. It was not fixed in su1. I am asking support if it is going to be fixed in su2, with a hotfix or not at all? Please be clear and open. That’s what I expect from any customer service. Thank you.