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.

FBW A380 Thrustmaster Throttle Quad

Featured Replies

21 minutes ago, DAD said:

That is also covered in the FBW documentation. I am not aware of the necessity to tone anything down. Here all working out of the box. Instead your comment „Throttles shoot straight up to climb when putting in power.“ sounds like your throttle is NOT calibrated IMHO

I will tone down resposiveness. With fenix/inibuilds no issues. It did the calibration job but the throttles shoot up to guess I have to manually edit the -1.00 to 1.00 points.

I9 12900K @ 5.1ghz P-cores/ 4.0 ghz E-cores fixed HT off / Corsair iCue H150i Capellix Cooler/ MSI Z690 CARBON WiFi / 32GB Corsair DDR5 RAM @ 5200 mhz XMP on / 12GB MSI 4090 RTX Ventus 3 / 7,5 total TB SSD (2+2+2+1+0,5 all NVMe)/ PSU 850W Corsair / 27" (1080P)

8 hours ago, Farlis said:

 

I would like to know how this system operates in the real world with fast exits. Because it will break your aircraft down to 10 knots upon reaching  the exit and that is of course too slow if you are dealing with a high speed exit.

SOP is to disengage BTV at 70 knots by pressing the autothrottle disarm button on the side of the levers

16 hours ago, DAD said:

Take those, x for 1 and 2 and likewise y for 3 and 4. just the input is more specific, called differently. Not in front of my pc now but FBW has neat documentation on their website how define the mapping.

https://docs.flybywiresim.com/aircraft/common/flypados3/throttle-calibration/

Just remember that clicking into that scan field during mapping and then moving the throttle does not work, at least on my end that will recognize and map buttons not axis, i needed to select the right mapping from the drop down list.

See picture from above link:

a380x-msfs-controller-2axis.png

 

All fine here now except reversers are only working for engines 3 and 4,see my other post elsehere, will need to check whether I selected the independent axis setting to 2 tomorrow as described in said FBW documentation (guess I set it to 4 axes by mistake)

a380x-2-independent-axis.png

EDIT learned that the 380 only has reversers for engines 2 and 3. just in case you may be wondering - like I did.

 

I also have the TCA two engine throttle, but despite binding engine 1 and 2 to axis 1 in MSFS i still had to calibrate 4 independent axis to get it work.

13 hours ago, David Roch said:

When the A380 was first designed, there was no reverse thrust at all. 

 

This needs to be corrected. During the design phase and before certification, there were initial discussions about the efficiency of the reverse thrust, especially whether two were enough. Due to wing and flap characteristics, brake design, and slower approach speeds, it was determined that two would be sufficient, which led to this kind of speculation.

747 Captain for the last 39 years, and still learning. 

On 11/1/2024 at 3:05 PM, Farlis said:

Exactly. Reversers don't shorten your breaking distance on dry runways they just help the autobreak system so that it can use less force, keeping the breaks cooler for the turn around.

And since most airports prohibit the use of reversers above idle except if they are necesarry for operational reasons, I never use them anyway unless I'm simulating a turnaround.


We probably didn’t fly the same planes !! 😮
Yes Sir, reversers can play a significant role in reducing braking distance on shorter or slippery runways.

- PC Hardware: AMD Ryzen 9 9950X3D //  Asus ROG Crosshair X870E HERO //  2x32Gb Corsair Dominator Titanium DDR5 6000MT/s CL30 //  ASUS ROG Strix GeForce RTX 4090 OC Edition // 4Tb Corsair NVMe M.2 MP600  //  Corsair 1600W PSU
Samsung Odyssey Arc 55" curved 165 Hz monitor.
- Simulator Hardware: VIRPIL Constellation Alpha Prime + VIRPIL VPC Universal Control Panel - #3 + MOZA AY210 Force Feedback Yoke + WINWING URSA MINOR 32 Throttle & PAC Metal + WINWING SKYWALKER Metal Rudder Pedals + WINWING Airbus FCU & EFIS + WINWING Boeing 3N PAP + WINWING MCDU-32 + WINWING PFP-4 + WINWING PFP 3-N + WINWING PFP-7. 

   

 

 

17 hours ago, LRBS said:

This needs to be corrected. During the design phase and before certification, there were initial discussions about the efficiency of the reverse thrust, especially whether two were enough. Due to wing and flap characteristics, brake design, and slower approach speeds, it was determined that two would be sufficient, which led to this kind of speculation.

No speculation on my side 😉
I was personally involved in the A380's design between 1994 and 1996 in Toulouse.
The first sketches of this super jumbo did not have thrust reversers at all.

- PC Hardware: AMD Ryzen 9 9950X3D //  Asus ROG Crosshair X870E HERO //  2x32Gb Corsair Dominator Titanium DDR5 6000MT/s CL30 //  ASUS ROG Strix GeForce RTX 4090 OC Edition // 4Tb Corsair NVMe M.2 MP600  //  Corsair 1600W PSU
Samsung Odyssey Arc 55" curved 165 Hz monitor.
- Simulator Hardware: VIRPIL Constellation Alpha Prime + VIRPIL VPC Universal Control Panel - #3 + MOZA AY210 Force Feedback Yoke + WINWING URSA MINOR 32 Throttle & PAC Metal + WINWING SKYWALKER Metal Rudder Pedals + WINWING Airbus FCU & EFIS + WINWING Boeing 3N PAP + WINWING MCDU-32 + WINWING PFP-4 + WINWING PFP 3-N + WINWING PFP-7. 

   

 

 

On 11/1/2024 at 8:18 AM, Piotr007 said:

Hey guys, how to tune with airbus thrustmaster from idle to clb to have it much less sensitive? Throttles shoot straight up to climb when putting in power.

I highly recommend ordering this.  It takes a few weeks to arrive but I've been very satisfied.  

 

5800X3D, 4090FE, 64GB DDR4 3600C16, Gigabyte X570S MB, EVO 970 M.2's, Alienware 3821DW  and 2  22" monitors, Corsair RM1000x PSU,  360MM MSI MEG, MFG Crosswind, T16000M Stick, Boeing TCA Yoke/Throttle, Skalarki MCDU and FCU, Logitech Radio Panel/Switch Panel, Spad.Next

3 hours ago, David Roch said:

No speculation on my side 😉
I was personally involved in the A380's design between 1994 and 1996 in Toulouse.
The first sketches of this super jumbo did not have thrust reversers at all.

It's interesting how we learn something new every day. Nobody mentioned anything to us during the initial and recurrent training sessions. Despite the questions raised about the choice of two versus four engines, it’s good to see some clarification emerging. 
 
Additionally, I hold dual qualifications for the 748 and 388 (not after DEC), and I really enjoy flying the 380. It is a marvelous aircraft, especially when it comes to technology and cockpit comfort, especially in comparison to the 748. Although I started my career with Boeing, after spending so many years in both the 748 and the 380, it would be difficult for me to choose one over the other. After DEC will be only 748 for a short period before retirement. At least the "QUEEN" will guide me through to the finish line.

747 Captain for the last 39 years, and still learning. 

Calibrated it again works like a charm now. Only issues I have now is A/P disconnect not stopping. Go to outside view and back to cancel it.

Edit:

Nvm different from A320. Second square knob beneath instead of the above.

During weekend now I have time to learn this beast to fly. What a gem😅😇

Edited by Piotr007

I9 12900K @ 5.1ghz P-cores/ 4.0 ghz E-cores fixed HT off / Corsair iCue H150i Capellix Cooler/ MSI Z690 CARBON WiFi / 32GB Corsair DDR5 RAM @ 5200 mhz XMP on / 12GB MSI 4090 RTX Ventus 3 / 7,5 total TB SSD (2+2+2+1+0,5 all NVMe)/ PSU 850W Corsair / 27" (1080P)

Another report:

 

My 4090 rtx with 8k liveries got crippled with max fsr/screen res during landing at LFPG. 

Began with heavy tearing when panning around suddenly. High VRAM usage was culprit.

Toned down from 200 max to 100 standard native res. It solved the tearing. What a hog on the resources. Jeez😂😂

I9 12900K @ 5.1ghz P-cores/ 4.0 ghz E-cores fixed HT off / Corsair iCue H150i Capellix Cooler/ MSI Z690 CARBON WiFi / 32GB Corsair DDR5 RAM @ 5200 mhz XMP on / 12GB MSI 4090 RTX Ventus 3 / 7,5 total TB SSD (2+2+2+1+0,5 all NVMe)/ PSU 850W Corsair / 27" (1080P)

  • Author

Thanks for all the replies. What this hasn't shown me is how to setup with FOUR throttle leavers...not just two. Assigning X to 1 and 2 and Y to 3 and 4 puts one throttle leaver for two engines. I want to assign one lever to an engine.  Thanks

AMD Ryzen™ 9 9900X3D, AM5, Zen 5, 12 Core, 24 Threads, 4.4GHz, 5.5GHz Turbo
64GB (2x32GB) DDR5 6000MHz Corsair Vengeance
32GB GeForce® RTX 5090 Graphics Card

One TCA Quadrant with switch at front to 'Eng 1&2' position.

Other TCA Quadrant with switch at front to 'Eng 3&4' position.

Both quadrants need their own USB cable plugged in.

In Controls page in the sim, you'll have one quadrant profile recognised by MSFS for Engines 1 & 2. The other quadrant needs to be manually set up.

Use 'Throttle 1 axis' for lever 1, 'Throttle 2 axis' for lever 2 on the quadrant for engines 1 & 2.

Go to the manual profile for the second quadrant and use 'Throttle 3 axis' for lever 3, 'Throttle 4 axis' for lever 4 on the quadrant for engines 3 & 4.

AMD Ryzen 5800X3D; MSI RTX 3080 Ti ; 32GB Corsair 3200 MHz; ASUS VG35VQ 35" (3440 x 1440)
Fulcrum One yoke; Thrustmaster TCA Captain Pack Airbus edition; MFG Crosswind rudder pedals; miniCockpit FCU; CPFlight MCP 737; Logitech FIP x3; TrackIR

MSFS; Fenix A320; A2A PA-24; HPG H145; PMDG 737-600; AIG; RealTraffic; PSXTraffic; FSiPanel; REX AccuSeason Adv; FSDT GSX Pro; FS2Crew RAAS Pro; FS-ATC Chatter

I have to confess it took me a good couple of hours to get my head round setting up 4 TCA throttles.  I did find this video helpful and it might help others... (although for some reason Engine 4 won't switch on properly even though the others are fine).

 

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.