-Ice's Falcon BMS Helios Profile Updated!
-
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.
-
Going through my profile today and have managed to double check all switches and knobs and hopefully everything is working fine now. I’ve added a few switches such as the MWS and EWS switches on the CMDS panel and the new buttons on the ICP (WX, FLIR). The new manual frequency knobs of the Backup UHF panel has not been put in yet and is a bit low on the priority list –- I don’t think this will be needed with any great urgency anytime soon so I’m putting it off for later.
I’ve also managed to make the JFS, Autopilot (Pitch), and Parking Brake switches respond to changes in the cockpit. The Landing Gear also syncs with the aircraft, going to the up or down position as necessary at the start of the mission, but this sync is quite temperamental. I think if you can keep focus on the BMS window, Helios will pick up whatever it needs to pick up to sync the LG. However, sometimes my PC will lose focus on the BMS window… need to test this out a bit more.
Obviously with the new .key file, much of the throttle buttons and switches are now sending callbacks they shouldn’t be. This is because in Morphine’s profile, the 32 DX buttons that can be assigned to “one” controller is mostly used up on the stick so almost all of the commands assigned to the throttle are done via the TARGET profile and it does so by issuing key commands and not callbacks. I’ve re-assigned the easily-accessed switches to what they’re supposed to be and these are the ones that are on the throttle itself. The switches/buttons on the throttle base are still “Morphine’s profile” so that needs fixing as well. However, most of his commands are what I already have in the Front Console of my profile. Things such as Master Arm, Landing Gear, Laser Arm, RF Norm, CAT switch, Parking Brake, etc. so I think it’s best if I just re-map these to what is most useful… for instance, I was thinking of mapping the Landing Gear Up/Down command to the flaps switch at the bottom of the throttle. The reason for this is accessibility. I think in the real jet, the pilot doesn’t even have to look down to locate and operate the landing gear lever; the size and location of the lever leaves no room for error and the pilot could find it in the dark, I would think. This is the same for the flaps switch… just follow the throttle down the left side to the base and even in pitch blackness, it’ll be a miracle if you miss the flaps lever!
Another candidate is the CATI/CATIII switch along with the Emergency Jettison button. Sometimes, I get jumped by enemy fighters and I need to dump my ordnance and go CAT I and during these times, seconds matter. With a little practice, I can press the AP Engage/Disengage button and throw the EAC switch forward without even looking down at my throttle. Also, pressing a real button and throwing a real switch can be much rougher compared to the “delicate” motions you need when operating stuff on a touchscreen.
So, any suggestions for what other commands/callbacks I can map to the switches at the TM WH base?
-
Yes i used your keyfile from the beginning a few years ago, and added dunc’s DX for the hotas
And yes checked that all callbacks assigned to the keyboard.some switches didnt work with callbacks
Masterarm on off shift (m on english keybord in belgium ,) so i had to assign shift , etc
rf norm silent Quit also assigned to keystrokesand a dozen more
For me its not a problem anymore
sometimes even keystrokes fail to work ,Helios can’t center the left APswitch in Helios (used “{LCONTROL}q”
From the keybord its okBTW when i open notepad and touch the heliossswitch i see the right code.
Like i said BMS is doing something strange with upper an lower case, on my keyboard.
But with the workaround its ok.
-
That’s the thing. There should be NO workaround.
What .key file are you using now? This is the hard thing about Falcon –- each of us starts with a .key file and modifies it and eventually we all end up with different .key files. For 4.33, I’ve cut all ties to 4.32. To start with, I’m using a totally new .key file which I’ve adapted by mixing the Full.key and Pitbuilder.key and making a few adjustments. Hopefully, once this is done, there won’t be much to add to it later on. I would suggest you use my .key file if you can, that way if you tell me Master Arm is working, I can check the .key file…
The main idea behind my Helios profile was to have everything available and eliminate the need for the keyboard and mouse once the pilot is on the 3D screen. Having to keep a keyboard handy for “workaround keystrokes” just defeats the whole purpose of Helios.
Currently, the only thing not working on my profile is the indicator light on the Landing Gear handle, but I’ve never gotten it to work ever since!
-
shure there is a workaround… the keystroke-editor in helios.
in 3D i dont need the keyboard at alldownloaded your keyfile and helios profile
Did a testflight , nothing was working from within Helioschanged keyboardlayout to english uk and later to english us… even restarted … no joy
reinstalled belgian layout and my modified keyfile,helios working again
Think we have a keyboardlayout/winversion/bms bug here -
OK Ice
Traced and solved my problem.
This is working as a callback in HeliosSimLeftAPMid 115 0 0x16 0 0 0 1 "MISC: ROLL Switch - ATT HOLD"
–----------------------------------------------------------
SimLeftAPMid 115 0 0x11 6 0 0 1 "MISC: ROLL Switch - ATT HOLD"
This code didnt work in Helios, but in BMS it was not a problem
Conclusion:
Helios is thinking that i use a standard Qwerty layout.Ballbacks with azwq,;:=µ$^m are “tabu” for me
-
weepop, all nav pages have the “extra toggle” built in and that’s why they should work. Have you tried downloading a fresh copy of my profile?
Hi Ice
Thanks for correcting Mediafire,I have downloaded your latest profile and I still have exactly the same problem.
Pages do not display unless I add an additional "toggle hidden on panel to each button plus one more to first button or it alternates between displaying first page and being blank when I press it.
IS ANYONE ELSE HAVING THIS PROBLEM??I am in the process of updating the charts to match ones in 4.33 docs, keeping your naming.Would you like a copy to save you the pain of doing it yourself?
Its pretty straight forward except for Hoengsong and Sokcho which have less pages.David
-
hi
Can this be used to say put an MFD on my second screen a long with the MFD buttons and allow me to use my mouse to iteract with them?
Or is it for touch screens onlyThanks
-
Does anyone know if it is possible to run this on an iPAD or Glaxay tab or something similar?