Lokalaskurar
Posts: 513 +0
(Now, it is in fact hard to categorize this kind of question, but I think it is best suited under the Windows OS forum.)
Which system process controls the keyboard input logging?
(on a PS/2 keyboard - not the same as on the USB keyboards, I've heard)
Details & Background:
I got my hands on a copy of Fallout: New Vegas. Being a fan of the franchise, I installed it on my system. (see my 'System Specs.' for details on my hardware)
The game ran like a charm with one exception; audio! (and some animations).
When running on the ground/jumping/shooting etc. the music (note: not the in-game radio) played nicely -- but I heard absolutely squat as for SFX. But once I pressed Esc, all the logged audio that was supposed to play came at me at once! Like a full symphony orchestra... (ouch!)
(Also, some animations (like the 'sit."animation" ', 'eat."animation" ' etc.) are non-functional, sometimes even prohibiting the storyline to continue.)
I figured the problem must lie within the process management.
So I set the FalloutNV.exe process priority to 'Higher than Usual', and whaddaya know, it worked!!
... part from another problem...
Holding down W as in 'walk forward' now logs each W pressed down. Meaning that the character runs for 20 miles each time I press W for 5 seconds... after ~12 seconds, the keylog is filled to its brim, and the PC starts swearing (bleep bleep bleep).
Presumably because the FalloutNV.exe is prioritised higher than the input logging process.
Hence the question:
Which system process controls the keyboard input logging?
My goal:
I'd like to prioritise that process as well.
(final note: ) I'm close to completing the game using q-walk and CAPS lock. So I'm not prohibited from playing the game at all. Just that I'd like to know how to make it more enjoyable by at least trying to prioritise the keyboard input process.
Which system process controls the keyboard input logging?
(on a PS/2 keyboard - not the same as on the USB keyboards, I've heard)
Details & Background:
I got my hands on a copy of Fallout: New Vegas. Being a fan of the franchise, I installed it on my system. (see my 'System Specs.' for details on my hardware)
The game ran like a charm with one exception; audio! (and some animations).
When running on the ground/jumping/shooting etc. the music (note: not the in-game radio) played nicely -- but I heard absolutely squat as for SFX. But once I pressed Esc, all the logged audio that was supposed to play came at me at once! Like a full symphony orchestra... (ouch!)
(Also, some animations (like the 'sit."animation" ', 'eat."animation" ' etc.) are non-functional, sometimes even prohibiting the storyline to continue.)
I figured the problem must lie within the process management.
So I set the FalloutNV.exe process priority to 'Higher than Usual', and whaddaya know, it worked!!
... part from another problem...Holding down W as in 'walk forward' now logs each W pressed down. Meaning that the character runs for 20 miles each time I press W for 5 seconds... after ~12 seconds, the keylog is filled to its brim, and the PC starts swearing (bleep bleep bleep).
Presumably because the FalloutNV.exe is prioritised higher than the input logging process.
Hence the question:
Which system process controls the keyboard input logging?
My goal:
I'd like to prioritise that process as well.
(final note: ) I'm close to completing the game using q-walk and CAPS lock. So I'm not prohibited from playing the game at all. Just that I'd like to know how to make it more enjoyable by at least trying to prioritise the keyboard input process.
