Crabby

Yes and no. When you intervene with the speed though other changes occur too. From the FCOM 3 SPD/MACH SELECTOR KNOB TURN Sets the speed/Mach target value. PUSH Allows a speed or Mach to be preset. The PRE SET light illuminates. (Second push deactivates pre-set function, and the PRE SET light goes off.) PULL (while PROFILE mode is engaged) Causes a manual reversion to selected modes: – If in level flight, PROFILE mode disengages and SPD mode (A/THR) and ALT mode (AP/FD) engage. – If in climb or descent, PROFILE mode disengages and LVL/CH engages. In both cases, the speed/Mach window synchronizes on the present aircraft speed/Mach.

1. Did you hit the LSK key next to where it says ILS08R? Have to ask. 2. Always select the runway first on departure and runway/procedure first on arrival. This allows the FMC to filter for only the procedures that are for that runway.

I don't think the Tropopause is entered. Those fields are populated for me when I initialize the flight from the ACARS menu linked to Simbrief.

The problem is separating a CTD caused by the A300 (or any addon of any type) from CTD WHILE USING the A300 (or any addon). Unfortunately, most of the CTDs fall into the second category. Why? I don't know. This is why I learned to be meticulous with my installation. The only thing I do not control in my install is when MSFS updates. Other than that, I control it all. I do this by 1. Never buying/using ANYTHING from the Marketplace. The only exception to that was the A310, which I have now removed because what I really wanted was the A300. 2. My community folder is full of nothing. Well, ok. It is full of symbolic links, but not many. 3. I use Addons Linker from flightsim.to to create the symbolic links. 4. The only addon I have that is always "turned on" (the symbolic link is active) is GSX and only because I use it every flight. 5. Before I start a flight, I use Addons Linker to "turn on" (activate the symbolic link) for only the aircraft I will fly, the livery I will use and the two airports I will fly from/to if they are not default. I learned early on that the drop it and forget it nature of the community folder would end up being a troubleshooting nightmare. I was on a flight from KONT to KPHX in the CRJ from Aerosoft. My sim crashed hard. What happened? I had no clue. Turned out after clearing out my community folder and adding things back in, a freeware airport in Japan was causing my CTD issue. I immediately got addons linker. I have had 18 CTD total since the day the sim was released (I log each one). I can tell you that I have never had any of my addon aircraft cause a CTD. 11 of the CTDs were caused by freeware scenery (why? I don't know. Maybe they did not follow the SDK or something. Don't care, sent to trash). 6 were caused by liveries (why? still don't know/care). 1 was and is still a mystery (why? Don't know/care. It has not repeated). 6. I only use the sim to be the sim. I don't use the in-sim controller profiles except for view commands. When I got the A300 I did not use (still don't) any livery other than American that is done by ini. My first 5 flights were less than 1.5 hours. I have now stretched it out to 4 hours after 20+ flights. Other than the known and mainly cosmetic "bugs", I have had zero issues with the operation of the airplane. The way I do things can be daunting for someone that is 2 years in and has hundreds if not thousands of folders and crap in their community, but if I were to be hired as an MSFS coach, this is the first thing I would make my pupil do. I started in 1979 and I can tell you that either you control the sim, or the sim controls you.

I am not understanding this issue. There must be a binding problem in the sim. I use AAO and have the knob in IAS a lot. My in sim controller profiles are all blank.

As a last ditch effort, go into your in-sim bindings under the mouse and see what you may have assigned to the button on the mouse you are clicking. Remember, you may not have assigned something, but Asobo could have. If that shows nothing, I am out of options based on my sim.

Can't replicate. Check all of your bindings, especially if using the in-sim profiles. I use AAO, so I would not see that issue.

I don't know what was done wrong or what was thought was done right. All I know Is I can enter speed and altitude restrictions at waypoints and modify them as I need. That is why I said doing SOMETHING wrong.

Yep, flew that yesterday to see whats up.. At most, I use Navigraph so I have to manually add the waypoints and restrictions, but it flew it without a problem. That is how I state it is not a bug. If it was a bug, I would see the same thing you do. So, either I have a better bug free version of the plane, or the bug does not exist. In 21 flights, I have not had a single issue with navigation on any SID/STAR/Route/ILS/RNAV APP.

After the scenery updated? You have already shown it is a scenery problem, not an A300 problem.

Key binding? Noisy pots on controllers? There could be a multitude of reasons this happened. Impossible to tell with the description and information provided. The only thing I can say for sure is that on my system, with my controllers, with my bindings, the WAY I do my bindings, in 20 flights between V1.00 and V1.02, I have not seen this even once.

Again, doing something wrong. Yesterday I was inbound CYYZ and got a descent to and maintain 17000 which was different from the SID. I selected the RLSK by the waypoint and typed 17000 in the scratchpad, then hit the altitude box and insert. Worked fine.

Very rarely these days. Back in the old days you could tune an NDB into an AM radio station for guidance (If you knew where the antenna was). Most of the time, you will only use an ADF/NDB on an ILS approach that has one associated with the approach, like an in conjunction with the OM.

If you were on an ILS approach, why were you still in NAV mode? You should have been on the ILS flight directors and in LND mode. You would not have reached your missed approach point in NAV mode. You guys are doing something wrong.

Well, can't assist then. Mine and others are working fine. Can't be a bug if that is the case. It will be on those seeing this to capture the triggers. I would suggest getting in direct contact with ini Support with proof of purchase. This appears to be over the heads of mere product users.

Not all RNAV departures have an initial RNAV let. Out of KCLT there is the BARMY4 RNAV SID. Depending on the runway you take off on you will fly a heading. For example from 18C you will fly heading 183 to 1260 feet then 183 thereafter or the heading assigned by ATC. At some point you will be either vectored to or cleared direct to MESHY. There will be no initial automated route to MESHY, just basically a straight out climb. If you try and hit NAV, it won't work and if you look at the FMC it will say MANUAL. Make sure departures like this are not the source of any "problems" you are seeing.

Yep, if I am with ATC on departure, I fly the SID with LVL CHG. Profile does not, by design/technology, fly the restrictions on climb. With no ATC, I just use profile mode.

Something is weird somewhere. Mine has not had a CTD even in v1.0.0 Granted, I keep my community folder lean and mean. At any given time there are only two airports, one aircraft and one livery active.

Ok, but you said PFD. 1. Detune the ADF units. In other words, change the frequencies so they are not receiving an active frequency. This is as simple as spinning the knob just a digit. 2. Unless you have a PFD/FD failure, you should be "flying the needles" (the flight directors) on an ILS approach.

Are you not flying the flight directors for an ILS approach?

Do you mean the Nav Display (ND). The PFD is the artificial horizon and speed tape.

5.3. TACT MODE KEY Allows access to the current flight phase page (climb, cruise, etc.). Changes made to the strategic modes on this page effect performance only in the current flight phase.

In the mean time, take a look here. Emi knows what he is doing. Watch the whole playlist.

I have seen a few posts with similar reported behavior. I cannot replicate it. NAV(LNAV) has been spot on for me on procedures and route. Without looking over your shoulder (video) from FMC/MCU inputs and actually flying, this will be hard to help out on.

I wish I could say I remembered this from the FCOM, however, what really happened is I was taxiing out at KRNO and noticed that my CG was not displaying. I got in a hurry and skipped the flow. So, no traffic on VATSIM at the moment, I shut down the engines on the taxiway and filled in the INIT page 2, restarted the engines and took off. Before doing that, I kept trying to go to INIT page 2 and of course it would let me. Only gained access by shutting down the engine.