"Esc" key don't opens the main menu of Doomsday (Solved)

edited 2013 Nov 11 in Technical Support
I don't know what I did, but I can't open the main menu of Doomsday engine anymore with the "Esc" key. That key simply don't responding and also don't allow me to exit Doomsday Engine.
I reseted the engine by using the -Reset in the Snowberry fronted, but this didn't help. Tryed to reinstall Doomsday, still don't help.
Is there a way to reset keyboard controls to their factory settings?
Help please.

Comments

  • I found how to solve the problem: I Run a game without any "Developer" commands that includes -warp, so that it will take me to the main screen anyway. The main menu appeared when I press any key. So I can reconfigure it again to be show/hide by the "Esc" Key.
    I tryed to check the shortcut that activate the "Screenshot" option, which operated by a key called "Print". I accidently deleted it, and I tryed to restore it again by pressing "Print Screen", buy the key didn't responded. And as I hit "Esc", that key disappeared from the "show/hide menu", and so the problem began. But why the "Print Screen" key, don't respond when configuring a shortcut?
  • Unfortunately the Print Screen key shortcut stopped working some time ago on Windows. I suspect this happened around the time when we switched to using Qt for keyboard input events. Its a problem that needs to be investigated. However because of all the other input problems on Windows we're actually planning to replace the input driver with a mechanism built using the RawInput API (as this seems to be the only reliable way to get full access to every key on the keyboard).
  • The "Print Screen" key, operates correctly in my Windows 7 Ultimate SP1. It correctly makes a screen shot in the clipboard, and I can paste it in Windows Painter.
  • Print Screen does take a screenshot and copys it to the clipboard, yes. The issue is that this key is not being recognised in Doomsday and so it cannot be bound to the "screenshot" command, which, saves that screenshot automatically in your runtime directory.

    So while it does "work" in an expected fashion its not working 100% correctly.
Sign In or Register to comment.