If you want a Honeycomb Alpha for Christma you better order fast because we are quickly running out of stock!

Jump to content

Recommended Posts

Another question gents:

 

I used the AS Updater to get the latest version but when I check within the driver program itself it’s telling me a new update is available. 
 

Any idea if there really is an update? How do I know if the Updater is working?

 

BTW, the profile you created Dave, is working great!

Share this post


Link to post
3 hours ago, VAFPilot said:

I used the AS Updater to get the latest version but when I check within the driver program itself it’s telling me a new update is available. 

 

Do you have Experimental Updates checked in the AS Updater?  It's under Configuration.

 

3 hours ago, VAFPilot said:

Any idea if there really is an update?

 

There is!

 

3 hours ago, VAFPilot said:

How do I know if the Updater is working?

 

The product color will turn from Red to Blue.

 

3 hours ago, VAFPilot said:

BTW, the profile you created Dave, is working great!

 

Most welcome.  Tomorrow I will create the A330 Profile for Honeycomb.  Actually, it's mostly done already!

 

Share this post


Link to post
22 hours ago, VAFPilot said:

I used the AS Updater to get the latest version but when I check within the driver program itself it’s telling me a new update is available. 
 

Same here ... and I have Experimental Updates checked

If I go through Honeycomb site, I have the October 15 version 1010 :(

 

Gérard

Share this post


Link to post

The latest version of the Honeycomb Software is 1.0.2.1.  As far as I know, it's only available via the AS Updater.

 

Also, I recommend you run the AS Updater "As Admin".

 

 

Share this post


Link to post

1.0.3 is now available via the updater.

 

Changelog

  • Added Condition Variable and Value
  • If you only have a toggle function you  can now define the correct switch position via the Condition Variable (take a look at the new Default Template)
  • Fixed a few spelling bugs
  • Added a new Request Windows
  • If you can't find your aircraft inside the Templates, send us a Request via the Config Tool (Menu ? -> Request Aircraft Template)
  • Updated Aircraft Templates (Default, JustFlight PA28, Aerosoft Airbus A32X)
  • Added new Templates (Aerosoft PBY Catalina, Alabeo DA42, Carenado DO228, JSS Transall, Vertxsim DA62)...more Templates will follow in the upcoming weeks

Share this post


Link to post
On 6.11.2019 at 01:11, gaab sagte:

Edit 2 : there are hundreds of error messages in the contenterror.txt file when the yoke add-on is activated...

 

[error.xxx]
error=Gauge/Script Error
Type: Unknown
Name: Unknown
Error: Empty parentheses or closing parenthese missing: "()"

 

 

 

Hi guys,

 

in addition to Mathijs' post: this bug is also supposed to be fixed.

  • Upvote 1

Share this post


Link to post

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

Share this post


Link to post

Mathijs,

 

Thanks for posting the information and for creating the files to map the switches. It makes it SO much easier!

Share this post


Link to post
vor 9 Stunden , gaab sagte:

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

Hi Gérard,

 

you can use both syntaxes...if the ">" is missing for "Variable" it will be added internally, now.

Share this post


Link to post
14 hours ago, BenBaron said:

you can use both syntaxes...if the ">" is missing for "Variable" it will be added internally, now.

 

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

Share this post


Link to post
vor 6 Stunden , gaab sagte:

In your  conditions I only see bool variables. Could we have something like

 

          "Condition": "A:AIRSPEED INDICATED, Knots",
          "ConditionValue": "gt 300",

...

Concerning "show button bindings", I have "x_x" with the switches Alternator, Battery, nothing with any other....

Hi Gérard,

 

regarding your first question: yes, this should work. I did e.g. test "A:ATC MODEL, string" as "Condition" in conjunction with "F22" as "ConditionValue". I obviously wasn't able to test each and every variable ;), so if you have one that doesn't work drop a note.

 

To specify a variable without variable type as with your L:var example...I would have to see how that would work out...right now that is not possible.

 

For the second one: the X_ ... _X is supposed to show that, although a command has been recognized, it won't be executed as it's condition is not met.

  • Like 1

Share this post


Link to post
On 11/4/2019 at 8:38 PM, BenBaron said:

[...]

To add to this, the extra software is basically useful for assigning more non-standard functionality whereas FSX/P3D e.g. only allows for toggeling of certain functions instead of actually setting distinct states. This will be extended in the future and the yoke is otherwise working, can be assigned and used like any other plug&play device.

 

Hi Benjamin,

 

I am wondering about the difference between a profile and a template. Am I correct in thinking that the resulting JSON files are basically the same, and that it is just a matter of 'organizing' what AS pre-made and what I make myself?

Share this post


Link to post
On 11/16/2019 at 8:05 AM, BenBaron said:

To specify a variable without variable type as with your L:var example...I would have to see how that would work out...right now that is not possible.

 

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

 

On 11/16/2019 at 8:05 AM, BenBaron said:

"A:ATC MODEL, string" as "Condition" in conjunction with "F22" as "ConditionValue"


I understand you can only test 'equal' to ConditionValue,  not 'greater' for example ?

 

Thanks for your input.

 

Gérard

Share this post


Link to post
vor 18 Stunden , Eric Bakker sagte:

 

Hi Benjamin,

 

I am wondering about the difference between a profile and a template. Am I correct in thinking that the resulting JSON files are basically the same, and that it is just a matter of 'organizing' what AS pre-made and what I make myself?

Hi Eric,

 

exactly. They are simply pre-made profiles that you can make use of straight away. Or you can alter them yourself, or even create new ones. In the end, there is always a JSON which is translated into action in the sim.

Share this post


Link to post
vor 17 Stunden , gaab sagte:

 

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

Hey Gérard,

 

ah, now I see what you mean. No..."Variable" doesn't need the definition of a variable type as it's being assigned to the sim. That's only needed for the "ConditionVariable", as this one is read out internally and thus needs to know what type to expect coming from the sim to make the correct comparison against "ConditionValue". And no...right now, there's just the 'equal' option...but if there is need for something different, I guess, we can also implement that.

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...