JF1997

I don't think its a case of the airports being at fault, since the update I've flown to LIPZ, LSGG and ENGM and all have been a stutter fest on final approach, before the current version I was having the same experience as you but in 1.06 the FPS experience has changed. In other aircraft the FPS remain as expected. All well and good stating a few pilots may be having this issue but its still an issue that needs to be resolved for paying customers.

Echoing this issue, v1.06 has just been ruined on performance for me. On the ground its fine, when in the air it just falls apart. I've just tried cw4ogden's temporary fix (thanks for posting that) and it appears to certainly help with solving the issue on a temporary basis but there is definitely something wrong with performance on this build. 7800X3D and a 3080Ti ran previous versions of the A300 really well but the current version is terrible for me.

Same issue here. This is ridiculous

+3

Exactly the same issue as others are experiencing.

Echoing this, the small angles on the ground the rudder just don't work, if you look closely the aircraft does try to do something but then twitches back. Also the takeoff now with the rudder authority is terrible, pulls to the left heavily under 100kts and as soon as you pass 100kts its suddenly less sensitive but still pulling to the left.

+1, back towards the FlySmart look previously used in XP the information included in the top right is great to have all in one place, I prefer the layout also. Even better if it went close to the IRL Fedex one!

Hey Ini, Starting off with saying great aircraft by the way, fully enjoying it! I'm doing packs off operations, running Pack 2 off during all operations on the ground and Packs 1 & 2 off during takeoff similar to the following video: Now, when I start the engines I get a Pack 2 error upon start and have to clear it when it pops up, I then taxi out and during my line up procedure I turn off Pack 2, I then get the same error and have to clear it. In the above video this does not occur (I know we don't see engine start so maybe the error pops up then but I'm **Assuming** it's similar to the A320 where an error doesn't pop up. **Assuming** it's a similar process to the A320 this error is one that usually pops up in the air when you've been too slow to turn the packs back on. Clearing the errors is a bit of a pain when trying to run the below the line checklists and line up on the runway while communicating with ATC. Can this be checked and compared against the video above?

Just had this on arrival into Toronto