Combine "BMS Full.key" with older Helios profile
-
If you are reporting a problem with the chart pages as well, I’m not really sure what’s going on there. I’ll need to look into it a bit more. As for the FPS button, Helios seems to be having trouble with how the key combo is done for Falcon. I’ll have to re-map that. Helios has issues with a few keyboard keys that it cannot seem to use… “Views” and “Smoke” are remnants of my old profile; I’ll have to check them as well. Apologies for that.
Yes I am not getting all the chart information for each airfield, only selected sheets. Taking Kunsan for example, I only see the ‘Patro Departure’ and ‘Aiport Diagram’ sheets. All other buttons except for ‘Spawn Points’ do not work. When I look to my \documents\helios\Ices Falcon BMS 4.33 ver.2\Charts\South Korea\Kunsan folder, I see all the .png charts that should be assigned to your buttons however they don’t appear to be linked. I am guessing it is a mapping issues in Helios but as Helios editing is well beyond me at this point I am not sure how to check.
On further investigation it appears the smoke button DOES indeed work (apologies…) - it is only the FPS and Views that don’t. I was doing some SAM hunting today and went to hit the ‘SEARCH’ button on the ‘TWA’ (Left auxiliary console) but found that this button did not work either. Perhaps it is worth checking this one out also when you find some time.
And no need for apologies! on the contrary, this profile has improved my experience immensely
-
As for the .key file editing, I prefer not to delete any lines that I don’t need, instead, I just “invalidate” them by putting a “#” sign in front of it… or three “#”. This is the beauty of editing the .key file in Notepad++, being able to put white spaces and characters so that it’s easier to “read” the .key file. Make a backup .key file with a different name, open the backup in the in-game UI, make a change or something, then save it in the in-game UI. Now open the backup .key file in Notepad++… headache!
I agree. The ‘irrelevant code’ I was speaking about was only the DirectX button ID’s that were relevant to your Warthog Throttle. Obviously the Cougar and Warthog throttle have a different amount of buttons and layout, and thus your key had ID’s that were of no use to me. I left everything else as it was for future ‘tweaking’. And yes, what a headache! at least now I’ve learnt to back the keyfile up after every change - nothing worse than opening up your hard work only to find you can’t find anything in its original place anymore…
-
I agree. The ‘irrelevant code’ I was speaking about was only the DirectX button ID’s that were relevant to your Warthog Throttle. Obviously the Cougar and Warthog throttle have a different amount of buttons and layout, and thus your key had ID’s that were of no use to me. I left everything else as it was for future ‘tweaking’. And yes, what a headache! at least now I’ve learnt to back the keyfile up after every change - nothing worse than opening up your hard work only to find you can’t find anything in its original place anymore…
The idea is to NEVER save a .key file in the UI. Do all your work and saving in Notepad++
-
Yup, learnt that the hard way…
-
Best types of lessons!
-
Weepop - Would you not be able to just add in any additions from BMS full.key that are not in your current key? I haven’t had a chance to play with your file yet as I have been trying to get Ice’s to work with my setup. See above.
Hi Wilkotaz, sorry for delay in reply,
I think you misunderstood when I said I do not use BMS full key.
MY keyfile is all and more than what is in BMS full.
BMS full is actually only BMS partly full and in many cases only has key presses associated to toggle up and down when there are call backs for each separate position.
Take section 2.16 as an example. BMS full has all the call backs for the UHF backup frequencies but only keys associated with the toggle call backs.
My latest key file (not released yet WIP) has keys allocated to all frequency digits (total of 34)I will be releasing it shortly
weepop -
Glad to know it’s working. One of Weepop’s issues was that he needed to “fix” the charts page but nobody else had reported that problem.
I just noticed that some of the buttons don’t work in the charts pages. For example when I click on ‘Kunsan’ the ‘Patro Departure’ chart displays on the left of the screen and the ‘Airport diagram’ on the right side, but the ‘Aladi, Coyote, Patro, Visual 18/36,ILS 18 and ILS 36’ buttons don’t do anything. Only the ‘Spawn Points’ button seems to work. I have a similar issue with the other charts also, any ideas?
Also, I’ve noticed the ‘FPS’ ‘Views’ and ‘Smoke’ buttons under the left MFD don’t function either? Has anyone else had these issue?
Wilkotaz see my helios profile post 111 and 115 to explain your loss of chart pages
weepop
-
Hello Wilkitaz,
As an avid follower of Ice and Weepop Helios development over time, I remember one of them suggesting that I use the .key excel profile editor in the BMS docs file folder. It is called: BMS Key File Editor.xlsm (developed by Boxer, thank you Boxer you have helped me a lot!!)
There’s also a YouTube video that explains how to use it but it is in a foreign language but with English subtitles. (Thank you Dasoxori!!! For taking the time to do this video even though it’s in your own language!) It consist of part one and part two. Follow that to get up to speed on how to use this file. Search for BMS 4.33 Key File Editor (Part I of II) in YT and you will find it. Try to be patient with the language or just turn the volume down and follow the screen instructions and you will be an expert on it.
This tool allows me to import any .key profile, whether it belongs to Ice, Weepop, or the original BMS .key files from your BMS Folders. I’m able to see how all the call-backs are being triggered. It also has any of the HOTAS DX assignments so you can use DX settings instead of the program that comes with your flight stick. It also takes into consideration the ability to use shift-pinky in order to duplicate how many more buttons you can have on your HOTAS.
I hope this helps. Please keep us posted as to your progress.
Thank you
Pika -
Wilkotaz,
I started using VAC for my comms. All I do is issue an order and BMS responds accordingly.
Check this link: https://www.benchmarksims.org/forum/showthread.php?8323-DeeJay-s-Voice-Activaded-Commands-(VAC)-Profiles (Thank you Deejay!!)
PikaPS: you can also find the Voice Activated Control profile on the documents folder in BMS.
-
Ice,
My FPS and Smoke buttons work as intended.
Pika