[SOLVED] Help > ViewSonic touchsceen issues with Helios and Wheelchock template
-
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.