KorEl

Same here, that's how it works for me since ethe first version, but I think it is a feature not a bug.

For me has happened 6 times out of 75 flights since release. The rate is not so annoying, but I hope it is fixed one day. 🙂

It is PC, but I dont think there is any actual difference between 1.0.7 and 1.0.8

Unfortunately not fixed... My first flight with 1.0.7, the bug occurred on the ground. While I was taxing for t/off the a/c started bouncing on the taxiway. I had the usual extreme negative values for fuel quantities. Restarted the flight and second attempt was OK. Maybe the bug is in the EFB, this adds and removes fuel, and the bug does not exist for the A310 which has a different EFB.

Same here... Was my 4th flight with 1.0.6, happened on approach after a 3hrs flight.

After v 1.0.6: The "violent AP roll to the right" seems to be fixed,at least when tries to enter a DME arc, but the AP still cant fly the arc, it permanently enters a turn now. After setting a direct to GONSO continues normally

MD82 is right, reverser sleeves are full open or full close, no intermediate position in any case, no connection with engine thrust setting. I am a retired engineer, worked with A300B4's and A300-600's for 30 years.

I confirm too. TOGA power can be achieved only with the A/T engaged pushing the buttons. Without A/T manually advancing the throttles N1 does not go over 87%. It is not a calibration issue, checked with the A310 and it works as it should.

LFRS RW21 has no ILS, only RW 03. You may tune the ILS, you will get the CAT category of the ILS, but there are no LOC and GS to guide the AP. So the only way for auto apr to minimums is the RNAV apr. To follow the VNAV path for the RNAV apr in the A300 is not the same with modern a/c. You must enter the DH in the MCDU and the a/c will make the required degrees decent after reaching the FAF. See the video tutorials (RNAV apr) for the exact procedure required.

Τhe inibuilds Α310 (and the A300 of the initial versions) could do DME arcs, although they make a scary turn to the opposite direction before entering -a bug reported here: but then they follow the arc quite good. This is the same procedure flown with the A310 today:

OK I 'm almost sure now: This happens every time the AP tries to enter a DME arc Try this LGAV KEA2F KEA UL607 GIVIS UJ62 NAVUS NAVU1A LGIR (VDM 27 GONSO transition)

This happened twice at the same route, same spot at descent after TIGRA, The FP was LIRF PEP9A PEPIX L50 UNIXO M620 SOR M603 KAPPO L995 TIGRA TIGR2T LGKR Approach VDM Y 34 DIREX transition If someone wants to try his luck 🙂

Yes, the difference is that normally when the AP tries to follow the course does it with a max 30deg bank angle and the control column moves accordingly. Here the control column does not move and if you don't disengage the AP the aircraft ends up doing a barrel roll.

Same here... Happened twice during descent after 1.0.5, I was in prof & nav I don't know why THR L was activated and the engines went to TOGA. Plus one more flight I had the "fall out of the sky" bug. Seems to me that all problems start when the main tanks are about to be empty. So, this is the end for now, the A300 is grounded since the next update...

Yes, always refuel using the EFB. BTW: today I found at ini manager that I had an update after updating to 1.0.5, a small one just 380bytes. Is there a new update after 1.0.5 or my files were corrupt/missing? Is this a possible cause for problems?

Occurred again in my second flight with 1.0.5 Something goes wrong with the fuel:

I tested the EPALO1A apr to LGIR which also requires a DME arc LGAV/03R KEA2T KEA DCT SOREV UL617 MIL UM749 EPALO EPAL1A LGIR/GONSO.D27 same behavior, left turn instead of right when reaching the arc wp

Tried the same route/apr and had the same behavior, turn left instead of right to follow the arc.

ASUS B560M-E, i5-11600KF, 32GB RAM DDR4 3200, win11 22H2, RTX 3060 12GB, 536.23 drivers. MSFS runs on DX12, DLSS super resolution-performance, vsync-off, LOD 200. I use FSLTL, simlink, a big number of freeware and a few payware airports, pmdg 737, DC6. Bug occurred 2 times out of 41 flights, average flight duration 2hrs.

Checked this in several flights, the TOD mark on ND disagrees with actual VNAV path, actually the mark TOD is later than the actual, you are 2500+ ft higher if you follow it.

OK, today I realized that the icing effect on wipers exists, but is barely visible because of the base color of the wipers. So what is required is just a darker color 🙂

This has nothing to do with the "falling out of the sky" bug. It is like hitting an invisible wall, falling vertically, the flight surfaces do not move with the AP off. Second time I experienced the bug I was cruising at 34000ft, m 0.80.

Could we have please icing effects on the windshield wipers? This is the most easy and realistic way to detect icing.

-After 4 flights with the passenger version, for my first with the freighter I realized that the maintenance effects are not airframe specific (had worn tires, required engine oil servicing). I think they should be. -15 minutes to service an engine with a few quarts of oil is a bit too much, of course you can click "finish now" but as long as it works, better make it more realistic, 5 minutes are ok. 🙂 keep up the good work!

Happened again today, 5th flight after 1.0.3. first with the freighter version. Just as I clicked on the FO's sunshade the AP disengaged and started falling vertically. I could lower the gear, operate the engines. shut them down as well as the batteries, no effect.