If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

I mess arround with my fov/sens settings a lot more regularly than I used to, and I knew my HUD was broken in a lot of game modes so I hadn't updated my CFG here in a while.

Finally finished my degree, so I fixed up the hud with all the new game modes, made sure skulls show up in harvester even, and uploaded what I've been playing with today in Post 4 yakumo_2012.zip

Oddly enough, I was exploring your old config just last night, so I guess I'll have to have another poke around. Gandim was kind enough to suggest a few things the other day, and it's made me look at my mouse settings more closely than just using the slider in the in game settings.

Your mouse settings as copied seem to work a treat with my Abyssus - it feels a lot smoother and more accurate, although I turn up the sensitivity.

I had updated my gfx drivers a while ago, and at that time had a few days off QL, and when played again i noticed QL was starting slow or like a waiting period *before* map *started* to load. I fixed this by re-checking that high precision event timer was disabled.
There's at least 4 options on that end.
HPET enabled in bios and operating system, enabled only in bios, enabled only in OS, disabled in both. I tried all variations, and with hpet off on my system, i no longer have the 5 seconds waiting time for map to close down or to start loading.
Very strange since i couldnt see the gfx driver changed hpet for windows.

The other thing is that some mobo's chipset only has 32bit hpet support while others have both 32 and 64bit, so it's really a system specific system. Albeit in theory pure HPET should be best, completely disabling it for my system which only supports 32bit from hardware is the better options since i run 64bit operating system.

The default option in w7 should be that it is disabled but u can doublecheck that by open an cmd.exe with admin rights and entering "bcdedit /set useplatformclock false" or true if you want to test that. As well as enabling/disabling it in bios - of course. In my bios this is related to/called ACPI SRAT table - which took me a while to figure out.

I read about others experience on this case, and indeed it affects mouse sensitivity, in the sense of response feeling.

If you have a some issue with mouse sensitivity or ql is loading slow, maybe this could be worth looking into.