DX shift but no FOV, has anyone seen this?
-
Good Day, All,
I was seeing the following sporadically pre U1, now it seems constant…
The Warthog button I have assigned DX Pinky Shift via the Alternate Launcher ( the throttle push button, to be exact) works perfectly well as the shift button, but now not at all as FOV. As a workaround, I set up another button as the non-shift Pinky, and it works perfectly as FOV.
In AL, it’s set to(on my setup) the DX15 and DX 15 shift settings like it’s always been
On a hunch I checked config, but it’s set to what it’s always been-set g_nHotasPinkyShiftMagnitude 256 // Enable DirectX Shifting and specify button offset
I’ve never seen this before, has anyone? -
256 is the default value. If it’s missing from cfg then it will be 256. It’s been a config variable for a long time. It’s not a new feature. Besides the magnitude won’t affect how the short-duration tap function works in any case.
The behavior of SimHotasPinkyShift depends on the duration of the tap. By default presses <200ms are expand function and >200ms are shift function. If your expand function isn’t working you might not be tapping the callback briefly enough. To change the time threshold, edit set g_nHotasShiftQuickPressTimeLimit 200 where 200 is the time in milliseconds the callback has to be held to do the shift function.
-
256 is the default value. If it’s missing from cfg then it will be 256. It’s been a config variable for a long time. It’s not a new feature. Besides the magnitude won’t affect how the short-duration tap function works in any case.
The behavior of SimHotasPinkyShift depends on the duration of the tap. By default presses <200ms are expand function and >200ms are shift function. If your expand function isn’t working you might not be tapping the callback briefly enough. To change the time threshold, edit set g_nHotasShiftQuickPressTimeLimit 200 where 200 is the time in milliseconds the callback has to be held to do the shift function.
Frederf, you da’man. That was exactly the problem. Thx