Avantar

That is one feature that is still in the works and will be still for some time. I am planning to have ability to map "ranges" of an axis and fire events based on entering or leaving the range. This is however as (or if not more) complicated as handling buttons and will be a major feature in the future. Avantar

you may also try and download latest version 0.47 :) If that one does not work I will need to collect some logs from your rig to find out what's going on.

Replied in a private message, but maybe for somebody else's use: 1. RS Mapper requires .NET Framework to be installed in the system. If you don't have it then the program will not run (but in most cases you should see at least some error). 2. RS Mapper could have been blocked by system as a "not safe downloaded program" - did Windows ask you to confirm you want to run it?

I will look into it, is this problem visible in all modules or a particular one only? Most likely it is related to the way certain in-cockpit delays work. As a temporary fix I'd suggest you create a sequence with longer press times (60-70 ms perhaps) and a 20-30 ms spacing and bind it to your device (instead of simple repeat action). Please let me know if that solved the problem. Avantar

For once, I would greatly recommend using aircraft countermesure program to dispense correct chaff number instead of external program triggerring 3 presses of dispense button. Having said that, yes - you can program this using the RS Mapper tool You can do it either by using 'repeat' feature in the action or by creating sequence and assigning it to the button of your choice. Regards, Avantar

I believe your best shot would be using sequences feature. There you can add specific interval you need for press / pause sequence to work. Due to some updates in DCS cockpits sometimes different press lengths are needed for DCS to register properly (seen this mostly in F/A-18 cockpit development - whenever they changed something some feature would not register regular key press). I am sure that if you play around the duration / spacing of the key presses in Sequence editor it will work just fine :)

Gosh, how could I miss it! thanks!

Hi guys, I am reading trough various F-16 manuals and certain training maneouvers or routines are generally described as "execute 4-5G turn" or similar - most of them are based on G loading for the aircraft. The thing is that all I can see in the cockpit is MAX G I attained, not the current one. Is there anything like that in the display options? Or is there any way to zero the max G displayed on the HUD?

(Sorry for longer response times, holiday season...) This should be achievable by Sequence functionality. Never tested it on Il-2 though so I am sure what to expects. If you set the sequence you can explicitly tell the program to "hold" the key for this and this amount of miliseconds, release for this and this duration and then press another key. It will probably take some tinkering to find just the right duration but it should work. Please let me know what you find!

Hi guys, I reset windows 10 yetsrday and since then DCS acts weird. In controls setting it detects ']' instead of '\'. I have only one keyboard layout in Windows and it detects the keys properly. Anybody knows how to fix it?

It was F/A-18 and.. yes, its there, it was my mistake. I was checking on a laptop with lower resolution and my list did not expand fully. My bad :) works fine :D

Actually the best way is to use Group AI OFF when triggered by missile in zone. This way group stops any kind of actions, stops emitting and acts as if shut down. This can be done on a toggle so when the missile is no longer in zone you can turn the AI back on.

Hi there, in the past there was a way to start an uncontrolled aircraft from the ramp by using perform command -> start command (triggered by "AI Task PUSH" Right now in Open Beta I cannot locate a "start" command. Is there another way to start an uncontrolled aircraft?

Ok, only now I have been made aware of how serious problem with vJoy is. Given that info I will focus on axis mapping in RS mapper. It will not duplicate vJoy functionality (for now I will not be making "virtual" devices) but basic axis recognition and event firing should be a good start. as for different master modes with single button the best way to achieve is to create couple of profiles and map the button to "chagne profile" - the same button. Only in profile 1 it will go to profile 2, on profile2 it will switch to profile 3 and on profile 3 it will switch back to profile 1. Very easily achievable.

Right Windows key support added (new version - 0.47)

Bump. Shaking after engine start is still there after latest F-14 update :(

Hey guys. Thanks for great feedback on the RS Mapper. Just to give you heads up where the software is going now I am posting prioritized list of functionalities I am currently (slowly :P) working on: - Remembering the app layout - Editable button names - Selected profile overlay window - Support for Saitek/Logitech flight panels (big one!) - Axis support for mapping (big one!) - Profile changes on keyboard key press (low priority) I cannot provide any ETA for these functionalities, but just letting you know I have them on my roadmap :)

I have just uploaded a new version of the RS Mapper tool (see the updated first post) With version 0.46 now you are able to: - use F/A-18 launch bar with keypress without problems (defect fixed) - Set sequence of keypresses to be used with single button - Use any key as modifier (including windows key) - trough sequence functionality, just set the start delay to the same value and both keys will be pressed at the same time. Gladman, jl88, Chic and Grajo - I think v0.46 should solve your problems :)

Hi Chris, yes - the RS Mapper allows to assign any number of functions to the same button - not just 3 but as many as you want. you just assign a profile change to other button and then in the new profile you assign different action to buttons. And again, again and again :)

OK, I can confirm that the issue can be resolved and is working fine if duration is set to 75ms for a keypress. It's already working in sequence functionality (still closed beta) but prior to release I intend to rework regular actios to this new method as well. Will work fine! :)

I've done some trials and what I observed is that indeed switch from Launch Bar Retracted to Extended will not fire if a "single press' event is triggered. If I manually click on the control and then use the button again it will go from extended to retracted. What I also noticed is that *sometimes* when I set single press to continuous, then it will drop the launch bar (managed couple of times but not always). My guess is that for some Hornet controls there is some delay built into the cockpit and RS Mapper simulated presses are too fast to register. I will try to test simulating these keypresses with different duration (via code ofc, not by holding the button) and then I should see if it can be resolved. Still, this will require considerable refactoring of the primary keypress functionality :(

I think it may be related to animation / effects that this command trigger. Can you try using "continuous" option for the taxi light and launch bar and let me know if this helped?

Sure, this is not something difficulty, it will take some time to find its way into the program, I will add it to my backlog

Thats exactly what is implemented and being tested as we speak :)

This is implemented in beta version of RS Mapper currently in tests (albeit a bit separate, not as modifier but serving the same function). I think I *can* add windows buttons as a called out modifiers but this will be in next release.