All Activity

HUES - ITA Airways Fleet 2026 - A359 ini. there were these liveries, but I've already deleted them. There was a Bat file inside the folder for deletion. I think I've deleted everything.

Ive had this issue since day one. But what works for me is to cycle the power whether it be APU or Ground power. I havent needed to restart the sim.

I’ve now recorded a new video, where I tested five airports: ZSPD (Shanghai) ✕ ZBAA (Beijing) ✓ ZUCK (Chongqing) ✓ ZGGG (Guangzhou) ✓ VHHH (Hong Kong) ✕ Besides, EGLL, EGKK and RKSI are also among the airports I’ve tried where the ILS still can’t connect.

so I need to get the new version on inimanager?

I’m genuinely shocked that all your gauges respond as soon as you enter the ILS frequency, while absolutely nothing happens on my end. Earlier today, I landed on Runway 25C using the Aerosoft A340-600. After pressing the APPR button, the entire ILS system engaged and started working. As for the L-1011(1.0.4), the only airport where I’ve ever successfully activated ILS is ZUCK (samscene3d). At that time, I didn’t even check whether I was in VLOC mode. That’s because I’ve never turned on GPS or INS+GPS in the PFB before — I’ve always been using pure INS mode only.

Im not sure what to add 🫠 https://www.youtube.com/watch?v=KkGpmhAK8FM Although I don't think it will make a difference, Is Navigraph up to date for the sim? Have you updated to the Tristar to V1.0.4? Does the radio freq work on another aircraft in the same location? Have you tried any other approach elsewhere in the world to check if the RADIO is working?

[WASM][IO] ./data\Textures\RMP\RMP-Main.png not found [WASM][IO] ./data/Textures/FCU/FCUCompo1k.png not found [WASM][IO] ./data\Textures\ECAM\Wheel1000More.png not found [WASM][IO] /Data\Textures\PFD\PFDA350Elements.png is neither a vfs path ('.\') or work path ('\work\)' WASM: Error during MFD_gauge_update execution. Error code : 0xc0000005 WASM: Module vfs://inibuilds-aircraft-a350/SimObjects/Airplanes/A350/attachments/inibuilds/Function_Interior_A350/panel/inibuilds-A350.wasm is now dirty Aircraft: A350-900 Simulator: FS2024 Version: 1.2.5 iniManager Navdata Method: NAVIGRAPH

Yes, I have thrustmaster TCA Quadrant Airbus edition and add-ons & side stick.

I relaunched the game and spawned on Runway 25C. I confirmed I was in VLOC mode, but none of the other data showed up at all. It seems entering the ILS frequency doesn’t load any additional ILS information for me, so my ILS button still won’t light up normally.

Actually, the HSI flickered at around 9:26 in my video — that was me pressing my custom-bound shortcut key.

Brilliant video, nice watching someone else do it. You and I, while we did the same departure, we have a few differences. (Use VOR/HDG until the 104 RADIAL after WHISKY, then get bored and hit INS), and usually MTOW 226,000kg. If a light hop to RJTT, then I will derate the engines and use manual thrust and VS to 250ias since I dont trust the TM/VNAV combo. One thing your video didn't do (that mine does), when you dialled in a new alt increase, your ALT stayed at "7000 ALT" until you hit VNAV. Mine almost always jumps up to "7200 ALT CAP" (always adds 200 feet to your currently selected alt) and starts the slow climb, regardless of what has been dialled into the ALT box. Did you use 1.0.4 or 5? The runway trim wheel happens infrequently but does happen for me. Made a video, its gone somewhere on my computer. Will wait till the new update this week and try again on Thursday. Thank you for your videos!

As pointed out, the radio freq data is not making it to the VOR/DME or HSI for some reason. Can you try the first thing again with the TOGGLE GPS DRIVES NAV1 whilst on the ground at an VHHH tuned to an ILS freq in RADIO and see if the instruments change? Maybe try selecting GPS option from the PFB and select CDI to change over to VLOC.. then turn the GPS off again in the PFB to see it that changes it over.

I've recorded a complete full flight along the VMMC–VHHH (Runway 25C) route. I uploaded the video to YouTube using some alternative methods. My recording setup and procedures weren’t very standardized or professional, and the video might be a bit longer than usual, so please bear with me. Also, could you help me figure out why the ILS approach was unavailable?

The list has been submitted to the team, I can't guarantee what is added, or when. Thank you.

Hi, this issue has been raised to the team, I will add this to the log for them, thank you.

Hi, do you have Hues Core or any other mods. Is this PC or Xbox?

Comparison with Fenix A320: In the Fenix A320, the SID altitude constraint is correctly capped at 7,000 ft and is consistently displayed on the altitude tape, navigation display (ND), and FMS, even when the FCU altitude is set to FL370. In contrast, on the A350, recent builds appear to have a regression. The altitude tape does not display the SID altitude constraint during pre-flight setup. Instead, the constraint only becomes visible after takeoff, once thrust is reduced to CLB. This behavior was not observed in earlier A350 builds, suggesting a recent issue affecting constraint visualization during initial flight setup.

I've removed all the liveries, and I've removed and reinstalled the aircraft itself. Nothing is working.

After hours of troubleshooting, I found a fix to this problem, but it only works if you have Navigraph subscription. The cause: This problem is actually not specific to just iniBuilds default A320/A330, it's applicable to all Asobo-distributed aircraft, such as ATR. It's caused by combination of factors, among them how MSFS2024 handles package priorities and how some 3rd party airports are able to override any other navdata. Apparently, some 3rd party airports somehow override MSFS default or Navigraph data, but they don't have airport-related fixpoints and other things properly defined in them, so this causes those fixpoints in airport's SIDs and STARs to have 0,0 coordinates. This is a reason why this problem never occurs for default airports. Many custom airports are also working fine. It's just those custom airports that have their own navigation layer are causing this problem. In my case, I specifically had it occur on freeware airports developed by x-flight team. The fix: If you are using Navigraph, you can fix this by setting priority of Navigraph data higher, so it takes over navdata in airport scenery. Open your Content.xml (located in [your_windows_username]\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\[your_MSFS_username]. In the file, find following entries: <Package name="communityfs24-navigraph-nav-base" active="Activated"/> <Package name="communityfs24-navigraph-nav-jepp" active="Activated"/> Now give highest priority to this data: <Package name="communityfs24-navigraph-nav-base" active="Activated" priority="100"/> <Package name="communityfs24-navigraph-nav-jepp" active="Activated" priority="100"/> After I did this, all my SIDs and STARs started to load correct for both iniBuilds default Airbuses and ATR. Sorry, I don't know if it's possible to fix this if you are not using Navigraph.

Any acknoledgement from the Ini team please? Don't forget that a serious competitor is rising up.

That’s great! For me it would be the air transit liveries and variations, KLM, American, Lufthansa, delta! Many thanks!

Ok, it doesn't sound like an ILS/LOC button issue. Can you upload a screenshot of the instrument panel including the glaresheild? Do you use this aircraft with the GPS?

UPDATE: Workaround: I restarted the simulator, powered up the aircraft (battery + ground power), waited for the GPS to boot up and the ENT button on the GPS worked as expected to get past the "OK?" prompt. Restarting the flight would be worth a shot if anyone else runs into this. Key here is to make sure the GPS is fully on before performing a bunch of other steps then realizing you can't interact with it. Will incorporate this in my startup procedure. Might be worth suggesting in the following topic https://forum.inibuilds.com/topic/35983-how-to-gps-navigation-ins-gps/

TriStar version 1.0.4 MSFS Update 5 version 1.7.27.0 Mode: INS + GPS Is there any trick to getting past the "OK?" blinking prompt on the Garmin 530? I started by trying the ENT button then all other buttons on the unit (including the big push buttons). Tried with various power sources--ground, APU and all engines on. Plus, double checked that all bus ties were connected (w/ all engines running). Ensured the master radio buttons were turned on. Tried after INS was fully aligned and in NAV. And tried unmapping the Avionics Master key binding which was set.

Hello, the new update 1.0.4 is still not available for the marketplace version. If you have the inibuilds PC Version...you should have the newest Version.