Crabby

Again, I think this is the case of a wipe off texture being used. Raindrops are not modeled correctly in MSFS (Asobo) and therefore there is literally nothing to wipe. Turning on the wipers activates "smear" textures. If you look closely the wipers are don't even "touch" the windscreen. This is a placebo effect similar to the "working" weather radars that don't actually work as airborne weather radars in some aircraft.

This tells you every thing you need to know. Now just add things back in until the issue crops up and you know what to delete. I would start with A300 liveries from freeware sources, but don't be surprised if it is something completely different. After, go get MSAddons Linker over at .to This will allow you to better control what is loaded into the sim before each flight. I only load the plane, liver and two airports. No chance something in Singapore screws up my flight in Florida.

Asobo issue. As far as I know it is the same issue for all developers. Don't know about the default or default modded planes. I have never flown them. There is some developer that put out a gimmicky wiped off texture, but the rain was still there.

If it is not a bug, and I don't see this on my system, then literally anything in your community folder could cause this. It could be a livery (even from another plane) a scenery etc. The only way to verify is to move/delete everything in your community folder and run the A300 with a default livery. If it does not happen then you found the place your problem is coming from. Now you have to add one thing at a time back until the culprit is found. This is a pain in the butt but a byproduct of dumping everything into the community folder and forgetting it. I use MSAddons Linker from flightsim.to This allows me to install NOTHING into my community folder and only use generated symbolic links. Before a flight, I take about 15 seconds and activate the plane, livery and two airports I am going to use. This way I run a clean community folder. If that does not do the trick I am out of options other than make sure you don't have some assignment (remember, MSFS does you the "favor" of making assignments across all your devices and many times there are multiple assignments) that could trigger it. One of the many reasons all my in sim controller profiles are blank.

Yea, that is on your end somehow. I don't speak French but it appears correct. The Z axis is the rudder on most pedals and the X/Y are the brakes. So, that looks good from what I can surmise. Do the lines on that page move normally when you move the pedals? Also, is Gouverne De Direction rudder or nosewheel steering? You should set that to rudder and then select the option to use the rudder as the nosewheel on the plane. Keep in mind that if you press the brakes one at a time you will get differential steering with the nose moving toward the pedal you pressed. So, pressing the left brake will turn the aircraft to the left and vice versa. I believe nose wheel steering is something like direction du train avant according to google.

I don't see this.

I will look at this.

I see no degradation. FSUPIC does have, or has had, a save feature that causes stuttering while actively saving and the severity/timing of that was directly related to the time between saves.

You could have done this yourself from day one and not waited on any "official" action. It takes about 2 seconds. Create a camera view that is to your liking then assign it as you wish.

Not sure if you noticed, but this is not a 767, or 777, or A350, or any other aircraft. If all the aircraft were the same, what point would there be to buying more than one? Also, this is a jet, you have to stay ahead of the engines. Unlike a piston prop, where you get immediate response to the throttle, that won't happen. I have never had the A/T let me down yet, though I normally fly by hand during takeoff and landing.

Did you guys activate the curved segments option in the EFB? Not realistic, but it is there.

I only speak to personal knowledge and experience. I don't make things up like "This is a Bug!". However, you are right. The number of instrument approaches I fly in general are low because I am not a magenta warrior. I am more than capable of hand flying any approach and don't need a system to do the work for me. Furthermore, I listen and learn from people that are doing it correctly and successfully, so I don't have issues. I will tell you this. If it is working on my end, then there are only two options to explain this. 1. I have the only working copy of the aircraft and sim. 2. You are not doing it right.

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.