W M O
M
O

Direct DL : http://nsx.cx/hidusbf-signed.zip

Well, even if I really don't like my WMO, I'm going to give it a try just because I can.

Yay

if only mousewheel of my wmo wouldnt switch weapons by itself...

Have you tried taking it apart and cleaning it?

thats becaus every button is very high sensitive, if i drop my wmo from 1cm is shoots, zooms and switches to mg :D

fix: http://www.esreality.com/index.php?a=post&...pid1714665

I want povohat's accel driver signed please! I can aim so much better with accel but I can't use it in other games that don't have the Quake accel, and povohat's accel thingy is labelled as a cheat by VAC/Blizzard etc afaik.

Povohat accel is remade so it doesnt need testmode any more

It still gets picked up as a cheat though?

dont think so

Sometimes used with ow, no prob (for now lol)

Anybody know why this triggers my antivirus? With TR/Agent.Elmo.pgli.309?

Ollir, bcause its a signed driver / unsigned. There are no viruses in the known version.

And no, it does not get picked up as cheat, bcause you dont have to use it in test mode.

Test mode was detected by VAC. This driver was signed in windows 7 under testmode.

Under windows 8/8.1 this fix didnt work. Now there is a fix, and you dont have to use test mode - no cheat just a signed driver.

Great, now we just need a way to fix the sensor reportings being translated into a somewhat consistent result in the OS and graphics drivers. The way it is now is just too inconsistent at times.

Mentioned in the thread was somewhat saying "when everything else is optimised" what would that include? There's definitely difference between a smoothed sensor and the mlt04 in snappiness just on a plug and play basis oc'd to 1000hz, I'm curious if what more can be done

Reviving old topic but since I heard only today that this hidusbf thing was now certified for windows and so on...

So I use Win7 64b, and the program says my mouse is in a USB 3.0 slot.

I installed the program and I changed the polling rate to 500 Hz but it seems it doesn't work. What bugs me is that if I chose to downgrade the polling rate to 62, it works correctly. I verify it with mouserate.exe.

So, what could possibly make it impossible to upgrade to 500 Hz, would it be the 3.0 USB port ? If yes, is there a way to make it work like an USB 2.0 port ?

62..? I thought the default was 125 for a WMO.

Stupid question but did you try running hidusbf as administrator?

I had a couple of issues when I was trying to use it years ago too and it took a few attempts to get right.

If you've got the mouse plugged into a front-panel USB port, try moving it to one directly connected to the motherboard

62 is lower but it's in the program to allow you to try less than 125 Hz. Basically, if 62 Hz works, it means the driver works. So, the driver works.

I went and ask at Overclovk forusm. The problem is actually that I use Windows 7 and my motherboard has usb 3.0 ports, which Windows 7 doesn't recognise naturally and so it uses a special driver that hidusbf cannot replace.

So, the solution for me would be to use Windows 8 or 10, or to buy a 10 euros USB 2.0 PCI card to have 2.0 drivers on it that hidusb could tweak.

It works normally for USB 3.0 ports on Windows 10 and so on, I'm only fucked because of Windows 7 apparently.

Did you try using test mode ?