All Activity

Today I wanted to enter some along track waypoints for my etops entry points and encountered two issues: For one i could not enter them from the coorinate waypoints that I had imported, but had to enter it from the last non-oceanic waypoint. I tried to enter it as 47N015W/+93 an as 4715N/+93, which both was met with a message "invalid navaid". What worked is entering it from Etiki as Etiki/+353. It then was inserted distance whise at the correct place, but somehow the waypoint, in this case PD03, is laterally offset from the original track. This should definitely not happen with along track waypoints.

v1.0.2 of iniBuilds Ponta Delgada (LPPD) for MSFS 2020 has been released. This update now splits the FS20 and FS24 downloads, adjusts ortho colouring as much as possible, fixes some default building exclusions and more. This update can be downloaded via the iniManager. v1.0.2 - Adjusted ortho colouring as much as possible - Added airline codes to parking - Fixed non-excluded default buildings

v1.0.2 of iniBuilds Ponta Delgada (LPPD) for MSFS 2024 has been released. This update now splits the FS20 and FS24 downloads, adjusts ortho colouring as much as possible, fixes terrain and more. This update can be downloaded via the iniManager. v1.0.2 - FS24 exclusive - Adjusted ortho colouring as much as possible - Fixed broken terrain/cliffs in FS24 - Added airline codes to parking - Fixed non-excluded default buildings - Adjusted LODs for some GSE elements - Removed exaggerated tire gum (white marks on taxiways - FS24 feature)

v1.2.1 of iniBuilds Honolulu (PHNL) for MSFS has been released. This update addresses some missing jetways, incorrect gate signage and makes taxisigns less blurry in FS24. This update can be downloaded via the iniManager. v1.2.1 - Fixed missing jetways C4, E9 - Fixed incorrect gate number E5/E9 - Fixed blue texture on JW gate number - Added GSX profile v1.5 - Taxisigns in FS24 should now be less blurry

Hi Guys, I don't know if anyone has had a similar issue, but I was recently doing a long haul flight from Sydney to Abu Dhabi and had been cruising for just over an hour, I was enjoying the quite stunning sunset whilst having a snack and vibing to music and then all of a sudden the in game altitude reader (the part that is built by microsoft and reads the altitude and speed whilst in external view) starting reading a sudden decent and I could visibly see the aircraft lurching forward and closer to the ground. I tried pulling back on my sidestick (Thrustmaster Airbus Sidestick) to get 0 response from the aircraft. Along with the loss of control, all of the inflight screens had frozen and you couldn't disable or enable anything on the lower half of the jet (auto pilot and thrust levers were inop and all the visual displays were still showing I was at FL340 at Mach 0.85) however the overhead panel was still active and I was able to turn on the APU before I crashed. I have no idea if it is a setting I need to disable to ensure that this doesn't happen again however, after reading some forums from the start of this year it seems like an ongoing issue. If anyone knows how to fix it or if it is a genuine glitch would be good to know. I do understand there is always a lot of coding that goes into something like this and kudos to the inibuilds because apart from this issue, it has been a joy to fly. Thanks, look forward to hearing back from someone!

Specifically EGLL. When I install for MS2024 I have multiple options in inimanager that allow switching such as detail scenery or clutter on and off. This is when the scenery has just been installed. If I go back into inimanager later to tweak them further they are missing, I have to uninstall and reinstall the scenery to get the options back and then the process repeats. Is there a solution to this please?

With the current GSX profile installed, push back west from stand 8 takes you all the way back to gate 11/12.

Hey Steve! Thanks for replying so quickly:) Xbox Series X. It seems the version number was a weird hiccup, as it’s now showing 1.1.8 in the OIS as well. I did 2 separate test flights, and the other bugs were persistent. On another note, performance is amazing!

Hey y'all, i'm on the go switching from 2020 to 2024 and wondered if the iBlueYonder Dallas Love is available for MSFS 2024. The iniBuilds sales page says it's only for 2020, but other pages selling the scenery say otherwise. I bought the product via iniBuilds. Thanks

FS20 has yet to receive any major sound modifications so it's possible your ears are deceiving you. Once we update it to the same standard as FS24, we'll make an announcement, and you'll be able to tell. 🙂

Also created a video highlight:

Hi Aya, Thanks for the report. Can you confirm which console variant you own? (X or S) There is def something wrong with the version if you're seeing 1.1.4. You followed the correct method to reinstall the product, but I would confirm that doesn't happen again. Regarding the the bugs we've already logged the Terrain/Navdata issue but it's something new affecting only xbox so we suspect it has do with memory management. The display issue on load is related to something in SU4, which we are also actively investigating.

Which variant of the Xbox are you on (X or S) and where/what kind of conditions where you flying? Xbox seems to have pretty aggressive memory management from what we've seen and while we've tested the aircraft in some pretty memory heavy areas (350 at EGLL in poor wx) there is a chance you found the perfect scenario to tax it further. Reply to this topic

The dev has pushed a compatibility update and since you own the product, it's available to you.

Anyone know why this is showing up for FS24. Obviously, we all know the story, so not sure where a FS2024 version came from.

Hi! I am experiencing a number of “gamebreaking” bugs in the A350 on Xbox. A350 1.1.8 (according to library - however in the OIS it says 1.1.4 (Xbox) • Navdata doesn’t update properly - Leading to issues with F-PLN and “airport not in database” etc. • Terrain doesn’t show on display after downloading it, and restarting flight from main menu. • No engine animations. - Engines are animated as idle when spooling up, on, and in the air. • Printer prints unreadable sized textures • Fully broken displays • Fuselage is transparent on exterior model, when looking through hatches and windows. Apart from the broken displays, all the other bugs are persistent 100% of the time. The broken displays were persistent 100% of the time, before I downloaded the A350 instead of streaming it, then deleted it, and had it streamed again. it seems fine for now!

The landing distance seems just a bit off. The real A350 would probably need a few meters more even if autobrakes are set to medium. Maybe you could have a look at this as well.

Just performing my first flight with the A350 since the recent sound overhaul. One thing im noticing is that the sound of the engines in the cockpit isn't getting quieter with altitude. Just reached 40,000 feet, and the engines sound just as clear as they did at 10,000 feet. The effect of the engines getting quieter at altitude was far clearer in the previous version. Same with wind noise. If it's more realistic this way, I stand corrected. Im using FS2020.

There is obviously an error in the flight plan. You are flying from DUGDA to CALVY, then backwards to SILTO and finally to ONTOK. 🤪Of course, the plane is making circles in that case. Two 180 degree turns on short notice - this won't work. You can see the colors in your plan, STAR and APPROACH are overlapping. Maybe you have chosen a wrong transition?

Hi guys, with the latest update v1.0.18 and latest navigraph data, noticing something weird planning/flying approaches into CYYZ. RVAN Z 23 LPV, ILS 23, and RNAV Z 24L. The FMC creates weird turns on final approach path as seen on the attached screenshots. Selecting the correct arrivals and approaches. Example: RAGID6 ARR all the way to CAVLY then using RNAV 23 Z SILTO to CYYZ . Something is not right here, please have a look at it @Eddie Regards

Never gonna work in these two birds. Touch screen v LSK key presses. FCU and EFIS do work in the 350 tho. Ini doesn’t make a 380 (yet). Blue skies, -A

v1.0.2 of iniBuilds Manchester (EGCC) for MSFS 2024 has been released. This update realigns Taxiways E and D with updated markings and lighting, while correcting object placement, airline codes, and various visual bugs. This update can be downloaded via the iniManager. v1.0.2 - Taxiways E & D shifted as appropriate to allow additional parallel spacing - All markings, connections and lighting adjusted to suit - Changed layout of D/E connection at NC - Some taxi sign adjustments - Moved blast wall to correct diagonal position. - Moved GSE per above - Added missing airline parking codes - Fixed z-fighting T1/3 - Fixed floating approach light 23R - Fixed mast light colouring - Fixed bugged exclusion on default street lights

I had actually feedbacked this and my post is disregarded. I had also prove of video showing it. But anyway, I will repost it again: The -900 variant is different from the -1000 in terms of flaps retraction and deployment timing. -900 is usually faster in deployment and retraction than the -1000. For your product, the -900 version is as slow as -1000. I can't make a video at sim but I can roughly provide the timing of -900. Inbuild A350-900 Flaps 0 to Flaps 1+F = About 20 to 22 seconds Real life A350-900 Flaps 0 to Flaps 1+F = About 10 to 13 seconds https://youtu.be/E80qj1C3rDM?t=272 Inbuild A350-900 Flaps 1+F Full 0 0 = About 20 to 22 seconds Real life A350-900 Flaps 1+F Full 0 = About 8 to 10 seconds https://youtu.be/E80qj1C3rDM?t=1001 Inbuild A350-900 Flaps Full to Flaps 0 = About 31 to 33 seconds Real life A350-900 Flaps Full to Flaps 0 = About 19 to 21 seconds https://youtu.be/KtKqg1tOjYo?t=754 Is just that the -900 variant need adjustments. The -1000 variant is pretty fine.

All of a sudden both Winwing fcu and efis and mcdu do not work in inbuilds A340, but in all other planes it works ( A350 - fenix A320 - FBW A380 ) however mcdu does not work in A350 and A380. I have tried everything - uninstalling all planes and simapp pro and completely new installation of msfs 2024 ver. 4 There are no lights at all in fcu and efis and no buttons work. PLEASE HELP ME .......

I confirm the same problem. At moment I identified as possible mod conflict (empty community folder seems solve the problem), but still not able to understand with mod is incmpatible.