-Ice's Falcon BMS Helios Profile Updated!
-
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!
-
Okay, I just fired up 4.33 and so far, my ICP DED is working fine. For some reason, it lost the audio feedback though. Will have to look into this more.
@ weepop: the nav charts should work fine in 4.33 as it only really interacts with Helios and the chart images. Again, note that Red Dog might’ve changed the charts so some might not be accurate, but this is a simple image change. The default interface should be working fine.
-
Thanks Ice. Much appreciated. I do not think what I proposed works. I loaded Boxin’s updated key file in the BMS UI, while keeping your keyfile for Helios. result: not hood. Some things unchanged in your profile, but others did not work. The DED DCS didn’t work…while the RWR on switch reset the whole electronics mid flight! Pity because my WG profile is now not working in areas that are important. So I kinda find I’m stuck between using your profile OR using an up to date working WH profile. For the moment I choose your profile because having Helios work is preferable to having all function work for the WH Hotas. But I would be fantastic to have them BOTH working up to date at some point. But go and fly 4.33 for the moment and ENJOY IT! It is a very good update. Thanks again.
apoll
PS: Boxin, if you are out there and following this thread, can you help? Merge Ice’s Helios profile with your updated version of Morphine’s WH profile?
-
@ 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?
Hi Ice
it’s all pages but I can make them work by adding an extra toggle hidden for each one!!!
Trouble is I have messed up one of them, CHONGJU and I am struggling to correct it.
Can you tell me is it possible to copy a button and include its bindings so I can revert chongju to its original setting from your untouched profile.
Every time I copy and paste a button it loses its bindings and they are what I want !!Thanks for earlier replies
David -
Can you link me to the thread regarding Boxin’s key file?
Please note that a .key file interacts with Helios and BMS only. A Warthog profile such as Morphine’s profile interacts with the TM WH and BMS only. There is no interaction between the TM WH profile and Helios.
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? I tried this in 4.32 and 4.33 and they are working fine. Like I said, this is just interacting with Helios and the relevant images that you can download as part of my profile, so the nav charts should work regardless of which version of BMS you are flying.
-
i’m not sure how to do that Ice on my iPad. It is, however, in the Warthog section, Morphine’s WH profile thread, page number 39…about half way down, a post by Boxin updating Morphine’s WH profile. You can see that he updates it in a post and then relieves a lot of thanks from then on. I think he does a mark 2 update a little further on. Hope this helps.
Apoll
-
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.