-Ice's Falcon BMS Helios Profile Updated… Again!
-
ICE
Do you have thoughts on this issue?Monitor ID # issue in Helios
This is not a question as to which monitor is my primary or which way they are located. This is a separate question as to monitor ID numbers that the operating system seems to allocate by itself.Before I changed video cards and connector cables, my top monitor was #1 and my bottom touch screen monitor was #2. Now that I am using different cables and connectors, the numbering order is reversed. The top is #2 and the bottom touch screen is #1. In most cases this is no big deal. However, when using Helios, it can become an issue when resetting monitors. For example, in Loz’s profile, when I reset the monitors, the cutouts for the view ports default to my #2 top monitor and not my #1 bottom touch screen monitor. I cannot figure out how to move the view port cutouts to my #1 bottom touch screen monitor.
I have searched the web and trying to change monitor ID numbers is much discussed but is no easy task. The only method that seems to work is deleting the monitor registry entries, and connecting one monitor at a time. Something I am very reluctant to do. Does anyone have any thoughts on moving the cutouts or changing the ID numbers?
-
Not sure what you’re asking me here. I do notice that monitor numbers are not consistent. Sometimes, my main Surround screen is [1], sometimes it’s [2]. Seems to change after going from Surround to Extended… but then again I’ve been fiddling with my PC so not sure if that’s a factor as well. I do plug my monitors in the same port each time, but the numbers still change.
Having said that, I’ve not had the need to reset monitors even with the numbers change. So long as my monitor arrangement is the same and my Surround screen is set to the correct resolution (5896x1080 bezel-corrected), I never have to “Reset Monitors.” I would expect that if you had three screens with the same resolution and numbered [3][2][1] and after some changes it went to [2][1][3], Helios will still work as it goes by monitor layout and resolution rather than monitor numbers… at least I think it does.
-
This is not a BMS issue but a DCS issue. When I go to reset the monitors in Helios for the A10c profile by Loz, the top monitor (monitor #2) ends up with just the cutouts for the viewports and the bottom #1 monitor which is my touch screen monitor has all the Helios gauges, buttons, etc. I cannot figure out how to move the cutouts from #2 to #1. There is no layer and when I go to properties, the only thing there is the name of the template FPBackground.png. If I could figure out how to move that png, then I would be ok, but the Loz profile is very confusing and when I just try to find FPBackground.png, things get mixed up.
-
Sorry bud, but can’t comment on DCS and Loz’s profile. I’ve not touched either in YEARS and anything I say will be purely speculation.
This is one thing I will say though –- Helios should not have the ability to discriminate between DCS and BMS. Therefore, it’s behavior should be the same regardless of whether you’re running DCS or BMS. Any “irregularities” you may find may well be due to the sim you’re running and not really Helios per se. The only “interaction” Helios has with the sim-of-choice is knowing what keyboard commands to send to the sim and how to recieve switch-state data…
-
This is what is see:
-
Ah, that’s easy. Zip up your profile and send me a link.
-
ICE
Per your request, I have attached 2 zip files. First some notes.My monitor 2 is my top monitor and is used for the HUD. Monitor 1 is my bottom monitor and is the touchscreen monitor for the Helios profile. Even though windows shows the monitors side by side, they are really one on top of the other.
Second, the monitor numbers are those assigned by windows and cannot be changed except perhaps by playing with the registry which I am still reluctant to do.
File A works in game despite the fact that when you go to the reset monitors commands, it looks wrong. I DID NOT HIT THE RESET BUTTON. SO HELIOS SEEMED TO FIGURE OUT WHAT TO DO BY ITSELF. File B is the same as File A except that I tried to reset the monitors and THE RESULT IS THAT monitor 2 now just shows the cut outs.
Good luck and please tell me what you ended up doing.
Thanks for the help.
-
You forgot to send me the image files, but no matter. Give this a try and tell me if it works.
-
Yes. It seems to work fine on my first flight. However, I am a little confused. I went to the reset monitor and the Helios cockpit did not show on the right side, only the left side. 1>1 and 2>2. I did not want to hit any buttons in the reset panel and it seems to work. There was no monitor with just the cutout view. Could you please tell me what you did so that perhaps I can understand what had to be done? Thanks
I tried to send the images but the file was to big. I will need to send it to your direct email address if you still need it You can also get it here http://www.gadrocsworkshop.com/downloads?field_dltags_tid=&sort_by=changed&sort_order=DESC&page=2
Loz SM v2.1
By Cap Loz On April 4, 2012 -
If it’s working fine for you now, then no need for me to download the images. The less clutter, the better
Basically, all I did was to copy the “background image” which is the cutouts from one monitor onto the other. I just moved FPBackground.png… sometimes when you RESET MONITORS, Helios doesn’t move the background image from one monitor to the next.
-
ICE! First off you kick ass as always sir! I’ve got everything lined up and for the most part working but the OSB’s on MFD’s are not functioning. Everything else is. Any idea where I should look to correct this? It’s not the touch panel as only the OSB’s aren’t functioning.
Thanks!
-
Hmmm… that is weird. Can you confirm everything is working in the sim? ICP buttons, Master Arm, etc? Does the sim cockpit respond as it should? How exactly are you testing the OSBs? Make sure you’re using my .key file and that you’ve pointed out your Falcon install directory in Helios.
The OSBs are the easiest and one of the first things I’ve set up on the profile and have not had to touch them again ever since, so you having an issue with them is a new thing to me.
-
ICE - sorry a bit behind the curve on your new profile - does the back up radio now work in you updated 2 screen profile?
-
Do you mean the UHF panel on the left console? Yes. So does the backup TACAN panel. This is implemented in both 1-screen and 2-screen profiles.
-
cheers
-
-
Hi !
I just bought a touch screen monitor to look mfd and instruments while on another monitor (not touch scrren) I see the simulator.
Very often I lost my focus when I press some button (for example OSB MFD to change or select range weapon ecc…).
I have to be ready to click on the simulator screen to regain focus.Do you know if there is any trick to avoid it ?
Thanks for your work !
-
LOL, I didn’t mean just re-post your question on this thread…
First of all, there is no “trick”… what you are experiencing SHOULD NOT HAPPEN. The fact that it is happening to you means you are doing something wrong.
You need to post more info regarding your setup, hardware, software, profile, circumstances when the error occurs, etc. More info needed to give your proper help.
-
ICE
I just leaned an interesting fact. In windows, the HDMI port will take priority as to the ID numbers of the monitors. These ID numbers are different than the windows numbers that you can manipulate in the Windows display. You cannot change the windows ID numbers like you can change the windows numbers in the windows display.
So the end result was that my new video card has only one HDMI port and several display ports and one DVI port. When I hooked up my touch screen to the HDMI port, it kept registering as ID#1 so when I ran Helios, my regular monitor was ID#2 and Helios was sent to ID#1, which screwed things up in the Helios profile.
With only one HDMI port, I found the solution to be to use a DVI to display port converter cable for my touch screen and a regular DVI cable for my regular monitor. So by bypassing the HDMI port, my regular monitor is now ID#1 and my touch screen monitor is now ID#2, the exact way Helios likes it. DVI = ID#1 and Display port = ID#2. This only took 2 weeks to figure out. Tell the guy that found his love after 40 years (I have been married since 1965) that there is no gain without some pain.
On a separate issue, the creator edition has screwed up Target. For some reason, Target keeps losing my TM rudder connection so I have to keep the rudder out of any Target profile. Sometimes, even my WH is dropped from target. While TM knows of the issue, so far they have not published a solution. Other than that, my touch screen works ok in Win10 creator ed. -
I’m just starting with Helios working on my first profile.
I would like to create a “background” image just like in Ice’s profile.
To do this I would like to use the same font that is used in the cockpit respectively in the Helios profile.
I tried to figure it out from Ice’s profile but I could not find any texts that were created by the Helios label function (where the font would be indicated).
Could you please help me?