Helios with 4.33

[coolhands]

Hello
My config for my cockpit with Hélios work on BMS 4.32 and not in 4.33. I make the same KEY files for the 2 versions.
Any ideas ?

[mantaray]

When 4.33 came out
I used my 4.32 keyfile in 4.33.
Didnt change anything in helios.

And its working

If you use mfdextraction from lightning you have to update to 0.6.01

[Guest]

+1

I used my 4.32 key in 4.33 and so far it’s worked, but I lost some sound feedback. Hopefully with my new .key file, I’ll get it back.

[Dee-Jay]

Please guys … is you are using your 4.32 keyfile … fine, but please … do not advertise it on the forum.

Why?
Because there will be issues (maybe not for you, but can be for some other ppl depending on mapping and/or callbacks used.)
But WE will have to deal with bug-reports and will have to figure out what is happening.

Thank you for comprehension and cooperation.

[coolhands]

When i used Helios, MFDextractor and Sioc systeme with Key file full or pitbuilders in BMS 4.33 i lost the DED or all elec in cockpit of F18C. When i used same config in BMS 4.32 its work fine. I don’t used any same key files 4.32 in 4.33.
I make a short video to show the problem

[-Wizard-]

Helios does not seem to recognize the winamp callbacks in the 4.33 keyfiles.

It was working in 4.32, but now the callbacks don’t even show up as an option.

Edit: The callbacks will NOT show up in Helios unless you map them to an actual keystroke. Annoying, but fixable.

[Guest]

@Dee-Jay:

Please guys … is you are using your 4.32 keyfile … fine, but please … do not advertise it on the forum.

Why?
Because there will be issues (maybe not for you, but can be for some other ppl depending on mapping and/or callbacks used.)
But WE will have to deal with bug-reports and will have to figure out what is happening.

Thank you for comprehension and cooperation.

Agreed. I am only using my 4.32 .key file as a stop-gap measure and I’m actually testing my 4.33 .key file now.

[mantaray]

@-Ice:

Agreed. I am only using my 4.32 .key file as a stop-gap measure and I’m actually testing my 4.33 .key file now.

Same here, loaded my keyfile in kolbes excel , modified and exported again.
Export showing the proper soundcodes now

[coolhands]

@-Wizard-:

Helios does not seem to recognize the winamp callbacks in the 4.33 keyfiles.

It was working in 4.32, but now the callbacks don’t even show up as an option.

Edit: The callbacks will NOT show up in Helios unless you map them to an actual keystroke. Annoying, but fixable.

Thanks i join my movie with problem.

[mantaray]

@Dee-Jay:

Please guys … is you are using your 4.32 keyfile … fine, but please … do not advertise it on the forum.

Why?
Because there will be issues (maybe not for you, but can be for some other ppl depending on mapping and/or callbacks used.)
But WE will have to deal with bug-reports and will have to figure out what is happening.

Thank you for comprehension and cooperation.

Maybe i have to explain something here Dee-Jay, i’ll try it here

This post is about Helios.
If Helios would work on callback’s only ….there is no problem at all using the new keyfile.

But

Sometimes Helios dont and you have to assign keystrokes instead.

1. Now you can imagine what a completly new keybord conf can do to the Helios program.
2. Callback’s and keystrokes are not so easy to assign , it takes a while to check everything ( i am talking about hours )
3. I do my full rampstart in Helios. When the new 4.33 arrived …flying was priority (only way was the old 4.32 file)— the transfer of the keyfile is in progress.

So this is not a bms problem but a Heliosproblem.

Hope you understand

Only posted in the wrong forum, maybe better in https://www.benchmarksims.org/forum/forumdisplay.php?57-Touchscreens

[coolhands]

You are right you can move the post

[Dee-Jay]

@mantaray:

Maybe i have to explain something here Dee-Jay, i’ll try it here

This post is about Helios.
If Helios would work on callback’s only ….there is no problem at all using the new keyfile.

But

Sometimes Helios dont and you have to assign keystrokes instead.

1. Now you can imagine what a completly new keybord conf can do to the Helios program.
2. Callback’s and keystrokes are not so easy to assign , it takes a while to check everything ( i am talking about hours )
3. I do my full rampstart in Helios. When the new 4.33 arrived …flying was priority (only way was the old 4.32 file)— the transfer of the keyfile is in progress.

So this is not a bms problem but a Heliosproblem.

Hope you understand

Only posted in the wrong forum, maybe better in https://www.benchmarksims.org/forum/forumdisplay.php?57-Touchscreens

Good explanation sir. Thank you.

For tree weeks we are tracking bugs and reports here trying to give the good and bad practices on 433 compared to the 432 … commencing to be a little tired and sometimes quick reading

[coolhands]

I found my problem, it’s my software FAST for my cockpit led who’s create the bug. Now All works fine with Helios and MFD extractor