Touchscreen stops working when Falcon BMS starts
-
I’ve just purchased a WIMAXIT portable touchscreen with an HDMI connection to use with my main DVI connected monitor. This means that the touchscreen gets detected as monitor 1 (due to the HDMI connection) and my main screen gets detected as monitor 2. This initially caused problems getting the touch to work but I finally got that sorted.
The problem I can’t solve is that as soon as a Falcon BMS flight is started on the main screen the touch is disabled on the touchscreen. Falcon BMS seems to grab both the mouse which becomes captive on the 3D screen and also the touch facility. Stopping a flight and returning from 3D and the touch returns to the touchscreen.
I’ve considered buying some different cables in order to swap the monitor ports which would then have my main display as monitor 1 and the touchscreen as monitor 2 but not sure if this would help.
Is there any way to stop Falcon BMS in 3D from grabbing the mouse and holding it captive i.e. not allowing the mouse to move off the 3D screen?
Any help with this would be appreciated.
PS. The operating system is widows 7.
-
Hello compass,
Yes it is necessary to activate the following line to allow the mouse to pass from one screen to another.set g_bEnableExclusiveMouseCapture 1 // Captures the mouse when in 3D so that you don’t click something on the desktop when running windowed mode
-
Hello compass,
Yes it is necessary to activate the following line to allow the mouse to pass from one screen to another.set g_bEnableExclusiveMouseCapture 1 // Captures the mouse when in 3D so that you don’t click something on the desktop when running windowed mode
Thanks for the reply.
g_bEnableExclusiveMouseCapture was already enabled but I wasn’t running in windowed mode which has fixed that problem. Is it always necessary to run in windowed mode when using a touchscreen?
Now the problem is that Helios accepts only a few screen taps before it disables the touchscreen requiring the USB cable to be removed and reinserted, particularly if you open the Data Cards Panel of -Ice’s Profile.
-
Yes you need to run BMS in windowed mode to run it with Helios.
For Helios support I highly recommed to join the Helios Discord
https://discord.gg/9fGKGgg
and to go for the new Helios 1.6 as well as the issue tracker at their github for any issues.
https://github.com/HeliosVirtualCockpit/Helios
Helios 1.4 which the Ice profile was build with is no longer supported by the Helios team and you shouldn’t run a 1.4 profile with 1.6. -
Thanks for the reply.
g_bEnableExclusiveMouseCapture was already enabled but I wasn’t running in windowed mode which has fixed that problem. Is it always necessary to run in windowed mode when using a touchscreen?
Now the problem is that Helios accepts only a few screen taps before it disables the touchscreen requiring the USB cable to be removed and reinserted, particularly if you open the Data Cards Panel of -Ice’s Profile.
As I’m using a WIMAXIT Screen as well. Are you running the USB Connection directly to the Motherboard or through a USB Hub. I found it more stable to have it connected directly to a USB 3 port on the motherboard. Haven’t had had any disconnects and I run it 24/7 foro at least 5 month now.
-
Glad I’m not the only one struggling with this setup. I’m trying to get a 24" ViewSonic touchscreen to work.
To piggyback off of Compass:
1. I’ve downloaded Helios 1.6 installer. If Ice’s profile won’t work, what’s the next best alternative profile(s) to use (I suck at building these things on my own)?
3. I’m confused on other posts about the MFD’s on external monitors. Is another application needed to get the left & right MFD’s to work using Helios? -
Yes you need to run BMS in windowed mode to run it with Helios.
Helios 1.4 which the Ice profile was build with is no longer supported by the Helios team and you shouldn’t run a 1.4 profile with 1.6.
Thanks for the links. I’ve been busy updating the Ice profile for Helios 1.6.xx and the editor appears to strip out obsolete code. Everything works now and I seem to have isolated the touchscreen issue to the data cards and maps, anything which requires a large data transfer. I will try removing those and retest when I find some time.
-
As I’m using a WIMAXIT Screen as well. Are you running the USB Connection directly to the Motherboard or through a USB Hub. I found it more stable to have it connected directly to a USB 3 port on the motherboard. Haven’t had had any disconnects and I run it 24/7 foro at least 5 month now.
It’s a USB 3 connection directly to the motherboard, I try and avoid hubs if possible.
-
helios 1.6 allows the extraction of MFDs as does MFDE.
No need for third-party software.
Wheelchock makes an F16 profile from captzeen’s profile, it is still in testing and requires a version of Helios which is not yet official.
I also made a profile, the link where I speak about it. -
I was able to find Wheelchocks profiles on GitHub. Looking forward to when the 1.0 profile is fully released.
-
I used 1.4 for DCS and 1.3 for BMS with ICE profile. The problem is, when you install 1.6 the other versions are not compatible with the 1.6 installation and versions 1.3 and 1.4 are deleted.
Sorry for my english.!!
ICe profile or Capt ZEnn V1.6 for BMS… AMAZING!!!:o
-
I’ve had some luck with Wheelchock’s 1.6 profile but I seem to be missing these two button images. Any ideas where I can get them?
DRAP_Nm.png
FOND_NOIR.pngI was also missing the TR Center button for the TrackerIR utility but I was able to just create a new button by copying and editing one already present.
-
Good evening,
Here are the missing images.https://www.dropbox.com/s/h1fyesv7guvdm3s/IMAGE%20EHSI.rar?dl=0
-
-
I know that Wheelchocks 1.6 profile is a work in progress but I noticed the buttons around the MFD don’t work on my end. I can push them on the touch screen but nothing happens (SWAP, etc.). I did select his version of the keyboard file. Just making sure I’m not missing something else setup wise on my end.
-
You’re welcome
Did you load their profile correctly in BMS?
sorry for my english, i’m french and i go through google translate.
-
helios 1.6 allows the extraction of MFDs as does MFDE.
No need for third-party software.
Wheelchock makes an F16 profile from captzeen’s profile, it is still in testing and requires a version of Helios which is not yet official.
I also made a profile, the link where I speak about it.Hi ertiyu,
I am interested in trying your profile, would you send it to me?
thank you. -
I have just installed Helios 1.6.3309.0 for trying ertiyu and wheelchock’s profiles.
The profiles get started on my touchscreen monitor,
however the cockpit extraction does not seem to work.
what is wrong here?
how do I set it up?
please advise. -
You’re welcome
Did you load their profile correctly in BMS?
sorry for my english, i’m french and i go through google translate.
Maybe that’s what I’m missing is loading the profile in BMS. I start the Helios profile and it loads fine on the touchscreen. I’m able to load BMS and fly without issues. The gauges and profile menu buttons all work but none of the cockpit buttons work (MFD, Comms, etc.). Is there something within BMS setup I need to do?
-
Maybe that’s what I’m missing is loading the profile in BMS. I start the Helios profile and it loads fine on the touchscreen. I’m able to load BMS and fly without issues. The gauges and profile menu buttons all work but none of the cockpit buttons work (MFD, Comms, etc.). Is there something within BMS setup I need to do?
If BMs is not recognizing inputs a) run BMS in windowed mode b)run Helios Control Center with administrative rights