Azlog

Yeah I’m not quite sure how it is done in real life as normally on an ILS you’d want 180kts at more than 8 miles out, 160kts between 8 and 4 miles out and then final approach speed at less than 4 miles out but RNAV doesn’t really allow for that. Or at least not in the A300/A310. In the A320 RNAV works the same as ILS in that you just press the approach button and don’t think it matters if not fully configured Could be the order you are doing it. I always think level hold, final 3.0, profile and it works almost every time. Had a couple where I’ve had interpreted the chart wrongly and had to descend further before trying again but it always gets there eventually. Since getting the A300, I’ve been doing quite a few cargo ops routes in the US which involves a lot of airports with RNAV approaches You probably could disengage auto throttle and it might still work manually. I’ve never tried it as I normally keep auto throttle on until around 400ft to avoid chasing around trying to find where the throttle was set which can very quickly destabilise the approach

I feel that it’s also worth mentioning that the speed it gives you should be the speed you should use unless the headwind component exceeds 10kts (in which case, add half the headwind component minus 5. So 16kt headwind, add 3) or it is gusty (in which case, half of headwind before and all of gust. So 16kt headwind gusting to 20kt you would add 7) but no more than 15kt addition I think it is. The reason for the speed it gives is to allow the aircraft to sink gently down onto the runway when you reach 5ft after idling the throttles at 20ft or so. If you come in too fast, you’ll just float down the runway and touch down far too late and/or hit it hard

So normally I would get to the 4000ft and make sure I was in alt hold mode. Then I’d go to the approach page, make sure I had entered the MDA and press the final 3.0 button on bottom right. I’d then go back up to the autopilot panel and press the profile button. This should cause PDES to appear in blue under ALT. The lights on the autopilot panel won’t change Prior to reaching the WS816 waypoint, I would ensure that the aircraft is fully configured with gear down and flaps fully extended, otherwise it won’t do the RNAV approach When the VDEV in the approach page hits 0, the light on the alt hold button goes out (you’ll hear a click) and ALT on the PFD is replaced with a green PDES. The light on the profile button will not come on at any point during this. The aircraft will then descend on the glide slope at speeds dictated by what is entered in on the approach page which you can add wind correction to if you want a little faster. You can’t adjust the speed on the autopilot panel as this will take it out of “profile mode” and initiate a go around

Is probably more likely around 3 seconds than you should set it to hold for

A few things with the A300 that I’ve noticed on Xbox Series X: No noticeable nosewheel deflection with rudder controls tiller turned off. It should have +/- 6° of movement with the rudder pedals which is present on the A310 but not on the A300 and allows for directional control on the runway at lower speeds On take-off, the flight director should direct you to chase a rate of climb that maintains the V2 speed at take-off thrust until thrust reduction altitude where the set speed becomes active and the engines spool back as you reduce the climb rate. Instead, following the flight directors always shows the same climb out angle that puts you up at 200+kts climb out when the V2 speed can be anywhere from 145 – 165kts Autopilot disconnect alarm should stop once disconnect pressed for a second time (?) but it continues to ring out for a good while after When disconnecting auto-throttle, should you not get the 3 short bleeds that indicate that a status has changed from green to amber on the PFD? Unsure if this is a A300/A310 feature/quirk or if it’s something that needs fixed. Final Approach activates by itself when getting close to destination airport (when the next waypoint is the first waypoint on approach chart?) and changes the target speed to the approach speed while still in profile mode. It starts to then chase that target speed and will hold it just above stall speed as you add flaps and slats. In the A320, it will do the same but the speed will chase the S and F points instead of pressuring you to keep extending in a hurry feeling like you are about to stall. Manual setting of speed not possible until LOC and GS both active unless in level change or alt hold mode. RNAV appears to work in the way described for the A320 and so I prefer to use these but RNAV approaches are not always available and if NAV not working then you can’t do them Aircraft prone to not always following NAV (I’ve posted elsewhere on forum about this)

I find you need to be level in ALT HLD mode at the altitude shown at the start of the RNAV approach on the chart with the altitude set to that height. You then press Profile and PDES comes up in blue on the PFD under ALT and turns green when VDEV approaches 0. I have occasionally had to descend to the final fix altitude on level change mode and try again

In the A310 and A300 you can set the glide slope capture altitude during the cruise and then arm profile mode (middle click on adjustment knob). Profile Descent will appear in blue under ALT on the PFD. Once you reach top of descent, Profile Descent will become active and start descending in accordance with the constraints on the flight plan. Great way to make sure you don’t miss it if AFK

Hi. I’m also on series X and flying the A300. So far only the freighter version as I’d heard that the passenger version has some issues for some reason CTD on loading is an issue that has been unresolved since the A310 first appeared on the sim and is very frustrating. Don’t know why it happens to these 2 aircraft and no others Do you have any assistance settings turned on? Go into assistance and set as true to life. And also in somewhere else make sure the flight model is set to modern. This may well be the source of some of your problems. If you want markers or AI ATC assistance then you can go back in and reactivate these and it will be fine. Only issue I’ve had with autopilot was it deciding once to “ride the waves” while trying to decide whether or not to capture an ILS glide slope. Fortunately it was a cargo flight or there would have been a serious cleanup required in the cabin 😁 Aside from a couple of minor bugs like simbrief flight plan not loading into CDU, the main issue I’ve had with it is lag and stutters which again, the A310 is also very prone to when coming into large airports, especially at night or in bad weather

The trouble is that you need to be able to see the navigational display at the bottom while flying. So the camera angle tries to cover everything. I use a keyboard and have saved camera angles for everything I need around the cockpit and so have a view similar to your “feels right” view that I use for takeoff and landing where I don’t need to see the ND and need better perspective out of the window

Xbox series X. CTD every time unless: loading in from having had a CTD and not restarted the console recording a video using “start recording” on Xbox menu just prior to trying to load in