-Ice's Falcon BMS Helios Profile Updated!
-
Chiba hat does nothing. But pinky and up and down with dms changes hsd zoom.
Check out the thread above to know what exactly the China Hat is supposed to do.
In the real jet, as I understand it, the range knob on the TQS adjusts the targeting pod zoom (at least it does on my TQS). HSD and radar range are not controlled by the HOTAS, but rather by the OSBs (or simply moving the cursor up or down the screen).
Yep. Apparently, the fact that it does this in the game is a bug.
-
Hey Ice. All going well with your profile. Sorted the dogfight switch: didnāt have the right line in the config. All fixed. A suggestion or question if I may: the antenna tilt function. Is it possible to map it to the Coolie hat 4 way switch on the WH throttle? It is pretty important to have it mapped somewhere and I donāt think it is, is it? The Coolie switch controls views and as I use a TrackIR and donāt really use those functions currently mapped to the coolie hat. If you would prefer not to alter your profile, how would I do it? Thanks Ice. Itās really great to have the profile up and working at last.
Apoll
-
(or simply moving the cursor up or down the screen).
This is how Iāve always adjusted the rangeā¦
-
Antenna tilt should be that gray INCR/DECR lever on the right side of your throttle assembly.
I use the Coolie to control view zoom as Iāve found that important when trying to get a guns kill on an enemy. The default FOV (130 on mine, IIRC) just wasnāt good enough.
-
This is how Iāve always adjusted the rangeā¦
I think heās referring to the TQS antenna knob which controls the altitude block (antenna tilt) the radar is looking at (i.e. The top and bottom numbers on the cursor). The radar range (not antenna tilt) is adjusted via the OSBs or moving the cursor.
-
Ice, the first thing Iād like to say is thank you for such a wonderful BMS Helios profile. I use keystrokes to control Helios and direct X to control the warthog hotas. The Helios profile works wonderfully, but Iām having some problems with the direct X shift on the throttle as I have read everything I can get my hands on and it just seems a bit glitchy. Also I use joy to key and keystrokes to control the coolly switch. The throttle boat switch works great for D,C,M. But back to my original problem, does anyone else have problems programming DX shift to the warthog throttle?
Also, Iād like to add that programming DirectX via the GUI in the sim works good, it is marked with a number eight in the keyfile, but the shift programming sometimes takes in some time does not. I do realize that you cannot program direct X shifts via the GUI, but do it manually in Notepad++. Any help would be appreciated.
-
Thanks for the kind words and I am glad you are enjoying my work.
As for editing the profile, I presume you are using all the files provided? This would be the Helios profile, the .key file, the TM WH profile, etc? I would not recommend editing stuff via the GUIā¦ I only go there to verify that my assigned commands work. Everything else I do in Notepad++. I have no problems assigning stuff on the shifted layer of the HOTAS.
Why are you using joy-to-key? What does it do exactly? Iāve not worked with it at all. If you just want the coolie switch to throw keystrokes, this is easily done in the Target profile.
I wonder if your āshiftā trigger is working properly or if it is the source of the problem? For my profile, it is the paddle switch that is the shift trigger.
-
This post is deleted! -
Ice, thanks again, I really didnāt expect you to reply so fast. I donāt use target, I just use your keyfile, which controls your Helios profile splendidly. I then use only DirectX for everything else. I have had some luck, programming DirectX with notepad++ which gives me shifted DirectX, but mostly it only works on the joystick. It doesnāt seem to work as well, at least with limited luck on the throttle. I have used the sim GUI to program DirectX to the throttle, but you canāt program the shift DirectX from there, you have to do it in Notepad++
Because I donāt use target, BMS only recognizes POV hats on the primary controller, which is the joystick, pitch and roll. Joy to key is a program that can send keystrokes from any controller and BMS recognizes the keystrokes. As far as I know, there is no shift for joy to key, but anyway, that was my workaround the missing throttle POV, the coolly switch on the warthog throttle.
I can program the shift trigger to be the paddle switch if I want which I may do later on if I can get the profile shifting on the warthog throttle.
I seem to be missing some information on DirectX programming with the shift or itās just glitchy. Anyway, thanks for your reply and I hope this explains better.
-
Snook - as i was not using target either at first and was having problems. May i make the suggestion that you give it a try. I was against it at first , but the work that ICE has done is working perfectly for me , especially in conjunction with helios.
give it a try and you might not look back - I havenāt.
-
Thanks for the endorsement, i3dman!
Give the recommended setup a try; I know you have your reasons for avoiding TARGET but, well, IMHO it is a great program and is made even better when someone else has done most of the work for you! (not me, I am referring to Morphine!)
-
I decided to try to understand the key file a little better so I did an experiment with iceās key file and target profile. I assigned alt n and ctl n to increase/decrease the radar range on the FCR. This was a 2 step process. First, I changed the key file to assign the alt/ctl n keys to the radar up and down commands:
SimRadarRangeStepUp -1 0 0X31 4 0 0 1 āSHORT: Radar Range Upā
SimRadarRangeStepDown -1 0 0X31 2 0 0 1 āSHORT: Radar Range DownāThen, I choose the flaps switch on the WH to control the range as ice hasnāt yet programmed that switch:
MapKey(&Throttle, FLAPU, PULSE+L_ALT+ānā);
MapKey(&Throttle, FLAPD, PULSE+L_CTL+ānā);To my amazement it worked. This was just an experiment, and if ice decides to program the throttle panel, I will simply remove this code. However, what you see was 2 days of reading/work. I had tried to do it as a shift command on the CMS button, but couldnāt get that to work as buttons 270 and 272. Was this because of the 32 DX limit?
-
AFAIK, that command is not realistic and not available to the pilot in the cockpit outside of using the OSB 19 and 20. That is why they are under the āSHORTCUTSā heading.
But nevertheless, good work in understanding both the .key file structure and the TARGET scripting!
-
Ice and I3Dman, thanks for the advice and I will certainly take it to heart. Over the years. I try to keep the controls the same from HOTAS to HOTAS, so I donāt have to relearn muscle memory so much. At this time. Iām quite sure that the warthog throttle is not taking DirectX shift commandās. This is a mystery to me and I would like to know why.
I have used more Morphineās profile a little and it is a very fine one, and I should have no complaints, but I would like to shift things around a little and probably need to learn target scripting for that.
I would like to thank Ice Again for his exceptional Helios profile and for his part in keeping BMS alive and growing.
-
You are welcome! Glad you are enjoying the profile.
As per your comment on the other thread, I will state again that the shifted functions of the HOTAS works fine. Just look at lines 1267 to 1327 on my .key file. To give you an example, the shifted pickle button and the shifted left throttle button (red one) are mapped to trim reset. Guess how many times Iāve used that? TMS, DMS, Coolie, and even the Radio switch have shifted commands as well.
Now whether this works WITHOUT using TARGET I am not sureā¦ it might be due to DirectX hardware mapping or whatever, as apoll has had a problem like this due to having a different device plugged in. Unfortunately, I canāt test at the moment because Iām getting ready to move stuff over into my new PC build.
-
Hate to have to post thisā¦ I had Helios working a while back. Hard drive crash. So set up new BMS 4.33, with Helios and Iceās profile and cannot get it to work at all. Made sure the Helios interface was pointed to the Ice key file and set it up key file in BMS controller set up as well. I am using a CH Fighterstick and throttle but thought that should not matter as far as just getting the Helios to work. It comes up on monitor 2 but no switches or anything work when clicked. I am not even extracting any MFD or gauages, etc, just to keep it lean for troubleshooting. Before when I had it working with 4.32 it set up fairly straightforward, worked first time. Different GPU now, Asus GTX960, otherwise same hardware. Have been trying for 3 evenings, nothing.
I have read this thread and a few others, other forums too, and tried a few things but no joy. Any ideas guys? -
are you launching Helios completely, prior to launching BMS? And is the key file being referenced within BMS as well?
-
Hi ice, wonderful work, i tried your amazing profile on my laptop, but now back at home i am trying to made it work with my main PC, but i am running in a very strange problem with Helios.
I opened the profile and reset the monitor (Main Hp envy 32" 2560x1440 touch screen monitor 19" 1600X900 packard bell viseo 2000t) but as soon as i start the profile in helios control center, i have a very weird issue (on the notebook didnāt have it with internal screen as primary and viseo 2000t as touch), i see the helios cockpit divided beetween the two monitors and very out of scaleā¦you can see from the screenshot that in helios the profile seems correct (image all stretched and scaled to the second monitor) while when the profile runs it is all messed up.
Can someone help me? -
first i would set the bigger monitor as your primary in windows.
Secondly , i have had issues when having monitor above or below each other, i would recommend putting the next to each other with the primary to the left.I run 6 monitors all side by side with the first 3 to the left running the main BMS output, the remaining 3 are showing Helios with MFD exports.
-
The bigger monitor is already the primary oneā¦ Anyway i solved the problem, it was different scaling options between the two monitor sā¦ Now both 125% and it is all good.