[patq911]

So I'm in the main menu and my mouse is just really unresponsive.  Left and right stops every second, and up and down feels really weird.  I can't explain more than that, but I can tell you that this happened in the free game Warsow, they gave me a console command to fix it. "m_raw 1"  I haven't played Freespace 2 in a while, I now I want to play it again.

I'm using Freespace 2 Open, the mod for increased graphics.

My mouse is the Logitech G9x.

[General Battuta]

Debug log, please!

[patq911]

I forgot how, sorry.  But I don't think that will help.

[General Battuta]

A) yes it will, and b) the instructions are pinned right at the top of this forum.

[patq911]

When I run the debug .exe, the mouse problems are gone!


[attachment deleted by ninja]

[General Battuta]

Try using 3.6.12 final.

[patq911]

It's still there after I update.

I ran it in debug again and it was fine, again.  I hope this is the right debug log though.

[attachment deleted by ninja]

[The E]

Please set the colour depth to 32 bits.
Also, try adjusting the mouse sensitivity in the in-game options menu.

In addition, please post details about the mouse you are using. Does it use any speciual driver software, or is there any software running on your system that would interfere with this?

[patq911]

I forgot to configure the 32bit color after I updated it, It's there now.  Mouse sensitivity does nothing except make the responsive stuff faster.

I'm running the Logitech SetPoint program in the background, that allows me to set different DPI settings and etc.

I'm using my OS native drivers for pointer speed and acceleration (I'll uncheck that and test)

The polling rate for my mouse is 1000 reports/second (Default when the mouse came I think).

And Angle Snapping is checked off.

Ok I just checked and when I uncheck "Use OS native drivers" the mouse is working in the game, but it feels really weird for me, and I can't get it back to where I like it, unless I check it again.

[The E]

I'm sorry, but making FSO work with strange 3rd-party drivers is really not on our todo list.

[patq911]

"Strange"!? It's freaking Logitech!

[The E]

Doesn't change the fact that it a) behaves strange, b) this is the first bug report of this kind I have seen in two years, c) we don't have the coders to research what's causing this and implement a workaround, and d) did I mention that you're the only person who has reported that bug?

Also, given that you apparently are able to get the mouse working correctly, I am inclined to believe that the fault is not with our input polling, but rather with how that driver interacts with the OS.