-Ice's Falcon BMS Helios Profile Updated!
-
Yes Ice. Hardware issue Nothing at all wrong with your excellent profile. But it’s a common hardware issue for sure; the forums are full of it for WH and Cougar owners. Thanks for your efforts; much appreciated. Now I can crack on and actually start learning this beast! Let me know if you want any further testing done in certain areas…happy to do so.
Apoll
-
Let me know if you want any further testing done in certain areas…happy to do so.
Just go ahead and play. If you find anything broken or if you think something should be changed, I’m open to suggestions!
Hi Ice,
Thank you so much for your new Helios (and add-on’s) profile. As soon as I have time to install and give it a test-fly, I’ll post my feedback here.
Cheers
Thanks, glad you found it useful!
-
the Radar range isnt working
pseudo-fix now is that I’ve mapped the range knob up/down directly as button presses. I’m not sure if that’s realistic though; Morphine did his as an axis instead of a switch/button. How does this work in the real jet? Does anyone know?
Also, is it supposed to be able to adjust the HSD range as well? Or just the radar range?
-
Ice, missile override button forward and back on the throttle just flashes the two modes up, but does not stick. Goes back to Nav mode immediately. Am I doing something wrong?
apoll
-
the Radar range isnt working , but the HSD zoom in and out both work.
Apparently, the china hat WAS working as intended. How exactly was it not working for you?
Check out this thread
-
Ice, missile override button forward and back on the throttle just flashes the two modes up, but does not stick. Goes back to Nav mode immediately. Am I doing something wrong?
Are you talking about the MRM/DF override switch? The one below the speedbrake? Should be working fine.
Check out your falcon bms.cfg file and see if g_bHotasDgftSelfCancel is set to 0. -
Chiba hat does nothing. But pinky and up and down with dms changes hsd zoom.
-
pseudo-fix now is that I’ve mapped the range knob up/down directly as button presses. I’m not sure if that’s realistic though; Morphine did his as an axis instead of a switch/button. How does this work in the real jet? Does anyone know?
Also, is it supposed to be able to adjust the HSD range as well? Or just the radar range?
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).
-
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?