Another Helios mystery. Beats me totally.
-
Hi everyone,
I think I’ve uncovered another Helios mystery.
I’ve been looking into it for days now and it still beats me.
Here’s what I see:
Whatever .key file I use as a Falcon interface in the Helios Profile Editor, some callbacks just don’t appear in the editor, even though they are present in the key file.
That concerns the following callbacks:
SimStepMissileVolumeUp
SimStepMissileVolumeDown
SimStepThreatVolumeUp
SimStepThreatVolumeDownIt’s really crazy because I can see the callbacks in the .key files with Notepad++ and in the BMS setup/Controllers page.
I noticed this while using Ice’s profile (the best IMHO), but even if I create a profile from scratch, I have the same problem, those callbacks don’t appear in the list in Helios Profile Editor.
I’m not even sure it doesn’t concern other callbacks as I’ve only tried with these, but it really beats me.Any idea? Thanks for your help
Judy
-
What key bindings are those callbacks mapped to? If you look at my .key file, you will notice that I’ve not mapped key bindings to certain locations in the keyboard. For some reason, Helios doesn’t see/like stuff bound to those keys.
-
Well, it’s, in every case, with the [ and ] keys.
It’s SHF CTL [ and ] for the missile volume rotary and
ALT CTL [ and ] for the threat volume rotary.I think you solved the mystery Thx a lot
-
Yep, you’ll see I’ve taken out a few of the [ and ] bindings in my .key file.
Re-map those callbacks to different key combos and you’ll see them in Helios.Quick question – why not just use my .key file in the first place?
-
Well, I had a key file of my own and I thought at first it wasn’t very different from yours. Guess I was wrong
Back to yours now.Judy
-
If it ain’t broke….