[DrCowPan]

Whenever I try to play EDuke32 the game keeps pausing every few seconds and its completely unplayable. Vanilla works fine, and I've tried playing it with no polymer or HRP etc on and it still occurs. This is what happens whenever I try to play.

OS: Win7 64 Bit
CPU: Intel i5 2300
GPU: Nvidia GTX560 Ti
RAM: 8GB

Played on EDuke32 2.0.0devel r3094.

Attached File(s)

•  eduke32.log (1.46K)
  Number of downloads: 191

[LeoD]

DrCowPan, on 28 October 2012 - 10:48 AM, said:

Whenever I try to play EDuke32 the game keeps pausing every few seconds and its completely unplayable. Vanilla works fine, and I've tried playing it with no polymer or HRP etc on and it still occurs. This is what happens whenever I try to play.

Most likely your keyboard mapping is messed up. Look into eduke32.cfg / settings.cfg. Or delete both files and reconfigure.

[DrCowPan]

LeoD, on 28 October 2012 - 11:47 AM, said:

Most likely your keyboard mapping is messed up. Look into eduke32.cfg / settings.cfg. Or delete both files and reconfigure.

I've tried searching for some sort of pause command but I can't find anything. The Pause key for me is also scroll lock, but I unbind-ed that and it still paused.

[LeoD]

DrCowPan, on 28 October 2012 - 12:52 PM, said:

I've tried searching for some sort of pause command but I can't find anything. The Pause key for me is also scroll lock, but I unbind-ed that and it still paused.

Post your *.cfg files. / Do you have any weird keyboard driver installed?

[The Commander]

Delete any .CFG files in your Duke folder and unplug and joysticks you may have plugged in then try again.

[DrCowPan]

Here are my .cfg files.
eduke32: http://pastebin.com/KihVKYKU
settings: http://pastebin.com/yXicWXfY

[LeoD]

DrCowPan, on 29 October 2012 - 11:03 AM, said:

Here are my .cfg files.

Pretty default ones. So I can only think of a reason outside of EDuke32. Try alternate keyboards or mouses if available. Remove joysticks if any. Stop or uninstall any OEM keyboard or mouse drivers.
...one more idea: try playing in fullscreen mode.

[Plagman]

Someone had the exact same issue a while back, but I can't find the thread.

[Hank]

I looked through your .cfg file
You should see a line
bind "ScrLck" "gamefunc_Holster_Weapon"
it is missing from the list.

My guess is that your keyboard driver no longer picks up the somewhat obsolete Scroll Lock, it should, even for modern OS? Anyway, try to add that line or bind that game function with another key, and see what happens.

Good Luck - Hey lock at the bright side, I can't play vanilla duke 3d !

[LeoD]

Plagman, on 29 October 2012 - 03:42 PM, said:

Someone had the exact same issue a while back, but I can't find the thread.

Here it is. It does not show up any solution however. So either those guys gave up or didn't care to tell us what they did to make the problem go away.

[Helixhorned]

I can think of a couple of hack-arounds, but these require developer tools on the end of the affected users. First, since it's clearly the pause game feature, one could create builds that have it disabled. They wouldn't be savegame- and demo-compatible with mainline EDuke32 though. The more reasonable approach would be to try to debug these pauses by setting a watchpoint on "ud.pause_on" from gdb.

[DrCowPan]

Helixhorned, on 03 November 2012 - 09:06 AM, said:

I can think of a couple of hack-arounds, but these require developer tools on the end of the affected users. First, since it's clearly the pause game feature, one could create builds that have it disabled. They wouldn't be savegame- and demo-compatible with mainline EDuke32 though. The more reasonable approach would be to try to debug these pauses by setting a watchpoint on "ud.pause_on" from gdb.

This method seems to be the most useful, I'll try that.

[Hendricks266]

Helixhorned, on 03 November 2012 - 09:06 AM, said:

I can think of a couple of hack-arounds, but these require developer tools on the end of the affected users. First, since it's clearly the pause game feature, one could create builds that have it disabled. They wouldn't be savegame- and demo-compatible with mainline EDuke32 though.

Why wouldn't they be? You wouldn't have to excise the entire pause_on structure member, you would just cut off its effects, or you could try disabling keyboard input from affecting it.

[Helixhorned]

Hendricks266, on 03 November 2012 - 01:45 PM, said:

Why wouldn't they be? You wouldn't have to excise the entire pause_on structure member, you would just cut off its effects, or you could try disabling keyboard input from affecting it.

The way I see it, pausedness is part of the game state: if you record a demo, pause and unpause the game and then play it back, the game state won't be updated in the paused interval, but it'll still show up as "Game Paused" instead of skipping to the point where the player continued the game again.

edit: OK, probably you're right... if ud.paused_on always stays at 0 in the demo, everything is fine.