imacken

Unless I'm misunderstanding what you mean, that is one of the main functions of the app. Select what Preset you want before you launch. I have one for VR and one for TrackIR.

Hallelujah! A result.

Thanks again. See attached. Harr1 shows the axis bind with knob near 0% turn, harr2 shows it at 100%, harr3 shows the axis tune and harr4 shows the workaround I have to use to make it work in 4 modules only. hor1 shows the same controller knob in the Hornet bound to a light panel item and it works perfectly from 0-100%. Let me say again, this is only light axes in 4 modules. In any of these 4, if I bind the same controller knob to a NON-lighting axis, all is good. In the Harrier example: Harrier>Console Lights Brt>mapped to (in this case it's) axis Y of my Total Controls MFBB, but it could be any axis on any of my devices. Same effect.

Sorry, I answered that in the other thread. It makes no difference if the control is set to slider or not.

I've just responded over on the other thread, best to keep it in one place, I guess. Best to keep it there as it affects 4 modules, not just F-14. Certain modules - A-10C (I and II), Harrier, F-14 and Mirage 2000 - lighting axes don't start until 50% rotation on knobs - Controller & Assignment Bugs - General - ED Forums (dcs.world)

Thanks Skate. However, it's not the controller that is the issue as ANY of my controller devices - see signature - exhibit the same issue and only for lighting axes in certain modules. As I said in the other thread, it is only F-14, Harrier, A-10C and M2000 lighting axes that exhibit this issue. All other modules lighting axes work fine with the same device knobs/axes. Let me expand a bit, 1) if I bind the A-10C lighting knobs AXES to any knob on any device, e.g. Virpil CM3 throttle, Total Controls MFBB, Virpil Control Panel2, etc., then the in-game knob does not start activating till 50% of device knob travel. 2) if I do the same binds as 1) to lighting knobs in ANY other module, e.g. Hornet, Viper, Spitfire etc., then this behaviour does not occur. Full 0-100% range works fine. 3) if I bind the same knobs in the affected modules in 1), to a non-lighting in-game AXIS knob in the same modules then the issue does not occur, full 0-100% synchronised travel on device and in-game knobs. Any further thoughts?

My other thread on this in the F-14 forum showed more discussion and others experiencing the same thing - although the dev responding didn't seem to 'get' the issue. Does this section get monitored by ED at all or should I post somewhere else?

As this thread is going nowhere and this affects the F-14, Harrier, A-10C and M2000, I guess I'll try again in DCS general bugs/issues.

Yep, from my testing, it seems to be OK when text is typed in from keypad or from PC keyboard, but it all goes weird when moving into any text coming from the sitrep or L/L.

Yep, it’s all over the place!

Strange. So, on a clear scratchpad, if you type 123 then hit backspace, nothing happens?

Ok, yep, there are some weird things going on with backspace. An example, type in 123. If you select it by double clicking and press backspace it gets deleted. If you select it by dragging the cursor over and then press backspace, it copies and pastes in the 123. Also, if you put the cursor inside any L/L coords and press backspace, then the character before the one you want to delete gets deleted. Weird things going on with spaces as well.

Hmm, works OK for me. What would be really nice is a show/hide button for the keypad/extensions. One like the check box for L/L.

This is great! Thanks a lot for your time. One little thing, why the change from 'E' to 'O' on the keypad?

I have no idea why you seem to be offended. Just trying to help while you wait on Chuck’s guide suggesting a good manual available atm.

While you're waiting, I assume you are using the excellent ED Apache manual.

Never even seen that right-click>add combo thing before. I just double click in the appropriate box.

Ah ok. Thanks for the clarification.

Why would he not want to support it? I'm sure a few pages back he was saying the opposite.

Stuart, the version of this mod I use does have an in-scratchpad keyboard.

Great for you blind typing, but not many people have that skill! I know it’s been discussed several times in this thread, but why can’t the virtual keyboard be incorporated in all the versions here? The one I use with virtual keyboard works a treat.

Looks good, however, and excuse me for being dumb here, I have a working version with a virtual keypad already, but this doesn't have it - unless I've missed something - so how do you work this in VR?

just in the interest of completeness, I thought I would link to our comments on the Virpil forum here in case they are useful to someone. Button to Virtual Axis Tutorial using Virpil equipment - VIRPIL Controls Hangar - VIRPIL Controls

Almost the exact same discussion going on here Customizing axis on CM3 throttle - VIRPIL Controls Hangar - VIRPIL Controls See the last few posts there, but basically, you bind a button for flaps up and a button for flaps down, and sometimes a button for half flaps, e.g. Hornet. Basically, 0-20%, 40-60% and 80-100% are the values I use. More complicated than that with A-10C though.

Exactly that if you can't afford the new CM3 base.