|
Post by Lombra on Aug 20, 2017 11:05:01 GMT
Hi,
This time I write as a developer. (sort of) I was able to modify a prototype C# feeder a friend made to suit my needs, and it works fine. There is, however, one odd thing going on.
It would seem that the first time I send any button input after launching any game (well, tried with two different games), that also causes momentary axis input. (for what I think might be the Rx axis) Subsequent button presses do not trigger this behavior. If I restart the game the same thing will happen again. I noticed when I tried to set up bindings in game, it would bind an axis instead. Next time I tried it would bind successfully.
I have the vJoy monitor running at the same time, and I don't notice anything peculiar there. All axes are enabled. X, Y and Z are constantly at 50% and the rest at 0.
I'm not touching any axes (maybe that's exactly the problem?), so I don't really know what's going on. https://gist.github.com/anonymous/5d3b767914bd536d07d742eef88e19dc
Edit: I have not experienced anything similar with my physical DInput devices in these games.
Tried to get logging working also, but no file would be generated even after setting the environment variables and rebooting. Edit2: Got that bit working on another PC.
|
|
|
Post by virtual on Aug 20, 2017 16:09:23 GMT
I think you can close this problem by setup all axis initial values = 50% (DirectInput (SlimDX) default axis value = 50%).
|
|
|
Post by Lombra on Aug 21, 2017 21:52:51 GMT
That seems to fix the problem, indeed. Thanks!
This is the intended solution for DirectInput?
|
|
|
Post by virtual on Aug 22, 2017 16:51:28 GMT
I using another method but it for my functions of DirectInput, not for game functions of DirectInput that can't be modify. Thus, it depend on game application. Example: If game using Absolute Axis mode (very high chance) and using the first axis value = 50% (very high chance) then first time occur axis change event with delta = (current value) - (first value). Thus, if yours current value on startup don't equal 50% then it causes axis "move" event. Furthermore if game using neutral axis position = 50% (very high chance) then any value that don't equal 50% (in anytime), causes axis "move" event. (Example: Rx responsible for camera look axis X; 0% = move camera to left, 50% = don't move, 100% = move camera to right). P.S.: Post of Similar problem: vjoystick.sourceforge.net/joomla256.02/index.php/forum/5-Discussion/1233-strange-analog-axis-behavior
|
|