My pause break key (the one that pauses the game clock)wont work after a while of playing the game. If I uninstall and reinstall it works fine untill it happens again is there anyway to fix this without me having to reinstall it.
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
This is rather odd.
Does simply exiting and restarting the game also restore the pause key function?
Does simply exiting and restarting the game also restore the pause key function?
Just a question, are you sure it's not your pause button that's semibroken?fowditty said:
You could try and use my keymapper tool to verify this.
Some people have to press 'Ctrl' once after they left and re-entered the game via 'Alt-Tab' - could this be the case for you?fowditty said:
G'Kar said:
I tried all of the suggestions and this one seems to work. Thank you for all the help guys.
Heh. That's a crucial piece of information you left out in the opening post.
Yes. Pressing <ctrl><esc> or <alt><tab> to switch back to the desktop leaves the status for the <ctrl> or the <alt> key in the depressed state as far as Windows is concerned for the application you switched away from.
This means that, when you come back to the game after whatever else you have done in other applications or the desktop, Windows will still think you are pressing down the <ctrl> or the <alt> key. If you then press <pause>, Windows will tell the game you pressed <ctrl><pause> or <alt><pause>, which the game (obviously) does not recognize as the pause function. Same story holds true for the '?' key to find a province by name.
So, each time you break out of the game using the keyboard shortcuts, simply hit the <ctrl> or the <alt> key by itself once you have re-entered the game. That will reset the proper shift status tracking inside Windows, and the keyboard will behave normally again.
Yes. Pressing <ctrl><esc> or <alt><tab> to switch back to the desktop leaves the status for the <ctrl> or the <alt> key in the depressed state as far as Windows is concerned for the application you switched away from.
This means that, when you come back to the game after whatever else you have done in other applications or the desktop, Windows will still think you are pressing down the <ctrl> or the <alt> key. If you then press <pause>, Windows will tell the game you pressed <ctrl><pause> or <alt><pause>, which the game (obviously) does not recognize as the pause function. Same story holds true for the '?' key to find a province by name.
So, each time you break out of the game using the keyboard shortcuts, simply hit the <ctrl> or the <alt> key by itself once you have re-entered the game. That will reset the proper shift status tracking inside Windows, and the keyboard will behave normally again.
Hmm, your explanation left open something: Why do some people have the problem, while others don't?
I know that it's happening frequently for a friend of mine, but it never happened to me. Our system configurations are comparable.
I know that it's happening frequently for a friend of mine, but it never happened to me. Our system configurations are comparable.
My explanation comes from personal experience with my on versions of Windows (yes: plural).
But since it's the tracking of the shift state of the keyboard that is causing the troubles, I can't exclude the possibility that differences in keyboard, driver and processor speed (plus maybe the way how the two finger salute is entered) can cause the shift state release to be seen by the game itself on one system, while it ends up with the desktop process on another.
But since it's the tracking of the shift state of the keyboard that is causing the troubles, I can't exclude the possibility that differences in keyboard, driver and processor speed (plus maybe the way how the two finger salute is entered) can cause the shift state release to be seen by the game itself on one system, while it ends up with the desktop process on another.
I see. We're using the same OS though and he had the same problem with three different hardware configurations, so I guess it boils down to the manner of pressing the keys.