Fab10

Is there anything I can do to restore my flood lights (panel & overhead) and dysfunctional dome light? it’s not good enough that a (new for me) £70+ product has lighting issues, so please can someone at INI Builds assist me? Thanks.

You know, I returned to the MSFS Forum after a long absence, and all I got for my trouble was immediate heart-sink. I recognised many older posts asking for the IB A320N V2 lighting fix (from 9/24) and missing paint-kits (from 11/24). Honestly, there is little point in adding yet another plea. Our only recourse is to call for an ombudsman to work and litigate for the needs of end-users. This is why end-users need developers to add palpable pressure where it’s needed because their voice carries the sort of weight end-users simply do not have. Think about it from our perspective; the bulbs failed in the IB A320N V2 in Sept. 2024, and despite posts galore imploring both developers and Microsoft alike, nothing has changed. In the interim, sim updates and monthly navdata are rolled out, so it’s clear that they have no intention of implementing a simple fix for the outgoing platform. And why is that? Well, the new platform is getting all the attention and the aim would be to migrate users because one is cheaper than two. From my standpoint, I refuse to move into MSFS24 because, of all things, the lack of paint kits for default aircraft. This ludicrously needless situation is 100% the reason I’m holding out, stubborn as I am. I’ve been livery self-sufficient way before many developers and associated team members were even born (possibly, though hopefully you get my point). And so we come full circle whereby so very many have posted pleas for paint-kits without Microsoft even batting an eye. End users are impotent in this regard and it can be no surprise that we become demoralised and despondent as a consequence, all the more so as we become older and wearier. I apologise if I previously caused you any distress, I just wanted to clarify its origin.

Agreed; edited.

It's disappointing that this issue has been reported by many, and that it is similar to the problematic IB A320N V2 lighting. I purchased this aircraft as it was a seminal release for MSFS20 & MSFS24, as a nod to support the developers. Still, I cannot shake the feeling that MSFS24 is receiving more support than MSFS20.

Hi Eddie, Thank-you for your reply. The thing is that users have contacted MS/Asobo regarding the broken cockpit flood lighting in the A320N V2 and INI Builds have acknowledge the issue and indicated that a fix was sent to MS/Asobo. However, it remains broken since the AAU3 update in 9/2024, so with respect, someone needs to try harder for the sake of their customers. It simply cannot be that it takes this long to fix an issue that has been acknowledged, so someone somewhere is isn't working hard enough for end users. The INI Builds A350 has equally flawed panel flood and dome cockpit lighting, so I have uploaded a video showcasing this issue in both models. Again, thank-you for your reply, I look forward to further input.

It’s like the INI Builds A320N V2 which has had broken main panel floods since AAU3 in (I think) Sept. 2024. The bulbs illuminate but no light is emitted. Whilst IB suggests a fix was issued to MS, the aircraft remains broken eight months later which, it is claimed, is out of their hands. Let’s hope IB can find the cause and implement a fix more quickly than that in this £70 pay-ware aircraft. It’s almost as if unseen forces are ushering MSFS 2020 users towards MSFS 2024…

I don’t wish to use BTV for now, but I’d like to simply set simple auto-brake retardation (low or med). Turning the auto-brake knob seems only to allow setting med auto-braking. How can I set, for now, low, medium or max auto-brake?

I’m new to the IB A350 having had it only a few days. I can’t get the forward cockpit panel flood lights to work. The PDF guide shows the flood lighting knob to be in a cluster of four lighting knobs on the pedestal, which are easy to find and operate. However, the forward instrument panel floods do not actuate and only the overhead down-lighting flood seems to operate. Of the four rheostats under the coaming, the centre pair operate the MCP lighting and the others illuminate for the tray tables (I forgot to try these out). However, when I start the aircraft C&D at a gate, the flood and dome lighting don’t always work as the bulbs (dome & overhead flood) illuminate but cast no light. In case the airport lighting is affecting the internal lights, slewing to a dark corner of the airport changes nothing. I can confirm that there are no user mods installed and that this is a fresh installation. I searched the PDF manual without finding any matches for flood but 8 were found for lighting though these don’t provide an answer. Thanks.

That’s incorrect, and somewhat presumptuous of you. Most users understand what a weather radar is and, more specifically, what it depicts. Most would want this facility replicated in the simulation. However, we don’t have this, and it looks as if MS/Asobo/Meteo-Blue cannot implement a cheap enough version. We are left with Active Sky who may still be investigating this as a feature just as they did for FSX/P3D. With that in mind, like many other users I would prefer to have something rather than nothing given how gorgeous the in-sim weather rendering is. Thus, I’d like to see all relevant aircraft feature some form of weather radar, albeit in its currently unrealistic form. Actually, I applaud INI Builds and PMDG for doing just this, along with all developers who have implemented the present Asobo WXR API. Remember that XP11 and XP12 both had WXR in nearly every aircraft, and yet this too was a 2D top-down model, but with significant tinkering a 3D representation was provided. In fact, Laminar Research only very recently implemented a full tilt/gain WXR model in XP12. I’m hopeful that such an API will make its way into MSFS 2020/2024. A payware study level airliner flown in the sublime atmospheric environment of MSFS 2020/2024 cannot be called complete without some form of WXR. Would a pilot really fly under or over an area of yellow or red? Well, they might fly over such an area in VMC but definitely not under it. In all likelihood they’d skirt around the area which is precisely what the 2D WXR representation allows us to do. The other question is whether being reliant (and happy-ish) with the present WXR API will impact the investigation of a properly simulated WXR; obviously, it would be easy to ignore that need if we are content with the basic API. Time will tell. That said, please don’t make assumptions about the knowledge levels of other users. It’s invariably best to know your audience.

NB. Believe it or not I am onside with INI Builds - I have uploaded 36 liveries for the A300 and 27 for the A310 not to mention a few in XP too.

FPS Locked at 30 on VSYNC without fluctuations on a RTX3080 and Ryzen 9. The oscillations still occur, indeed it recurred again today at LFML RW31R, if the AP manages the initial descent but the moment the AP is switched off the aircraft ceases the pitch oscillation. Yes, the speed is very slightly higher than Vref as often approaches are flown at 160 kts or thereabouts depending on traffic to then slow at 4 nm or so. Please stop calling out the piloting abilities of your loyal customers and begin reading and, more importantly, processing what is written in their communications, as they have taken the time to communicate the issue to you in the hope that INI Builds will read, understand and appreciate instead of seemingly always taking a defensive line. Beginners are most unlikely to purchase such an in-depth old school airliner whereas a knowledgeable connoisseur will.

Well, I managed to post the wrong link above in my second post (LYTV to LRTM) instead of the mini loop MGMM-MGMM. Not sure how I managed that! Heres the right link:

Yes, it is an issue, and cannot reflect real world yoke movements. The yoke obscures the instruments, breaks immersion, and if the yoke is hidden then disconnecting the AP can be frustrating as one needs to restore the yoke to switch off the AP DIS sound. To illustrate how spurious the yoke movements can be, please check my approach in this video (from 01:24):

For what it's worth, I uploaded a short video of this phenomenon (below). Also, please could INI Builds adjust the WXR 1/off/2 switch whose operation is reversed, and rejig the yoke that seems to move excessively and disproportionately to the actual bank angle of the aircraft (as it gets in the way of instruments and dampens immersion). The V1.1.2 update has been great otherwise (though I've yet to test RNAV), and I'm also grateful for the terrain radar and t/o trim indication on the EFB takeoff perf page.

Thank you for the latest update, I'm pleased that the IB A300 is edging ever closer to perfection. I have complete two ILS approaches in it and both times the aircraft began an ever increasing longitudinal phugoid oscillation with the AP engaged. I was not yet at Vapp but I was nearly fully configured with one stage of flap to extend. Both times this occurred early in the approach with several miles still to run; my preference is to hand fly without AT which also helped to dampen and remove the oscillation. I thought to report this in case others have noted the same. Thanks.