[SOLVED] Help > ViewSonic touchsceen issues with Helios and Wheelchock template
-
I thought I’d just surrender on this headache and start over with a new flare gun for help.
BMS 4.35
Windows 10 Home
(#3) Primary Monitor: LG 38GL950G Gsync (3840x1600 native - 120Hz)
(#4) Touchscreen: ViewSonic TD2430 (1920x1080 native – 60Hz)Helios version 1.6.3426.0004
Wheelchocks BMS-Viper-435-V.10BMS Config settings other than default:
set g_bExportRTTTextures 1
set g_bEnableExclusiveMouseCapture 0Issue 1: Receive the following warnings when the cockpit loads after clicking the commit/fly button.
Issue 2: All gauges and MFD panels work, the profile buttons themselves work (utility, maps, panels, etc.), however none of the cockpit buttons work. I can click/depress them, but nothing happens. For example, clicking on the MFD SWAP button does nothing – or – clicking on AA/AG does nothing. I did copy over the BMS-Full keyfile from the profile and loaded in in the BMS setup screen.
The only odd thing I have noticed is that the monitor numbers in Windows 10 are reversed. So, the 38” LG monitor is shown as Number 3 in Helios but is Number 4 in Windows. The ViewSonic touchscreen is Number 4 in Helios but Number 3 in Windows.
I’ve tried troubleshooting in different modes: fullscreen, windowed and borderless…same problem.
Otherwise, the sim works fine, and flying is great. All cockpit panels and buttons inside the game work but nothing happens with the touchscreen.Thanks to ertiyu for your help and suggestions!!!
-
The lua warnings are just warnings about either value translation from numbers to strings or other non-critical problems. I have since fixed those warnings and will push an update to GitHub when I finish fixing a few other things wrong with it.
As for the other issue with button presses. You issue is due to having different windows scaling applied to monitor #3 and #4. There is a bug in Helios that causes this problem. The work around at the moment is to set all monitors to the same scaling percentage. I had this same problem and discovered the issue so I am well aware of it.
Helios bug https://github.com/HeliosVirtualCockpit/Helios/issues/151
There’s a channel on CaptZeens discord server https://discord.gg/yYYsExTW channel # bms-f16-support for things related to Helios BMS issues.
-
Thanks Wheelchock for the feedback (excellent work by the way)!!!
I removed the custom scale factor and all four monitors are now at 100%:
Still having the same issue, pressing the cockpit buttons does nothing (using finger or mouse).
I will add that the large screen monitor is hooked up to a Nvidia RTX 2080-Super video card in a eGPU (connected via Thunderbolt 3 and Display port). The other three monitors are tapped into the gaming laptop’s 970M integrated video card. The touchscreen itself is connected via HMDI into the laptop and then has the USB3 cable for the touchscreen to work. The touchscreen does otherwise work in native Windows with this setup without any issues. I did try it with both monitors (3&4) hooked up to the same GPU (2080-Super) and still had the same issue with the buttons.
I feel like I’m missing something very small (and stupid) on my end. Also, I’ll mention that I’m using Nvidia driver 456.98 in case it matters.
-
Hello,
Test this profile which has button 1 of the icp.
It uses the “BMS - Full.key”
This is to see if it’s Helios or the profile that has a problem.
I tested the profile at wheelchock and no problem on my side.https://www.dropbox.com/s/hao6zoxvkbc61y2/TEST%20Helios.zip?dl=0
-
Thanks ertiyu! I tried and got the same results. The button depresses, but nothing happens in the cockpit. Did that help in troubleshooting?
-
Which key file are you using? You should use the one that came with the profile. Its called BMS-Viper-435-V1.0.key or something like that. I think the Helios archive extracted it to the Documents/Helios folder.
-
Which key file are you using? You should use the one that came with the profile. Its called BMS-Viper-435-V1.0.key or something like that. I think the Helios archive extracted it to the Documents/Helios folder.
Well that could certainly be the problem. The only keyfile I’ve used is the “BMS - Full.key” that I found in the profile. However, I can’t seem to locate the one you just mentioned.
-
If that is the default key file then NO the profile will not function properly. The BMS-Viper-435-V1.0.helios16 archive should have a key file that it wrote to the Document/Helios directory. If you don’t see it there you can open the Helios archive using Winzip or 7zip, its just a zip archive. within the archive you will see a structure like this:
BMS-Viper-435-V1.0 <–directory
-----Helios <–directory
|---- BMS-Viper-435-V1.0.key <–keyfileJust extract the key file and plop it within the BMS user config directory. Setup BMS and Helios to use the same key file.
NOTE: my HOTAS setup is in that key file. You will need to replace it with your own. It’s towards the bottom of the file.
Good luck!!
-
UPDATE: Found the key file but still not working!
I did pull the correct key file and then loaded it in the BMS setup screen and applied the change. Still having the same issue where the cockpit buttons don’t do anything.
“Setup BMS and Helios to use the same key file.”
Is there something else I’m supposed to do on the Helios side to match the same keyfile?
I’ve tried BMS in fullscreen and windowed modes but can’t seem to get BMS happy in borderless mode (it becomes unresponsive). Could that be part of the problem?
What modes are BMS and Helios supposed to be in to work?
-
In helios falcon interface you need to point to the key file that bms is using
Sent from my iPhone using Tapatalk
-
1. Are you running Helios as administrator
2. Have you checked that Helios is sending keystrokes with i.e a Texteditor or a keyboard checker as active window -
Ugh, I miss the old days when all of the instructions were included in the box tops.
-
Hello, try to do a test profile on your side.
I made a little video for you that explains how to do it from scratch. -
Hello, try to do a test profile on your side.
I made a little video for you that explains how to do it from scratch.Thanks ertiyu for doing that video as it helped a ton!!! I have it working now.
Lessons learned:
1. The first missing piece was lack of the correct keyfile (thanks Wheelchock for pointing me at right file AND the location)!!!
2. The second missing piece was lack of the Falcon Interface with the matching keyfile. The video above walked me right to it and everything seems to be working brilliantly!!!One thing that did throw me a little at first was I couldn’t select a “Falcon” Interface as in the video test.
However, I just opened the profile and was able to edit the file location with the interface included in Wheelchock’s profile. Not sure if that is normal or not…?
Tried a quick flight test in borderless and fullscreen. Both worked fine as far as I can tell. Any issues or things to note if one mode should be used vs the other?
Lastly, thanks again to everyone for the help and support. No way in hell I could have figured out this on my own but so glad the community can warmly support those who are struggling.
Cheers!!!
-
The falcon interface was already added to the profile so that is why it doesn’t show in the list of interfaces to add. If it had not been added to the profile the entire profile callback binding process would be completely borked.
-
Glad to hear that everything is working for you now.