imacken

Thanks for that. I think your link is missing to the file.

Ah, do you mean the one I posted here? If so, why isn't everyone using this? Sorry, I think I've missed something recently. I just tried it, and it still works OK for me. Well, on monitor anyway, haven't tried VR yet.

Do you guys use touch typing from memory for VR when using this mod?

Thanks, but I said that in the first post!

Why does the George interface show in bottom left for CPG and bottom right for pilot? The pilot position is annoying as the kneeboard default position sits on top and then the kneeboard has to be moved/resized. Is there a way to define the positions?

Why is it not possible to get the virtual keyboard back? I can’t see that this is useful in VR without it.

The keyboard?

Haven't used this mod for some time since the virtual keyboard went. Has anyone managed to get that keyboard back yet?

Unless I’m missing something obvious, the Batumi frequencies are incorrect on all Caucasus missions.

Eh, try the first post!

That's great. Thanks for that. Pity about the button toggle as I have a common bind on a button for it on other modules.

Thanks BN. Fly through the streets of Dubai looking to the side with and without ms/mc and you’ll see why I can’t live without it!

Yep, that’s why I asked him the question further up. He hasn’t replied though.

Yep, flying without it is horrible with all the stuttering and ghosting when looking to the side. Glad to see it’s happening on G2 and other headsets and not just my VP2. So, hopefully, BN can report this. I said that in my original post!

I’m not so sure. As I said above, the same issue with Warbirds was resolved by ED.

Thanks but please read my original post.

BN, do you have Motion Smoothing (or whatever the G2 equivalent is) switched on?

Hi, yes, the A-10C and A-10c II work the same. The bind you need is 'Left/Right Engine Throttle OFF'. Works the same as off/idle in others. Not sure why it has a different name.

If you’re looking to configure the detents on the CM3, you don’t need virtual any more with the new software. Here is a guide I have posted over in the Virpil forums - more than once! Virpil Throttle Detent Setup 1) Idle detent. a. The new versions of VPC software have a new way of defining the detents with buttons for off/idle. We will just concentrate on the idle detent, as DCS does not have buttons for activating the afterburners. b. To configure the idle detent, it is necessary to do several steps. c. Firstly, in the axis settings page, change the calibration to ‘Both Detents’. d. Place the stick in the off position – fully aft - and input the raw value in the ‘Axis begin’ box by double clicking. The value will be entered automatically. Also, enter ‘0’ in the ‘output %’ box, then e. Place the stick in the idle position (just past the 1st detent) and input the raw value into the ‘Detent #1’ by the same method above. Also input ‘0’ - yes, 0 again! - in the ‘output %’ field. I also recommend a ‘Deadzone %’ of 5 for Detent #1 to compensate for the handle movement when going past the physical detent. f. Do ‘Axis end’ and ‘Detent #2’ in the same way. (See below for ‘Detent #2 advice.) g. Then, you have to define the idle off virtual button. (This is also done in a new way to before.) Firstly, note the ‘Axis begin’ and ‘Detent #1’ raw values, 29423 and 29905 in my case. h. Do this for both axes (inputting the appropriate values for each!). i. Go to the Axis page in VPC software, and look at the ‘Axis to button’ section. j. Select your axis – 1 for rX and 2 for rY, in my case – and then under ‘Type’ select ‘hardware’. Then enter the ‘Range from’ and ‘Range to’ values so that your raw values between the off and 1st detent are included. For the above values, I would input 29400 and 29800 to allow for a margin of error. k. REMEMBER TO ‘SAVE VPC DEVICE’ for any of these changes to take effect! l. If you then go to the Button page in VPC Configurator, you can see what physical button the software has allocated your 2 new buttons to, and then give them logical buttons that you can then bind to for off/idle in DCS. (Each module has slightly different naming and binds for this, but it works well for all for me, but you do have to make the correct choices for the binding in DCS.) 2) Afterburner detent. a. The purpose of setting this a value in Detent #2 in VPC Configurator is twofold. Firstly, to correct the discrepancies in the throttle outputs when they are not bound together by the axis lock lever, and secondly, to coordinate the afterburner kick in spot in DCS. b. Looking at each one in turn, firstly, if an output value for the position at the second detent is not set, you will see that the 2 axes have different output values throughout the throw, but easy to see when both are at the 2nd detent. (In my case, the left is 67% and the right is 70%). This discrepancy can cause issues in-game with the imbalance. It is adjusted to the lower of the two when the axes are hardware linked, but still, this is a better solution. When you set a – same for both axes - value for the 2nd detent in VPC software that issue disappears. This is done by inputting the desired value into the ‘Detent#2 Input’ and ‘Output %’ boxes of the axis setting tab in VPC Configurator. (You put the stick at the 2nd detent and double click in the input box. The raw value at that point will automatically be filled in. Also, put in the required output %age in the appropriate box. In the above example, 67% would probably be the optimal value, but see next step.) c. Secondly, syncing with DCS for the afterburner kick-in point. In my experience, leaving this at default means that the axes are not sufficiently advanced in DCS to fire the afterburner at the original output level when just going past the 2nd detent. (In my case it is 67% with both axes linked.) So, in order to fix this, it is necessary to find what your output level is to match that required by DCS to fire the ABs. This is largely trial and error, and in my case it is 74%. This works well for Hornet, Viper, F-5E, Viggen, etc. The only one that still had a slight delay was the Mirage, but I was OK with that. When you get the correct value for the output level input to VPC Configurator, the afterburners kick in just past the 2nd detent, and it feels much better. d. Now, the other thing you have to do, is adjust the planes that don’t have afterburners, e.g. Harrier, A-10C, warbirds, etc., to allow to you have the full travel between detents, rather than having to go past the 2nd detent to get full throttle. You do this by adjusting the ‘Saturation X’ in Axis Tune for each module affected to the value you set above, in my case 74%. I hope you find it useful.

Yep, as I said above, it's the same as what happened with propellers in some Warbirds, particularly Spitfire, but the thing is, that issue was resolved by ED, so I see no reason why this shouldn't. Turn it off? No thanks, as the ghosting looking to the sides of fast moving jets with it off is too much to bear!

@BIGNEWYhas this one been missed? Thanks.

Thanks for all the replies. Looks like the weapon trigger 1st and 2nd detents are needed, but the 1st LRFC trigger is not.

There are at least 3 other threads on this already. Here is one

On another note, what is the difference between 1st and 2nd weapon trigger? Weapons seem to fire on the 1st for me. Can't remember using 2nd at all. Having said that, I'm just learning weapons!

Yep, thanks guys, that's what I thought. A quick press and release of the 2nd detent seems to do the same thing, so I'll just release the bind to the 1st.