-Ice's Falcon BMS Helios Profile Updated!
-
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.
-
Hi Ice,
I am trying to run your profile in the editor but nothing shows up and then it would crash. Any ideas? Thanks.
-
Hi Ice,
I am trying to run your profile in the editor but nothing shows up and then it would crash. Any ideas? Thanks.
Hi ice, and guys.
I have some little but annoying issues with your profile…90% works very well, but other aspects are not working as expected, for example when i press f-ack i have the MFD brightness that decrease, when i press master caution, fps, right hardpoint and fcr on/off switches nothing happens. I checked in Helios and the callbacks bindings is correct, for just a check i tried using my key profile (Full BMS with only my Saitek X55 bindings modified) and the f-ack button and master caution works well.
I am using your profile just with saitek x55 stuff instead of Warthog ones, but i tried also loading your profile with no changes at all and the results are the same. Others have similar problems?With these i cannot do a Cold start without using mouse and keyboard… but i really don’t understand what could be the problem if for other works well.
Thanks anyone for help -
Update…i tried to load both in helios and in BMS the default pitbuilder profile, and the results are the same…so what happens here?pretty strange
-
Hi Ice,
I am trying to run your profile in the editor but nothing shows up and then it would crash. Any ideas? Thanks.
Same here… :wfish:
-
try this link
-
Thanks.
That profile does load without crashing in the Helios Editor. I was able to Reset the Monitors to match my monitors.
However, that profile does not have any of the gauges showing up at all… I guess I could try and figure out how to add them all back. But somebody must have a full working profile?
-
did you download all the image files as well? they are separate.
and the gauges themselves are populated by MFD EXTRACTOR, another separate program.