-Ice's Falcon BMS Helios Profile Updated… Again!
-
I have a question on your setup with respect to YAME64. My main monitor is screen 1 on my left and my second monitor with Helios is on the right and both monitors are 1920x1080. Helios is setup ok and is working.
In your setup for the right screen is -1920 for pos x. Why not 1921? Also, for example, the Left MFD is x=291. Why not 1920 + 291? I guess I don’t understand this method as it appears different then what we do in DCS.
I am running my 2 screens in windows in extended mode side by side. Should I be running in extended mode or 2 separate screens?
I just read a forum thread that recommended the gauges/Helios should go on the left of the main screen. This is the opposite of what I do in DCS, but I guess that I can just use the Windows display settings to change the main screen depending on whether I am using DCS or BMS.
UPDATE: I changed -1920 to 1921 and so far things seem to be working.
Next step, check that the charts are working, then figure out how to get the map in WPD integrated into the setup. Finally, I need to review ICE’s target profile and keyfile to understand the changes from Morphine. I notice that some users are having issues with the keyfile/target profile, so this is going to be a slight detour until this review is completed. I am not sure if ICE is working on a new keyfile/target profile and PDF or not. This is going to be a long process. -
There are several switches not working yet. I.e. FCR on/off, MDF on/off, CMDS Mode Semi, Ext Fuel Transfer Norm/Wing First, all buttons on the Threat Warning Prime. Furthermore I am having Problems with the rotary knobs. Mostly they turn to far (i.e. two or three positions instead of only one). Then I cannot find the compass nor the gear handle.
Sorry, what exactly do you mean by the FCR? The switch on the Sensor Power panel? That should be working. Same for MFD on the Avionics Power panel and everythign else you’ve mentioned. Note that the TWP buttons are “off” until the jet is started and you’ve turned the power on via the TWA Power button. The rotaries are activated by touching to the left/right or top/bottom of the rotary image. There is no compass on the profile but the gear handle should be, well, where it should be. Have you calibrated your touchscreen recently? Whe I was having issues like trying to flick a switch but it won’t activate, I spent two days trying to “fix” it but it wouldn’t work. Calibration solved the issue; the switch was working fine all along.
If you continue having issues after calibrating your touchscreen, if you could post a video of this problem, that would be great!
In your setup for the right screen is -1920 for pos x. Why not 1921? Also, for example, the Left MFD is x=291. Why not 1920 + 291? I guess I don’t understand this method as it appears different then what we do in DCS.
This is my screen setup. [2] is my main screen and the upper left of that is 0, 0. So the upper left of [1] is -1920, 0.
As for the MFD coordinates, they are in respect to the RIGHT SCREEN 0, 0. That way, whatever the coordinates of the screen used to display RIGHT SCREEN, the MFDs will still be located correctly.I am running my 2 screens in windows in extended mode side by side. Should I be running in extended mode or 2 separate screens?
Not sure what you’re asking here. However, I would recommend that the touchscreens be configured so that they are TO THE LEFT of the main screen, so that your main monitor used for BMS is on the RIGHT side.
I just read a forum thread that recommended the gauges/Helios should go on the left of the main screen. This is the opposite of what I do in DCS, but I guess that I can just use the Windows display settings to change the main screen depending on whether I am using DCS or BMS.
This is because when running BMS on fullscreen mode, it messes with the screen’s resolution and any screen to the RIGHT of this will be messed up as well. Although things should get back in alignment once you go to the 3D world and the main screen returns to it’s default resolution, some people do not like this, so they put their extra screens on the LEFT side.
UPDATE: I changed -1920 to 1921 and so far things seem to be working.
It should… But like I said, I’d recommend putting your extra screens on the LEFT side instead of the right side, no matter where they’re physically located IRL.
Next step, check that the charts are working, then figure out how to get the map in WPD integrated into the setup. Finally, I need to review ICE’s target profile and keyfile to understand the changes from Morphine. I notice that some users are having issues with the keyfile/target profile, so this is going to be a slight detour until this review is completed. I am not sure if ICE is working on a new keyfile/target profile and PDF or not. This is going to be a long process.
Chart fix – check out the 2nd post here.
TARGET and .key file – lots of changes from Morphine. Might as well just use mine. As Morphine’s work was the original base that I worked with back in 4.32.3 (or maybe even earlier!!), I continue to give him credit. Not using my .key file and .tmc file will obviously lead to interesting and unexpected results.I am working on a new .tmc file and learning how to make a PDF “map” of things, but I’m currently pre-occupied with other things… should be ready by mid-next week.
Also, there may be an issue with the pinky switch that’s supposed to control the master lights in ver6 of my .tmc file. Should be easy enough to fix, but I won’t bother for now as this is fixed in my new .tmc file.
Hope that helps!
-
I’d just want to give a public THANK YOU!! to the people who have decided they liked my work enough to click on the donate button. You guys know who you are and thanks for being awesome! So again, THANK YOU VERY MUCH for your kind gesture!
Next is a small PSA: I’ve spent the last few days moving my system over to the Win10 Creators Update version (clean install), only to be sorely disappointed. My War Thunder game doesn’t seem to want to run under CU, it just gets stuck on the “garage screen” without any of the other buttons and I have to ALT+F4 to get out of the game. While BMS runs fine under CU, my center touchscreen is acting weird… I can manipulate switches on the left touchscreen with no issues, but I cannot do anything on the center touchscreen at all. I can see feedback that the screen sees my touch input, but Helios does not respond. I can click on the relevant area with the mouse and Helios will respond, so the profile is working, but for some reason, it will not respond to touch input.
I can manipulate windows and double-click icons on the center touchscreen, so again, the screen DOES recognize my input and it DOES work, so I don’t understand why Helios refuses to work. I’ve even swapped the images around so that the front console is on the left screen (works perfectly!!) and the left aux console is on the center screen and now none of the left aux console switches respond to touch input.
I’m not sure how this affects single touchscreen setups, so upgrade at your own risk.
-
ICE
I know that you are busy with your Win10 update, but I just wanted to tell you that I figured out how to put the gauges on the left side. Physically, monitor 1 is on top and monitor 2 is at the bottom. 1 is the main and 2 has the gauges. In windows, 1 is on the left and 2 is on the right. I just found out that in windows display settings you can move 2 to the left of 1. So for DCS, I will have 1>2 and for BMS, I can change it to 2>1. Just one more thing on my checklist.
PS sorry to hear about your win10 woes. -
Physically, monitor 1 is on top and monitor 2 is at the bottom.
It does not matter where your monitors are PHYSICALLY. If you have [1] on the left and [2] on the right PHYSICALLY but you have [2] on the left and [1] on the right in Windows, I can see how that can be confusing. However, if you have a vertical setup PHYSICALLY, the it’s less confusing, but still does getting used to. Even now, I sometimes have to remind myself to GO LEFT to go to my touchscreens.
So for DCS, I will have 1>2 and for BMS, I can change it to 2>1. Just one more thing on my checklist.
You can set up DCS to have 2>1 and also have BMS to be 2>1 and that way, problem solved!
PS sorry to hear about your win10 woes.
Don’t be! In some weird way, I like this sort of thing. At least I can say with conviction that Win10CU is NOT for me. Initially, my plan for this setup was to have two PCs operating my screens but Helios put an end to that… then there was the plan to have two GPUs but again, testing put an end to that. I like testing and knowing WHY something is NOT a solution for me rather than keep wondering whether or not something would work or not.
I do lose some time to all the testing but in the end, I learn a lot of things. For example, I now have a streamlined clean install procedure for Win10 and I plan to bring my son’s PC back to Win10 later on, so all that time and effort is not a complete waste
-
There would be too many changes to the viewport calculations in DCS to do now while I am trying to get BMS into shape.
-
There would be too many changes to the viewport calculations in DCS to do now while I am trying to get BMS into shape.
Ah yes, the joys of DCS. Used to take me 2 days to reconfigure my setup after a patch, and that’s if they didn’t move settings to different .lua files.
-
ICE
I have your BMS profiles working to most extent. However, I have a few issues:While the parking brake switch moves in Helios and is recognized in the controller section of the game, the parking brake switch does not move in the cockpit and I have to mouse it up in the cockpit. Unless I do that, the jet will move.
Sometimes when I put the Main Power switch to Main, I lose the sound in the game and I am not sure if Helios stops working until I click around the screen then the sound comes back on. The last time I did a ramp start everything was fine so I am not sure if this is a problem with my computer or not.
I get a lot of beeps when pressing buttons and switches. Is that normal?
Otherwise, this is a fantastic system of profiles and I love YAME64. On my next flight, I intend to try to use the Central Pedestal map system.
-
“I get a lot of beeps when pressing buttons and switches. Is that normal?”
If you go to BMS set up screen - then Sounds then look at the bottom slider “Interface Sounds” you can move the slider to control the sound level of the “beeps and clicks” when activating buttons and switches … if you can hear them I would suggest that the slider is to the right hand side - bring it down to a comfortable level - warning other sounds in the 2D world are affected by this slider.
Hope this helps.
Ps - I like to hear the “Beeps and click” as it compensates for the lack of tactile movement on the switches and buttons ;0)
-
ICE
If I start a game when the jet is hot, I assume that the game switches and the Helios switches may not be in sych. Is the only way to handle this is to have a second Helios profile where some of the switches have their default position “on”? -
I thought that perhaps something was wrong with the keypress in Helios
Ps - I like to hear the “Beeps and click” as it compensates for the lack of tactile movement on the switches and buttons ;0)
-
What is the central pedestal map system?
-
While the parking brake switch moves in Helios and is recognized in the controller section of the game, the parking brake switch does not move in the cockpit and I have to mouse it up in the cockpit. Unless I do that, the jet will move.
Something wrong with your setup… move the parking brake in Helios and the cockpit switch should move as well. When you increase RPM past 80%, the in-game switch would go back down and so does the Helios switch and your jet will start rolling. Just tested it now and works as intended. Note that if you have your throttle up (past 50% travel) and engage the parking brake, the Helios one will respond but the in-pit one doesn’t. Throttle IDLE then engage the switch. I have seen the Helios and cockpit switch respond and engage the parking brake but my throttle had set just below 80% RPM so the brake was on but there was enough thrust that the jet continued rolling.
Sometimes when I put the Main Power switch to Main, I lose the sound in the game and I am not sure if Helios stops working until I click around the screen then the sound comes back on. The last time I did a ramp start everything was fine so I am not sure if this is a problem with my computer or not.
Should not be an issue. See if you can replicate.
I get a lot of beeps when pressing buttons and switches. Is that normal?
There is audible feedback as intended. That gives you audible confirmation of your input. If you tried an input and didn’t hear a sound, check to confirm that your input was recognized. This is the downside of having a touchscreen vs. an actual, physical switch or button where the “displacement” or movement of the switch/button gives a tactile feedback as well. Having said that, 99% of buttons/switches should just give ONE beep/click upon activation. Also make sure you turn off mouse input so that you’re not accidentally “clicking” with the mouse cursor as well as Helios.
Otherwise, this is a fantastic system of profiles and I love YAME64. On my next flight, I intend to try to use the Central Pedestal map system.
CPD is fine, map isn’t so awesome now due to low res. Once the next release of YAME comes out THAT is an awesome moving map display.
If I start a game when the jet is hot, I assume that the game switches and the Helios switches may not be in sych. Is the only way to handle this is to have a second Helios profile where some of the switches have their default position “on”?
You can, but it’s not really needed. The switches use switchstate callbacks and not toggle callbacks so once you activate a switch, you’ll get the correct response. For instance, you start in a jet in the air with Master Arm ON and the Helios profile has Master Arm OFF/SAFE. When you put the Helios switch in Master Arm SIM, the switch in-pit will sync correctly. Was there a switch or button that you were worried about not being in sync?
-
-
ICE
I got the CP map system working. This is neat and better than the dance you had to do to put the map on the kneepad.Scotters
The CP map is discussed on pages 32-35 of the YAME64 manual. Yame is part of the profiles that ICE prepared for the community and with the combination of WDP and Yame 64, together with ICE’s profiles, your Helios cockpit looks just like page 33 of the Yame manual. This is really cool. If you need further info on this, let me know. -
with the combination of WDP and Yame 64, together with ICE’s profiles, your Helios cockpit looks just like page 33 of the Yame manual. This is really cool.
Don’t understand, our manual at p33 just shows the moving map of YAME itself, nothing to do with WDP or Helios or -Ice’s profile?
-
ICE
If I start a game when the jet is hot, I assume that the game switches and the Helios switches may not be in sych. Is the only way to handle this is to have a second Helios profile where some of the switches have their default position “on”?correct - or do a ramp every time ;0)
-
Don’t understand, our manual at p33 just shows the moving map of YAME itself, nothing to do with WDP or Helios or -Ice’s profile?
Focaldesign
You are correct. YAME, target, WDP and Helios are all separate programs. However, ICE has spent hours putting together all 4 products into one coherent package for us flyers. If you are just looking for Yame, then there is a seperate forum thread just on Yame that you can direct questions to. Generally, here we discuss the integration of these programs. Yame can run the map without WDP. I can probalby still walk you through the use of Yame without the complete package so let me know. -
Focaldesign
You are correct. YAME, target, WDP and Helios are all separate programs. However, ICE has spent hours putting together all 4 products into one coherent package for us flyers. If you are just looking for Yame, then there is a seperate forum thread just on Yame that you can direct questions to. Generally, here we discuss the integration of these programs. Yame can run the map without WDP. I can probalby still walk you through the use of Yame without the complete package so let me know.I know mate, thanks. I’m one of the 3 guys making YAME
I was just clarifying for others as your description could be read dubious. WDP or Helios is not necessary to get the map like shown on the YAME manual p33, that’s all -
Don’t understand, our manual at p33 just shows the moving map of YAME itself, nothing to do with WDP or Helios or -Ice’s profile?
I’m not sure what he means by p.33…… those are just gauges. Does he mean p.3?
Focaldesign
You are correct. YAME, target, WDP and Helios are all separate programs. However, ICE has spent hours putting together all 4 products into one coherent package for us flyers. If you are just looking for Yame, then there is a seperate forum thread just on Yame that you can direct questions to. Generally, here we discuss the integration of these programs. Yame can run the map without WDP. I can probalby still walk you through the use of Yame without the complete package so let me know.Yeah, Focal… I spent hours and hours putting these programs into one coherent package… if you need any help, we can assist you with YAME use
Hehehehe… just kidding. sobe, Focal’s the guy who helps out making YAME and he’s the one writing the manual…