Jump to content

  • Log In with Google      Sign In   
  • Create Account

We're offering banner ads on our site from just $5!

1. Details HERE. 2. GDNet+ Subscriptions HERE. 3. Ad upload HERE.


Don't forget to read Tuesday's email newsletter for your chance to win a free copy of Construct 2!


Raw Input mouse stutter/jitter


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
1 reply to this topic

#1 DrColossus   Members   -  Reputation: 473

Like
0Likes
Like

Posted 20 July 2013 - 04:13 AM

I'm using the raw input API for all input events in my own engine, and everything works just fine.
Well, as long as i only run the executable itself.
 
I also started working on an editor tool suite in Winforms/C#.
The editor starts the engine in a separate process and passes it's window handle along. The engine then creates a child window and renders everything inside the editor, similar to how the BitSquid tools work (http://bitsquid.blogspot.de/2010/04/our-tool-architecture.html).
 
And that's where my problems arise:
Whenever i hold down a button on my keyboard while the engine is running within the editor window, the mouse input gets very jittery.
 
Here are two small 60fps videos (~500KB in size) showing the issue:
 
The jitter starts to appear whenever the windows key repeat kicks in.
I don't have a lot of experience in Win32/WinForms, so i'm currently at a loss about how to fix this.
 
Other games seem to exhibit similar (the same?) issues:
 
Battlefield 3:
 
Counter-Strike Source:
 
The BF3 fix was to limit "RenderFramesAhead" to 1, forcing that in the driver (Nvidia 320.49, GTX580) doesn't fix it in my case.
the CS:S solution was to use raw input, which i already do.
 
 
Does anyobody have any ideas on what might be causing this?

Edited by DrColossus, 20 July 2013 - 04:21 AM.


Sponsor:

#2 DrColossus   Members   -  Reputation: 473

Like
1Likes
Like

Posted 29 July 2013 - 10:57 AM

I have since changed the rawinput message handling to run on a different thread as a workaround, using an invisible window with blocking GetMessage() calls.

 

Everything is smooth now in all circumstances, though i'd really like to know what was causing this behaviour.






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