Jump to content

  • Log In with Google      Sign In   
  • Create Account


Rawinput gives me only pixel accuracy


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
8 replies to this topic

#1 nico3000   Members   -  Reputation: 131

Like
0Likes
Like

Posted 29 June 2013 - 04:53 AM

I set up Rawinput to process mouse events like this

        m_rawSize = 0;
        m_pRaw = 0;
        RAWINPUTDEVICE pMouseRid[1];
        pMouseRid->usUsagePage = 0x01;
        pMouseRid->usUsage = 0x02;
        pMouseRid->dwFlags = 0;//RIDEV_NOLEGACY;
        pMouseRid->hwndTarget = m_hwnd;
        if(!RegisterRawInputDevices(pMouseRid, 1, sizeof(RAWINPUTDEVICE)))
        {
            IG_ERROR("RegisterRawInputDevices() failed!");
            return false;
        }
        else
        {
            return true;
        }

And I listen to them like this

UINT dwSize = 0;
        UINT result = GetRawInputData((HRAWINPUT)p_lParam, RID_INPUT, NULL, &dwSize, sizeof(RAWINPUTHEADER));
        if(result != 0)
        {
            IG_WARNING("GetRawInputData() failed (Result " << result << ", lParam " << p_lParam << ").");
            return;
        }
        if(m_rawSize < dwSize)
        {
            SAFE_DELETE_ARRAY(m_pRaw);
            m_pRaw = (RAWINPUT*)(IG_NEW unsigned char[dwSize]);
            m_rawSize = dwSize;
            if(!m_pRaw)
            {
                IG_WARNING("Failed to allocate space.");
                return;
            }
        }
        if(m_pRaw) 
        {
            result = GetRawInputData((HRAWINPUT)p_lParam, RID_INPUT, m_pRaw, &dwSize, sizeof(RAWINPUTHEADER));
            if(result == (UINT)-1)
            {
                IG_WARNING("GetRawInputData() failed.");
                return;
            }
            if(result != dwSize)
            {
                IG_WARNING("GetRawInputData does not return correct size! Expected " << dwSize << ", got " << result);
                return;
            }
            else if(m_pRaw->header.dwType == RIM_TYPEMOUSE)
            {
                WmInput input;
                input.m_message = WM_INPUT;
                input.m_deltaX = m_pRaw->data.mouse.lLastX;
                input.m_deltaY = m_pRaw->data.mouse.lLastY;
                input.m_flags = m_pRaw->data.mouse.usButtonFlags;
                input.m_data = m_pRaw->data.mouse.usButtonData;
                IG_INFO("WM_INPUT " << m_pRaw->data.mouse.lLastX << ", " << m_pRaw->data.mouse.lLastY << ".");
                m_inputs.push(input);
            }
        }

But with this code the WM_INPUT events only come in as the cursor moves one pixel and the lLastX/Y vars do represent that on pixel. So it doesn't have the promised advantage of being more precise than the WM_MOUSEMOVE messages. Am I wrong? What is the proper way to get high resolution input from my mouse?

 

I have a Logitech G500 + Logitech Gaming Software 8.45.88 installed. The DPI is set to 1500.



Sponsor:

#2 superman3275   Crossbones+   -  Reputation: 1976

Like
0Likes
Like

Posted 29 June 2013 - 07:35 AM

How are you supposed to get more precision than pixels? Why would you need that anyway?

 

Cheers :)!


I'm a game programmer and computer science ninja ph34r.png!

Here's Breakout:
Breakout!

Want to ask about Python and / or Pygame? What about HTML5 / CSS3 / JavaScript? What about C++ and / or SFML 2 (and 1.6)? Recruiting for a game development team and need a passionate programmer? Just want to talk about programming? Email me here:

Superman3275@Gmail.com

or Personal-Message me on here smile.png!


#3 Paradigm Shifter   Crossbones+   -  Reputation: 5121

Like
0Likes
Like

Posted 29 June 2013 - 07:37 AM

You used to be able to get mickeys (raw mouse units read from the hardware) but I had a search of MSDN and couldn't find anything, it may be device driver level only. It used to be called MouseGetMickeys I believe, but I dunno where it's gone?


Edited by Paradigm Shifter, 29 June 2013 - 07:39 AM.

"Most people think, great God will come from the sky, take away everything, and make everybody feel high" - Bob Marley

#4 Hodgman   Moderators   -  Reputation: 27585

Like
2Likes
Like

Posted 29 June 2013 - 08:45 AM

How are you supposed to get more precision than pixels? Why would you need that anyway?

Say your OS/hardware is configured so that every time you move the mouse 1mm, the cursor moves 1 pixel.
In your game (let's say a first-person shooter), you might create a mapping so that every 1px the OS cursor moves, you rotate your player 1 degree.
 
The problem is that modern mice are much more sensitive than that - detecting movements in the range of a few microns, not millimetres!

If your user has such a mouse, it would be nice for you to detect that they moved their cursor the equivalent of 2.1423mm, and rotate your camera by 2.1423 degrees, which will provide much a smoother feel to the camera controller, especially at low speeds.


Edited by Hodgman, 29 June 2013 - 08:46 AM.


#5 superman3275   Crossbones+   -  Reputation: 1976

Like
0Likes
Like

Posted 29 June 2013 - 10:31 AM

 

How are you supposed to get more precision than pixels? Why would you need that anyway?

Say your OS/hardware is configured so that every time you move the mouse 1mm, the cursor moves 1 pixel.
In your game (let's say a first-person shooter), you might create a mapping so that every 1px the OS cursor moves, you rotate your player 1 degree.
 
The problem is that modern mice are much more sensitive than that - detecting movements in the range of a few microns, not millimetres!

If your user has such a mouse, it would be nice for you to detect that they moved their cursor the equivalent of 2.1423mm, and rotate your camera by 2.1423 degrees, which will provide much a smoother feel to the camera controller, especially at low speeds.

 

Thanks for the explanation!

 

Cheers :)!


I'm a game programmer and computer science ninja ph34r.png!

Here's Breakout:
Breakout!

Want to ask about Python and / or Pygame? What about HTML5 / CSS3 / JavaScript? What about C++ and / or SFML 2 (and 1.6)? Recruiting for a game development team and need a passionate programmer? Just want to talk about programming? Email me here:

Superman3275@Gmail.com

or Personal-Message me on here smile.png!


#6 nico3000   Members   -  Reputation: 131

Like
0Likes
Like

Posted 29 June 2013 - 03:25 PM

And how do I achieve this? wink.png


Edited by nico3000, 29 June 2013 - 03:25 PM.


#7 Khatharr   Crossbones+   -  Reputation: 2818

Like
1Likes
Like

Posted 30 June 2013 - 02:17 PM

I thought this was discussed in the RawInput docs.

 

Let me dig up my Raw Input stuff and look at it. brb

 

--------------

 

http://msdn.microsoft.com/en-us/library/windows/desktop/ee418864%28v=vs.85%29.aspx

 

You should already be getting hardware resolution results from what you're doing.

 

?


Edited by Khatharr, 30 June 2013 - 02:30 PM.

void hurrrrrrrr() {__asm sub [ebp+4],5;}

There are ten kinds of people in this world: those who understand binary and those who don't.

#8 nico3000   Members   -  Reputation: 131

Like
1Likes
Like

Posted 02 July 2013 - 01:53 AM

Yes, I read that before. I think Windows does also use the the high precision data from your mouse and moves the cursor one pixel for each unit of mouse motion IF you set the pointer speed in your mouse properties to the 6th notch. I Set my mouse to 5700dpi and chose the 3rd notch. The cursor has now perfect speed for me in windows and rawinput  gives more than pixel accuracy.

I think the MSDN article is a little bit confusing at that point.



#9 Khatharr   Crossbones+   -  Reputation: 2818

Like
0Likes
Like

Posted 02 July 2013 - 04:48 AM

All MSDN articles are either confusing, incomplete or incorrect. It's a matter of contract.

 

The only time you'll find an MSDN article that clearly explains everything you need to know without errors, the actual implementation of whatever it's discussing will have some bug that renders it ineffective.


void hurrrrrrrr() {__asm sub [ebp+4],5;}

There are ten kinds of people in this world: those who understand binary and those who don'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