-Ice's Falcon BMS Helios Profile Updated!
-
It has been awhile since I ran -ice’s old Helios profile, so perhaps this is a silly question. Don’t you also have to run Morphine’s target profile for the WH in order to get the full benefit of this great Helios profile? Has anyone just ran this profile with the new key file but using 4.33?
-
The profile should work fine under 4.33 as long as you use my old .key file. I will get around to updating it but if you guys find a problem with my .key file or Helios profile with 4.33, then just let me know.
apoll, check out my YouTube tutorials for Helios:
flyway, I used to play with a program that did something like this for the iPad; I’m sure someone else has made one for Android. However, that’s the extent of my knowledge in that area. Sorry.
sobe, obviously I’ve not tried using my Helios profile with a different TM WH profile; feel free to test this out and tell me the results!
However, AFAIK, Morphine’s profile only ties the joystick and throttle together so they are seen as one device which makes it easier to map the axis on the Setup screen. There are a few Direct X command that are in the .key file that obviously corresponds to a button in the WH, but I guess that would work in a different HOTAS as well. Might not be the same button, of course.
-
Ok. Managed to get Ice’s Helios profile going. This is where I have stuff:
- morphine’s target script in the Target script editor; runs every time I launch Bms 4.33. Is this the right Target script editor script to be running with Ice’s Helios profile or is there another?
- Ice’s Helios 4.33 profile v5 in Helios; I noticed when I set up Helios to run with Falcon, in the drop down list to associate Helios with Falcon, there is no 4.33 selection, only 4.32, which I selected. Is this right? And for the associated key file in BMS/user/config is Ice’s key file for use with his Helios profile. All good do far?
- I’ve extracted the gauges via Lightning’s tool and the native BMS extractor.
That’s about as far as I’ve gone at this point. Just starting to text it. One other question: in the Morphine WH thread, I notice a guy called Boxin has updated Morphine’s original BMS key file to bring it into line with 4.33. Which is really great. But I know that we have to use Ice’s key file for his profile, so we are not using the most up to date key file with Morphine’s Target script file…unless of course Ice has also updated his key file used for the Helios profile. Is this ok? Not using Boxin’s latest updated key file for BMS?
Ok, thanks in advance.
Apoll
-
- morphine’s target script in the Target script editor; runs every time I launch Bms 4.33. Is this the right Target script editor script to be running with Ice’s Helios profile or is there another?
I use Morphine’s script because I use a TM Warthog. Feel free to use your own controller/HOTAS with a different control profile. Helios interacts with the Falcon .key file so Helios+Falcon .key file should be good. Using my .key file with your controller/HOTAS, that’s where I can see there might be issues.
- Ice’s Helios 4.33 profile v5 in Helios; I noticed when I set up Helios to run with Falcon, in the drop down list to associate Helios with Falcon, there is no 4.33 selection, only 4.32, which I selected. Is this right? And for the associated key file in BMS/user/config is Ice’s key file for use with his Helios profile. All good do far?
I’m not exactly sure what you’re asking, but if it’s just “where to put the .key file?” then yes, put it in the User/Config folder in 4.33
One other question: in the Morphine WH thread, I notice a guy called Boxin has updated Morphine’s original BMS key file to bring it into line with 4.33. Which is really great. But I know that we have to use Ice’s key file for his profile, so we are not using the most up to date key file with Morphine’s Target script file…unless of course Ice has also updated his key file used for the Helios profile. Is this ok? Not using Boxin’s latest updated key file for BMS?
It’s been a while since I played with the .key file, but I did make extensive modifications to it mainly so that it triggers sounds when switches/knobs were activated in the pit. Again, you are free to try out Boxin’s fix but I make no guarantees.
-
Tks Ice. yes, I use a TM Warthog as well. So that’s why I’m using Morphine’s script. S0 I’m using your helios profile with a TM WH and Morphine’s Target script in the Target Script editor, which I understand must be run BEFORE I start BMS. 2nd question: I mean when you add an interface in Helios. There is a choice of Falcon/BMS 4.32, OF, FF…BUT NO 4.33.o I have to select 4.32 as the interface. I hope that is OK? (No other choice really…)
Re Boxin’s updated keyfile…do you think it might be okay to use with your Helios profile? Add it in the Helios interface screen so your Helios profile uses Boxin’s updated keyfile? Might work? (Yes, I will try it but you can’t see any immediate showstoppers?)
Thanks Ice for responding and creating your profile.
apoll
-
Yeah, you run the script BEFORE starting BMS so that when BMS runs, it will see “one” controller. If you do not run the script, it will see two (throttle and stick).
As for Helios, yes, just select 4.32. AFAIK, that’s just a “name” for the program and doesn’t really do anything aside from telling Helios what commands to expect.
As for Boxin, I’ve not really looked at it so I can’t comment. Should NOT be much of an issue since Helios uses the callback itself and not the key combination. However, the callback MUST be mapped to a key combination! For instance, you could have “Landing Gear Toggle” (AFGearToggle) mapped to “G” key, and you also have “Landing Gear Up” (AFGearUp) and “Landing Gear Down” (AFGearDown). Helios will not care what keys AFGearUp and AFGearDown are mapped to, as long as they are mapped to a key or key combination. If they are blank or not mapped to anything, it will not work with Helios.
-
Ok. Thanks Ice. Got it.
Apoll
-
Hey Ice, one further question if I might. If in Helios i have the Falcon 4.32 interface mapped to your key file, Ice’s key file, then that means your profile uses that key file when I load it up, right? Can I then, in the BMS setup/controllers UI use ANOTHER key file to load, such as Boxin’s modified key file of Morphine’s original key file? In short, can I have two different key files in use statue same time; Ice’s for the Helios profile set in the interface screen of Helios, and Boxin’s loaded in the BMS UI for my throttle and stick? The point of this would be to have the latest key file for my Warthog HOTAS while still using your key file that works with your profile. Can I do this? Your Helios profile needs your key file which is set in the Helios interface screen. Right? It doesn’t need the key file loaded through the BMS UI, right? I can have Boxin’s loaded in the BMS UI for my WH and that has nothing to do with your Helios profile successfully running in game, right?
Thanks in advance.
Apoll
-
Ice
Can you tell me how the different pages of the Korean Nav Volume are supposed to be displayed.
I find that with your profile as is nothing happens when I press the individual buttons.
I can make them work by adding extra “hide on panel” commands but I would much prefer an explanation of how they should work.Thank you David
-
Ice…do you use MFDE to get the MFDs and indicators, gauges, MFDs, etc?
- dawgboy
-
Dawgboy, I have Ice’s profile up and working. I use the native BMS display extractor to extract the MFDs, the DeD and PFL. I then use at the same time MFDE to extract all the other guages and bits and pieces, including the RWR. So, when I fly, I first load the MFDE which extracts the various gauges to my touchscreen. Once I see they are in their right places and up and running, I then load my Helios profile (Ta da…Ice’s). I then load my Target script editor to run Morphine’s script because I am using a Warthog HOTAS, and then I start my TrackIR. Once all that up and running and good to go, the last thing I do is launch the BMS applet which starts the MFDs, DeD and PFL boxes; I can see them initialise on my touchscreen in the right spots against Ice’s Helios profile, and I know they are good to go when I see that. All is in order and ready to fly. One thing: with the MFDs, DeD and PFL being extracted by the native BMS extractor…when you are arranging them on the touchscreen in their right places, if you tick the ‘borders’ box in the extractor, you can drag them around the screen with your mouse easily to place them in the right spots. I didn’t know that at first. I always thought you had to punch in the correct coords in the applet to get them in the right spots, a tedious and time consuming task.mnup. Just enable those borders when arranging and drag them around as easy as pie. Then, when in the right spot, just go back into the applet and unlock ‘borders’. Done and dusted.
Hope this helps.
Apoll
-
apoll
I have the same setup as you do and I do almost everything you do except I use MFDE for the MFDs, Ded and PFL. In post #35 above you raise an interesting question about using different key files for the WH and for Helios. I am doing that know but I never gave it any thought. Now I am not sure, but I think it would be ok. It is my understanding that -ice may not even be using the WH with Morphine’s profile so it could well be that they are independent. Will have to wait for ice to comment. -
Sobe. Hi. I could not not get MFDE to display my MRDs, DeD and PFL. No idea why. That’s why I went with native extractor. Re different key file. Well, I’ll give it a go and see what happens. It should be ok, if I understand it correctly. Yes, interesting to see what Ice says.
apoll
-
Sobe. Hi. I could not not get MFDE to display my MRDs, DeD and PFL. No idea why. That’s why I went with native extractor. Re different key file. Well, I’ll give it a go and see what happens. It should be ok, if I understand it correctly. Yes, interesting to see what Ice says.
apoll
MFDE works for all of my extraction needs, too. And I really like Ice’s Helios profile.
-
Hey Sobe. Not sure it’s going to work. Just tried to load a different key file in the BMS UI and things would not work in the Ice profile, like the DeD data switch return or sequence. Hmm. Need to see what Ice says. You there Ice?
Dawgboy, glad it worked.
Apoll
-
apoll
that does not sound good. maybe we just have to twink one of the files. I can understand the keyfile that goes into the WH, but how to change the Helios callbacks are beyond me. -
Yea, me too. If it was just a matter of locating the relevant bit in the key file and making sure both were aligned, no probs. but callbacks….aieeee! Too hard. Hope someone can figure this out for us.
Apoll
-
I am starting to use the key file and WH profile that someone named Boxin did, which no doubt is different from the keys/callbacks used by ice in his profile. Do you have a list of changes that you have had to make so far?
-
Hey Ice, one further question if I might. If in Helios i have the Falcon 4.32 interface mapped to your key file, Ice’s key file, then that means your profile uses that key file when I load it up, right? Can I then, in the BMS setup/controllers UI use ANOTHER key file to load, such as Boxin’s modified key file of Morphine’s original key file? In short, can I have two different key files in use statue same time; Ice’s for the Helios profile set in the interface screen of Helios, and Boxin’s loaded in the BMS UI for my throttle and stick? The point of this would be to have the latest key file for my Warthog HOTAS while still using your key file that works with your profile. Can I do this? Your Helios profile needs your key file which is set in the Helios interface screen. Right? It doesn’t need the key file loaded through the BMS UI, right? I can have Boxin’s loaded in the BMS UI for my WH and that has nothing to do with your Helios profile successfully running in game, right?
Thanks in advance.
Apoll
@ apoll: Again, I have no clue to be honest. Give it a try and post the results!
It should work but I can see a few issues that might happen:
1. They changed a callback in 4.33 so it won’t work in Helios whether using my .key file (I don’t have that new callback) or using Boxin’s or anyone’s new .key file (Helios would not know to use the new callback).2. A callback that I use is in the new .key file but is unmapped. See previous post why.
3. Helios doesn’t like the new .key file and the universe implodes
As far as I understand it, Helios looks for the callback and issues the relevant key combo to “send” the command. If there is a callback but now key combo, Helios cannot work. My profile tells Helios to look for a Falcon BMS .key file (that’s why you set Helios to Falcon BMS 4.32), then you select a .key file to load. You can use my .key file or someone else’s, but all that really does in Helios is to tell the program what callbacks it has available for use.
Hope that helps!
-
@ weepop: The nav pages should display the relevant runway or departure information based on what button you’ve pressed. Is this problem present on all airbases or just specific ones?
@ dawgboy: Yes, as per instructions, I use MFDE for the gauges, countermeasures, RWR, and fault panel, and I use the built-in extractor for the MFDs, DED, and PFL. Everything else is Helios.
@ sobe: I am using Morphine’s profile for the TM WH but I think I made a few changes. However, my .key file has nothing to do with Morphine’s profile and vice versa.
The reason I use the built-in MFDs, DED, and PFL is mainly because when I tried the MFDE MFDs, there was a bit of lag between my in-pit MFD and the extracted ones. As for the DED and PFL, IIRC, MFDE’s versions were yellow-text? I preferred the green text of the built-in ones.
As for dragging and dropping extracted displays, I did that initially but I hated it so I calculated the X/Y coordinates for my stuff and screenshotted it so it is easy to replicate. If for some reason my built-in extracted stuff gets messed up, it’s just a few button-presses to get it fixed and fixed EXACTLY RIGHT. Having to manually drag, resize, test, resize, test, reposition, etc. stuff in MFDE is a nightmare for me and I wish there was an “enter coordinates and gauge size” option for MFDE. If nothing, just a “nudge the gauge using the arrow keys” option would be great! Nothing more annoying that just having to nudge a gauge about 1-2 pixels and end up moving it 5 pixels!
Anyway, for all other concerns regarding the new .key file, you will all have to give me some time to catch up with 4.33. As of yet, I’ve not even cracked open the new .key files so I don’t know what’s new. I’ve been quite busy in real life with family and work and I just finished organizing a massive Group Buy for TacView Professional Edition so I’ve not had a chance to enjoy 4.33 yet!