Install Problem - Help Please

[attacker5]

SO i switched pcs to a new Alienware m15x 64bit, now i got a new 1.4 installer from JLV and installed the game, when i click the desktop icon to launch it, a dialog appears "mx.exe has stopped working, windows is checking for a solution to the problem." and teh game closes, well it never even started, and im left with nothing, any help please?

[jlv]

Here's the last Alienware topic. In that case there was a driver called "G2 Desktop" that was causing the crash.

[attacker5]

Thx but i donbtr seem to have such thing as g2 desktop

her is my lastlog file, any help would be appreciated thx.

[0:12:14.48] Options:
[0:12:14.48] threaded: [off]
[0:12:14.48] Creating window
[0:12:14.80] DirectInput roll call...
[0:12:14.82] Mouse (Mouse)
[0:12:14.82] 3 axes, 5 keys
[0:12:14.82] axis 0 is relative
[0:12:14.82] axis 1 is relative
[0:12:14.82] axis 2 is relative
[0:12:14.88] Keyboard (Keyboard)
[0:12:14.88] 0 axes, 109 keys
[0:12:14.89] Microsoft eHome Infrared Transceiver (Microsoft eHome Infrared Transceiver)
[0:12:14.89] 0 axes, 0 keys
[0:12:14.90] Microsoft eHome Infrared Transceiver (Microsoft eHome Infrared Transceiver)
[0:12:14.90] 0 axes, 573 keys
[0:12:14.91] Wow! This thing has a lot of buttons!
The first ignored button is called "Button 500"
[0:12:14.91] Button count (573) doesn't match actual number of buttons (500)
[0:12:14.91] Microsoft eHome Infrared Transceiver (Microsoft eHome Infrared Transceiver)
[0:12:14.91] 0 axes, 0 keys
[0:12:14.92] Microsoft eHome Infrared Transceiver (Microsoft eHome Infrared Transceiver)
[0:12:14.92] 0 axes, 256 keys
[0:12:14.93] HP Wireless Eco-Comfort Mobile Mouse (HP Wireless Eco-Comfort Mobile Mouse)
[0:12:14.93] 0 axes, 0 keys


Im no expert but i think it might be something to do with too many buttons?

[jlv]

The too many buttons thing is normal. Can you post the entire lastlog.txt file? Knowing the last thing that happens before the crash will help me guess what's happening.

[attacker5]

Sure,


[18:01:21.76] Logfile "C:/Users/Ramon Brand/AppData/Local/MX Simulator/lastlog.txt" opened
[18:01:21.76] JUGL 0.31
[18:01:21.79] Registry mode is 1600x900x32@60hz
[18:01:21.79] Found mode 640x480x32@60hz
[18:01:21.79] Found mode 720x480x32@60hz
[18:01:21.79] Found mode 720x576x32@60hz
[18:01:21.79] Found mode 800x600x32@60hz
[18:01:21.79] Found mode 1024x768x32@60hz
[18:01:21.79] Found mode 1088x612x32@60hz
[18:01:21.79] Found mode 1152x864x32@60hz
[18:01:21.79] Found mode 1280x720x32@60hz
[18:01:21.79] Found mode 1280x768x32@60hz
[18:01:21.79] Found mode 1280x800x32@60hz
[18:01:21.80] Found mode 640x480x16@60hz
[18:01:21.80] Found mode 720x480x16@60hz
[18:01:21.80] Found mode 720x576x16@60hz
[18:01:21.80] Found mode 800x600x16@60hz
[18:01:21.80] Found mode 1024x768x16@60hz
[18:01:21.80] Found mode 1088x612x16@60hz
[18:01:21.80] Found mode 1152x864x16@60hz
[18:01:21.80] Found mode 1280x720x16@60hz
[18:01:21.80] Found mode 1280x768x16@60hz
[18:01:21.80] Found mode 1280x800x16@60hz
[18:01:21.80] Found mode 1600x900x16@60hz
[18:01:21.80] Found mode 640x480x8@60hz
[18:01:21.80] Found mode 720x480x8@60hz
[18:01:21.80] Found mode 720x576x8@60hz
[18:01:21.80] Found mode 800x600x8@60hz
[18:01:21.80] Found mode 1024x768x8@60hz
[18:01:21.80] Found mode 1088x612x8@60hz
[18:01:21.80] Found mode 1152x864x8@60hz
[18:01:21.80] Found mode 1280x720x8@60hz
[18:01:21.80] Found mode 1280x768x8@60hz
[18:01:21.80] Found mode 1280x800x8@60hz
[18:01:21.80] Found mode 1600x900x8@60hz
[18:01:21.81] Options:
[18:01:21.81] threaded: [off]
[18:01:21.81] Creating window
[18:01:22.22] DirectInput roll call...
[18:01:22.23] Mouse (Mouse)
[18:01:22.23] 3 axes, 5 keys
[18:01:22.23] axis 0 is relative
[18:01:22.23] axis 1 is relative
[18:01:22.23] axis 2 is relative
[18:01:22.23] Keyboard (Keyboard)
[18:01:22.23] 0 axes, 109 keys
[18:01:22.24] Microsoft eHome Infrared Transceiver (Microsoft eHome Infrared Transceiver)
[18:01:22.24] 0 axes, 0 keys
[18:01:22.24] Microsoft eHome Infrared Transceiver (Microsoft eHome Infrared Transceiver)
[18:01:22.25] 0 axes, 573 keys
[18:01:22.25] Wow! This thing has a lot of buttons!
The first ignored button is called "Button 500"
[18:01:22.25] Button count (573) doesn't match actual number of buttons (500)
[18:01:22.26] Microsoft eHome Infrared Transceiver (Microsoft eHome Infrared Transceiver)
[18:01:22.26] 0 axes, 0 keys
[18:01:22.26] Microsoft eHome Infrared Transceiver (Microsoft eHome Infrared Transceiver)
[18:01:22.26] 0 axes, 256 keys
[18:01:22.27] HP Wireless Eco-Comfort Mobile Mouse (HP Wireless Eco-Comfort Mobile Mouse)
[18:01:22.27] 0 axes, 0 keys
[18:01:22.28] APT-USB-3 (APT-USB-3)
[18:01:22.28] 6 axes, 35 keys
[18:01:22.28] axis 0 is absolute
[18:01:22.28] axis 1 is absolute
[18:01:22.28] axis 2 is absolute
[18:01:22.28] axis 3 is absolute
[18:01:22.28] axis 4 is absolute
[18:01:22.28] axis 5 is absolute
[18:01:22.28] Adding axis "APT-USB-3 axis 0"
[18:01:22.28] Adding axis "APT-USB-3 axis 1"
[18:01:22.28] Adding axis "APT-USB-3 axis 2"
[18:01:22.28] Adding axis "APT-USB-3 axis 3"
[18:01:22.28] Adding axis "APT-USB-3 axis 4"
[18:01:22.28] Adding axis "APT-USB-3 axis 5"

[jlv]

Try this:

http://mxsimulator.com/snapshots/mx-2011-02-19.exe

Save it to your install folder and run it.

If it still doesn't work, copy the following script to your install folder and run it.

http://mxsimulator.com/junk/nodinput.bat

[attacker5]

Genious, thank you so much,
the exe did not work, but the bat did, how would i go about getting it to a exe so i can run it from my desktop?

Out of curiosity, what was the problem? if it isnt too complex

[attacker5]

I have also noticed that my controller doesnt seem to work on it, and it used to work, does the bat you gave me exclude controlls or something?

[jlv]

That one skips the DirectInput device enumeration. You have a driver crashing when the game asks it how many buttons and axes it has.

I'll post another exe in a bit that will log more info and hopefully I'll be able to figure out which device it's crashing on and skip it.

[jlv]

Give this a shot. This will ignore all DirectInput devices that aren't joysticks.

http://mxsimulator.com/snapshots/mx-2011-02-20.exe

[attacker5]

Awesome, ur a legend, it works and my controller also works, but now what will happen when i download a future snapshot?
BTW, thank you so much.

[jlv]

These changes will be in future versions too.

[attacker5]

Oh right sweet, thank you for everything.

[sesto5]

jlv, i tried this but the only one that worked was the nodinput.bat but i couldn't use a controller with it.

[jlv]

Post the lastlog.txt file. Also, does it work if you unplug your controller?