Fab10

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.

Thank you, that’s greatly appreciated, I will check it out on my next flight.

The A310 MCP has a speed intervention feature, whereas the A300 appears to not have this. Whilst I cannot recall my differences training between the A300 & 310 in XP (too long ago!), I believed that the A300-600R featured the avionics and systems of the A310 with all improvements and updates. Is there a way to speed intervene whilst in Profile mode? Thank-you.

I will add that no-one is under any obligation to take thread based advice, and whilst your offering may work for you, the underlying issue still needs to be addressed with the result that you may need to revise your A&Os mappings. So, instead of being a trooper and helping, you’ve been advocating your solution needlessly and to the detriment of this thread, and getting all uppity in the process. The reason for me posting is to make INI Builds aware of this as a potential issue for them to investigate and address as required. The idea was this to help INI Builds, their A300 product, and their user base. With that, I’m out.

With such poor “throw more money at the problem” advice, I’d expect no less. Happily, there are better ways of problem solving, which I’d be delighted to not share with you, so don’t ask as that way you’ll not be offended.

I’ve left your posts largely unread as I figured, based on your initial narrative, that they’d contain little useful technical content. At the end of the day, I have A&Os and FSUIPC, but after much early experimentation, my preference is to leave the sim to manage assignments as it does this very adequately, and this is largely the point. The A300 should work seamlessly with default assignments and systems, and this specific issue seems to indicate a faulty interaction with default settings. Simply, I asked you to try the AP IAS knob without firing up A&Os, but you felt unable to assist, so I must await clarification & confirmation elsewhere. I have asked the mods to close this thread as I really don’t want to start 2024 in this way, and I hope that we might agree on this. Cheers.

Yes, this is very strange; thanks for confirming this is not a one-off. It took me a while to find the culprit, and now that I know to not use the Honeycomb TQ AP controls, I can at least fly the A300. My profiles are pretty much default other than reversers, so hopefully INI Builds will be able to confirm and offer a solution.

I couldn’t help but notice the big brash banner at the bottom of your signature to correctly place you in your niche. If you are willing to help, please do so, otherwise don’t waste time with things beyond your capacity. Cheers.

Is that comment evidence based and do you speak for INI Builds? Please could you set the AP knob to IAS mode on your Honeycomb TQ but without Axes & Ohs running as this would be useful information to share? At the end of the day, users cannot buy A&Os for the sake of a single aircraft, and we are essentially exploring default sim settings here. I have several MSFS profiles setup, and this particular Airbus centric setup is fine for the A310, FBW, and Fenix though not for the A300. My profiles simply swap reverser preferences and gear setting for PMDG requirements otherwise they are default.

Well, I've not yet taken the aircraft aloft as I'd prefer it to be 100% - at the end of the day, I'm no Airbus test pilot!

Hi, This is very odd. My first encounter with the A300 wasn't great given that both engines went to full thrust immediately after start-up irrespective of the position of the throttles themselves. The throttle calibration was straightforward and my throttle setup has no special commands applied (it's pretty much default except for Parking Brake). Even if starting at the gate Cold and Dark or with Ready for Take-Off applied, the engines did the same; the throttle position indicators were at idle and moved properly with throttle position and yet the engines were at full throttle. After a (long) while I discovered that this is an interaction issue with the Honeycomb AP mode knob being turned to IAS (left hand knob set to position 17 as shown in MSFS settings). Note that the autopilot and autothrottle are OFF and that the moment the knob is returned to HDG or any other mode allows the throttles to return to idle. Here's a handheld video to show my Honeycomb unit along with the in-sim screen (hope it's clear): https://www.dropbox.com/scl/fi/mk5dnzljcxgmbmvssezmm/IB-A300-MSFS-Honeycomb-IAS-Knob.mov?rlkey=2np0wale2buwc7qx19y0jz7f0&dl=0 Thank-you, Fabio

IM now working, purchase made!

Hi, I was attempting to purchase KPSP from the INI Manager, but I couldn't find the discounted price so I closed it to allow a INI Manager update (a new IM icon appeared on my desktop). However, the INI Manager won't restart and hangs with the progress bar just midway through the "r". Thanks, Fabio

Yes, that has totally solved it. Thank you, what a revelation that is!

Will do, stand-by…

Yes, I use FS Realistic. Is there an issue with it? Can camera effects affect simulated flight? Curious!

Hi, Please don’t misunderstand my post, the INI Builds A310 is a firm favourite. However, I still feel that the low speed handing is not correct. The aircraft is sluggish, unstable, and even the AP fights to keep it on track. This is felt most during departure and in the approach phase. It’s hard to imagine certification being granted for an aircraft featuring an unstable approach or low speed regime. I use Vref + 10, but with full flaps and gear down, the aircraft rolls left/right, and the AT struggles to keep pace with the commanded speed. I am always happy to learn and out right my mistakes, so please let me know how I can again get the feel for this aircraft? I don’t remember the A300/A310 having this handling in XP. Thanks, Fabio

Will do.

Hi, I often change waypoint altitudes from "at or above" to "at" in order to ensure compliance with altitude constraints. On top of this, I also dial in the platform altitude on the MCP. This is belt and braces, as well as correct procedure. However, too often during the approach phase, the aircraft continues to descend beyond the altitude constraint as well as the altitude dialled into the MCP. At this time, the LOC may be already active, but the G/S is not yet alive let alone one dot above. The A310 really should not descend at this descend, and yet all too often, and easily reproducibly, it does. Thoughts? Thanks, Fabio