Fab10

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.

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.

Hi, The newly implemented MDPP airport (part of the MSFS Caribbean World Update) doesn't display properly in the A300-600R MCDU. Instead of listing SIDs for RW08/26, it shows RW01/19 instead. I've not tried MDPP in the A310 but MDPP in the PMDG B737-900ER is fine. Thanks.

Thank you. INI Builds, have you anything to help us out, and is this a known and recognised issue, especially considering that the A310 does the same at LGKR? Thank you

Thank you, I appreciate the confirmation. Over to INI Builds?

For what it's worth, here's a very short video of the issue: Perhaps I have missed something with respect to flying this type of arrival/approach in the A300/A310 as the IB A310 also exhibits the same behaviour:? Thanks.

Hi, I twice repeated the flight listed below in the A300 with exactly the same results, which leads me to believe that there may be an issue with DME ARCs The STAR TIGR2T is essentially a 20DME ARC from VOR GAR colocated on LGKR. The IB A300 descends on PROF just fine but then turns left at the 22.5DME GAR direct towards the airfield instead of turning right to establish on the ARC. For reference, I had the RNAV RW34 inserted, and the MCDU list the waypoint as an INTERCEPT just as it fails to establish. The Maddog behaves as expected and follows the DME right down to the approach. I thought I’d report this in case it is of use, but TBH I’ve not flown other DME/ARCs with this latest build. For now, I can fly a descending DME ARC manually with the RMI/DME. Thanks. LIMC/35R TELV8G.ROB5J ROBAS L153 OSBUL Y765 ANC M736 PES M872 DIVKU P92 KAPPO L995 TIGRA TIGR2T LGKR/DIREX.R34

TACT mode is a temporary selection which remains active until the next phase of flight. PROFILE follows the cues as shown in the MCDU. PROFILE mode ALT & IAS/M can be changed by selecting the RLSK and entering new values (A300 & A310).

Yes, thanks, I knew that one, but still a good reminder.