All Activity

Who knows where they are getting data from. Fenix told us that most of the stuff is scripted and doesnt take into account RW variables. In other words, we have some fakery going on.... MY A380 is in the hangar for now. Honesty, im not real keen on buying anymore product form ini...Its good plane, just not good enough. Cheers!

Good Evening, I'm guessing what's the right procedure to load a flight plan made with the MSFS2024 flight planner or with the original LSFS2024 EFB. I'm asking because in this article is confirmed as possible. Maybe I misunderstood the article Thanks iniBuilds A350 Airliner for Microsoft Flight Simulator 2024 & 2020 v1.0.11 Released - Updates - iniBuilds Forum

Are you streamed version or downloaded version? For Streamed, somehow still v1.0.1, but already v1.0.3 if you downloaded it, and restart Sim. I dunno why 🤷

Good Afternoon All. I am in the process of trying to make a setup for the Streamdeck and Streamdeck + for the L1011 and cannot find the display output variables for the Vertical Speed, Altitude Select, and EPR (for the autothrottle). I will be using Hanger Control to do this (and possibly AAO). Also, I am trying to make an INS Touch Panel using Hanger Control and GlassOut, and want to know if it is possible to get the panel, the knobs, and the buttons as separate files s that I can animate them. This is my first attempt at this so it will be interesting to see how it goes. I have most of the Autopilot and all of my Axis programmed through Hanger Control and Streamdeck. Thank You

No, But i did have a wasm crash during the decent. irratating indeed. EDIT : and a second WASM on final, after resetting via autosave... back in the hangar she goes.\

After 1.0.3 the OIT is dead. Clicking the screen, which used to boot it, does nothing. Brightness is already at BRT, GPU and batteries are on, WASM is not crashing, and a full Marketplace reinstall changes nothing. The EFB just sits on "Awaiting Data / Initiated through OIS", so takeoff performance is gone. Your own FAQ still tells us to use an "OIS PWR" switch on the side console. That switch is not there. The actual power button is now hidden behind the oxygen mask box, by the yellow hose, behind the tiller, and it is off by default in cold and dark. Nobody documented this. People on this thread only found it by accident. I spent hours clearing WASM, reinstalling, and hunting for a button that your manual does not show. Shipping a paid aircraft update that silently kills the only performance calculator, then hiding the fix behind the oxygen mask, is a bad release. Put the computer back on by default, put the switch where the manual says it is, and stop making customers reverse-engineer a cockpit to get V-speeds.

Hey yall, so I was hesitant to download the A380 because I had issues with the A350's FMS, mainly the click spots (I use trackir5). I bought the A380 and man do I love that bird! With the A380, I'm able to look down right at the FMS and click exactly on what I want with no issue. With the A350 (my other favorite bird), I have to move my cursor around multiple spots in order for the click to register. My question is, are the A350 amd A380 displays essentially the same? If so, is there a hot fix to bring this over to the A350?

Thanks, but I'm not looking for a moving map. I'm referring to the map screen as indicated in the manual:

Anybody having these issues ? front nose gear isn't turning when taxing ? fuel not loading even though you tell the plane to load the fuel only engine 1 stats up and gets to 3%, everything stays at 0% all screens for the instruments are red.

Severe stuttering during take-off and landing when the NVIDIA app is installed. Even though neither the MSFS 2024 game optimisation nor the overlays are enabled. If I uninstall the app, the stuttering during take-off and landing disappears. Once reinstalled, the stuttering returns. Tested in EDDF and OMDBV2 I’m only speaking for myself, as there shouldn’t actually be any connection. But is there a problem with the A380 and the NVIDIA app?

Welcome to Inibuilds patches....!!!

Sorry what do you mean programmed approach i need to planned it in the fms or where?

You can click on this button, next to the oxygen mask. I assume this is a bug, and will be fixed, but it worked for me.

After exhaustive attempts to nail down the correct behaviours for this throttle, it is clear that there is a signal issue in MSFS 2024 from the Winctrl throttle with this V1.0.3 A380 selected in MSFS 2024. Multiple attempts, cleaning the throttle data config, setting axis to 0 to 100%, setting throttle axis as per forum instructions, following the forum instructions to the letter, 4 axis selection vs 2 axis selection, single stroke double shaft in simapp, re-calibrating in simapp, confirming Winctrl firmware is up to date, confirming simapp is up to date, and all points in between end in the same situation. When viewing the Current Axis Value in both throttle axis 0-100% AND throttle axis, the signal will increase when moving to the CL ident, (engine to 69%), then return to the idle signal value (engine at 50%) when moving up to the FLX ident. This occurs before and after calibration. NOTE: when only moving a throttle during a scan to the FLX position, a full signal is registered. Moving to TOGA reduces signal strength back to 50% I currently stream the A380, but tbh, the original download at release was to my PC and the defect appeared then. Uninstall and re-install has zero effect. For reference, every single other aircraft I use with the Winctrl throttle behaves correctly. Fenix, Ini A350, etc, and has done since Fenix release and Ini A350 release. Nil change to my set up. Please ingest the situation here....If I am missing a basic setting change, I would love to understand that.

Just so you know, the METOTS issue still hasnt been fixed since the last updaete (1.0.3), even though mentioned that it is.

Well the crash has been submitted

Yes to both

Thanks it worked for the jetway creation Thanks it worked for the jetway creation. Still not seeing any passangers coming through.

i am using the xbox controller

It seems to be a widespread issue among Xbox users. Which raises the question: If this is not a particular niche issue some unlucky ones are having why on gods green earth was this not detected in testing the update?

Hello, Since updating to v1.0.3 I have been experiencing the following issues, none of which were present in the previous version. 1) Incorrect path drawn by the FMS on arrival/approach Arriving into SCEL via the UMKA6A arrival (SAFEL - UGOLA - AMB25 - PUMAR - TEGEB - FI17L) for the ILS Z RWY 17L, the FMS computed and displayed a path that does not match the published procedure. With NAV engaged and the approach armed, the aircraft followed this incorrect path and deviated from the arrival track instead of flying the published legs towards the 177° final approach course. 2) DIR TO does not recover the route To correct the deviation I performed a DIR TO a waypoint on the approach. After the DIR TO, the aircraft did not track properly to the waypoint and was unable to re-intercept the flight plan route. The recorded ground track shows the aircraft wandering west of the procedure before finally joining final. Expected: the FMS draws and flies the procedure as published, and a DIR TO takes the aircraft directly to the selected waypoint and resumes the flight plan from there. 3) Light states reported incorrectly via SimVars The aircraft is not reporting the exterior light states correctly through the standard SimVars. With the BEACON and STROBE lights switched ON in the cockpit for the whole flight, external applications reading the SimVars see them as OFF. My flight tracker (NewSky) logged Beacon: OFF and Strobe: OFF and penalised the flight with "No BEACON lights for 15886s when required" and "No STROBE lights for 14900s when required", which is essentially the entire flight. Expected: the light SimVars (LIGHT BEACON, LIGHT STROBE, etc.) reflect the actual switch positions in the cockpit, as they did before 1.0.3. Steps to reproduce: 1. Load the A380 v1.0.3 and plan a flight to SCEL with the UMKA6A arrival and ILS Z RWY 17L. 2. Fly the arrival in NAV with managed descent and observe the path drawn on the ND. 3. Perform a DIR TO a waypoint on the approach and observe the aircraft's tracking. 4. With BEACON and STROBE ON, read the light SimVars from any external tool. Attachments: - PFD/ND screenshot during the arrival - Recorded ground track of the approach - Published chart with the expected route - NewSky light log and flight report I can provide more details or run further tests if needed. Thank you.

does plane work with FSUIPC ?

Hello! This is off topic but when can i expect the 1.0.10 update on Xbox?

Hello same for me since 1.0.3 Xbox