imacken

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.

Maybe because they didn't rate as highly as the Alphas, or maybe no one has tried VKB Ultimate. I owned the VKB MCG with GFIII non-ultimate, and it just didn't feel as good in the hand as the Alpha. Buttons/hats were much more difficult to reach and that wouldn't change with the Ultimate.

Where are you seeing that?

So, which lua will have these lighting binds in?

Thanks for that. So glad to hear that it’s not just me! So, why do you think this just affects lighting axes?

If it’s working ok for you then great, but varying brightness from 0-100% range is not the same as making specific selections on a dial. Normally, encoders, certainly on Virpil devices, have to be made virtual axes to make that kind of bind work. It’s because of the button on/off nature of encoders.

Encoders, by their nature, are not suited to that kind of bind. Either convert them to virtual axes or use them for dials where there are specific options, e.g. radio channels, radar options, etc.

Thank you again, but I don’t think you’re fully understanding what I’m saying. It’s not an issue with the mod, it’s an issue with lighting binds. I know it sounds weird, but there is something going on. Forget the Tomcat for a moment. See my previous post. There are only about 4 modules where this happens, e.g. Harrier, M2000, and they do not have added axis commands from the mod. Let me repeat, in these few modules, the LIGHTING axes only have this issue. If I bind a knob (on any device) in these modules to any lighting axis, then it starts at 50%. If I bind the same knob to a non-lighting axis, then the issue does not occur. I understand that it seems strange that this is only lighting axes, but the facts are there, and that’s why I posted here. The 50% user curve start is a great workaround, but is a pain to implement about 30 times over the affected modules. Why don’t you try it yourself on the Harrier, or the Mirage 2000 if you don’t want to try the injected Tomcat axes?

Thanks, but that’s not really the issue. As @lunaticfringesaid, if users curves are used starting at 50% incrementing up to 100% then the axes knobs work perfectly. The F-14 axis commands for lighting come from @Quagglesinvaluable injector mod, but that isn’t the issue either. This is only a problem with lighting axes in the F-14, A-10C, Harrier and Mirage 2000 and most of these lighting axes are not from the injector mod. All other modules’, e.g. Hornet, Viggen, Viper, Spitfire etc., lighting axes work perfectly normally.

Sorry about all the posts on this, but could someone please try this - bind an axis to a lighting control, e.g. ACM panel light, see if the control in-cockpit only starts working at 50%. Then, bind the same knob to a non-lighting bind, e.g. HUD brightness and see if it then OK?

Sorry, I have no idea what you mean. The hat in the top right is even bigger on the Prime!

Guys, the trim hat is normally the one on the top right of the stick.

Looking into this a bit more, it is only lighting binds that are affected. If I bind the same knob to a non-lighting bind, e.g. HUD brightness, then it works OK. If I go back to assigning it to a lighting axis, then we're back to the 50% thing. (BTW, your user curve thing works, but it's problematic if I change binds for the reasons above, i.e. if it wasn't lighting then I'd have to reverse the user curve option.) I should also say that it's not a device thing, I've tried various and the issue is the same on the F-14 and the 4 other affected. Others (as above) are OK.

Thanks for that. There is a fuller post here on this 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) where I note that changing to/from slider makes no difference. Only a problem with A-10C (I and II), Harrier, F-14 and Mirage 2000. Modules not affected: Hornet, Viper, Viggen, Bf109-K4, F-5E, P-51, Spitfire, Huey and T-51P. I'm sure this behaviour didn't happen until recently.

I noticed that all my lighting control axes on certain modules don't start turning the cockpit dials until 50% rotation on my controllers, i.e. 0-50% does nothing. Looks OK with full defection in Axis settings. I've also tried changing to/from slider, but no difference. Modules affected: A-10C (I and II), Harrier, F-14 and Mirage 2000. Modules not affected: Hornet, Viper, Viggen, Bf109-K4, F-5E, P-51, Spitfire, Huey and T-51P. I have tried different devices for the bindings, but always the same issue. Any ideas?

I have the same issue with 3 or 4 other modules, so I guess I'll raise this in the main Controllers bug section.

No, I’m using with a Virpil desk mount, but initially I had it on a desktop and it was fine. My current preferred stick is the Alpha, and there is a 4th 4-way hat as the analogue mini stick can be used as buttons if you want. DCS allows both buttons and axes on the mini stick, so it’s win-win!

Well, there are 2 good reasons. Firstly, price. The new CM3 base is approximately 400 Euros plus shipping and the WarBRD base is about 240 Euros. Secondly, the CM3 has to be mounted, whereas the WarBRD can be used on a desktop. (I am speaking as a WarBRD owner with the CM3 on order.)

Yep, couldn’t agree more. Replica grips are fine for the aircraft they are replicating, but usually not vert very useful if you fly many modules. Apart from its functionality, the Alpha just feels great in my hands. Very tactile with all buttons etc. easily reachable. As I said above, it is the best flight stick I have owned, and I have owned quite a few. But, it’s all down to personal taste.

I really don’t understand why people talk about the lights like this. Just turn them off in the software. Well above average I would say.

Had the non ultimate version. Didn’t like it. Didn’t feel good in my hands compared to the Alpha.