Mapping controls to the throttle HAT switch
-
Was really hoping for just a DX solution that I can input into my key file
thanks for your help, I’ll try this for now. What’s the advantage of using AHK instead of target?
TARGET gives you many more options but it is also more complicated.
All that the .exe file will do is convert a dx input to a keyboard output for a single button.
WH HOTAS doesn’t work through it and is independent. -
Not really understanding what you’re saying there but I also have very little experience with AHK but have heard of it a number of times. I have had experience with target obviously as I’ve been using my WH for many years now, so I guess I’m more comfortable with target. Might be time to check out AHK then and see what it offers. Cheers for the help!
-
I shall explain again…
TARGET is better suited for BMS for it gives many more options than using key files you edit.
But it is also cumbersome (at least for me) and when it operates it actually runs the HOTAS through it and thus the HOTAS is not connected to Windows but only to TARGET which changes its input.TARGET and Autohotkey do essentially the same regarding the key input…eg they change the HOTAS key input to a predefined keyboard key.
So…if you want the change a whole bunch of HOTAS keys you better work with TARGET…but if it’s only one or two than Autohotkey generates a much smaller executable in terms of system resources and complexity.
And Autohotkey doesn’t “cut” the HOTAS from windows but takes the HOTAS’ input to windows and changes that. -
Thanks for explaining!
If I was using still the WH stick and throttle, then I would simply use target, but I don’t see the need for it now with just the throttle. Is this not the case? As for options, we only really need the shifted layer and maybe the in/out layer, right? I don’t think many people use target for complex macros, at least not in BMS?
It was a pain using target and BMS and forgetting to start up target and run the script before starting BMS. I guess this won’t be an issue now with AHK. Interesting how AHK can recognize the HAT input but the sim does not.
-
Voice attack works well too. Works great in combination with a communication script!
-
I don’t forget to open anything…and I mean the whole chain of Discord/ TrackIR/ MFDE/executables and so on and the reason is I made one batch file that opens them all one after the other, including changing the desktop background, so all I have left is getting into the opened BMS that awaits me all shines and whistles.
So…one double click of the mouse and I’m all set.As for the reason why BMS doesn’t “see” the POV …it has to do with the fact that BMS uses DX and it’s un solvable if you use DX…unless you bypass it somehow (either through TARGET, Autohotkey or the likes).
-
I’ll be using some sort of voice command program anyway (voice attack better than others?) so can I use that program to configure the HAT switch?
How do you make one batch file? And why the need to change desktop background? Sorry for all the questions but you’re talking about new things!
-
Voice attack imho is the best, I use it in many other sims/games and usually people create profiles/modules for most of them using voice attack. And it understands my southern US accent better than others
If you choose VA, then why not use it to map your hat presses on the throttle to a keypress rather than using another 3rd party app? Seems logical to me and reduced the number of stuff that can go wrong.
-
How do you make one batch file? And why the need to change desktop background? Sorry for all the questions but you’re talking about new things!
1. Example attached…save in Notepad++ as BMS.bat
@echo off
rem change wallpapaer to Sim
cd /D C:\Users\Owner\AppData\Local\Microsoft\Windows\Themes
start Sim2.theme
timeout /T 1 /nobreak
rem Acivates TrackIR Software
cd /D C:\Program Files (x86)\NaturalPoint\TrackIR5
start /min TrackIR5.exe
timeout /T 1 /nobreak
rem Activate Discord
cd /D C:\Users\Owner\AppData\Local\Discord
start Update.exe -processStart Discord.exe
timeout /T 1 /nobreak
rem Activate MFDE
cd /D W:\Falcon Utilities\Falcon MFD Extractor
start MFDExtractor.exe
timeout /T 1 /nobreak
rem Activate VAC PTT
cd /D W:\Sim Utilities\Sim Prep
start Vac_PTT.exe
timeout /T 1 /nobreak
rem Activate BMS POV
cd /D W:\Sim Utilities\Sim Prep
start BMS_POV.exe
timeout /T 1 /nobreak
rem Starts VAC
cd /D W:\Sim Utilities\VAC System
start VACSystem.exe
timeout /T 1 /nobreak
rem Activate BMS 4.34
cd /D W:\Falcon\Falcon BMS 4.34
start Launcher.exe -window -acmi
timeout /T 1 /nobreak
exit2. I’ve got 3 screens with a lively desktop.
When I get into the pit the background of all changes to the cockpit colour which better suits extractions and the side monitor for flight time.
When I’m done I start another .bat file that closes everything and return everything back to normal. -
reduced the number of stuff that can go wrong.
Exactly the idea!
Polaris, that’s cool, I’ll have to try that!
-
This post is deleted! -
Voice attack imho is the best, I use it in many other sims/games and usually people create profiles/modules for most of them using voice attack. And it understands my southern US accent better than others
If you choose VA, then why not use it to map your hat presses on the throttle to a keypress rather than using another 3rd party app? Seems logical to me and reduced the number of stuff that can go wrong.
Finally got voice attack installed but can’t seem to map my hat presses properly. It looks like I can map a hat press for listen but need to map another hat press for stop listen. I want it to listen when the key is pressed (or hat is pressed) and automatically stop listen when key (hat) is released, but to do this looks very complex unlike in DWVAC.
-
This post is deleted! -
I was able to get this to work so that the Alternative Launcher responds to it, but it doesn’t work in game.
I do not understand what doesn’t work in game.
Did you follow each and every step mentioned in that post?
What are the commands you chose?I use it on a regular basis for zoom and radar elevation and it works like a charm.
-
I do not understand what doesn’t work in game.
Sorry, I deleted my post just before you responded. I didn’t realise the Alternative Launcher responds to the POV hat anyway (for whatever reason) regardless of if the script is working or not
I was able to get the script to run, and it sort of works:
#Persistent ; Keep this script running until it is explicitly exited SetTimer, WatchPOV, 5 return WatchPOV: GetKeyState, POV, 1JoyPOV if POV >= 28250 Send, ^{Home} if POV between 0 and 6750 ;up Send, ^{Home} if POV between 2250 and 15750 ;right Send, ^{PgDn} if POV between 10250 and 24750 ;down Send, ^{End} if POV between 20250 and 33750 ;left Send, ^{Delete} return
This is setup to work as my DMS (by using the default keys). UP works fine, but LEFT and DOWN seem to flicker on and off when I’m pushing hat, and right just doesn’t work at all
I also get this error message: >“C:\Program Files\AutoHotkey\AutoHotkey.exe” /ErrorStdOut “C:\Users\name\Desktop\Falcon.ahk”[edit] realised I was using the wrong syntax for commenting. All POV’s work now but they flicker.
This is a video of what it looks like when I either press the hat once or hold it down: https://streamable.com/lct5s -
Sorry, I deleted my post just before you responded. I didn’t realise the Alternative Launcher responds to the POV hat anyway (for whatever reason) regardless of if the script is working or not
I was able to get the script to run, and it sort of works:
#Persistent ; Keep this script running until it is explicitly exited SetTimer, WatchPOV, 5 return WatchPOV: GetKeyState, POV, 1JoyPOV if POV >= 28250 Send, ^{Home} if POV between 0 and 6750 ;up Send, ^{Home} if POV between 2250 and 15750 ;right Send, ^{PgDn} if POV between 10250 and 24750 ;down Send, ^{End} if POV between 20250 and 33750 ;left Send, ^{Delete} return
This is setup to work as my DMS (by using the default keys). UP works fine, but LEFT and DOWN seem to flicker on and off when I’m pushing hat, and right just doesn’t work at all
I also get this error message: >“C:\Program Files\AutoHotkey\AutoHotkey.exe” /ErrorStdOut “C:\Users\name\Desktop\Falcon.ahk”[edit] realised I was using the wrong syntax for commenting. All POV’s work now but they flicker.
This is a video of what it looks like when I either press the hat once or hold it down: https://streamable.com/lct5sTry inserting a delay for each command.
It looks ti me like each press sends too many key stroked.
I shall send you an example later if needed.