A320_SX ALX

Unfortunately I cannot help more as I don't use SPAD. From discussions with other users of it, I gave them the variable and values and then they got it to work.

Use -1 (left) to 1 (right).

As far as I know there is no reason why add-on linker shouldn't be used. If someone said it he either isn't an SWS developer or gave wrong information.

Just to clarify this, there is method to the madness. 🙂 The reason it takes time to acknowledge a problem has to do with bias and testing. Bias means that we are "used" to the quirks of the plane and can't see the problem, while a customer is not used to them and may see an issue where there is none. You must follow procedure, then see where it is good and where it isn't to be able to narrow it down. We also need to probe you in order to get ourselves over our bias and see the problem. This takes time and always happens when you've worked for so long on a plane. Then comes testing. We take both sides and throw them to the SMEs to try and distill the actual truth. Finally we consider how to fix it and what will bite us if we move something else. It is slow, but helps avoid more mistakes down the road.

For FSUIPC/Spad/AAO users, if you don't want the default bindings you have to use these L:vars: ARI_RudderInput for the pedals ARI_AileronInput for the rudder Regardless of preferred setup, make sure you use linear response curves.

You are right, flaps I should have written 15 instead of 40. @RichieFly the plane does float on landing if your speed is high. Flaring at 80kts with full flaps can keep you airborne for a while. The trick is to burn that speed as you are crossing the fence and be idle and 10kts below your approach speed over the numbers. A short list for an 85kt approach, flaps 40: 1) Approach: 9psi, 85kts 2) Fence: start pulling back to idle while applying left rudder because the nose will come right from torque reduction. Desktop yoke slightly right to counter the interconnect and keep virtual yoke centered. 3) Numbers: idle and 75kts, start flaring. You don't flare much before in order to dart through ground effect. 4) Touchdown: 65kts. Let the nose down and gain control of the steering 5) Reverse. Get out of it at 40-50kts and apply brakes 6) Ground idle

Hello, For takeoff: 1) Hold brakes 2) Throttle up to 15psi -no need to do it slowly 3) When engine reaches 1700rpm, throttle up to 44.3psi. Again, don't do it slowly 4) Brakes off 5) Rotate at 70kts (flaps 30), 83kts flaps 40. Give it left pedal as the plane will crab when it lifts off 6) Gear up, yaw damper on Landing: check the manual for correct settings We have a fix in progress for the skidding. VP guidance: it depends on the GPS unit. We discovered different problems with the AP and each different GPS. Working with PMS and TDS to improve things.

One way or another yes.

In our website the price is tax-inclusive because we don't pay re-seller commissions and can keep it low. Most other shops add tax on top of the base price. We used to do it this way too, but it is simpler for the customer -they pay what they see. @JYW the sun visor can be easily used with the scroll wheel, it only has 10 positions. Because it is indeed a nuisance, click its pivot point on the ceiling and it will automatically be stowed to neutral. Thank SimAcoustics for the idea he gave me. 🙂

The pitch response is correct, knowing from experience; three of us were flown in a PC-12 in Lausanne where we timed control responses and performance manoeuvres. Plus we spent five 16h days in the sim with instruction. The elevator trim takes 42 seconds end-to-end and the rudder trim 28. Timings and effect are as close as we could get them. One area that suffers is the rudder relief and yaw damper. Because of MSFS AP limitations we can't have full authority because it will disconnect it, so it is less coordinated than it should be. IRL the yaw damper is able to coordinate better but is still slow and that is so the pilots can overpower it if they need to.

The green indication on the rudder trim does not stand for "neutral" but for "take-off", which is 45-55% to the right from centre. It is a lot of rudder, as cruise and approach are almost neutral and one right of neutral respectively. For landing, with correct torque settings (9-12 psi) you should come in coordinated with little or no rudder input. Regarding engine power, powering down will cause the nose to yaw right, adding will cause it to yaw left. Small power increments aren't that big a deal, but big ones will yaw the plane IRL and in the sim. As for level flight & yaw damper, it is slow IRL, but in MSFS our yaw damper is also underpowered, as giving it correct output disconnects the autopilot (MSFS thing). Still, I'm getting some reports that indicate the PIDs for the autopilot might need refinement in certain cases. Glass on GTNs: part of a hotfix. It's a case of "it was fine yesterday, it wasn't today" but when it gets in your hands it no longer matters. We'll straighten it out. Let me know if these help you and I'll be happy to get as much feedback as you can give me.

The tablet is empty, until we build our own -see manual, installation section, or here: https://trello.com/b/vqQ3jKeG/pc-12-pulic-roadmap). We have an option in the installer for Sky4Sim compatibility, so if you have that installed it will light up with S4S.

That's a good topic, I'll take it early. Paypal usually reverses the excess payment within 2-3 business days. If it doesn't do it let us know via a ticket and I'll take it to them.

Experimenting with extremely low prices would be more accurate. Still haven't put out my $1 full aircraft to see how it does.

It will be on April for a similar price. 2.99 I think.