JS2Tango

Same issue here. Engaging AP after loading from an autosave produces a nose up pitch and sends the aircraft into A.FLOOR

Same issue here. Engaging AP after loading from an autosave produces a nose up pitch and sends the aircraft into A.FLOOR

Same issue here. Engaging AP after loading from an autosave produces a nose up pitch and sends the aircraft into A.FLOOR

Definitely not a sim issue, as the PMDG doesn’t have this. @Eddiecan this be passed on to the team please. Thanks

Why in MSFS 24 is the cockpit and cabin glass opacity ‘smokey / grey’ compared to being clear on MSFS 2020? It looks awful.

Thanks for the information! In that case, I’m looking forward to to v1.0.9’s release - hopefully sometime soon! Cheers!

Using version 1.0.8 I am no longer hearing the “Autobrake Off” callout, only an ECAM warning tone instead. I’ve also read (haza2) that the ANF auto-open behaviour on landing has been disabled in v1.0.8 - I assume this choice was made due to possible lag on touchdown when loading the ANF for the airfield, if it has not already been loaded earlier in the flight. A suggested fix - pre-load the destination airport within the ANF in the background after importing the route into the MCDU. This will alleviate any lag on touchdown. Loading the destination airfield in the ANF at the gate prior to departure, reduces the opportunity for lag elsewhere in the flight. Thanks.

Yes, same experience here.

Agree with this, the engine shake is near nonexistent at the moment.

+1 for this

Fixed V1.0.2

I solved mine by turning off my rolling cache.

For those of us wanting to use the A350 in a home cockpit, it would be fantastic to access the avionics via a web browser, hosted in a localhost fashion, to allow us to export them to other machines. This would be a significant performance increase. Heck, even add it as a paid 'pro' package, I'll buy it immediately.

Hmm, there goes my theory then. I had major stutters landing at EGLL, thought it was because my v-pilot was loading in iniBuilds A350s as model matching. Maybe not.

Are you flying on VATSIM when this occurs?

Seems to not be implemented

I also noticed this on an ETOPS flight last night.

I'm on the latest update, MSFS2020, and have had the same error occur twice.

Hi, Has anybody experienced a Resolution Advisory yet? I've just been in a situation where an RA would definitely have occurred in the real aircraft (mid air collision) but received no notification to descend or climb, no 'TRAFFIC' callout, etc. Is it not simulated, or is this a bug? Thanks.