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).

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.

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.

Not at all. The Working Title 430/530 are now included with the base simulator, so the Marketplace version is redundant. The only purpose it serves is to allow 3rd party planes that used the Asobo 430 to use the WT one. Just like with the NXi and SU10, this is will only be valid until the next update by which time developers that want to use the WT430 will need to update their aircraft. That said, @Matchstick I am here at 1:00 on a Saturday night trying to assist you and explain this as best as I can, but it feels like talking to deaf ears. If I am coming across as apologetic, I won't continue down that path as there is nothing to be blamed for. If you think that we are beating around the bush or trying to coax you into buying a faulty product, please send a request via e-mail and I will gladly refund you every SWS product you bought from our shop on Monday. Of course, should you need any assistance our regular support venues are open.

As the RV was built under license, back when we started it we were asked to represent it to the most modern standard. So that was not an option. Also it was MS/WT's decision to leave the G3X behind and at their own timing. Why don't you give any thought to my suggestion which will allow you to keep the WT430 on any planes that use it while allowing the G3X to work properly? Needless to say that if/when the G3X is updated, so will be the RV-10.

The problem doesn't lie with the aircraft but rather with the avionics. The solution that I propose allows you to have the WT430 on every aircraft and the Asobo 430 in the RV-10. Either way, we cannot do something if the WT430 is incompatible with the G3X.

The MARKETPLACE version of the 430 has to be uninstalled, because it overrides Asobo's older 430. There is also a Core version of the WT430 that was added with AAU1. This one is used on the default planes now, can be used with 3rd party aircraft and can co-exist with the asobo one, unlike the Marketplace WT430. The WT430 doesn't talk to the G3X because the autopilot & GPS logic were completely rewritten for the former, but the 3X hasn't been updated with it. That one can only be fixed by doing a fully custom G3X or WT updating it -which is up to them. Regarding the TDS 650, if I can integrate it seamlessly on PC without causing problems on Xbox, it will be in by Friday. As I said it's cooking, I just need to make sure it is digestible.

I have something in mind for the TDS650 and if the right boxes are checked, it will be in. Splitting PC and Xbox was and still is a nightmare for maintenance and I don't want to do that again. From a financial perspective, both are great earners. From a technical perspective, if you use good practice with graphics design and programming Xbox is just as capable as the PC. I will refer you to the discussions about Xbox not having enough power for circuit breakers and the Kodiak was the first to do them and did just fine.

There is good reasoning behind it. We needed to have NAV radios (requirement) and Xbox compatibility. Options: GNS430 and GTN650 because they are the only ones that can fit in this panel. GNS430: it has NAV radios and can work on PC & console (default unit exists). GTN650: There is a default unit from the Cabri G2, but it has less functionality even compared to the G3X and no NAV radios. The payware replacement (TDS) is PC-only. That leaves us with the 430 as the only viable option, for now. 🙂