I haven't tested this yet, but it sounds like it's essentially the modified quake3 executable for cpm equivalent for QL. I know I'll be giving this a shot when I can.

2 feels good to me, never realized my windows had so much accel

haha @ arqon

sorry i couldn't resist it :)

arqon is working on ql actually

he propably means http://www.esreality.com/?a=post&id=1565939#pid1566833

QL doesn't use virtual machine to remain compatibility with different platforms. So thats ok to use some platform-dependant features.

why so serious :/

http://www.esreality.com/?a=post&id=1565939

More info.

so it has less lag? So the only argument against would be that the sensitivity is gonna be a abit different than in_mouse 1? guess im gonna use this as default setting.

Argument against it is that you'll get used to something that's not present in everygame.

It was the reason not to use it in Quake3.
That, and the uncertainty if it would be allowed on LAN tourneys.

real quakers only play quake, so no problem there

Quake2 and Quake4 don't have this.

oh....my bad

QW, Q3 and QL does though, 3 out of 5 is good enough!

Will this change the feel of the sens?

Beginning with Windows XP, Direct Input internally uses the "Raw Input" API anyway, so there shouldn't be any effective difference (stupid buffer limitations excluded). It's interesting to see yet another case of placebo.

Prooflink?

My google skills is not enough to find it :)

"Internally, DirectInput creates a second thread to read WM_INPUT data, and using the DirectInput APIs will add more overhead than simply reading WM_INPUT directly."
http://msdn.microsoft.com/en-us/library/bb206183(VS.85,printer).aspx

Hehe, thanks pal (or gal :)

LET ARQON SPEAK

.

same but I still use it, feels better even with the buffer overflow

Feels different for me. May also depend on the mouse you're using?

If you get buffer overflow you're probably using your mouse at 1000hz. put my DA at 500 and it works without overflowing.

wrong

I'm so happy about this! I almost stopped playing ql after arqon said that ql will never get raw input.
After playing other quakes with raw input for over a year i was always bugged by the inferior mouse feel in ql, now its great.
Havent gotten any bufferoverflow with ie3.0 on 500hz.
Now it they only could unlock fps too that would be great so one can use 320 or 480fps and monitor on 160hz witch is better than 125/125

what exactly is the difference?

This is great. On 1 i have a lot of accel, which fucks up my sens. On -1, buttons 4 and 5 don't work (i have a x-750f). 2 feels just about perfect. :)

zoom on mouse 5 with in_mouse 2 doesnt work...it changes the fov to zoom fov but doenst return to the normal fov.Its like it just does +zoom without -zoom :D

thank go...arqon, for in_mouse 2!

not me - probably ttimo.

faict, ql actually needs this, because of issues with DI in child windows (especially with ?IE8? which is apparently royally fkd) so there's potentially a real point/benefit to it there.

if i use in_mouse 2, will that make it so the sens will be the same if i change from xp to vista (using same drivers and mouse) ?

Why would someone go xp > vista?

64bit

I'd better will stay with 3.2 GB of RAM. :)

:D

vista is not THAT bad really. you need to tweak it alot, but most do that to xp anyways.

I assume this is like the ezQuake option?

they gonna remove the overflow shit?

They said they would remove it in the next update.

cl_mouseaccel 0 and set it to 500hz it works...and make sure other kind of accel is turned off aswell like that mouseaccelstyle etc.

not for me

how do i notice buffer overflow? negative acceleration?

lags and about 30 consequent messages in the console "buffer overflow bla bla"

My MX310 sill reports buttons 4, 5, 6 as the same 0X00, and doesn't recognize button 3 :( Nothing helps.