Crabby

There are FCOMs available on the internet. Just search A300-600 FCOM

My bad. I was in another plane in my head. Once at the platform altitude (the altitude that intersects the iron cross on the chart) press profile button on the mcp. You should see P.DES arm in the PFD, if everything else is set right. When I fly, I use profile descent to about 30 miles from the airport then I switch to LVL CHG to get down to the platform altitude. This puts me in ALT mode when I hit that altitude. Once there, I hit the profile button on the MCP and check that P.DES is in standby. I know it is a little weird but remember this aircraft was released when MTV was only two years old and still ONLY played music videos. For most, this is not your dad's VNAV it's your grandad's VNAV.

1. you have to be at the platform altitude in a mode other than profile (ALT hold for example) 2. Once at the platform and with the MDA set and the descent angle showing, you then arm profile descent (pull on the alt knob). Profile descent should show on the PD as armed. You should be fully configured at the FAP for landing.

Well without pictures of the overhead to include the ADIRs section, can't tell what might be going on.

First thing I would look at is the little knob just below the HDG push button in your picture. That controls the MCP lighting (both the integral and windows). It appears everything is working but would need to see top panel to be sure.

Going off a bit of memory here as I am in the field working (someone has to build those communication towers). Also, not sure if this is a A310 memory, but the 300-600 should have the same ability. It can fly a coupled DME Arc, however the ND will show a straight line between the arc. I think I saw INI say this was a quirk of the real aircraft. That being said, I have not done one yet. Also, I do not actually build the towers, my crew does. I am basically a gopher when in the field for the guys that do the actual hard work.

Well, after over 100 hours of flying the A300 with an average flight of about 3 hours each, never suffering any kind of issue, I came back from a short dinner while at cruise going from KDFW to KPHX at FL280. Except I was not at FL280 but bouncing around on the ground near the Arizona border. I have no idea what transpired, I was not at the controls, but the only thing that came to mind is the "falling out of the sky" issue. I don't know what the fuel state was as I was so pissed I didn't check.

CI, cost index, etc. etc.

"The ones lacking test" Is there somewhere where I can go to see which releases "lack test"? I can't seem to find that. Is this just an assumption? I looked over the release notes to 1.04 and did not see anywhere that indicated that the release was not tested. You post is such a side handed complaint about a now old release. I wonder why you posted it in what is basically a congratulatory thread.

I have to be silly and ask. You guys are not using the in sim refueling, correct? You are only using the EFB for fueling? I have not seen this (yet?) so I just wanted to confirm to see if there is a difference in what I am doing and what is being done that causes it.

yep. Lot of people updating. No need to wonder.

Oops.

Did you enter the Vspeeds on the TO page of the FMC. Mine are working fine and have always worked. V1 and Vr are entered in the TO page. V2 is entered in the speed window on the MCU.

5 flights. Cannot replicate.

I am flying online right now with VATSIM coverage. The controllers are not saying anything (and they would) about what they are seeing on their end. My transponder is set to TA/RA. I am showing Mode C in teh Vpilot app. No issues. I will take a look at the FCOM to see if I can decipher the rest.

Cannot re-create on my set up.

Cannot recreate. It is in inHg for me on the performance page.

A search of the systems forum should yield what you are looking for. I am traveling and would have trouble posting a link

You need to have the approach phase filled out (selection of flaps and MDA). You also need to activate the approach phase by hitting the bottom right button on that page. I do it between 30 and 20 miles out from the airport. If you are autothrottle after that, you would extend slats at the S on the speed tape, then flaps. The autot throttle should adjust the speed accordingly. All of this is from memory because I am traveling and I don't fly the aircraft on auto pilot/throttle below 10K as I like to fly it. The only exception to that rule would be if I am anticipating a true need to auto land (weather).

Extremely bad guess (assumption). I now have over 40 hours in this plane, average flight 2 hours, and have never seen it. So, that leaves only three possibilities by Occam's Razor: 1. I have the only working copy of the plane. 2. There is an underlying issue triggered by any number of causes (geographic location of aircraft, winds, weather, altitude, speed, time of day, length of flight, input combination, button push combo, yadda yadda etc etc ad infinitum). See why this whole trouble shooting thing is hard? You can't just scream fix it! It does not work that way. You cannot fix what you cannot find and replicate. 3. The problem is on the end of the MINORITY users. Tricky too. Common addon conflict, common control issue, common system config, common gpu version, common gpu firmware, common radio station playing in the background and again, yadda yadda, etc etc ad infinitum. Can you see how that also is hard? Now, number one, we can most likely rule out. I don't know INI and I probably stir up enough crap here that I would not be on their let's be especially nice to Crabby list. (Everyone should have that list though, in my opinion). We are left two difficult to work through options. One is difficult for INI and one for you. I get it, this sucks. However, tantrums, speculation and some of the outright ridiculous things said or guessed don't and won't help. We can also, at this moment, not rule out the issue being sim/Asobo related. Not every developer implements their aircraft in exactly the same manner. The SDK is reportedly thin on meat. Every developer that I use has had to work developer magic in some way to make their complex aircraft work. Many times, right after that magic works, the ground rules are changed (see PMDG UFT for example). In order of probability, this would be number two after the Crabby is the only one with functioning software.

Not a proper statement or starting point for trouble shooting a problem. Almost as bad as “it worked yesterday”. I run it fine (30 fps min no stutters) on a 9700KF 32Ram and a 2070 Super gpu. I have all the study level aircraft. My setting are DX11 DLSS frames locked in Nvidia to 30. My graphic settings are all on high. I run my TV native resolution.

What the literal hell? This is childish behavior at best. The A300 did not have in air refueling. How about you grow up and properly plan your flight instead of trying to force a company to make their product stupid to comply with stupid use.

First check your calibration

7500...7500...7500

So far I have seen nothing about being able to do this in the FCOM. My guess is it was not an option. I think only Russia and North Korea(?) use metric flight levels. China changed to the RVSM format in like 2007ish. To be really confusing, I remember reading that some of the "stan" countries use feet for light levels and below the transition they use meters. Could be wrong, going from memory.