No, I'm not using a laptop, I have both version 1.42 and version 1.35, and this occurs even when zsnes is the only program running and I have the task priority set to realtime (I use windows XP as my operating system by the way), and effects every key. I'm using the stock keyboard i got when I bought my Emachine, but it's only at most 3 years old. I have about 754 megs of ram, and I really doubt (and hope it isn't) something to do with my computer's performance (outside of the keyboard itself).
Now that that is all out of the way, my problem: When running any game with zsnes, it fails to respond when I click keys, or goes on for about 3 seconds as though I had either been holding the button down or rapidly pressing it repeatedly. Running the same games, I notice that the stickyness is almost nil with version 1.35, but inescapable with version 1.42! manipulating the gui is smooth and problem-free, but transitioning from playing the game to using the topbar and vice versa is sometimes just as sluggish as activating the keys!
This is a very aggravating problem because I greatly prefer using zsnes over snes9x, so if someone can help me figure out why this is happening or how I can fix it, I would be grarteful, I can always use zsnes 1.35, but I'd rather this problem not continue with the rest of the zsnes's developments (if of course, this is a problem coming from within zsnes)
Keyboard sluggish, then overcompensates
Moderator: ZSNES Mods
-
- Dark Wind
- Posts: 1271
- Joined: Thu Jul 29, 2004 8:58 pm
- Location: Texas
- Contact:
1) Are you running WhatPulse or any form of keylogger? Make sure to do a scan with an anti-virus and anti-spyware tool.
2) Are you running a background virus scanner or spyware scanner? Try disabling those.
3) Try toggling the high priority option in ZSNES.
4) Lastly, try deleting your zguicfg.dat file. This is especially important if you extract one version of ZSNES on top of another and keep the config files.
2) Are you running a background virus scanner or spyware scanner? Try disabling those.
3) Try toggling the high priority option in ZSNES.
4) Lastly, try deleting your zguicfg.dat file. This is especially important if you extract one version of ZSNES on top of another and keep the config files.
[u][url=http://bash.org/?577451]#577451[/url][/u]
As far as my anti-virus/anti-spyware checkers (yes, multiple) are capable of detecting, I have no virus's or spyware.The Giver wrote:1) Are you running WhatPulse or any form of keylogger? Make sure to do a scan with an anti-virus and anti-spyware tool.
The Giver wrote:2) Are you running a background virus scanner or spyware scanner? Try disabling those.
have you scrubbed?! wrote:this occurs even when zsnes is the only program running
The Giver wrote:3) Try toggling the high priority option in ZSNES.
have you scrubbed?! wrote:and I have the task priority set to realtime
I will try this and get back to you, however both versions of zsnes which I have downloaded were extracted to seperate files and never overwritten.The Giver wrote:4) Lastly, try deleting your zguicfg.dat file. This is especially important if you extract one version of ZSNES on top of another and keep the config files.
*edit* Deleting the guicfg file seems to have put the stickyness at bay, may I ask what exactly it was that might have caused the problem?*end edit*
-
- Dark Wind
- Posts: 1271
- Joined: Thu Jul 29, 2004 8:58 pm
- Location: Texas
- Contact:
Download HijackThis, run it, do a system scan, and post the log file.
EDIT: If that worked, it's really hard to say. Somehow either you got an outdated config file which was confusing ZSNES, or the file got corrupted.
EDIT: If that worked, it's really hard to say. Somehow either you got an outdated config file which was confusing ZSNES, or the file got corrupted.
[u][url=http://bash.org/?577451]#577451[/url][/u]
I would not advise using maximum process priority in Windows NT 5, aka 2000, XP, 2003. I once did so with a PC 2D platformer years ago. It took over my machine and stopped responding to the keyboard. In fact, the only input it saw was the gamepad I had connected, and its menu navigation lacked a joystick button for backing out, so it was impossible for me to quit.
Avoid priority elevation at all costs. It should not be necessary for gaming. Offending background tasks should be eliminated, and necessary CPU hogging processes should either be suspended or reduced to the minimal priority level.
Avoid priority elevation at all costs. It should not be necessary for gaming. Offending background tasks should be eliminated, and necessary CPU hogging processes should either be suspended or reduced to the minimal priority level.