myth versions above 1.6 crash immediatly
-
- Posts: 13
- Joined: Wed Jun 26, 2013 3:20 pm
Re: myth versions above 1.6 crash immediatly
even when i hit alt-p and get to the preferences screen it still closes a half second
after i see the preferences screen.
after i see the preferences screen.
-
- Posts: 13
- Joined: Wed Jun 26, 2013 3:20 pm
Re: myth versions above 1.6 crash immediatly
i can go to the tutorial, but when i am there the 'game paused' box flashes on and off constantly and i cant see my mouse pointer..crucial hints at whats wrong maybe?
Re: myth versions above 1.6 crash immediatly
Definitely sounds like a stuck escape key to me.
-
- Posts: 13
- Joined: Wed Jun 26, 2013 3:20 pm
Re: myth versions above 1.6 crash immediatly
well i'll get a usb keyboard soon, how do i disable my laptop keyboard? why wouldnt any other applications or windows close if i had a stuck escape key though? v1.6 never closes on me like 1.7.2 and 1.8 do
Re: myth versions above 1.6 crash immediatly
For the main menu, the only things that could force the Quit button to light up other than clicking it would be Esc key or Alt-Q. The fact that the game pause flashes on and off narrows it down to just the Esc key. Try tapping that key a few times to get it unstuck just to be sure. Remember, it doesn't actually have to look stuck to be stuck. Then load up Myth to see if it fixed the problem.
If the issue persists, another option that doesn't involve replacing the keyboard or having to get a separate keyboard would be to remap that key with a program like AutoHotkey. I made this little script and converted it into an executable file so that you don't need to install AutoHotkey to run it. When you run it, it disables the esc key. A green icon with a white "H" will be in the task bar. Just close it to disable the script by right clicking on the icon and selecting Exit. Let us know how it goes.
If the issue persists, another option that doesn't involve replacing the keyboard or having to get a separate keyboard would be to remap that key with a program like AutoHotkey. I made this little script and converted it into an executable file so that you don't need to install AutoHotkey to run it. When you run it, it disables the esc key. A green icon with a white "H" will be in the task bar. Just close it to disable the script by right clicking on the icon and selecting Exit. Let us know how it goes.
-
- Posts: 13
- Joined: Wed Jun 26, 2013 3:20 pm
Re: myth versions above 1.6 crash immediatly
when i try to run that program windows says
"the version of this file is not compatible with the version of windows you're running. check your computer's system information to see whether you need an x86(32-bit) or x64(64-bit) version of the program, and then contact the software publisher"
..
im running windows vista home premium operating system
service pack 2
32 bit
....
when i try to 'run it as an administrator'
it says 'c:users\username\documents\disable esc.exe is not a valid
win 32 application
"the version of this file is not compatible with the version of windows you're running. check your computer's system information to see whether you need an x86(32-bit) or x64(64-bit) version of the program, and then contact the software publisher"
..
im running windows vista home premium operating system
service pack 2
32 bit
....
when i try to 'run it as an administrator'
it says 'c:users\username\documents\disable esc.exe is not a valid
win 32 application
-
- Posts: 13
- Joined: Wed Jun 26, 2013 3:20 pm
Re: myth versions above 1.6 crash immediatly
i tried tapping on the escape key, and i got your program to work and see the green H in the corner of the screen, but
myth still closes immediatly after the main screen comes up
myth still closes immediatly after the main screen comes up
Re: myth versions above 1.6 crash immediatly
So you have the program running before you load Myth2, right? Ok try this, have the program running and load up 1.6.0. Then tap on Esc to see if it makes Myth2 quit. If it works on 1.6.0, it should work on 1.8.0.
-
- Posts: 13
- Joined: Wed Jun 26, 2013 3:20 pm
Re: myth versions above 1.6 crash immediatly
2013-06-30 04:44:15
Myth II Build 427 running under Modern Windows 6.000000 ----------------------------------------------
Loading poweruser.txt... not found.
DEBUG: Updating monolithic tag cache:
Initial count: 17
Number removed: 7
Number added: 7
New count: 17
INFO: ignoring non-required patch file 'Patch 1.4 Interface'
INFO: ignoring non-required patch file 'Patch MariusNet'
DEBUG: Adding 11 monolithic tags:
small install
medium install
large install
international small install
international large install
Patch 1.2
Patch 1.3
Patch 1.4
Patch 1.5
MariusNet
Patch 1.8 Interface
Scanning for software devices...
Found 1 to use
Scanning for Direct3D devices...
Found 1 to use
Scanning for DirectX 11 devices...
Found adapter: ATI Radeon Xpress Series
Adapter does not support DirectX feature level 10_0; DirectX 11 will not be available.
Found 0 to use
Scanning for 3Dfx devices...
Found 0 to use
Scanning for OpenGL devices...
Found 1 to use
ATI Radeon Xpress Series | ATI Technologies Inc. | OpenGL 2.1
Initializing sound with DirectSound...
Initialized for DirectSound3D using COM
DirectSound initialized successfully.
Warning: Unable to find cutscene 'prologue'.
KEYBOARD DEBUG: got key event {code = 0 | char='ÿ' | repeat=0 | modifiers=0}
KEYBOARD DEBUG: refresh_device_states(): detected the following changed keys:
key 0: 1 -> 0
Closing Myth.
Myth II Build 427 running under Modern Windows 6.000000 ----------------------------------------------
Loading poweruser.txt... not found.
DEBUG: Updating monolithic tag cache:
Initial count: 17
Number removed: 7
Number added: 7
New count: 17
INFO: ignoring non-required patch file 'Patch 1.4 Interface'
INFO: ignoring non-required patch file 'Patch MariusNet'
DEBUG: Adding 11 monolithic tags:
small install
medium install
large install
international small install
international large install
Patch 1.2
Patch 1.3
Patch 1.4
Patch 1.5
MariusNet
Patch 1.8 Interface
Scanning for software devices...
Found 1 to use
Scanning for Direct3D devices...
Found 1 to use
Scanning for DirectX 11 devices...
Found adapter: ATI Radeon Xpress Series
Adapter does not support DirectX feature level 10_0; DirectX 11 will not be available.
Found 0 to use
Scanning for 3Dfx devices...
Found 0 to use
Scanning for OpenGL devices...
Found 1 to use
ATI Radeon Xpress Series | ATI Technologies Inc. | OpenGL 2.1
Initializing sound with DirectSound...
Initialized for DirectSound3D using COM
DirectSound initialized successfully.
Warning: Unable to find cutscene 'prologue'.
KEYBOARD DEBUG: got key event {code = 0 | char='ÿ' | repeat=0 | modifiers=0}
KEYBOARD DEBUG: refresh_device_states(): detected the following changed keys:
key 0: 1 -> 0
Closing Myth.
-
- Posts: 13
- Joined: Wed Jun 26, 2013 3:20 pm
Re: myth versions above 1.6 crash immediatly
2013-06-30 05:07:48
Myth II Build 427 running under Modern Windows 6.000000 ----------------------------------------------
Loading poweruser.txt... not found.
DEBUG: Updating monolithic tag cache:
Initial count: 17
Number removed: 0
Number added: 0
New count: 17
INFO: ignoring non-required patch file 'Patch 1.4 Interface'
INFO: ignoring non-required patch file 'Patch MariusNet'
DEBUG: Adding 11 monolithic tags:
small install
medium install
large install
international small install
international large install
Patch 1.2
Patch 1.3
Patch 1.4
Patch 1.5
MariusNet
Patch 1.8 Interface
Scanning for software devices...
Found 1 to use
Scanning for Direct3D devices...
Found 1 to use
Scanning for DirectX 11 devices...
Found adapter: ATI Radeon Xpress Series
Adapter does not support DirectX feature level 10_0; DirectX 11 will not be available.
Found 0 to use
Scanning for 3Dfx devices...
Found 0 to use
Scanning for OpenGL devices...
Found 1 to use
ATI Radeon Xpress Series | ATI Technologies Inc. | OpenGL 2.1
Initializing sound with DirectSound...
Initialized for DirectSound3D using COM
DirectSound initialized successfully.
Warning: Unable to find cutscene 'prologue'.
KEYBOARD DEBUG: got event from WM_KEYDOWN; wParam = 0x000000ff, lParam = 0x010d0001
KEYBOARD DEBUG: got key event {code = 0 | char='ÿ' | repeat=0 | modifiers=0}
KEYBOARD DEBUG: refresh_device_states(): detected the following changed keys:
key 0: 1 -> 0
Closing Myth.
Myth II Build 427 running under Modern Windows 6.000000 ----------------------------------------------
Loading poweruser.txt... not found.
DEBUG: Updating monolithic tag cache:
Initial count: 17
Number removed: 0
Number added: 0
New count: 17
INFO: ignoring non-required patch file 'Patch 1.4 Interface'
INFO: ignoring non-required patch file 'Patch MariusNet'
DEBUG: Adding 11 monolithic tags:
small install
medium install
large install
international small install
international large install
Patch 1.2
Patch 1.3
Patch 1.4
Patch 1.5
MariusNet
Patch 1.8 Interface
Scanning for software devices...
Found 1 to use
Scanning for Direct3D devices...
Found 1 to use
Scanning for DirectX 11 devices...
Found adapter: ATI Radeon Xpress Series
Adapter does not support DirectX feature level 10_0; DirectX 11 will not be available.
Found 0 to use
Scanning for 3Dfx devices...
Found 0 to use
Scanning for OpenGL devices...
Found 1 to use
ATI Radeon Xpress Series | ATI Technologies Inc. | OpenGL 2.1
Initializing sound with DirectSound...
Initialized for DirectSound3D using COM
DirectSound initialized successfully.
Warning: Unable to find cutscene 'prologue'.
KEYBOARD DEBUG: got event from WM_KEYDOWN; wParam = 0x000000ff, lParam = 0x010d0001
KEYBOARD DEBUG: got key event {code = 0 | char='ÿ' | repeat=0 | modifiers=0}
KEYBOARD DEBUG: refresh_device_states(): detected the following changed keys:
key 0: 1 -> 0
Closing Myth.
Re: myth versions above 1.6 crash immediatly
The fix for this is now in the repo.
The problem was something on his machine was sending a WM_KEYDOWN with key code 255, which is some kind of fake key or escape code. Myth was looking up the myth equivalent of this code by doing lookup_table[255], which was out of bounds and ended up reading a zero, which is the code for _key_escape.
The problem was something on his machine was sending a WM_KEYDOWN with key code 255, which is some kind of fake key or escape code. Myth was looking up the myth equivalent of this code by doing lookup_table[255], which was out of bounds and ended up reading a zero, which is the code for _key_escape.
Re: myth versions above 1.6 crash immediatly
Weird, but good job debugging!