RS Mapper Release
-
Fellow pilots.
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, BMS 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 deal with all your devices as you please. Major functions include- key mapping on button single press - RS Mapper will trigger single keyboard stroke when you press the device button.
- key mapping on button long press - RS Mapper will trigger single keyboard stroke when you press the device button for more than 1 second.
- Repeated single press - RS Mapper will trigger X keyboard strokes when you press the device button
- Continous press - RS mapper will mimic long keyboard press as long as you have the device button pressed
- 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 for 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 usefull for people with simpler joystics 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.
The software is free and tested, no known bugs exist as of version 0.42. Full details can be found in readme.txt file.
Get it here:https://drive.google.com/drive/folders/1mQtbeRHVqS872fEXugrOrEDK7ZbpPCAV
Enjoy - and leave feedback.
(this is a duplicate post, this time posted in correct forum. Admins, can you please delete thread from software corner?)
-
Thanks m8, will give it a try.
-
Fellow pilots.
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, BMS 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 deal with all your devices as you please. Major functions include- key mapping on button single press - RS Mapper will trigger single keyboard stroke when you press the device button.
- key mapping on button long press - RS Mapper will trigger single keyboard stroke when you press the device button for more than 1 second.
- Repeated single press - RS Mapper will trigger X keyboard strokes when you press the device button
- Continous press - RS mapper will mimic long keyboard press as long as you have the device button pressed
- 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 for 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 usefull for people with simpler joystics 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.
The software is free and tested, no known bugs exist as of version 0.42. Full details can be found in readme.txt file.
Get it here:https://drive.google.com/drive/folders/1mQtbeRHVqS872fEXugrOrEDK7ZbpPCAV
Enjoy - and leave feedback.
(this is a duplicate post, this time posted in correct forum. Admins, can you please delete thread from software corner?)
Hi
Please you would have a guide how to configure, with joysticlk and your program ??
I have a X52 PRO joystick, I disabled the steering wheel twist joystick through 64-bit Windows 7 registry key commands (VID_06A3 and PID_0762), I enabled in the BMS X and Y mini-stick configuration,Thank you,
malpaso -
Hi
Please you would have a guide how to configure, with joysticlk and your program ??
I have a X52 PRO joystick, I disabled the steering wheel twist joystick through 64-bit Windows 7 registry key commands (VID_06A3 and PID_0762), I enabled in the BMS X and Y mini-stick configuration,Thank you,
malpasoIt should be pretty straightforward - launch the application, go to Edit-> Select Devices. There you select any devices you want to map keys for. Later on the GUI you will see states for all buttons / povs present; just click button (green button or arrow) you want and choose correct key / action combination. That’s it. As soon as you confirm trigger action dialog it becomes active and your device will start sending key stroke on button press.
-
It should be pretty straightforward - launch the application, go to Edit-> Select Devices. There you select any devices you want to map keys for. Later on the GUI you will see states for all buttons / povs present; just click button (green button or arrow) you want and choose correct key / action combination. That’s it. As soon as you confirm trigger action dialog it becomes active and your device will start sending key stroke on button press.
What would these dialog boxes be?
SP, LP and RL, should I mark any ??
Sorry for my inquiries !!!
I have rudder CH products -
if you mouse over them you will see popup with explanations. Checkboxes only mean that there is something mapped, when you click the green button you will go into proper action select dialog. As for checkboxes they mean criteria on which there is some action mapped: SP - single press LP - long press (over 1s), RL - on button release.
-
if you mouse over them you will see popup with explanations. Checkboxes only mean that there is something mapped, when you click the green button you will go into proper action select dialog. As for checkboxes they mean criteria on which there is some action mapped: SP - single press LP - long press (over 1s), RL - on button release.
Avatar, do you have a YouTube channel?
If you have, post video tutorial on how to configure your program with Joystick !!!
Best Regards,
malpaso -
If you make this output dx directinput from a virtual device, that might be interesting. Keyboard output isnt going to be very useful once you run out of keys and start playing with key modifiers.
Most of the features are already supported by BMS. You can do key release commands in BMS, you can do key down and key held commands. Although, the ability to switch stick profiles hands on could definitely come in handy for simpler sticks.
-
If you make this output dx directinput from a virtual device, that might be interesting. Keyboard output isnt going to be very useful once you run out of keys and start playing with key modifiers.
Most of the features are already supported by BMS. You can do key release commands in BMS, you can do key down and key held commands. Although, the ability to switch stick profiles hands on could definitely come in handy for simpler sticks.
Hi Blu3wolf,
I think you are mistaken. So far pure BMS GUI lets you to setup button (or keyboard key) press only. There is no option to fire action on button or key release. Take Warthog APU switch for example. If you move it up to start position, BMS will register it as joy button 20, and this you can assign to any cockpit function. When you move it down to off, BMS will NOT register any button press, and you cannot map action on off position. Also, BMS DOES NOT recognize input from Warthog Throttle POV AT ALL. So, I would be veeery careful saying “most of the features are already supported”. RS Mapper lets you decide whether you want to have an action (currently sending the keystroke, modified any way you like) on button press (APU start), release (off) or both (of course, different action - like master arm on / off). Aditionally, RS mapper lets you configure repeated actions, very useful in invoking radio commands (take: Q, Q, 1 for active threats call to AWACS). With RS Mapper you can call AWACS like that with one button only Also, most of the software (take TARGET for example) works with sending keyboard commands, as most sims are coded with different keyboard shortcuts mapped to specific actions of the plane.
In theory I can simulate virtual DX device, that is not a big problem. Problem is that when this device IS being simulated you would need extra mapping of virtual DX device into the BMS, so that correct action / virtual input is mapped to correct cockpit action, while keyboard strokes are already assigned by default.Avantar.
-
Hi Blu3wolf,
I think you are mistaken. So far pure BMS GUI lets you to setup button (or keyboard key) press only.Well, this is partly correct, and partly incorrect. The BMS GUI lets you setup keypress actions only. BMS supports key release actions, and has done since 4.32 U1. You just cant set them through the GUI.
Hence the third party launcher which lets you set them in a GUI, and the excel spreadsheet included with BMS for that purpose, the several manuals explaining how it works and the manual explaining how to use a text editor to do so manually, if none of the other options works for you.
There is no option to fire action on button or key release. Take Warthog APU switch for example. If you move it up to start position, BMS will register it as joy button 20, and this you can assign to any cockpit function. When you move it down to off, BMS will NOT register any button press, and you cannot map action on off position. Also, BMS DOES NOT recognize input from Warthog Throttle POV AT ALL. So, I would be veeery careful saying “most of the features are already supported”.
Well, the GUI doesnt. BMS follows pretty standard DI convention there in that it supports only one POV hat, and up to 32 DI buttons (counting the POV buttons, so for a stick which has POV on it, then up to 28 buttons).
So lets take that APU switch for example. If you move it up to the start position, BMS will register it as DI button 19, and you can assign any callback you like. When you move it down to off, you can create a new line in the keyfile for the keyrelease for DI button 19, and assign any callback you like to that line.
-
Well, this is partly correct, and partly incorrect. The BMS GUI lets you setup keypress actions only. BMS supports key release actions, and has done since 4.32 U1. You just cant set them through the GUI.
Hence the third party launcher which lets you set them in a GUI, and the excel spreadsheet included with BMS for that purpose, the several manuals explaining how it works and the manual explaining how to use a text editor to do so manually, if none of the other options works for you.
Well, the GUI doesnt. BMS follows pretty standard DI convention there in that it supports only one POV hat, and up to 32 DI buttons (counting the POV buttons, so for a stick which has POV on it, then up to 28 buttons).
So lets take that APU switch for example. If you move it up to the start position, BMS will register it as DI button 19, and you can assign any callback you like. When you move it down to off, you can create a new line in the keyfile for the keyrelease for DI button 19, and assign any callback you like to that line.
Agreed. Keyfiles do provide this functionality - for BMS. It requires manual edit of the text file/ excel spreadsheet, though. Also, RS Mapper was intended for any sim - (take DCS, Il Sturmovik, or civ sims) - and they do not support those functions even trough key files
-
If you make this output dx directinput from a virtual device, that might be interesting.
Agree.
For a proper use of key-files, DX buttons is definitively THE WAY to go to configure keystrokes in order avoid key conflicts. Keyboard key generation should be used as a strict minimum. Keeping a key pressed, even for a short period of time is a VERY bad thing, especially when it is automatic. Better pass via BMS key-file modifications (more painful we agree) to minimize possible issues.
This app would be MUCH more interesting/useful if it could assign DX buttons.
However, it is looking good at this time and seems to be user friendly … just badly needs the DX function.
-
Yeap. I was about to ask for the dx.
Στάλθηκε από το MI 5 μου χρησιμοποιώντας Tapatalk
-
OK guys, I think I start to understand the feature you are requesting.
- RS Mapper would create a number of simple virtual devices with buttons, detectable by BMS and other sims
- RS Mapper would allow mapping button press, long press or button release of a physical input device into single button press of a selected virtual device
Virtual device button input could then be mapped either directly in GUI or via key-files to any function desired.
I think this should be pretty doable, will look into this.
Avantar
-
, RS Mapper was intended for any sim - (take DCS, Il Sturmovik, or civ sims) - and they do not support those functions even trough key files
DCS supports key release. DCS GUI does not. It’s more painfull than editing BMS key file manually and also does not support one dx button to command 2 or more callbacks like BMS does, but they do.
Well, the GUI doesnt. BMS follows pretty standard DI convention there in that it supports only one POV hat, and up to 32 DI buttons (counting the POV buttons, so for a stick which has POV on it, then up to 28 buttons).
BMS supports up to 4 POV if it is on the primary(roll/pitch assigned) joystick. But never support any POV switches if its on non primary device. Primary device with 1 pov hat can assign 32DX + 8 Direction of 1 POV.
-
This post is deleted!