Crabby

Use reverse hold. When this is activated, it puts the aircraft into reverse idle. Moving the throttle forward will increase the amount of reverse thrust. When ready to stow reversers, move the throttle back to idle and deselect reverse hold. The throttles then go back to normal operation.

Spoilers arm as a toggle in AAO is done with this script (L:INI_SPOILERS_ARMED,·Bool)·0·==·if{·1·(>K:SPOILERS_ARM_SET)·}·els{·0·(>K:SPOILERS_ARM_SET)·} Just create the script and assign it. This is done as a toggle.

Good question for MSFS/Asobo. It's their plane to release.

I have mine set to ELEV_TRIM_DN and ELEV_TRIM_UP on recommendation from INI. This works to trim up and down, not sure if it moves the switch though. I would have to check that next time I am in the plane. I actually hide my yoke in the sim since I have a real yoke right in front of me for visual feedback.

I use a number of the scripts from here: iniBuilds A300 StreamDeck XL & PLUS profile & AAO Scripts for Microsoft Flight Simulator | MSFS Plus some that were for the A310 that I modified to work with the A300. If you don't use StreamDeck (I don't) you can ignore everything in the above download but the scripts. Once you have them imported into AAO you can assign them as needed.

I use a script with this since my gear lever, HQ Bravo, only has two positions Gear UP: 0·(>L:INI_GEAR_HANDLE_STATUS,·Number)(WAIT:60000) 1·(>L:INI_GEAR_HANDLE_STATUS,·Number) Gear Down 1·(>L:INI_GEAR_HANDLE_STATUS,·Number) (WAIT:100) 2·(>L:INI_GEAR_HANDLE_STATUS,·Number) Gear up will raise the gear then wait 60000 ms or 1 minute and then put the gear in the off position Gear down will lower the gear. Use the script editor to create them and call them what you want. I call it A300-Gear Up and A300-Gear Down. Once created assign each script to the button or lever you want.

You will love AAO. I think SpadNext will do this too, but I know for sure AAO remembers what profile you want to use down to the individual livery of an airplane. So you never have to worry about activating or deactivating in sim profiles again.

I believe this data is taken from Simbrief. It is more like the departure/arrival board at the airport. Actual estimated arrival time in real time can be viewed on the FMC Prog page.

Really? As a result of your purchase choice, you had to suffer in an old version and then go run to mom and dad to fix it. Your choice also made you come into here and bash INI for things they do not control. You made an uninformed choice. Good luck trying that next time. That is what I would call an impact. Also, my comments are never borderline anything. Offense cannot be given only taken and taking offense says more about the offended than the supposed offender. I'm lucky I guess that the Marines took my feelings out when they removed my wisdom teeth.

I assign mine to Reverse HOLD then use the throttle to increase reverse. Allows me to control full range. I assign the reverse hold to one of my HC Bravo reverse levers. When I pull the levers, it activates minimum thrust and as I move the throttle forward reverse increases. Release the reverse handles and normal thrust is restored.

I have no problem disconnecting the AP1 or 2. However, I use AAO and run a script that activates the disco button on the captain's yoke. It looks like this: 1·(>K:AUTOPILOT_OFF)·(L:__CPT_AP_DISCOIsPressed,·Bool)·!·(>L:__CPT_AP_DISCOIsPressed,·Bool) I assign that script to red button on my HC Alpha and no issues. In fact all my controls/bindings are using AAO. I prefer to have complete control over how I interact with the plane and not have them in MSFS where things can get mucked up. Another example is I have a short push of the HC Bravo auto pilot button set to AP1 On and a long push set to AP2 On. You can't do that in the sim. As always, I highly suggest getting AAO or SpadNext and take control of your controls. The in sim system is too limiting for complex aircraft like the A300. You have to choose to accept the limitations or get rid of them.

On approach, when you have visual reference to the runway, you should be looking at the aim point markings. Once you hear the 50 AGL call shift view to the end of the runway as you prepare for the flare. At 20-30 feet AGL begin the flare with your eyeballs on the far end of the runway. As you begin your flare, begin to retard the throttles smoothly. Your wheels should touch just as you throttle comes to idle. Avoid chopping the throttle. The best way to gain proficiency is to fly patterns to get burn the movements into muscle memory.

I did not mean to infer that one would watch some kind of G meter. What I meant, as you saw in the part 25, is the g-load is most important. 720fpm at MLW is probably the same or about the same g-load as 360 at MTOW. Think about jumping off a ladder from the third rung with just you and then imagine doing it with a 50 lb bag of concrete on your shoulders. The main thing is in the real world they do not chase a landing rate number. Put it firmly down in the zone and if you did a proper flare and there is no bounce, you will have made a successful landing.

Bindings. Check them all.

Well, I guess you could say "it COULD be a bug". However, the dearth of people seeing this means it is probably local. Check all bindings. MSFS loves to surprise you with bindings it thinks you need to have. When I say all I mean ALL. Every profile you have in msfs from the keyboard/mouse and all of your other controllers. I found a crazy throttle binding on my in sim profile the first time I connected my MFG Crosswind pedals. I am not at the sim now, but I believe there is an EFB setting for auto pilot disco sensitivity. If you accidently bump the controls, depending on where this is set, the a/p will not disco. Check your controls for noisy pots. I have yet, in all the versions, to see the a/p or a/t disconnect without my express permission. Caveat, I do not use the sim for my controllers except for views. My profiles are all blank. That is another story though.

"Worked fine yesterday" is not a troubleshooting starting point. Recheck ALL of your in sim bindings. Search each profile (keyboard, yoke, TQ, mouse, second yoke etc etc). What controllers do you use? I have a Bravo TQ with a trim wheel, if that is set to trim, bumping it can turn off the A/P. I can't remember but check and see if there is a setting in the EFB for the plane that says something about disconnect sensitivity. Setting this to low can help with spurious trips. If it worked fine yesterday and then didn't today and there was no update or any other change, it has to be a local issue. Only you can find it. It can be frustrated. I use Axis and Ohs with some voice commands set. They would activate without me pushing the correct button to turn voice rec on. Turned out that when I updated my video drivers, I accidently installed the HDMI audio drivers to my TV too. I pounded my head on the wall for a week and a half trying to fix this. Glad I didn't post a message in the Axis and Ohs forums about how it was that program at fault.

Well crap, tried to edit a/p for a/t and it posted twice. Anyhow, a/t disco is what I meant.

Three chirps are the alarm for a/t disconnect. Check ALL your bindings. MSFS loves to double bind things across multiple to help us simmers out. Most of the time we don't know 100% what is bound to what. You may have something bound to the A/T disco that you are unaware of. I have also heard of this happening with the Thrustmaster airbus system again due to what automatically set "suggestions" are assigned when you first plugged that in. I got away completely from the in sim control bindings. Mine are all blank except for view commands. I use Axis and Ohs. Early on in MSFS I got tired of constantly searching for "helpful" default bindings and the problems that early updates had of messing up controller profiles. Some use SpadNext to do the same thing. I can tell you that I have never had a problem with a spurious trip of the A/T on this plane.

Three chirps are the alarm for a/p disconnect. Check ALL your bindings. MSFS loves to double bind things across multiple to help us simmers out. Most of the time we don't know 100% what is bound to what. You may have something bound to the A/T disco that you are unaware of. I have also heard of this happening with the Thrustmaster airbus system again due to what automatically set "suggestions" are assigned when you first plugged that in. I got away completely from the in sim control bindings. Mine are all blank except for view commands. I use Axis and Ohs. Early on in MSFS I got tired of constantly searching for "helpful" default bindings and the problems that early updates had of messing up controller profiles. Some use SpadNext to do the same thing. I can tell you that I have never had a problem with a spurious trip of the A/T on this plane.

Understand, Ver 1.03 was released to MS/Asobo a while back when it was released to the non-market clients. It took them this long to "approve" it and get it on the store. In the meantime, Ver 1.04, 1.05, and 1.06 have come to the non-market customers. They were probably sent to MS/Asobo the same time they were released to us. This is not on INI. This is wholly on MS/Asobo and their procedures. You will probably receive these updates in 2-6 weeks. In the interim, us non-market users will probably be on version 1.10. That is just the market client life right now.

Then the community awaits you doing it. You have written three, go for four. Or possibly you could take the reins and negotiate an agreement with Airbus. If is a word normally used by people who got no other option.

Neither the FBW 320N nor the ATR72 are the INI300. This is important in any trouble shooting/support endeavor. That start will always throw the process off. Treat each plane/developer as individual cases. It is just as bad as "well it worked yesterday". I question whether the ILS stations should even show there. I will have to dig in the FCOM, but that page should be reserved for navigation aids (VOR, Fixes, ADF) only. Maybe this is the way the 300 did it, as it is an old aircraft. I will report back what I find on the FCOM.

Could be. Settings for example. I run a 9700 KF with a 2070 Super and never get below 30 fps when I look. I don't look a lot as the number is meaningless. My eyes are analog and therefore I trust my analog senses to know if I like what performance I am being shown. No stutters and smooth are my measurements. My sliders are at a minimum on high and I run DX11 with DLSS and my TV's native resolution 3840 x 2160

From what I can see, there are 6 different navigation items in the world called IKA 2 NDB stations 3 ILS 1 VOR/DME with FREQ 114.30 So, the VOR is shown correctly. As for the first entry, the GPS coordinates shown are for one of the ILS stations and the freq is 109.3. The third entry is an ILS with freq 110.1. The last is an ILS with freq 111.70. Again, all based on given coordinates. Now, the question is why. Are you using Navigraph in the simulator? (Replacing the simulator base data with the Navigraph data.) If you are, try it without that. If you aren't, it could be an A300 glitch or a sim data glitch or some combination of both. Either way it is not the VOR stations that are cutoff.

Decisions bring consequences that are all uncontrolled by the decision maker. When MSFS first came out I purchased a scenery from the Market. Within two days I repurchased that scenery direct from another store and vowed I would never go back and even look at the market. I would uninstall it if I could. You will be, based on what I have seen, 4 weeks to 2 or 3 months behind in what the rest of us get. Frankly, I am shocked the market is not on 1.0.0. If you want different results you will have to change your purchasing choices.