imacken

Sorry Don, we were talking there about mouse movement option, not the full screen discussion.

As an aside, the F5 issue is resolved by selecting non-linear joystick in the Specials options. Thanks Stuart!

Yes, that is really important. Doesn't work without setting the resolution to same as desktop. That caught me out for a long time!

Any time! Glad you got it sorted.

No, keep the detent. It’s not spyglass you’re seeing, that’s a vr thing. you see zoom in and out

Thanks. Yes, your calibration of that axis is bad. If you look at the CAL LOW value, that is the mid point, and your RAW value is very close to the CAL END one. It should be (approx) mid-way between BEG and END. Recalibrate in VPC software and you should now be OK.

Trouble is, that it's impossible to know what you are doing in that video. Post a screenshot of your axis tune setting in DCS, and also from VPC software. I suspect this could be a calibration error.

Yep, sorry, my first post was incorrect, I've edited it now. I was just using a gut feeling on that. When I actually measured it on JoyTester, it was about 85% in the aft direction. Well, it's only as important as any other similar discussion. Making the saturation/user curve adjustments does make a difference in response. There may be a good design reason why the controls are like this on 3 modules only, but at the moment, we don't know.

Thanks for that, but honestly, I know what you are saying, but that is not the issue here. This occurs with the lighting binds I've mentioned with any device and any axis. Binding non-lighting commands to the same axis is without issue. Or binding to lighting commands in the other modules I mentioned that are not affected. To test, simply bind AN AXIS to INST PANEL LIGHTS BRT in the Harrier. and without any adjustment, you should see the knob doesn't respond until 50% of travel on the controller. Then, try the same controller knob on a non-lighting bind, and you should see it working OK. Let me repeat, this is only happening in a few modules. Most are OK.

I get 50% in forward and 85-90% in aft movement. (BTW, it's the Virpil CM3 base I use not the WarBRD as you mentioned above.) Do you mean the aircraft might not be reacting to the elevator position we see from the external view?

Are we talking about the same thing here? This is the relationship between player stick movement and elevator movement when viewed in F2 external view.

Sure, the only point of this discussion is to get a way of making the player stick movement match elevator movement in a few modules, as with using the default settings, it doesn't. Different solutions for different people, I guess. Always the way!

Sorry, I am saying that you get more sensitivity with reducing the saturation value. Reducing the Y say value gives you full stick authority over the elevators. At the default, you are only using half (approx) of the stick deflection to get full deflection on the elevators. For me, the A-10C is perfect at defaults, as are all modules except the 3 I mentioned. BTW, after discussions with @speed-of-heat, I'm now using user curves for the Hornet to emulate the lowering of saturation, but working in a better way for me and Stuart.

@SkateZillabeen a few weeks now. Have you had a chance to look at this issue?

Well, I mean you could mess around with the user curves. Maybe start at 50% rather than 0% as a slider, but really, why don't you just not pull back from the detent if that's your issue.

Yep, roll can be adjusted as well in the 3 modules mentioned.

We’re talking about VR here. There is no axis bind, hence the discussion on spyglass and normal, the only options available in VR as 2 button binds. Yes, of course, for monitor DCS the axis would be bound to zoom.

I think you may be missing the point. By changing the saturation, you get more stick movement for the same elevator movement, hence adding sensitivity by nature of the longer throw. Btw, I do have an extension on my stick.

Sorry, not sure what you mean. If you don’t want the spyglass view, then don’t bind anything to it.

You can bind it whatever way you want!

I am more confused now. I run DCS in full screen mode (with the 'full screen' ticked in DCS options), which I can tell is working as doing an alt+tab minimises the window. If it was in windowed mode, it would still be in the background, which is exactly what happens if the 'full screen' option in DCS is not ticked. So, I can get windowed or full screen mode in DCS, just not using alt+enter. What is the issue I am missing here?

Not sure that is its function, but never mind, what is the issue with DCS and alt + enter?

It also requires Vive Console which you can download on Steam or on the Vive web site. VP2 is NOT a Windows mixed reality headset!

Sorry, but what is the 'alt + enter' issue and why is it causing 'big pains'?

WMRP? Windows Mixed Reality Portal? If so, why are you installing that for the VP2?