Sorry, but what does that mean?
Are all the variables, and the specific controls they bind to, listed in the documentation?
Are there variables that are specific to the aircraft?
“They’re all there” could mean a bunch of Kvars, or Ovars.
Please elaborate.
its will all be provided, dont worry
Another vague answer. I’m out.
I’m going to go out on a limb that based on his TWO replies to your question that the answer is yes.
To best fit our response, I want ask what do you plan on binding with the hardware that’s so important to you? I’ve been flying with my joystick and throttle forever and all the sim default keybinds work… Just the essential gear, flaps, throttle, and flight controls.
I’ve never heard of SPAD until now. What does it do? Do they have a dev toolkit?
And to your response, I think what Tommy was trying to say is that all the variables are involved with creating the airplane. There ARE aircraft specific variables, in my case most of the animations that are specific on the da42 are our own variables.
To give you an idea, I remember using custom defined names for these items, there’s likely more, but here’s a small list:
-canopy animatiion
-rear door animation
-pull cage animation
-auxiliary fuel pumps
-ECU function and buttons
-Flood lights and instrument lights
-All circuit breakers
-Icing controls
The rest are binded per the default simulator such as essential G1000 buttons, alternators, battery, avionics, gear, flaps, etc.
Personal Comments and Observations
If you’ve not heard of Spad, Axis and Ohs, Mobiflight and the rest, your control configuration hasn’t moved beyond basic keybinds. That’s fine, but even basic Garmin (FMS and AFCS/GFC) controls, such as the two-tier FMS knob, the Range Knob, and the VNAV button do not have keybinds. I opened a WL post long ago on the latter - it’s still unfulfilled. There are many commands within the sim that are not key bind mapped. The only way they work is via VARs through FSUIPC utilities or mouse in Virtual Cockpit.
I’ve had to get custom scripts from the Mobiflight Devs for the electric start key on the DA40NG (with MrTommyMxr’s mod) so my standard hardware four position rotary knob that emulates an ignition/mag start would work. That’s a small sampling of what gaps are present for anyone having even a small modicum of hardware controls/panel emulation.
Can’t wait for this… release it!
I am guessing that since we had to learn to work with LVars etc just to fly the latest DA62 modification, the fully custom DA42 will have lots more custom variables.
But if it is of such importance to a user….simply wait until it is released and then find out from someone who actually owns the released product.
it’s happening!
I’ve been doing just that more and more lately. It doesn’t make my instant gratification monkee happy, but such is life.
Waiting is not a perfect solution however, for multiple reasons:
People like me, who despise mouse clicks, and have even a modest set of peripherals with controls we want bound to every possible event, are, I believe, a small minority.
Many developers code their planes (especially the more complex ones) with multi-variable events that are difficult to suss out, even with tools like SPAD’s Event Viewer and Data Monitor.
The vast majority of users are far more interested in flight dynamics, textures, model realism, and failure modes, than they are with reviewing the ease with which controls can be mapped to event variables which are only accessible through tools like SPAD. Nothing wrong with that, and those things are important to me as well with some (but not all) of the planes I buy.
So waiting for users to report on how well a newly released plane’s controls can be mapped is not (yet) very productive.
I always wish that a complete list of variables, along with plain language describing what those variables control, would be provided with the model, or even before the model is released. I can see how devs might not want to do that - after all their code is their livelihood, and the better devs are becoming quite adept at writing code that makes their planes worth buying. The best devs provide aircraft-specific variables. There are some planes for which a significant percentage of controls use variables that are categorized for that unique model. Those variables show up in SPAD. They’re easy to find, and make my monkee happy. Unfortunately, it’s almost impossible to know which planes those are before I buy them. Reviewers don’t often care about that aspect (look at the YouTube reviews, and watch the mouse clicks…) and the developers who focus on making it easy to map events are few and far between.
It’s a conundrum. I really want to buy the DA42 on Day 1. But I’m reticent to do so, because I’ve made other Day 1 purchases that are sitting in my hanger because of the level of frustration I’ve had with trying to map their controls. Others have been a joy as I found them both excellent to fly, and relatively easy to map.
I certainly don’t absolve myself of blame: I’m still just an advanced beginner when it comes to using SPAD and developer mode to map my peripherals. I just wish more developers would hop on board and focus on making the task easier for those of us who take great pride and joy from having a ‘mouse-free’ flying experience.
Sweet!
(10characters)
Included is this text file with the comands that can be used.
additionally ill be there and we can figure the stuffs out. We can make a thread in the discord to share profiles and stuff
This are the Lvar bindings for the buttons in the COWS DA42
default value is given first "L:LVAR; Values/Range" or marked with "(D)"
If you use SPADNext/FSUIPC and have control problems, you can use these LVARs to control the plane
L:INPUT_AILERON, percent; -100 - +100
L:INPUT_RUDDER, percent; -100 - +100
L:INPUT_ELEVATOR, percent; -100 - +100
---------------------[ECU voters]----------------
L:DA42_ECU_VOTER:1; 0 L:DA42_ECU_VOTER:2; 0
L:DA42_ECU_VOTER:1; 1 (D) L:DA42_ECU_VOTER:2; 1 (D)
L:DA42_ECU_VOTER:1; 2 L:DA42_ECU_VOTER:2; 2
---------------------[ECU TEST]----------------
(both)
L:FADEC_ECUTEST_BUTTON:1; 0/1 L:FADEC_ECUTEST_BUTTON_B; 0/1 L:FADEC_ECUTEST_BUTTON:2; 0/1
--------------------[Gear fire test]----------------
L:GEAR_FIRE_TEST; 0/1
-------[Emergency gear extention]----------[Engine Alternate Air]----
L:GEAR_EMERGENCY; 0/1 L:ENGINE_ALTERNATE_AIR; 0/1
---------------------[Deice panel]----------------
L:DEICE_MAX; 0/1
L:DEICE_SWITCH; 0
L:DEICE_SWITCH; 1 L:DEICE_ALTERNATE_COVER; 0/1
L:DEICE_SWITCH; 2 (D) L:DEICE_ALTERNATE_SWITCH; 0/1
L:DEICE_WIND; 0/1 L:DEICE_PUMP_SWITCH; 0/1
KEY_TOGGLE_WING_LIGHTS
L:DEICE_LIGHT_SWITCH; 1 and/or KEY_TOGGLE_WING_LIGHTS (D)
L:DEICE_LIGHT_SWITCH; 2
---------------------[AUX pumps]----------------
9 KEY_ELECTRICAL_CIRCUIT_TOGGLE (These are normal circuit toggle "K" commands)
10 KEY_ELECTRICAL_CIRCUIT_TOGGLE
--------[Headset]--------
L:HEADSET; 0/1
--------[Backup attitude indicator]--------
L:ATT_CAGE; 0/1
Everything else is pretty much standard.
Excellent. This DEFINITELY sways my purchasing decision towards an emphatic “YES!”
Great preview here: https://youtu.be/29k2CXfHvn8?si=d0VNyE4tdAcLpiNM
I’m very excited for this aircraft.
Available now
Looking forward to early feedback …
Seems expensive. I am going to refrain unless the release reviews are sky high. All of what I have seen to date on YouTube about this plane looks ok but nothing outstanding. I’ll be sat here on the fence 
Have to agree, it does seem a bit expensive to just take a punt on as an unknown developer. But it does look good.
