Fab10

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.

I am so pleased to hear this, but I haven't the opportunity at the moment to check. They mention a rebuild of SID/STAR/HOLD entry, so perhaps this encompasses the DME/ARC. Whichever it is, I am greatly relieved, and my faith and confidence in INIBuilds entirely restored. Thanks.

Open arms is one thing, though personally I'd prefer items such as these to be on the drawing board too. Thank-you, however, for your initial reply, I forget my manners sometimes. Fabio

I think my error was not updating the livery to the correct P&W container. My other error, of course, was having bought the still incomplete A300...

Sorry for the late reply; yes, Navigraph navdata is in use. Thanks.

I’m trying to complete my first P&W livery, and whilst the livery itself is OK, the EPR gauges seem not to work. I’ve copied the file structure of a few other P&W liveries, but still I can’t get the EPR gauges to work. Could someone please point me in the right direction? Thank-you.

Approaching Busan Gimhae RKPK; The MCDU allows users to select the VORA18 and RNAVB18 but without SIDs (NONE). Also, if loaded without SIDs, then no waypoints are added to the MCDU or route shown on the ND. The images show what I am trying to put across (NB. the MCDU shows INSERT but they have been inserted).

DME/ARCs are still broken in V1.1.1. This DME deficiency needs to be addressed, as well as the lack of T/O TRIM setting. Thank-you for your prompt attention to this. I feel like going back to my XP version, that was a hole in one.

Of course, but this has no bearing on the actual lateral path flown or how it is displayed on the ND (for the DME ARC approaches I have flown).

Well, I’ve stopped making repaints for this aircraft by way of modest protest!

Yes, I noticed that too landing at LGIR, it straightened the ARC. And still no take-off trim setting… Not quite the INI Builds of old then.

Hi, I’ve not tried it with the latest build, maybe there were improvements in that area? I was well below weight limits (the flight was a short hop from MMCE). I will give it another go, and I really appreciate that a few have provided feedback on this by trying the route. Thanks!

I will try at 180kts and I saw the overshoots but still it turned out of sync with the procedure. That said, we should be cleaned up and going higher & faster. I'll give it a go though.

That’s interesting. I also used FLC and kept it slow but the arc was nowhere near the 10DME point, and it didn’t follow the correct lateral path. I will try again.

I know, I reported this a while ago, but cannot believe it’s still an outstanding issue.

I flew a route containing two DME ARCs, one each in the SID & STAR, but the A300 had tremendous issues at both ends. it is as if it loses track of the sequencing. I let it meander through both procedures to see how it would pan out and yet I had to intervene on both. Here’s the route: MMCE/13 CONT2A CONTO DCT ROLMI UT30 CZM UG765 IMOLO UR506 NUDUG L212 VTICO DCT UNG DCT BENON BENON3 MUHA/I06 We are several iterations into the build, yet reading through the forum posts it is apparent that there are still serious flaws in this payware aircraft.

The MU-2 is a nice looking aeroplane, and one I enjoyed in FSX/P3D and XP. Compared with the others, the MSFS INIBuilds MU-2 is not so good. Rotation comes too late and it’s hard to unstick. Like the notorious real world aircraft, the IB MU-2 handling is full of horrific vices but seemingly worse than any other simulated MU-2. The AP is hard to interact with; reading labels is impossible, and the master on/off impossible to click from the P1 view. Please duplicate some click-spots elsewhere on the panel. The cockpit textures are very poor. There is no IB forum section for this aircraft but nevertheless I hope IB will update it. Where to start? I’ll start by not starting it until it’s fixed…

Hi, The A300 is fast approaching perfection, but there are still issues. Profile VNAV seems to not manage descent altitude constraints (speeds seem OK). The PAUL2K into MMUN has one between, one at or above, and two at constraints, and whilst according to the “banana” it would have made the 3000’ constraint before the RNAV (which it flew wonderfully), it was over ten thousand feet too high for the first few even though the descent profile said it was spot on profile. To manually catch up with constraints, I used V/S mode plus spoilers, but then V/S mode switches itself off periodically. The PERF takeoff trim is always zero, and clicking trim automatically sets this to zero. As always, thanks.

Am I correct in thinking that the INI Builds A300 uses stock MSFS navdata as there isn't a dedicated Navigraph component for it? Could someone else please confirm whether they can see the right runway data and SID/STAR dataset for MDPP? That way i'll know to stand down whilst IB fix things, thanks.