[HoneyComb Charlie rudder pedals release date]

Quote

PRE-ORDER NOW | Limited quantity of the first production expected to be available from March/April 2024

 

And once more no email to waiting customers... 

 

Gérard

[Honeycomb AFC Bridge and P3DV6]

Is/will the AFC bridge runs under V6 ?

 

Is there a "trick" to make it work ?

 

Thanks

 

Gérard Benéteau

(Still PATIENTLY waiting for the Charlie Pedals delivery...)

 

[HoneyComb Charlie rudder pedals release date]

On 10/20/2022 at 8:51 AM, Marius Ellenbürger said:

100% agree with this, and every customer with a pre-order can expect an email soon.
Until now, we have always sent an email in case of postponements and always keep our customers up 2 date.
"Unfortunately", you were a little bit faster than us in this case.

Greetings,
Marius
 

I just received your mail.

Thank you

 

Gérard

[HoneyComb Charlie rudder pedals release date]

Hi,

 

Would be good customer support if we had received an official  mail, instead of discovering it only through a customer query...

 

Gérard

[ConditionValue semantic issue]

Prepar3D v5.3 hf2

Thanks

[ConditionValue semantic issue]

Hi,

 

I am trying to specify a "negative" condition, like Lvar not equal 10.5 and I would like to not be obliged to multiply the tests... (<10.5 or >10.5)

 

I tried

- "ConditionValue": "<>10.5"

- "ConditionValue": "!=10.5 "

 

with no luck...

 

And I have an issue with the Configurator which refuse to load some "hand modified" profiles (with no information !), perfectly validated by a json formater AND by the Bridge which load and execute them perfectly...

 

I know I have suppress "useless" parameters like "VariableBoundaries" which are not even initialized by the Configurator....

 

             "VariableBoundaries": {
               "MinValue": "",
                "MaxValue": "",
                "Clamp": false
              }

 

Let me know the mandatory fields for the configurator...

 

Thanks

 

Gérard

[Honeycomb Bravo - 2 issues]

 

Hi Ben,

 

On 3/18/2022 at 2:02 PM, BenBaron said:

Technically, the var type of the INTERNAL variables also does not necessarily be included anymore in the name as the bridge module is trying to infer that from the provided value...which "should" work fine in most cases. If you find a case where it does not, let me know and I will look into it.

 

 

I recently used a profile I had updated to erase the " string" specifier on the INT:FCU_SELECTOR vars. The increase/decrease (button 12 and 13) was no more working.

Just "re-introduicing" the "string" for the INT:FCU_SELECTOR only solved the issue.

 

I confirm that not specifying any unit description for "INT" vars when the value is numeric works correctly.

 

Regards - Gérard

[Honeycomb Bravo - 2 issues]

Hi Ben,

I am recreating some part of the "default" profiles with the v2.2 Configurator to see how the corresponding .json file is looking.

I noticed that now the "var type" of the INT:vars is no more included and the xxxIsCustom has changed from "false" to "true". I was wondering if there are other changes we should take into account.

So, I think it would be important to get these profiles updated for the new Configurator, as they should be the starting base when creating new profiles.

 

Is it more clear ?

"Communication is a difficult art"

 

Gérard

 

[Honeycomb Bravo - 2 issues]

P3D V5.2 HF2

 

If you make an update, please consider adding checks that both key and name at least are specified for Custom Vars entry

 

It is easy to miss one when repeating conditions or variables and the error is very difficult to trap...

Currently, in this case, you only get in the .json file     "Variable": "" or  "Variable": "L:" ...

 

It would also be great to get the default profiles with the "new rules". I discover that now the "string" type is no more specified AND the VariableIsCustom is "true" when created with the Configurator.

 

In the included Default, they are specified as

              "Condition": "INT:FCU_SELECTOR, string",
              "ConditionValue": "ALT",
              "ConditionIsCustom": false

and

              "Variable": "INT:FCU_SELECTOR, string",
              "Value": "IAS",
              "VariableIsCustom": false,
 

Both seam to work, but this creates some doubts...

 

Thanks

 

Gérard

[Honeycomb Bravo - 2 issues]

Hi,

 

If you update the Configurator, please consider adding LED to the Mapping Summary...

 

 

Gérard

[PMDG Honeycomb Interface utility now available]

Mark,

 

Great finding - I will start to think about what make sense be connected to the  Alpha and Bravo numerous switches

 

I am really impatient to discover how the new Alpha/Bravo driver works !

I dream of an evolution which would give the possibility to write scripts attached to buttons (in lua or javascript which are now introduced by P3D V5.1).

 

Gérard

[PMDG Honeycomb Interface utility now available]

Thanks,

 

It works fine.

 

I hope PMDG could publish the varaibles names for the most usefull function (specially with the new coming Bravo TQ).

 

Gérard

[PMDG Honeycomb Interface utility now available]

Mark,

 

I crossed check : no SDK folder for the DC6 on my installation; I just run again the installer - no option and no SDK folder...

 

Let's wait the V5 version. As usual "will be ready when it will be ready"....

 

Thanks for your answer.

 

Gérard

[PMDG Honeycomb Interface utility now available]

Hi Mark,

 

Thanks for this utility !

 

I read carefully your manual, but I still have few questions.

 

- I own only the DC6 (still waiting for V5 version...), is there a SDK for her, and where should I look on PMDG site (at least to know if...)

- I use the "official" Yoke Interface for all my aircrafts. Should I still keep it running for PMDG aircraft or are they conflicting ?

 

And the BIG one : as I should receive my Bravo TQ before the end of THIS year ;), do you intent to include support for it in the future ?

 

Cheers

 

Gérard