MikeTheFlyer

Can we expect more realistic implementation on the OIS in any future update, so every system can be tested. And pages like the Aircraft Control domain. And can we expect a implementation of the maintenance pannel.

On this KLM a330-300 (GE) the landing gear has a a330-200 decall. Should be a330-300.

Yeah I know that. It was just post informing you guys about it. Not that im asking support or anything. But thanks

Tried to launch the A300 in the sim, and faced infinite wasm loading. I run the sim with only the a300 in the community folder (No other 3 party addons, or marketplace content), Prior to loading the wasm folder was completly empty. There are also no background addons running like GSX engine, or fenix, or Navigraph simlink or anything like that. Tried reinstalling the aircraft from the inimanager, and reinstaled the manager itself. I tried 2 times now and the first try it was loading for 1hour+ with no succes and the second try is now 15 min in. Im fairly known to the SDK and how WASM works, so all ususal user error are mostly ruled out here. Im running Su7 Beta. And this message isnt a "problem post" or "Bug post" it is just to let you guys know that the plane doesnt work in Su7 beta so far, plus this happend to all my other inibuilds planes aswell like the a340-300, a350, tristar.

How to get acces to discord Inibuilds without a phone number since my brother uses mine phone number on his discord account. Thanks in advance!

You dont see Rnp in youre FMS since a RNP approach is a rnav based approach. RNP is basicly a rnav approach but with extra performance monitoring and alerting. RNP allows for much tighter, scalable accuracy (down to 0.1 NM or less). So that is why there are no "RNP" on youre arrival page, for the rest im unknown on how good the planes flies therse approaches.

The autopilot doesnt follow the glideslope if the localiser isnt caputured yet. So you will need loc* or loc for the gs to be capsured. other wise it will just stay level.

The Inibuilds A350 has quite alright system airbus depth and exceeded my inital expectation, however, after spending significant time digging into emergency procedures and non-normal scenarios, there is a clear disconnect between the underlying depth of the aircraft's ECAM logic and our ability to actually utilize it via the EFB Failure Manager: 1. Advanced ECAM Logic with Limited Failure AccessThe issue that the a350 has is that the A350 features rich, highly accurate ECAM procedures and conditional logic for complex system failures. Yet, the current EFB failure menu only offers a very basic, high-level subset of failure toggles (e.g., basic engine failures, basic A-Ice valves, and simple TCAS/XPDR faults). This is quite a missed potentional, because the EFB lacks toggles for core system nodes (like individual ADRs, IRs,), a huge portion of the complex ECAM logic and procedural depth you built cannot be intentionally simulated or trained for. 2. Example: Air Data & Unreliable Speed IndicationAs a clear example, the ECAM contains full interactive checklists and switching logic for NAV UNRELIABLE AIRSPEED and NAV ADR 1+2+3 FAULT (complete with flight control law degradations, Backup Speed Scale options, and pitch/thrust memory item steps). However,s a resul looking under ATA-34 Navigation in the EFB, there are zero options to induce pitot/static blockages or individual ADR faults. At, one of the most vital non-normal training scenarios in modern Airbus flying can't actually be triggered by the user. I would hope Inibuilds will expand the EFB Failure Manager across the ATA chapters to allow triggering granular failures that feed directly into these built-in ECAM states such as in this example: ATA-34: Pitot/Static probe blockages, individual ADR/IR faults, Air Data switching failures. But this isnt specific for the UNRELIABLE SPEED, more overall. Because the ecam pages exist but cant be used realisticly. The system have so much potentional