Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Aerosoft Airbus, not happy....

Featured Replies

Works perfectly for me. Best plane I bought and currently the only plane I fly

  • Replies 36
  • Views 8.8k
  • Created
  • Last Reply

Top Posters In This Topic

  • Commercial Member

Great post Dave and I concur with everything you verbalized.

 

Hey, thanks Greg!  Very nice of you.

Dave Hodges

 

System Specs:  I9-13900KF, NVIDIA 4070TI, Quest 3, Multiple Displays, Lots of TERRIFIC friends, 3 cats, and a wonderfully stubborn wife.

  • Author

I spent the day flying the Airbus for many, many  hours today. Yes, it is different that the Boeing aircraft which I have had thousands of hours in. Still trying to figure out some of the difference, but anyway, flew the tutorial flight this evening and it flew great. Only problem I had was using the co-pilot and thought the co-pilot was supposed to slow my approach speed down. I realized on very short final I was still going 210 knots and the co-pilot hadn;t dropped any flaps or the gear either  :unsure: . Anyway I got the flaps down, gear down, and managed a good landing with runway to spare..... Got to have a conversation with that co pilot tomorrow....... ^_^

 

 

 

Happy to hear that!

 

If you had been down to green dot speed (= minimum clean speed) already, the active PM should have taken care of your flaps and gear. Something wasn't quite the way it should have been, I reckon. Would be interesting to see whether you can replicate that issue.

 

EDIT:

Any chance, you weren't in approach phase, but in descent phase, and the 210 kts resulted from a speed restriction in your STAR/approach? If you don't overfly the DECEL point, the approach phase will not be activated automatically. Then the activation would have to be done manually in the left MCDU, but this is not part of the F/O's flows.

 

At some point in the future you may consider getting the FS2Crew edition for the AS Airbuses: Procedures are more refined there. For example, in FS2Crew you actively have to call for 'gear down'; with the Aerosoft First Officer it is simply assumed you want the gear down, you hear the Captain's voice ("your" voice) calling for gear down, and the F/O will comply, without any actual intervention from you.

Edited by olli4740

What happened to AVSIM

  • Author

Happy to hear that!

 

If you had been down to green dot speed (= minimum clean speed) already, the active PM should have taken care of your flaps and gear. Something wasn't quite the way it should have been, I reckon. Would be interesting to see whether you can replicate that issue.

 

EDIT:

Any chance, you weren't in approach phase, but in descent phase, and the 210 kts resulted from a speed restriction in your STAR/approach? If you don't overfly the DECEL point, the approach phase will not be activated automatically. Then the activation would have to be done manually in the left MCDU, but this is not part of the F/O's flows.

 

At some point in the future you may consider getting the FS2Crew edition for the AS Airbuses: Procedures are more refined there. For example, in FS2Crew you actively have to call for 'gear down'; with the Aerosoft First Officer it is simply assumed you want the gear down, you hear the Captain's voice ("your" voice) calling for gear down, and the F/O will comply, without any actual intervention from you.

 

Thanks for the tips and you were correct.  I flew a route again last night and on the approach I realized that I was going to fast the first time, around 215 knots,  so the descent rate to intercept the ILS was way too fast, and that is why I never got gear down. I started the descent phase too late the first time. The second time I did it properly, got the aircraft started down right at the TOD prompt,  and it worked fine. I wound up flying this aircraft about 5 hours yesterday and am really starting to like. it. Even got a repaint for my Intercity VA. I have FS 2 Crew for my Q400 and it came with the Airbus as standard , which I was surprised at. I haven't activated FS2 Crew  yet, because I figured I would get used to the aircraft and just the co-pilot for now.   What I am really surprised at , and wasn't expecting , is the frame rates I am getting are just about the same as I get with with the Q400, locked to 30, and smooth as silk. 

 

 

 

Welcome! The FS2Crew stuff built into the Airbus is the FS2Crew RAAS (it's a limited edition that only works with the Airbus, not with other planes).

 

The FS2Crew crew simulation is not part of the package. You may ponder it once it gets on sale again, or just check the online manual in order to find out whether it provides an additional benefit to you.

 

Your frame rates are good news, too. Time to change the topic title, I guess!   :lol:

What happened to AVSIM

For those who are experiencing throttle issues, you can definitely get the 'bus to work with FSUIPC mappings. There is a supplement all about throttle setup included with the manuals. If you have a dual throttle you need to make sure this is reflected in the AS Config Utility. If you use FSUIPC you need to make sure you have the correct axis selected otherwise the plane won't "see" your throttle(s). I can't remember off the top of my head which is (are) the correct FSUIPC axis (axes), but one works, the other doesn't (play around) ! This evening I will check and update with the correct one.

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.