October 31, 20241 yr I have the Thrustmaster Airbus throttles and I'm having difficulty assigning them to engines 3 & 4 on the A380. I've clicked on the 3 & 4 button and in windows calibration they are all working correctly, however when trying to assign in MSFS to throttle 3 and 4, it recognises them as X and Y and tries to override engines 1 and 2 (which are working perfectly). Can anyone help with this? 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
October 31, 20241 yr You need to assign Axis 1 to Throttle 1 AXIS and Throttle 2 AXIS in the MSFS settings. Same for axis 2 to for throttle 3 & 4 You can also do the same thing with the fuel cutoff, switch 1 to engine 1 and 2, switch 2 for 3/4 Cheers N.-
October 31, 20241 yr On another note, i noticed there are two issues with the TCA throttle and the plane - Spoiler lever is finicky. Setting it to 1/2 gives me like 1/4 in the cockpit. 1/4 in the hardware gives almost 0 spoilers. It works fine if I use the throttle axis from my joystick as a spoiler - Auto brake selector also does not work properly. Imposible to select BTV. Cheers N.-
October 31, 20241 yr Author 1 hour ago, neucoas said: You need to assign Axis 1 to Throttle 1 AXIS and Throttle 2 AXIS in the MSFS settings. Same for axis 2 to for throttle 3 & 4 You can also do the same thing with the fuel cutoff, switch 1 to engine 1 and 2, switch 2 for 3/4 I only have axis X and Y not 1 and 2? 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
November 1, 20241 yr 1 hour ago, BWBriscoe said: I only have axis X and Y not 1 and 2? 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: 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) EDIT learned that the 380 only has reversers for engines 2 and 3. just in case you may be wondering - like I did. Edited November 1, 20241 yr by DAD Stupidity and lack of 380 thrust reverser knowledge Phil Leaven i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"
November 1, 20241 yr When the A380 was first designed, there was no reverse thrust at all. A380s are designed to come to a complete stop using their brakes alone. Then Airbus added 2 reverse thrusters to minimize the risk of aquaplaning. The A380 has massive brakes - its thrust reversers actually don't stop the plane in a shorter distance, they just take some of the strain off of the brakes. The engines are massive and having only two reversers does the trick while also saving a bunch of weight and putting less stress on the wings structure. - 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.
November 1, 20241 yr 10 hours ago, neucoas said: - Auto brake selector also does not work properly. Imposible to select BTV. You can only select BTV if you have selected a runway and runway exit on the OANS map by clicking on them. Inflight you only do this in plan mode. 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. Edited November 1, 20241 yr by Farlis
November 1, 20241 yr 1 hour ago, David Roch said: its thrust reversers actually don't stop the plane in a shorter distance, they just take some of the strain off of the brakes Which scientifically would mean... They WOULD stop the plane in a shorter distance if the same braking was used. Russell Gough SE London
November 1, 20241 yr 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. 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)
November 1, 20241 yr 5 hours ago, David Roch said: When the A380 was first designed, there was no reverse thrust at all. A380s are designed to come to a complete stop using their brakes alone. Then Airbus added 2 reverse thrusters to minimize the risk of aquaplaning. The A380 has massive brakes - its thrust reversers actually don't stop the plane in a shorter distance, they just take some of the strain off of the brakes. The engines are massive and having only two reversers does the trick while also saving a bunch of weight and putting less stress on the wings structure. The A380 only has two reversers because Airbus figured the outboard engines hang too close to the runway edges and could throw up FOD when used aggressively. And when doing performance calculations for landings, I’m under the impression that no credit is taken for reverse to shorten landing distances. If you’re using autobrakes, which you are in any modern jetliner, using reverse doesn’t shorten the distance at all, it just adjust how much brake force is used to hit the deceleration rate programmed by the autobrake system.
November 1, 20241 yr 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.
November 1, 20241 yr 3 hours ago, 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. You did not happen to read the link above and did not calibrate the throttle via the EFB, did you? Phil Leaven i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"
November 1, 20241 yr 12 minutes ago, DAD said: You did not happen to read the link above and did not calibrate the throttle via the EFB, did you? Well I did in flypad the calibration. But I think I have to tone down responsiveness in msfs control settings I guess? 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)
November 1, 20241 yr 21 minutes ago, Piotr007 said: control settings I guess 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 Phil Leaven i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"
Create an account or sign in to comment