Today I'd like to share with you software that I hope at least some of you will find useful. While building my flying rig and talking to colleagues that fly with me I discovered sad truth: most of the simulators, DCS included, will not recognize all the potential behind advanced HOTAS setups (like Thrustmaster Warthog, for example). Even though Warthog exhibits plethora of switches, most sims will only detect one position of a switch and will NOT generate event for it's "normal" position. For this we require additional software. I know there are SOME apps like that out there, but they are either not developed / supported, detect devices either in finite number or random order, or are simply cumbersome in use. Hence, I wrote my (and I hope now: our) own software - RS Mapper - that enables you to deal with all your devices as you please. Major functions include
- Key mapping on release - RS mapper will trigger keyboard stroke when you release button. This function effectively gives you two events for single-throw switches found on most hotas setups or MJoy devices.
- Profiles: you can save all required mapping in one place. Furthermore, you can create multiple profiles (for instance: one per sim) and have it stored conveniently in single file. Profiles are also useful if you want to temporarily remap your device.
- Profile change on button press: you direct RS mapper to change key mappings after pressing (or while holding) the device button. This might be particularly useful for people with simpler joysticks as this doubles options available on single device. Also, you might want to have different setup for combat and different for landing ect. Possibilities are limitless.
Using this function you can program action sequence of arbitrary length, for instance: "flaps, wait 2 seconds, gear down, wait 50 ms, landing lights on" - and all that with a press of a single button It should also be useful in programming long ATC conversations (awacs, airfields and such).
0.52: Bug fix
- Loading saved RS Mapper file when one or more devices are disconnected is again possible.
- Correct version is displayed when minimizing to tray.
- Added option to choose to minimize to taskbar instead of system tray.
- Fixed a bug with deleting sequences with no actions assigned.
- RS Mapper now features option to change between profiles on button/POV press. This means you can create "pinky switch" behaviour that completely remaps your keystrokes as long you have a button (or mode switch) toggled.
yes, that's exactly what "change profile on button press" feature was designed for. Instead of keystroke, after button press you change entire profile so new key definitions from new profile are instantly assigned to the buttons.
1. As for TM Target I never used it, but I heard it is not user friendly and is difficult to use. I would assume they have similar functionality (although I am not sure if Target features profile-change-on-button-press function)
2. As for multiple position switches you are only partly right. DCS does support multiple position switches like autopilot or flaps on TM warthog throttle base. BUT most of the switches in that throttle base (or devices like MJoy) are single button only. Take APU button for example. It only registers in DCS on START position - as Joy Button 20. When you move it back to off DCS will not recognize this as a valid button entry and will do nothing - at least in some modules (checked in KA-50). RS Mapper explicitly allows you to map action at any button release, regardless of module or sim you are using.
Your software looks very interesting, especially now that I understand the profile-change-on-button-press function. This together with the long press would seem to give each button 4 different states. short regular press, long regular press, profile change then short and long again. Am I correct?
I am happy to tell you that I am not using HID intereface directly, so the limitation you mention is not in place. I am connecting to the devices using Direct Input libraries and I deal with throttle and joystick separately. RS Mapper detects up to 4 POVs per device (this is mandated trough DirectX / Direct Input standards) and so far I have been able to map both POVs - on Throttle and Joystick. Interesting enough, Comm switch on Warthog throttle although looking like POV is in fact a combination of 5 buttons.
I do have profiles for Falcon BMS and K-50 done at least partially. However, I did actually prefer to mix in-game buttons settings with RS mapper, so these profiles are not "complete" - only certain functions on "release" buttons are mapped. I will try to post them when I am back home and log into my flying rig.
unfortunately I have no experience with Xpadder, but description seems pretty similar. RS Mapper does not simulate mouse movements but honestly, that's rather trivial thing to code if it was ever needed. And yes, RS mapper is a freeware app, developed within some 2 or 3 weeks of "free time" in the evenings, not "started over 10 years ago" ;-)
Greetings. If a button is assigned to "Trigger on single press" and "Trigger on long press", a single press is activated first, then a long one. It would be nice to point out the delay in milliseconds to which a single press would trigger, and after which a long one would work. Ie with a long hold, a single press would not work.
Unfortunately if you have both events mapped then the program does not know if you want to invoke a single press or long press, until full 1 second of long press passes. Then the long press event is fired.
I could change the code so that if both events are mapped and the button is released before the full second timer expires the RS Mapper would fire the single press event. Seems OK - BUT: this would effectively mean that you fire single press event ON RELEASE rather and not on button press. Should not be a big difference but still gives a little bit of latency before the button press and action.
One thing i would request as a feature: Key-sequence, like if i flip a Switch for fence-in - it will switch off all lights, master-arm on, gun-arm on and so on. That would be very usefull, esp. with VR, when you dont need to use the mouse for all that buttons.
First, It seems that if you use both the short press and the long press for the same button that you cannot then use the continuous function for the short press but can use the repeat function for the short press even though you use the long press. Is that correct?
Second, the heading on the RSMapper dialog box for the file profile name does not seem to change when you change profiles and the only way you know which profile you are using is to use the drop down menu under profiles. Is that correct? If so, can you provide a method to ID the name of the profile you are working on without having to use the drop down menu?
I may have been wrong on the profile names appearing at the top of program. It seems that you have to open a profile for it to appear on top and merely going to the profile drop down does not do it. However, I am a little confused on the interplay of the open command and list under the profile drop down.
The Big Bag has moved! Go find the updated and even more wonderfuller Big Bag at .
Some less central content may not (yet) have been moved though, so if you're missing something make sure to look in both places before you despair.
My mission is to make your keyboard a lot more comfortable and powerful, even if you don't have an expensive programmable board. To this end, I use the Colemak layout with several ergonomic mods and additions that I and others have created over the years, on different OS platforms. These "tricks" are what this Big Bag is about.
Some just want Colemak for Windows and just want it to work now, without reading up first. I recommend that you browse the contents below to know more about your options! But if you're impatient and would rather come back later to learn about Tarmak or Extend or ergo mods or Colemak[eD] or whatnot, here you go:
Take me directly to EPKL with Colemak for Windows! There's No Place Like Home!
[1] Character/Key Mapping Layers
Getting the most out of each key with more shift states
[1.1] Colemak[eD] AltGr letter/symbol mappings
[1.2] Extend layers using Caps Lock as a modifier for navigation/editing/browsing/etc from the home position
[1.3] Several Dead key enhancements giving access to lots of glyphs (presently for Windows/EPKL only)
[3] Layout Variants
Layouts for learning, for different languages, for the disabled...
[3.1] Tarmak transitional Colemak layouts for learning Colemak in smaller steps if so desired
[3.2] For several locales, a 'Unified Symbols' layout with only a few necessary changes from standard Colemak[eD]
[3.3] Intuitive Cyrillic, Greek and Hebrew Colemak phonetic layouts to write other scripts (e.g., using a toggle switch key)
[3.4] Mirrored Colemak, allowing one-handed typing without extra learning
This is my own preferred AltGr mapping layers (modifier lv3-4 in Linux terminology) for the Colemak layout. I've tried to add much functionality while keeping it intuitive. In particular, I want to be able to write different scripts and tech/maths symbols. Since the start, there's been some minor tweaks based on my experience and forum feedback, but it's been stable for a long time now.
b37509886e