Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[tgraupmann]

I have a controller with a slider that's being detected as an axis.

How is OIS::JoyStick::mSliders being populated, if nothing sets it in _enumerate()?

Code: [Select]

void Win32JoyStick::_enumerate()
{
//We can check force feedback here too
DIDEVCAPS  DIJoyCaps;
DIJoyCaps.dwSize = sizeof(DIDEVCAPS);
mJoyStick->GetCapabilities(&DIJoyCaps);

mPOVs = (short)DIJoyCaps.dwPOVs;

mState.mButtons.resize(DIJoyCaps.dwButtons);
mState.mAxes.resize(DIJoyCaps.dwAxes);

//Reset the axis mapping enumeration value
_AxisNumber = 0;

//Enumerate Force Feedback (if any)
mJoyStick->EnumEffects(DIEnumEffectsCallback, this, DIEFT_ALL);

//Enumerate and set axis constraints (and check FF Axes)
mJoyStick->EnumObjects(DIEnumDeviceObjectsCallback, this, DIDFT_AXIS);
}

[tgraupmann]

Still awaiting an answer... I'm not sure how the sliders can be getting set because I didn't see the win32 code that does it.

[pjcast]

In order to solve this, you need to be more specific.

When you say it is detected as an axis, do you mean you see an extra axis? Do you get call backs with axis values? ie axisMoved? Or do you simply see an extra axis and no data coming from it? Whether or not the slider was detected as an axis, it should still fire the slidermoved callback not the axisMoved callback.

The Sliders are a static array, so enumeration would not cause any problems of reading them. Though, I did notice (I don't have any sliders) that the mSliders variable that kept track of the number of sliders was never set to any value. Probably because the enumeration doesn't seem to have any values for slider count. However, I think slider count maybe combined with axis count. So, I have a small tweak that may fix this specific count enumeration. I'll commit to CVS v1_2 since I don't think it will impact anything and may improve - at least it won't try to adjust any settings when an enumerated axis is a slider axis. Can you test again in a few.

[pjcast]

Change is committed.

I must also say, for some reason DirectInput is really enumerating my joystick oddly. But, it might be because I use a modified XBox controller & unofficial drivers. For some reason, it enumerates 6 Axes, when all I have is two, and 20 buttons, when all there is is 12. And, it marks one of the axes (now) as a slider.. But, there is no slider on this device. I think my problem is simply the XBCD driver probably allocates all these devices but only puts values in them when you alter the layout via the control panel.

[tgraupmann]

Awesome, I'll give 1.2 a shot. When I said my slider was enumerated as an axis. I meant the axis is functional and returns values as if it was an axis.

Code: [Select]

cvs up -r v1_2

[tgraupmann]

Ok interesting.

My slider is being enumerated and is returning values.

However, I had expected a slider to be a single axis. At least the slider on my joysticks are a single axis. Yet, slider has absX and absY. I had assumed each would be enumerated as absX is slider 0 and absY is slider 1.

But anyway, this would be an easy fix. I'll just wrap the input to change this how I expected.

Also why doesn't SLIDER have a MIN_SLIDER and MAX_SLIDER const property. It looks like values are coming in at the 65535 range.

[tgraupmann]

How can you detect whether a joystick has an X or Y slider? I only have an X slider, so the Y is extra...

[tgraupmann]

Can DirectInput distinguish between an X or Y slider?

[tgraupmann]

What's the difference between an X slider and Y slider? Isn't a slider a single axis? What does a dual-axis slider look like?

[pjcast]

I don't know much about sliders except that it is a DirectInput component only. Other OS's (at least) linux treat it as an axis. I'm not sure what the range should be of a slider.

So, with the CVS change, your slider now comes in as a sliderMoved event? But before the change it came in as an AxisMoved? I need to know specifically so I know if the fix did anything useful. It is possible to also set the min/max range, but I need to know the answer to the first question - does this code change the behavior?

[tgraupmann]

I'm not accessing the state using an event. I'm just using the Joystick state to get access to the slider.

Code: [Select]

long S13OISJoystick::GetSlider(short _sliderId)
{
if (m_Joystick)
{
const OIS::JoyStickState& joyStickState = m_Joystick->getJoyStickState();
const OIS::Slider& slider = joyStickState.mSliders[_sliderId / 2]; // bit shift maybe faster than / 2

if (_sliderId % 2)
{
// cap value X / MAX_AXIS * 1000
return ((slider.abX * 500.0f) / OIS::JoyStick::MAX_AXIS);
}
else
{
// cap value Y / MAX_AXIS * 1000
return ((slider.abY * 500.0f) / OIS::JoyStick::MAX_AXIS);
}
}

return 0;
}
Also check out how I'm normalizing the output using OIS::JoyStick::MAX_AXIS, but it'd like to be using OIS::Slider::MAX_AXIS.

[pjcast]

Ok, I made a small change to force enumerated slider axes to min/mac range. Can you update cvs and check again?

[tgraupmann]

Ok I got the update. I'm testing shortly. I figured I'd upgrade Ogre at the same time.

[tgraupmann]

I verified the slider range is now in the range of 32767.

I still need a way to detect x vs y slider axii...?

[pjcast]

You'll be wanting to setup some kind of action binding/user configuration menu. This way, you can let the user move a control to setup a bind action - which in that case you would detect either X or Y axis was moved. Perhaps the Y value is useless anyway, you'll probably be safe with just using the X axis.