All Activity

As you might know, the Enroute tab in the OIS is an infinite scrollable map of the world. For some reason, my blue aircraft location indicated seems to randomly move to the next world over to the right in the middle of flights for no apparent reason. In the first screenshot, you can see that the route shows up correctly, but the aircraft location indicator is nowhere to be seen. The second screenshot shows that after scrolling to the right one world, the aircraft shows up again in the place it's supposed to be, but in the wrong world.

I've just purchased LGZA for MSFS 2020 via marketplace. A little disappointed to find that the runway edge lighting is all incorrectly depicted as blue taxiway edge lights! It even shows in the product gallery photos of the iniBuilds store. Can we get an update for this to correct it? I'm also fairly sure that LGZA does not have CL lights.

Ah, okay, I'm guessing that might be my problem. I only load the 777 PMDG NavData package using the Navigraph Hub, not the gereral Navigraph Airac into MSFS. Do I need both the 777 Airac cycle and the Navigraph base cycle loaded together? I have never used the Navigraph Base Airac in the past, just the 777 package and have never had any problems. Thanks.

Would be a perfect airport for ini to do at some point!

Username for simbrief/navigraph is correct. I can't seem to get passed this error.

Thank you for this, I looked through some forums and users are saying that this is an issue with Default Heathrow when flying into 27L/09R; as you stated above the default EGLL is disabled. What I think may have happened is the airport navdata for EGLL default is being prioritized instead of the scenery data. There is a way to check this; Launch MSFS 2024. Go to Options from the top menu, then select General Options. Scroll down the left-hand menu and select Experimental. Find the Package Reorder Tool and toggle it ON. You will see a list of installed scenery packages. Low-level base content is at the top (and usually locked). Add-on scenery and navdata are at the bottom. Before you re-order anything, attach an additional screenshot of the load order from when you open it that way I can at least verify before any changes are made that might not be necessary. Thanks Use the Up and Down arrows to arrange the order. To place navdata first: Move the "navigraph-nav-base" package near the top. To give scenery priority: Move your custom 3rd-party airport or navdata folders below the default Asobo scenery so they overwrite it.

Hi Robert. I sent you a PM. Please look at it. Thanks - Trevor

Hi, thanks for the reply. I'm using Navigraph and with a different cycle, the default EGLL is disabled. Never done a video before, so not sure on how to, but I've done some screen grabs, hope they help. Again, full auto land on 27L and the same amount of offset occurred. Thanks.

Try the following: 1 (>L:INI_MCDU1_ENTER) Works on my setup. Kevin

With your initial fuel load, you should have been running Tank to Engine with your crossfeeds closed. With all crossfeed valves open and all pumps on, you're basically seeing which pumps have the higher output...in this case, Tank 1 pumps. That's why you have an imbalance of 4,500 lbs between tanks 1 and 3.

Hi, I have a very similar repeatable crash to the others here. 100% reproducible when manipulating the STAR on the ARRIVAL page. 1.08 PW Freighter, loading from cold and dark on the ramp KPAE-KGEG, route: KPAE/34L N0478F290 DCT ZADON DCT ZELAK DCT ZIRAN DCT ZOOMR ZOOMR2 KGEG/21 Flightplan loaded via SimBrief. When going to insert the STAR, only certain selections give me the *INSERT prompt at 6L. The way the flight plan is constructed needs the STAR without a transition (which you normally do by not selecting a transition). If you play around in the menu you can get it to give you the *INSERT prompt (try selecting an approach, selecting and then deselecting a transition, etc. and when it does give you the insert prompt, press it and it produces a WASM crash for me every time.

Sorry, should be public now.

Can someone please tell me how to get liveries on the A330's in msfs,nothing works.

Venice Beach and Hooper are still being addressed, I'll have to update the team on SOFI following CU13 and 1.0.2

Video is private.

Hi, I've now tried uninstalling and rebooting then reinstalling, still no luck. Hopefully the video helps https://youtu.be/tJUHArSxCeM

Any update on this?

Hey, I'll ask the team on Monday as most of the guys that would be able to give me an answer are gonna be away for the weekend, until then and then if you don't hear back in here by Wednesday bump this thread. Thanks

Disable autopilot first for best effect. Make sure to disable all THREE primary and secondary flight computers.

Issues seem to circle around the STAR insertion for sure. Come on, Inibuilds, please give us the A300 back. I purchased a few days ago and flew with it exactly 4 times, only reached my destination once, all because of this.

Please make it so you can use the EFB on an external device like your tablet or something like they do in the fenix. The only reason I haven’t bought any inibuilds plane is because of this 😭😩🥺🙏🙏🙏🙏🙏

Dear Team, any chance for an estimate when I can get at least the "Enter Key" information? Everything else works fine with the input of the MCDU with the latest version. Kind regards Airliner001

Aircraft: A350-900 Simulator: FS2024 Navdata Method: MSFS OFP: PFD Attached WASM Error: Imported flight plan and was about to enter W&B Data. Specs: Intel(R) Core(TM) i9-10900KF CPU @ 3.70GHz (3.70 GHz), 64gb DDR4 RAM, ASUS TUF Gaming GeForce RTX 5080 OC90YV0M30-M0NA00 Autosave File: attached1780165438.bin LFPGLSZH_PDF_1780163962.b533e496.pdf

Another WASM crash, this one is pretty reproducible KMHT-KPHL KMHT/35 PPORT4 CCC DCT MANTA Q439 BRIGS JIIMS4 KPHL/I27R When executing the KPHL STAR and approach, it instantly WASM crashes Using the A300-600F PW SPECS RTX 5070 I9 9700k 32GB ram MSFS 2024 1.7.27.0 Using Navigraph