Jump to content

  • Log In with Google      Sign In   
  • Create Account


How to Handle Controller's Phantom Axes


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
2 replies to this topic

#1 Kanefa   Members   -  Reputation: 122

Like
0Likes
Like

Posted 25 March 2014 - 02:34 PM

I put together some preliminary code just to inspect the axes of my controller.  What I notice is I am able to properly detect movement in 6 axes. However, there are 2 axes that don't exist that are returning a maximum range result.

 

How can I filter out these false positives when detecting a new controller that I know nothing about? 

 

 



Sponsor:

#2 Kanefa   Members   -  Reputation: 122

Like
1Likes
Like

Posted 26 March 2014 - 01:28 AM

SFML has calls to check whether an axes exists.  Verify it exists before trying to read it.



#3 Endurion   Crossbones+   -  Reputation: 3337

Like
0Likes
Like

Posted 26 March 2014 - 06:47 AM

Maybe some analog buttons that get mapped to an axis?

 

What interface are you using? DirectInput, Raw Input?


Fruny: Ftagn! Ia! Ia! std::time_put_byname! Mglui naflftagn std::codecvt eY'ha-nthlei!,char,mbstate_t>




Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS