gaab

You must bind the button 22 to LIGHT OFF and 23 to LIGHT ON (or the way around according to your taste ... is UP On or Off , that is the question The same logic applies to each switches, linked to 2 so called "buttons" in the Yoke Input. Enjoy

Thanks Ben, Not big deal Stay Safe. Gérard

Hi Ben, I know that you in the process of updating the Yoke driver. Once more, thanks for that. I have a new suggestion : I am missing the possibility to select events repeat rate (Prepar3D offers none, slow, fast). This is very usefull depending of the aircraft. Would be nice if you could offer the same, as changing profile is easier than modifying the P3D control parameters. Thanks to consider it. And take care and stay home Gérard

Hi Ben, I "nice to have" for the Yoke driver : in the P3D Honeycomb AddOn menu, would be nice to get the name of the profile loaded, as well as in the YokeInput. I have started to create various profiles and I never know which one is current Thanks - Gérard

Could explain a little bit more a "drastical" change in policy compared to the Alpha Yoke. Are you becoming so confident in your success when you propose a 12 month time frame incertainty. Regards

Hello, I am surprised to discover that the pre-order offer as disapeared from your site - but still no serious information on delivery. I am very dispointed - could you comment on this ? Regards - Gérard

I asked " Wheelstand" supplier if they made some progress on this topic Gérard

Hello, I asked this question directly to the supplier of wheelstand pro some weeks ago. He told me I just receive its Yoke and would look at it. So far no feedback - may be you could ask them to show that some people would be interested to buy it (see mail address on their site). Not very active Gérard

Hello, Any update on the schedule with new pictures of the last design and maybe a review like for the yoke ? I am waiting a better estimate to put a "pre-order" Thanks Gérard

Sorry, my question was not well spelled : in the templates distributed with the "driver", assignation of local variable don't specify a "unit" Take a look at any template - last lines "ButtonNumber": 34, [ ......] "ReleaseEvent": [ { "Variable": ">L:LEFT_LOWER_ignition", "Value": "0", I was expecting "Variable": ">L:LEFT_LOWER_ignition, enum" or something similar ... I understand you can only test 'equal' to ConditionValue, not 'greater' for example ? Thanks for your input. Gérard

Great ! Another question, if I may, concerning variables (A: L:, i.e. not event K:). in conditions A; or L: variables are specified with there format descriptor ("L:bus:Avionics:State, bool" or "A:GENERAL ENG GENERATOR ACTIVE:1, Bool"). but when assigning (local) variables, you don't specify one (">L:AB_VC_OVH_ExtLight_Nose_Sw"). In your conditions I only see bool variables. Could we have something like "Condition": "A:AIRSPEED INDICATED, Knots", "ConditionValue": "gt 300", To be frank, I don't see practical use of this for the time being, but when the throttle becomes available ... Concerning "show button bindings", I have "x_x" with the switches Alternator, Battery, nothing with any other.... But if I specify a text in "FR" (my system language) in the YokeConfig.json, as already mentionned, it is displayed as expected. Thanks for dedication. Gérard

Thanks for the update, which raise some question : As suggested in your "changelog", I took a look to the updated templates. And I see the following examples : "Variable": ">K:TOGGLE_MASTER_BATTERY", or "Variable": "K:TOGGLE_GENALT_BUS1_CONTACT", Could you confirme that the first one, with ">" is the right syntax to use.... Thanks - Gérard

Same here ... and I have Experimental Updates checked If I go through Honeycomb site, I have the October 15 version 1010 Gérard

Yes - I am a retired IT project manager - I know the feeling Gérard

I know it can run as is, but hundreds of error messages in ContentError.txt should be fixed in the future ! My message was meant to help to identify error origin. I really expect that the next version will address these points. Gérard