-Ice's Falcon BMS Helios Profile Updated!
-
Okay guys, I’ve just posted my 4.33 .key file. Please refer to the link on the first post. Still using my custom profile from Morphine as I couldn’t really see what was new with Boxin’s stuff.
Please share any more errors you may find. Thanks!
-
Thanks Ice. Very much appreciated. Will test it out now.
apoll
-
Hey Ice. Been testing your profile. i confirm that it ain’t gonna work if I use your 4.33 keyfile in the Helios interface setup yet use another keyfile in the BMs UI. I need to load your keyfile in the BMS UI for your profile to work properly in Helios. So it seems I can’t have two keyfiles in action at the same time; one for the Helios profile and another for the TM WH. Pity. Now, your new 4.33 profile. I can’t seem to get the ILS on switch in the Audio 2 side consol panel to work. The animation works; it switches on but the ILS in the DeD still says off. I have to go into the 3D cockpit and use the mouse to activate the same switch in the 3D cockpit view. That works. So whatever Helios callback is in your profile does not work. I also could not get the HDG knob in the HSI panel in your Helios profile to work. I moved it upwards but the tapping on the HSI only changed the course, not the yellow heading bars. The only way I can move the yellow heading bars on the HSI is again in the 3D cockpit view, using the mouse to move it on the HDG knob. Not sure if I’m doing something wrong here?
Will keep testing.
thanks.
apoll
-
Hi apoll.
Sounds familiar : troubles with HSI
For me it was working quite a while (2 years) and suddenly HSI course incr 5° stopped.
Assigned the callback to another key….no joySometimes callback’s dont react at all and i am forced to assign keystrokes instead.
-
I know the CRS/HDG problem and will look into it. I can’t seem to make the 5-degree callbacks work as well.
I’ll look into the ILS problem as well. Thanks!
-
I know the CRS/HDG problem and will look into it. I can’t seem to make the 5-degree callbacks work as well.
Hi Ice
Have you seen post 17 in:-
-
As for the HDG/CRS problem, it might be a BMS issue as I’ve tried using the Full.key and Pitbuilder.key and used the keyboard to control the HSI and I could not get the 5-degree increments to work.
-
This post is deleted! -
Hi Ice
Have you seen post 17 in:-
Ah, interesting! Testing it now.
-
that’s working ice i have tested it.
-
Aha!! Sorted now! And I’ve made it so that a single press will increment/decrement the HDG/CRS by 5 degrees! Also did this for the altimeter.
As for the ILS knob, this one has fallen prey to the new changes that the 4.33 callbacks have brought about. I think you will find the JFS switch won’t work as well as the Threat Warning Aux power button. I’ll have to go through the changes to fix them and also to add the new ones.
For now, I’ve uploaded the profile that has the working HDG/CRS/altimeter for you guys to try out.
-
Tks Ice. I’ll do some more testing. Looking good though…
apoll
-
I am probalby very wrong on what I am going to write, but here goes. I am having an issue with the SRM/MRM override switch on my TS WH. I looked at the key file and for some reason, the hex code appears to be different than the old key file code
MRM is the same but in the new file, SRM has a hex code of N and not D (0x20) and cancel has a hex code for a comma and not C (0xE0). Morphine’s old key file has a hex list at the end and that is where I found this info.
Hex Code
0x20 D
0x32 M
0x2E C
Helios callbacks
SimToggleMissileCage -1 0 0x30 1 0 0 1 “TQS: MAN RANGE Knob - UNCAGE”
SimSelectSRMOverride -1 0 0x31 1 0 0 1 “TQS: DOGFIGHT Switch - DF Override”
SimSelectMRMOverride -1 0 0x32 1 0 0 1 “TQS: DOGFIGHT Switch - MRM Override”In addition, this switch appears to have a problem in the pit.
Sorry but I very confused. -
Ah yes. It appears that in the Full.key file, the SRM/MRM override is mapped to D, M, and C. However, in the Pitbuilder.key file, it is “Shift+N,” “Shift+M,” and “Shift+,” so I’m not sure exactly what to change. We could alter Morphine’s profile to match the .key file. I’m a bit hesitant to alter the .key file because I wanted it to be as close to the original Pitbuilder.key file as possible.
-
Aha!! Sorted now! And I’ve made it so that a single press will increment/decrement the HDG/CRS by 5 degrees!
Hi Ice
I presume you must have also found the missing bindings to set panel HSI and panel CSI hidden.
I have over written the “PUSH” under this button with CRS , it makes more sense.
BTW I am unable to get onto mediafire to download your new profile can you put it somewhere else.
David
-
-Ice
It would be easy to just change the profile by Morphine, but the real question is–-how many more little inconsistencies are lurking out there? -
BTW I am unable to get onto mediafire to download your new profile can you put it somewhere else.
MediaFire works fine now.
-
-Ice
It would be easy to just change the profile by Morphine, but the real question is–-how many more little inconsistencies are lurking out there?Quite a few. The really obscure ones I don’t really care about, but it’s the important things that needs sorting out such as the MRM override switch… these things shouldn’t take too long. I’m going over the Helios switches now just to double-check that all callbacks used are still good.
-
Ice another question for you:
In Helios you use callbacks only ?
As you know i have an other keybord layout (azerty Belgian /dutch )keyfile too
Some callbacks didnt work and i had to use keystrokes.Yesterday i needed the bms chatbox to config a custom view (with .gvd)
Could not produce a “.”
What i found out = i could type lowercase “azerty” … but the same keys with the shift pushed gave me “QWERTY” -
Ice another question for you:
In Helios you use callbacks only ?
As you know i have an other keybord layout (azerty Belgian /dutch )keyfile too
Some callbacks didnt work and i had to use keystrokes.Yesterday i needed the bms chatbox to config a custom view (with .gvd)
Could not produce a “.”
What i found out = i could type lowercase “azerty” … but the same keys with the shift pushed gave me “QWERTY”I cannot say for certain, but it seems that Helios only “sees” the callback that have keys mapped to them. If the callback is blank (0XFFFFFFFF) Helios cannot “see” the callback. Even if you map a key to the callback, map the callback to Helios, then remove the mapped key from the callback, Helios cannot use that callback. I think the callbacks are like the “labels” for the key combination, so Helios still throws out the key combination mapped to the callback. Therefore, Helios cannot use a blank “label.”
Can you give me more details regarding your problem? What callback was it? What key was it mapped to? While I have a feeling you’re not using my profile, I’ll see what help I can give you. Having said that, if you just map things properly and follow the instructions, I don’t see the keyboard layout being a problem.