All Activity

You have to fill in all the required parameters in the first 4 pages or so like BOD distance etc. Happened to me as well until I figured it out

Added Nose wheel to the binding, changed the input sensitivities in MSFS and it's working great now. Thanks !

Great software (A350) but Inibuilds is killing me with WASM crashes every time I try to change my arrival runway or approach transitions during a flight. EXTREMELY frustrating at the tail end of a 13 hour flight that goes right into the garbage! This is NOT what I paid for. For the price of their aircraft I would expect more after the initial release has been out for this length of time. My platform is MSFS 2020 on Windows 11. Pls lmk if anyone has managed a fix or workaroud to this issue, as I see MANY posts with the same issue but no reliable resolution. Thank you.

Also I’m pretty sure when you’re switching to Radio Navigation, the the distances on the HSI are still to the INS waypoints instead of to the tuned VOR/Dme which it should normally do.

Hello everyone, I have the problem that whenever I want to use the Thrustmanagement mode to climb, it shows the EPR 000 and the engines spool down. I have set everything up correctly including both PMS, have already played around with switching of probe Heat, and many more things. I would be really glad if anyone had a solution or at least knows if this is a bug or I’m missing something systemwise. kind regards Elias!

Please add the user keyboard entry features for INS, thanks

Crashed when selecting runway ils approach in FME. Aircraft: A350-900 default cabin Simulator: FS2024 Version: iniManager 1.2.4 Navdata Method: NAVIGRAPH OFP: HAAB-OEMA as attachedHAABOEMA_PDF_1775126693.ba090cbe.pdf WASM Error: Specs: AMD 9800X3D DDR5-6000 64G RX9070XT Autosave File: 1775134946.bin

cant find the ap disconnect, or toga bind thats on the yolk

When selecting the RADIO/INS switch to INS the HSI correctly switches to display true compass information instead of magnetic compass information, however the MAG/TRUE flag does not switch to TRUE and instead continues to show MAG.

Pero cuando lo generas en la pista, funciona bien. (I'll record a video when I get home)

Intenté aparecer en el cielo y aparece descendido, y cuando el avión se avería por exceso de velocidad, también aparece descendido al reaparecer.

Hello, The issue with the pink vehicles has nothing to do with the FAOR Johannesburg Scenery by Inibuilds! It was caused by a corrupted scenery package named “microsoft-world-point-of-interest” in my Official2020/OneStore folder

During my decent I was descending in VS mode at 2500 and I was a bit high on the path so I opened the speed brakes for a bit and when I closed the speed brakes the nose pitch hard up over 6000 feet a minute on the VSI and I cycled VS off then on and VS window had 8500 feet per minute up I had to quick run the VS back down to 2500 a minute down. The autopilot was very slow to respond even when I ran the VS back down I gained a few thousand feet and lost a ton of airspeed.

Waypoints on a SID ( such as e.g. DF526, DF527, etc ) would just be inserted as a normal waypoint. Floating waypoints on a SID ( such as „when passing ALT xyz turn left…“ ) would need to be flown raw data anyway. T/C and T/D would not be entered on the INS anyway, they are calculated manually and thence be related to a waypoints ( distance inbound/outbound of a waypoint ). Navigraph charts is not an option in VR, as it costs performance and breaks the immersion.

Sounds simple, but what if You want to hand fly a SID ? Where should WPT1 be ? How about TOC and TOD - do You want none, one or bothe inserted as a WPT ? Opening up Your OFP in Navicharts You can use the new hnad drawing tool to write the numbers for each required WPT.

For the purists amongst us, who like to insert each and every waypoint manually into the INS ( just as real flight crews did ) it would be of great benefit if there would be an option to manually number the Waypoints on the OFP. This would aid in assigning the Waypoints to their slot-numbers in the INS. For instance such as a manually placeable circled number next to the waypoints on the OFP ( like selectable „stickers“ numbered from 1 to 9 ). Best regards

Further information of unexpected behaviour during test: Loaded at EGVN on threshold RWY 25 with flightplan to EDDV loaded. Aligned all three INS to current location correctly (51 45.2N 001 33.8W), loaded plan on PFB and sent to INS. Checked waypoints loaded correctly. Set both sides to INS and verified HSI readouts correct. Changed INS 1 posn to same coords but E instead of W. Observed Pilot HSI change to give a larger distance ~120nm and lateral deviation before it then returned to match Copilot side. I don't believe the Tristar INS' were loaded in a Triple Mix config and almost certainly didn't have error rejection in so Pilot INS should continue to report erroneously. See below video (note DME did not change in this recording) https://drive.google.com/file/d/10QXu7MvoKVst0D9W2GsB4cAMIknQ5Xi-/view?usp=sharing

Hi. The GSX profile from the inibuilds installer is missing many remote parking stands. For example on B, F & D apron. See my screenshot. Any chance to get an profile update here?

Really a minor issue: GW and fuel seems to be displayed in lbs and not in kg´s at the FI panel in it´s specific gauge after pressing the button for display. Units are set to metric at the EFB.

There is blue flickering on the right main wheel well door on the Pan Am livery from the iniManager.

It's wildly wrong. I put an incorrect position in INS 1 (E instead of W) on a nav update and it somehow still followed the track as though it was in the correct position.

Simply put, the reference aircraft we had access to had the gauges you see in sim.

Same...

Ouch!! Same fate as the B-1B?

I believe Rudder Axis