Ice’s Falcon BMS Profile Updated for BMS 4.37
-
@zeek thanks… I was working on updating my Ice 4.35 to a 4.36 keyfile but I must have done somthing wrong as stuff is getting triggered that shouldn’t be. I’ll see if yours works any better.
-
Ok, have identical profiles for 4.35.3 and 4.36 (of course each points to the proper executable) . The 4.35.3 profile runs perfectly smooth with no hesitations or stutters. Same profile in 4.36 is a stuttery mess with all gauges and the MFD s and the OSB buttons even have a delayed reaction on the exported screens. Looking at the cockpit itself everything is smooth and external OSB response is instantaneous. Using RTT for MFD extraction all displays perfectly but no matter what I try the gauges are not smooth at all. I have tried with and without the updated C:\Bin files, same results. I can try building a new profile from scratch but it has to be something in 4.36 causing this, just have no idea what? Goint to toss it into the Tech issues area also, but no one else running Helios seeing this?
-
@Icer Are you using the 4.35-12 profile modified for 4.36 or are you using a previous version. All of the gauges in 4.35-12 are now Helios Controls and use shared memory directly so there shouldn’t be a delay.
-
@linknet said in Ice’s Falcon BMS Profile Updated for BMS 4.35 U3:
@Icer Are you using the 4.35-12 profile modified for 4.36 or are you using a previous version. All of the gauges in 4.35-12 are now Helios Controls and use shared memory directly so there shouldn’t be a delay.
@linknet the profile was taken from 4.35-12 but i’m going to make a new one and see what happens. Again, the same profile in BMS 4.35 works perfectly…
-
After pulling (what’s left of) my hair out I decided to drop a nuke and uninstall 4.36 completely and do a reinstall from scratch. No add-on theaters, nothing (though I did all my testing in OEM KTO anyway). Works perfectly now. Wish I could say what the issue was…
-
@Icer said in Ice’s Falcon BMS Profile Updated for BMS 4.35 U3:
@linknet said in Ice’s Falcon BMS Profile Updated for BMS 4.35 U3:
@Icer Are you using the 4.35-12 profile modified for 4.36 or are you using a previous version. All of the gauges in 4.35-12 are now Helios Controls and use shared memory directly so there shouldn’t be a delay.
@linknet the profile was taken from 4.35-12 but i’m going to make a new one and see what happens. Again, the same profile in BMS 4.35 works perfectly…
@Icer Are you saying the ‘BMS - Full.key’ works fine in Helios, we don’t need copy the content of ‘BMS - Ice’s Helios Profile.key’ into it?!
-
@CriticalMass said in Ice’s Falcon BMS Profile Updated for BMS 4.35 U3:
@Icer said in Ice’s Falcon BMS Profile Updated for BMS 4.35 U3:
@linknet said in Ice’s Falcon BMS Profile Updated for BMS 4.35 U3:
@Icer Are you using the 4.35-12 profile modified for 4.36 or are you using a previous version. All of the gauges in 4.35-12 are now Helios Controls and use shared memory directly so there shouldn’t be a delay.
@linknet the profile was taken from 4.35-12 but i’m going to make a new one and see what happens. Again, the same profile in BMS 4.35 works perfectly…
@Icer Are you saying the ‘BMS - Full.key’ works fine in Helios, we don’t need copy the content of ‘BMS - Ice’s Helios Profile.key’ into it?!
No, use the “Ice’s” keyfile for Helios unless you add the (necessary) missing bindings to the BMS-Full file…
-
I’m about to give this a try, can someone please confirm this works with 4.36? Thank you!
-
@Atlas said in Ice’s Falcon BMS Profile Updated for BMS 4.35 U3:
I’m about to give this a try, can someone please confirm this works with 4.36? Thank you!
Works fine for me, yes…
-
@Icer Thanks!
-
I seem to be having some issues with touch recognition. When testing, if I press the IFF button, the screen shows me that I’ve pressed the IFF button but on Helios, it is the LIST button that is pressed. When I press LIST, A-A gets pressed, when I press A-A, A-G gets pressed. However, pressing COM1 does not end up pressing COM2. Same thing for the horizontal MFD buttons, it seems like if I press to the left of the MFD, I trigger that MFD. But that is not the case for the vertical MFD buttons, pressing to the left of it will not press the button. Instead, it is pressing ABOVE that button!
I have calibrated my touchscreen zones a couple of times now and as mentioned, the feedback from the screen (small white + cursor and a white circle that briefly appears) shows that the touchscreen is registering input right where my finger is.
-
@Atlas Are both your monitors set to the same DPI “Windows Scaling % percentage?” If not that could be a cause
-
@Atlas also, be sure to disable 3d cockpit mouse interaction by pressing the “mouse” light in helios in the left eyebrow lights panel, below and to the left of master caution. When i forget to do that, helios touces also flip unintended switches in my bms 3d cockpit.
-
@Atlas Are you using a US QWERTY Keyboard?
-
@Todd1215 My main 4K monitor has 125% I think. My 2 touchscreens is 100%. My 2 touchscreens is arranged one on top of the other, both of which are on the left side of my main 4K monitor. This is a LG C1 OLED which I think sometimes displaces the image a few pixels to the left or right (can’t remember which side) as some sort of method to even out pixel wear, but still does not fully explain the vertical offset for vertical OSBSs but horizontal offset for horizontal OSBs.
I will try resetting scaling to 100% to all of them and see if that fixes it.
@ispolin no issues there, the behaviour shows itself even when just using Helios and BMS is not running.
@linknet UK QWERTY keyboard, but is that a factor?
-
@Atlas UK QWERTY is fine, that’s what I use.
-
@Atlas Helios is not able to determine which display is using which dpi so you have to set all monitors to the same dpi or else you’ll get odd key pressing occurring just like you are seeing.
-
@Todd1215 Changing scaling back to 100% fixed it, thanks! Weird how the touchscreen detects the touch input at the correct position but Helios does not. I had to “reset monitors” fix as well after I changed scaling. I guess I’ll just have to change back-and-forth whenever I fly.
There seems to be a small delay/lag between press and input though, is this normal? Same thing for display extraction, panning the radar cursor, the response seems to be delayed by maybe 0.5-1 second. Is this expected behaviour?
-
@Atlas One little caveat to Windows scaling and Helios, if you change the scaling logout and back in or reboot before opening the profile in Helios and performing a monitor reset. This will allow Helios to properly reset the window according to what it thinks is the screen size.
Regarding slow keypresses and slower than expected rendering, I would first look at your hardware. Helios typically doesn’t really take any CPU to run it once its in memory but ymmv depending on what hardware you are running. For the rendering there are a few Helios Falcon Interface settings that you could try. Texture refresh by default is 90 but you do have other values, 60 & 30. These settings are found on the Helios Falcon Interface in the Profile Editor.
-
@Todd1215 I presume if I scale everything to 100%, reset monitors in Helios, the return my main screen to 125%, Helios will not run as it will detect a change and will ask for a new monitor reset?
Slow keypresses - I am on a 5900X default clocks, 3080, 32GB RAM. My main screen is connected via HDMI but the touchscreen is connected via DP. Since the touchscreen can only do 60Hz, I think I’ve reset the Helios profile to run at 60. Should I change that to 90?