-Ice's Falcon BMS Helios Profile Updated!
-
Cobalt, is your touchscreen working with OTHER programs? I cannot imagine why it would work in other areas but not in Helios. In any case, might be a good idea to troubleshoot in a more dedicated forum/site.
My screen is an iiyama PLT2250MTS and it works flawlessly.
-
Yep1 single pc
-
Cobalt, is your touchscreen working with OTHER programs? I cannot imagine why it would work in other areas but not in Helios. In any case, might be a good idea to troubleshoot in a more dedicated forum/site.
My screen is an iiyama PLT2250MTS and it works flawlessly.
It works ok as a touchscreen but I was never able to get it to function with bms/Helios. Its been a long time (screen gathers dust since new) but as far as I remember it would not transfer key presses in helios into bms game.
Been so long now that what familiarity I had struggled to get in the use of helios has gone
-
Cobalt, clear inbox please.
-
Hi mates,
I would like to export the cockpit files for helios on another laptop with a touchscreen. Is this possible? And how. Im new to this helios thingy, so maybe one can point me in the right direction……Thx
-
Search for GPT, that should help you IIRC. Sorry I cannot be of more help as I do not use it.
-
Ice is it possible to have two separate BMS display extractions set up at the same time.
I want to be able to use two separate Helios profiles and they of course have different location for mfd’s etc.
-
I have no clue as I have not tried it.
What exactly are you trying to do?
-
I am working on introducing your Helios profile but want to keep my profile till done.
-
This post is deleted! -
@-Ice, is your profile working correctly with 4.33?
-
Going to set this profile up on my touchscreen. Wondering where are the detailed instructions for installation? Yes, there are instructions for placing the filed in the Helios directory and which key file to use and place where. But what about how to set Helios up with it, how to get the gushes working and anything else needed? Forgive newby, but I need a ‘do this now, then that, then this…’ guide. Is there one here?
Thanks,
Apoll
-
Going to set this profile up on my touchscreen. Wondering where are the detailed instructions for installation? Yes, there are instructions for placing the filed in the Helios directory and which key file to use and place where. But what about how to set Helios up with it, how to get the gushes working and anything else needed? Forgive newby, but I need a ‘do this now, then that, then this…’ guide. Is there one here?
Thanks,
Apoll
Check out Gadroc’s site
-
Hey to all, is there any way of having an application like this for android?
-
It has been awhile since I ran -ice’s old Helios profile, so perhaps this is a silly question. Don’t you also have to run Morphine’s target profile for the WH in order to get the full benefit of this great Helios profile? Has anyone just ran this profile with the new key file but using 4.33?
-
The profile should work fine under 4.33 as long as you use my old .key file. I will get around to updating it but if you guys find a problem with my .key file or Helios profile with 4.33, then just let me know.
apoll, check out my YouTube tutorials for Helios:
flyway, I used to play with a program that did something like this for the iPad; I’m sure someone else has made one for Android. However, that’s the extent of my knowledge in that area. Sorry.
sobe, obviously I’ve not tried using my Helios profile with a different TM WH profile; feel free to test this out and tell me the results!
However, AFAIK, Morphine’s profile only ties the joystick and throttle together so they are seen as one device which makes it easier to map the axis on the Setup screen. There are a few Direct X command that are in the .key file that obviously corresponds to a button in the WH, but I guess that would work in a different HOTAS as well. Might not be the same button, of course.
-
Ok. Managed to get Ice’s Helios profile going. This is where I have stuff:
- morphine’s target script in the Target script editor; runs every time I launch Bms 4.33. Is this the right Target script editor script to be running with Ice’s Helios profile or is there another?
- Ice’s Helios 4.33 profile v5 in Helios; I noticed when I set up Helios to run with Falcon, in the drop down list to associate Helios with Falcon, there is no 4.33 selection, only 4.32, which I selected. Is this right? And for the associated key file in BMS/user/config is Ice’s key file for use with his Helios profile. All good do far?
- I’ve extracted the gauges via Lightning’s tool and the native BMS extractor.
That’s about as far as I’ve gone at this point. Just starting to text it. One other question: in the Morphine WH thread, I notice a guy called Boxin has updated Morphine’s original BMS key file to bring it into line with 4.33. Which is really great. But I know that we have to use Ice’s key file for his profile, so we are not using the most up to date key file with Morphine’s Target script file…unless of course Ice has also updated his key file used for the Helios profile. Is this ok? Not using Boxin’s latest updated key file for BMS?
Ok, thanks in advance.
Apoll
-
- morphine’s target script in the Target script editor; runs every time I launch Bms 4.33. Is this the right Target script editor script to be running with Ice’s Helios profile or is there another?
I use Morphine’s script because I use a TM Warthog. Feel free to use your own controller/HOTAS with a different control profile. Helios interacts with the Falcon .key file so Helios+Falcon .key file should be good. Using my .key file with your controller/HOTAS, that’s where I can see there might be issues.
- Ice’s Helios 4.33 profile v5 in Helios; I noticed when I set up Helios to run with Falcon, in the drop down list to associate Helios with Falcon, there is no 4.33 selection, only 4.32, which I selected. Is this right? And for the associated key file in BMS/user/config is Ice’s key file for use with his Helios profile. All good do far?
I’m not exactly sure what you’re asking, but if it’s just “where to put the .key file?” then yes, put it in the User/Config folder in 4.33
One other question: in the Morphine WH thread, I notice a guy called Boxin has updated Morphine’s original BMS key file to bring it into line with 4.33. Which is really great. But I know that we have to use Ice’s key file for his profile, so we are not using the most up to date key file with Morphine’s Target script file…unless of course Ice has also updated his key file used for the Helios profile. Is this ok? Not using Boxin’s latest updated key file for BMS?
It’s been a while since I played with the .key file, but I did make extensive modifications to it mainly so that it triggers sounds when switches/knobs were activated in the pit. Again, you are free to try out Boxin’s fix but I make no guarantees.
-
Tks Ice. yes, I use a TM Warthog as well. So that’s why I’m using Morphine’s script. S0 I’m using your helios profile with a TM WH and Morphine’s Target script in the Target Script editor, which I understand must be run BEFORE I start BMS. 2nd question: I mean when you add an interface in Helios. There is a choice of Falcon/BMS 4.32, OF, FF…BUT NO 4.33.o I have to select 4.32 as the interface. I hope that is OK? (No other choice really…)
Re Boxin’s updated keyfile…do you think it might be okay to use with your Helios profile? Add it in the Helios interface screen so your Helios profile uses Boxin’s updated keyfile? Might work? (Yes, I will try it but you can’t see any immediate showstoppers?)
Thanks Ice for responding and creating your profile.
apoll
-
Yeah, you run the script BEFORE starting BMS so that when BMS runs, it will see “one” controller. If you do not run the script, it will see two (throttle and stick).
As for Helios, yes, just select 4.32. AFAIK, that’s just a “name” for the program and doesn’t really do anything aside from telling Helios what commands to expect.
As for Boxin, I’ve not really looked at it so I can’t comment. Should NOT be much of an issue since Helios uses the callback itself and not the key combination. However, the callback MUST be mapped to a key combination! For instance, you could have “Landing Gear Toggle” (AFGearToggle) mapped to “G” key, and you also have “Landing Gear Up” (AFGearUp) and “Landing Gear Down” (AFGearDown). Helios will not care what keys AFGearUp and AFGearDown are mapped to, as long as they are mapped to a key or key combination. If they are blank or not mapped to anything, it will not work with Helios.