Crabby

Cost Index should be entered as part of pre-flight. You shouldn't even take off without that.

I have flown 5 RNAV approaches in 1.10. KCOS, KPHX, KSAN, KBOI and KPDX. Short flights as I work through my control set up on AAO. All were done with no problems. Granted, I have not tried LGIR and runway 27. However, another user did, and it worked. Based on this we can conclude that it is not the aircraft. The possibilities left are navdata for that airport if you are using Navigraph to overwrite the in-sim data, scenery if you have addon scenery, something else in your community folder buggering things up (could be anything even if it is not being used since it is being loaded), pilot error. Ockham's razor. Eliminate all possibilities and whatever is left, no matter how un-probable, is the answer. I cannot replicate a bad or non-working RNAV approach on my end....Yet.

You can actually solve this more permanently two different ways. 1. Clunky way-create profiles for every plane you fly in MSFS and on that controller profile delete the mixture binding completely for the A300. It is clunky because now you have to remember to change profiles when you select a plane. 2. Best way-use Axis and Ohs (or SpadNext) to control your controllers outside the sim. This is best because you don't have to remember to set your profiles. They do all the remembering for you. Bonus, you get to unlock the full potential of controlling your aircraft including using your voice to activate commands.

I just flew an RNAV yesterday on 1.10. It was perfect. I will guarantee you missed a step/procedure while setting up. Review the myriad of videos on Youtube. This will fix the problem.

Take off calculations are not designed nor supposed to be "feasible". It is feasible does not mean safe. Calculations are done so that you will hit V1 with enough runway left to stop safely and not kill any of your pretend passengers. If you want to just willy nilly take off, don't even bother with the calculator. Load up and get to the runway and hit toga. If you are trying to simulate ops, understand that you might have to make some adjustments.

Well, personally I have not had any of these issues. I have an i7-9700KF and a 2070 Super GPU with no overclock. The INI 300 is as smooth as any of the other aircraft I have (PMDG, FENIX, Maddog, CRJ).

No, they are not calibrated correctly. You can see that by looking at where the IDLE and TOGA tick marks are on the calibration graph. Either the calibration was never done or you have to redo it. Hit Start Calibration and follow the instructions.

Think of take offs and landings this way... EVERY takeoff is planned as a rejected take off. Becoming airborne is just another acceptable outcome of the takeoff roll. EVERY landing is planned as a go-around. Landing and taxiing to the gate/fbo is just another acceptable outcome. A takeoff performance calculator (or manual calcs) is designed to get you to V1 with enough runway left to safely stop or get to Vr.

You will never know if it is solved for your system unless you update.

Yea, I read your post. My post still stands. Variables are not just interaction but actions and movement.

LOL. Now there will be an untold number of posts along these lines: "When is the update with the Honeywell EPIC avionics suite coming out as was promised?"

In many in-depth addon aircraft, like this one, that type of functionality is unlocked using variables the sim does not have access to. I say normally because it is the case of many if not most. I don't use the in sim bindings for a number of reasons (this is not one of them as I hide the yoke since I have a yoke in front of me). I use Axis and Ohs. Many use SpadNext, and some use FSUIPC. These programs allow you to unlock the full potential of the bindings that are available. The in sim bindings are too limited and you should ( I would say HAVE) to create a profile for every aircraft. Same as I do with AAO, however AAO remembers what bindings you want to use for a certain aircraft so I am never in the scenario of rolling down the runway in the A300 while my bindings are set to a CRJ or 737 or worse a GA prop job. Also, I am in no danger of losing bindings during an update. It happened to me early on and though the community seems to think this won't happen again, 6 hours of work down the tubes made me not take the chance. In my opinion, AAO (or SpadNext) is a MUST have addon for anyone serious about simming on a PC. X-boxers can't use it.

I am not seeing this using AAO. Everything working as expected.

I believe that this may come from the MAGDEC.BGL file in the sim itself. I have not tried this particular approach but will when I return home. I have been in the habit for a long time (since FSX days) of replacing that file with the one available here: Navaids tools (sors.fr)

Ah yes, Hollywood. I went there too. Of all the things that time has erased from my memory, boot camp is not one of them. I can vividly remember all of it almost down to the exact days. The only thing that has changed is perception. While going through it, every day was chock full of suck. Now, everything, including the suck are things I look back on as the building of a man or just plain freaking hilarious. I constantly marvel at the drill instructor's ability to maintain bearing with all the dumbass and hilarious recruit stuff that happens around them.

Yea, I am pretty old school in every way.

Not helpful nor relevant to the potential issue and plane discussed here, plus it is not all instances of the 737 just like it not all instances of the A300. As noted, INI needs SPECIFIC information. There must be some confluence of events that triggers this, but it has yet to be identified. If it cannot be identified, then INI can't fix it. I had it happen once a few versions ago while I was away from the keyboard. I never saw it before or since. Some people have this happen every other flight. It is not "this issue" from the 737.

I would have to look on the actual performance tables in the FCOM. I am traveling without access. I am not saying it IS unsafe, but that the EFB thinks it is. In general though you have to be able to reach V1 at a calculated point on the runway that allows enough room to stop. The variables are weight, wind, temperature, altitude, density altitude, flap settings etc. I am sure you can take off in that distance, but takeoff is just an acceptable outcome to the takeoff roll. A good takeoff calculation assumes you will need to abort.

LOL, not applicable does not mean no limit exists. If you are in Class B air space you are on final or taking off. You are NOT interpreting the information you are presenting correctly. Good luck to you.

It says "Unable to find SAFE performance data" This is based on your weight, runway length, altitude and temperature. It will not present you with an unsafe option. Kick some fatties or gold off the plane and try again. Try another flaps option.

I am not talking about the CFR. I am talking about ICAO airspace classifications and speed restrictions. You are interpreting things incorrectly.

That jives with the performance tables I am seeing +/-.

Yea, no. 1. I have seen zero issues with NAV. It works for me. 2. I have had to change things in my route dozens if not hundreds of times because ATIS changes or ATC wants me to do something else. Takeoff runway, destination runway, change SID, change STAR, add a waypoint, go direct to a waypoint, delete a waypoint. None of these things has caused my nav to go off the rails.

No, there are a number of reasons it won't arm. 1. Not at platform altitude and in some other mode other than profile. I am normally in ALT HOLD 2. Did not enter the MDA from the chart on the Approach page. 3. Did not activate the approach on the approach page. I never look at the legs page to set up and activate an approach. The 3.00 that is important is on the Approach page, and when you activate it will read how far above or below that 3.0 you are.

I don't think it's a simbrief error, in fact I am sure of it. Everything looks fine until INIT B is filled out. It is either some issue with the plane or some conflict with the navigation data.