#How to crack aerosoft airbus x extended how to
#How to crack aerosoft airbus x extended full

(Electric, hydraulic, flight controls, engine, etc.)

Detailed systems including fault injection for currently about 90 failures.

Very accurate FBW implementation, including reversion to alternate and direct law.

Choice of sharklets or classic wing tip fences (Affects aircraft drag).

Choice of CFM or IAE engine, affecting aircraft performance and fuel burn.

Detailed FMGS with SIDs/STARs/Airways, performance prediction, temporary, alternate and secondary flight plans, fix info, etc.

You'll find lots of useful stuff there.This add-on is an officially licensed Airbus product! Please always check the Subforums on this site. I can provide the tools, and have done, but i cannot possibly provide the solutions for every different add-on.

#How to crack aerosoft airbus x extended how to

The addition of the Lua plug-in facilities was the only answer, but then it is up to others to find out how to fix things in whatever way it can be done. FSUIPC does have a lot of options to try to cope with them all, but in the end it is impossible. The problem with FS add-ons is that every 'clever' developer has his own idea about how to do things 'properly' and perverts the standard FS controls to suit that aim. Have you checked the User Contributions subforum at all? There are quite a few threads relevant to the Aerosoft Airbus. I'm pretty sure that works judging by other users. Note that I am pretty sure there is a solution using Lua plugins to set the throttles directly. How would it be an FSUIPC problem? If you are not calibrating the thorttles in FSUIPC then how does it come into this?

I'd be glad to provide further specs as needed. I'm open to anything you can suggest about my setup.ДЇor the record: I'm running FSX with Acceleration on a W7 PC, i7-3770K overclocked to 4.8 gHz on a custom water cooling loop, 16 megs of DDR3 2400 RAM, and a GTX 680 card, also water-cooled. This is the first time I've run across an aircraft with a critical control that won't respond to FSUIPC calibrations. I've also found that A2A's configuration utility can't read FSUIPC inputs, but most of those can be replicated within FSUIPC, so it's not an issue. But in that case, I was able to use the Katana's configuration routine to define the axes as a normal one without the governor, and that allowed me to use it, but without the governor function.

In that case, the prop lever was inverted, and I was unable to set it up to use the prop governor. I do recall one similar issue with a different Aerosoft product - the 4X Katana. My FSUIPC setup works with all my other aircraft, and with a suite of control devices including a PFC yoke and throttle quadrant, a Thurstmaster Warthog HOTAS (I was trying to use its joystick as an Airbus sidestick), Saitek pedals (soon to be replaced with PFC) and a custom set of helicopter controls. Their reply is that the problem is with FSUIPC, not with their software, and they're not going to take any action to address my issue. I've asked them whether there's a way to address a single axis (or in this case a pair of axes) inside their module. But Aerosoft's FADEC module is unable to read FSUIPC calibration - if I try, the axes become unreadable altogether. Under any other circumstances, I'd go into FSUIPC and check the 'reverse' box in the calibration pages for the two throttles.

#How to crack aerosoft airbus x extended full

a full left aileron command deflects the ailerons to the left, and so on).

When I try to un-invert them using the Aerosoft Airbus configuration tool (by de-selecting 'invert axes'), the throttle problem is cured - but all of the other axes are inverted as well (e.g. All of the controls work properly with one exception - the throttle axes are inverted. The issue is this: I've followed the instructions on their forums for setting up controls under FSUIPC. I've already taken this issue up with Aerosoft tech support, and have been told rather firmly that it's not something they're able or willing to address. I regret having to join the group of users having problems with FSUIPC and the Airbus X Extended.