Crabby

Well, I am very happy and do not see any of the issues that so disappoint you. So, if it works for me and many others (hundreds on VATSIM yesterday), I think you need to look at your system first.

Another suggestion would be to use google and find a wealth of information. Try something like A-300-600 FCOM for example.

Check all of your control bindings.

You should always select the runway/approach first. This allows the FMC to filter out STARS not authorized for that runway.

As stated above, the best thing any simmer can do is stop using the MSFS controller profiles. 1. They make a ton of "suggested and helpful" settings for you that results in a myriad of duplicate entries across all your controllers (keyboard and mouse included). 2. While maybe (I stress maybe) it is good enough for the majority of default planes, they are nowhere powerful enough to take advantage of even a rudimentary study level aircraft. 3. The MSFS update process can, has and will at some point set all your in sim profiles back to default. This is especially true if you participate in the betas. If it hasn't happened to you, just wait. 4. You are responsible to remember that that profile you set up for the A300 is not active because you last flew the B737. You are on takeoff roll and nothing works because you forgot to change. I recommend Axis and Ohs. I recommend this because it is what I use and know. SpadNext does the same things. The interfaces are different, and you will have one camp tell you how much better the one is over the other. Just get one of them and use it. I have tried both, began using Axis and Ohs first though and that is more familiar and comfortable to me. I am sure that if I started with SpadNext that would be my choice. 1. They work with every aircraft, past, present and future. 2. They remember what profile goes with what plane down to the level of the livery (no more thinking, thinking is dangerous for most people) 3. There are ton of folks smarter than us who gladly make and publish profiles that you can load and go so you don't even have to know what you are doing (dangerous too though, learn what you use) 4. Your controller profiles are outside of the sim and the wonky and required update process can't touch them. 5. You won't have MS/Asobo telling you how you want your controls to work. Take control. If you read this and other forums, there are three reasons for most issues. 1. You don't know what you are doing. Never read the manuals or searched online for other information. 2. You don't have control of your sim. You blindly allow the sim to control you. (Xboxers are somewhat exempt to this as they have no control, but that was their choice). 3. You think all issues are caused by the developers and compare one developer's plane to another even though they are different planes. No plane is released in finished form today and thank God for that. In the good old days, when we got a plane that was it. It worked the way it did and that was the end of the story. No beta team can catch every use case, every system set up, every desire ("I want my aircraft to include midgets in the cargo hold putting on a circus for desert penguins"). In short, get AAO or SpadNext and take control.

When aircraft are at or reaching their performance limits (in this case altitude), the good side of the envelope and the bad side of the envelope are very close together. In the case you show, going to fast or going too slow does not leave a lot of margin. That is straight and level, it changes even more with turns.

My first thought is that you started the engines with parking brake off. It does not move for me until after I release the parking brake. After pushback, that is the first item to set.

When it comes to navdata and the FMC, comparing to Fenix and PMDG is not the way to go. They use the Navigraph data, not the sim-based data. As seen on other threads, the sim based data is good, but not Navigraph good.

Why can we not put questions/suggestions/complaints about the A300 or any other INI product into the correct forum. We ask developers to quickly respond to our questions, yet we make it harder for them to find them as well as making it hard for other users. I came here looking for feedback on the A300. I went to that forum, read every post and thought "Well done, I now know what everyone else knows". I jump into the general forum to see general stuff and there are very specific posts on products for which there is a forum. It's someone building a garage for you then you park your car in their bedroom.

An unfortunate consequence of using Xbox for MSFS is that you are restricted to putting things on your system that are allowed by Microsoft. In the case of MSFS through the MSFS store. So... 1. There is a limit to the size of a file that can be added to the store. 2. I don't think that a developer would be able to add too many liveries with the base plane and stay below that threshold. 3. Other than what is offered in the base, you will have to pay for everything else at whatever the asking rate is. I have not read Ini's EULA so I do not know if folks are allowed to create liveries for their aircraft and sell them. PMDG, for example, does not allow this. All in all, your universe of available liveries will be smaller and cost some amount of money that PC users do not have to deal with. Not a good thing, or a bad thing, just a consequence that comes depending on what decisions precede it. I thought about using Xbox for MSFS for about 3 seconds. Once I read about encryption and the closed environment, I dropped that thought.

GSX

Weird. I don't see this at all using MFG Crosswind pedals and as stated the steering on another controller.

I am not seeing this at all. In a flight now and didn't see it.

Yep, and as was stated, non-normal sim rates are not supported on their planes. Since it is not supported the issue that is seen is normal and not a bug and everyone will see/have it. Since it is not supported you have a few options: 1. Fly 1x sim rate 2. Fly other than 1x and accept that you will have more fuel when landing or plan accordingly. 3. Wait to see IF they support faster than 1x

Works fine for me. Either local issue or operator error. Study level aircraft require a bit of studying. Youtube videos by A330 Driver are a good source. Also search for the FCOM and give it at least a look over. I suggest a deep dive.

@Nico - Gumby @Helibrewer That worked! Thanks.

@Nico - Gumby The change recommended by Helibrewer worked for me.

Glad to hear, though frankly, I would never have noticed it since when I am taxiing I look outside. I only saw it because of when I assigned it. To me it was a minor issue, but saw others focused on it. Off to fly!

Search this forum. I put some links up to the A300 and A310 FCOM I found using the Google search term "A300-600 FCOM".

If I was on a SID with so many restrictions and could not get unrestricted climb, I would climb using LVL CHG instead. That way you would control both Altitude and Speed.

I will try this in the morning! Thanks @Helibrewer and @Nico - Gumby

Yep. Steers fine just the animation is fubar.

A search for A300-600 FCOM will provide you endless opportunities for reading enjoyment, including deep dives into the FMC. The A310 has the same FMC as the A300-600. Airbus A300 FCOM - Documents - Avsim.su (avsimrus.com) theairlinepilots.com/forumarchive/a310/a310vol1rev40.pdf You won't find or get any better documentation than you can find yourself.

I see the same thing here are my bindings through AAO. I have experimented with Repeat on/off and on with FAST, MED and Slow. This is set to my trim button on my HC Alpha yoke (left horn)

What controls are you using from the rudder? Since you are on Rudder Controls tiller, if you are making a crosswind landing and adding rudder after a crab to straighten up, that is also turning the nose wheel. You also could have some noise in your joystick or pedals (depending on what you use). I don't see this at all, but my tiller is not attached to my rudder.