Horizons TM Warthog HOTAS TARGET driver loads -> keyboard types in reverse

I can't get rid of this weird behavior. I'm using the TM Warthog Virtual Device Driver to map most of my bindings in combination with VoiceAttack profiles. I launch my ED thru the TARGET launcher running the .CFG profile.

Everything works as it should, however, when I search for systems in the Galaxy Map, for example, my character string in the search fields appear in reverse order from right to left. System settings are set to the correct US-North American keyboard profile. This is only an issue with this particular game (when the TARGET software drivers are loaded).

Did anybody come across this? I can't find a solution anywhere at all.
 
Are you using version 3 (released very recently) of version 2 (released about 4 years ago) of the TARGET software?

I never met that problem using the older software.
 
I don't have this issue using both the warthog and voice attack. Are you attempting to use voice attack or target to send specific strings to the text field, otherwise I cannot see how this would happen? The cursor should be left justified making it impossible to manually type the entry in reverse. Even attempting to change the default language in the launcher there are no languages available that support right to left text entry.
 
Last edited:
Problem occurs with both versions. Currently using V3. TM support had nothing, basically wanted me to reproduce the problem "on a second PC." I don't have one... Using the latest released VA software (tired the latest Beta but had not solved the issue so I had downgraded back to release).
 
Did you use the GUI tool, or did you go full geek and write your own void main()? If it's the full script, maybe post your program and macro files someplace and I can load them on mine to see if I get the same behavior. If it's the simple GUI setup, then I don't know if those files can be transferred around or not.
 
It's the GUI version, started out with the published ED profile and made some changes on button mappings, but nothing involving keyboard or mouse virtual devices. Frankly, the complexity of the whole setup had caught me off guard; learning the scripting language was just a nonstarter for me primarily because of the time would have needed. It's great that they offer that for advanced users and developers, but I'm still baffled as to why it is left to the user community to essentially develop an at least 80% complete starting profile for the essential functions of such a popular game nearly two years after its release.

I have also tried mapping the buttons and controls using DirectX "direct-mode" calls bypassing the TARGET to avoid the mouse/keyboard issue but without initializing the virtual device drivers it just simply wasn't working at all for me. Now with the revised ED 2.1 control mapping UI, there may be some other options available, but I haven't had time to check yet. Frankly, I don't want to invest countless more hours into this since I'd rather enjoy the actual game instead.

The Saitek X52 Pro was nearly fully functional with the factory preset profile, but the Warthog hardware is at another level in terms of robustness and feel.
 
Back
Top Bottom