Windows 7 64 - MXS won't open

[doubledragoncc]

Quick question, where r u? Its better to talk on phone and I can talk to you and maybe help. No probs where you r.

[suzuki98]

I have it on my windows 7 64bit it works fine i have it in the program files (x86) folder is that where you have yours installed

[Red619]

Werent you on 19802 last night prologue?

[jlv]

I just got a new laptop (Alienware m11x) and I can't get MXS to open. The drivers that are installed are the newest available for this laptop (has switchable graphics) but are version 188.XX. I've tried with both the integrated Intel 4500mhd graphics and with the nVidia 335M and both behave the same way. I tried using some driver cleanup software as was recommended in another thread and it just wiped out my drivers so nothing would work (didn't recognize the cards anymore). Here is my last log:

[0:10:05.86] Logfile "C:/Users/Person/AppData/Local/MX Simulator/lastlog.txt" opened
[0:10:05.86] JUGL 0.31
[0:10:05.90] Registry mode is 1366x768x32@60hz
[0:10:05.90] Found mode 320x200x8@60hz
[0:10:05.90] Found mode 320x200x16@60hz
[0:10:05.90] Found mode 320x200x32@60hz
[0:10:05.90] Found mode 320x240x8@60hz
[0:10:05.90] Found mode 320x240x16@60hz
[0:10:05.90] Found mode 320x240x32@60hz
[0:10:05.90] Found mode 400x300x8@60hz
[0:10:05.90] Found mode 400x300x16@60hz
[0:10:05.90] Found mode 400x300x32@60hz
[0:10:05.90] Found mode 512x384x8@60hz
[0:10:05.90] Found mode 512x384x16@60hz
[0:10:05.90] Found mode 512x384x32@60hz
[0:10:05.90] Found mode 640x400x8@60hz
[0:10:05.90] Found mode 640x400x16@60hz
[0:10:05.90] Found mode 640x400x32@60hz
[0:10:05.90] Found mode 640x480x8@60hz
[0:10:05.90] Found mode 640x480x16@60hz
[0:10:05.90] Found mode 640x480x32@60hz
[0:10:05.90] Found mode 800x600x8@60hz
[0:10:05.92] Found mode 800x600x16@60hz
[0:10:05.92] Found mode 800x600x32@60hz
[0:10:05.92] Found mode 1024x768x8@60hz
[0:10:05.92] Found mode 1024x768x16@60hz
[0:10:05.92] Found mode 1024x768x32@60hz
[0:10:05.92] Found mode 1280x600x8@60hz
[0:10:05.92] Found mode 1280x600x16@60hz
[0:10:05.92] Found mode 1280x600x32@60hz
[0:10:05.92] Found mode 1280x720x8@60hz
[0:10:05.92] Found mode 1280x720x16@60hz
[0:10:05.92] Found mode 1280x720x32@60hz
[0:10:05.92] Found mode 1280x768x8@60hz
[0:10:05.92] Found mode 1280x768x16@60hz
[0:10:05.92] Found mode 1280x768x32@60hz
[0:10:05.92] Found mode 1366x768x8@60hz
[0:10:05.92] Found mode 1366x768x16@60hz
[0:10:05.93] Options:
[0:10:05.93] threaded: [off]
[0:10:05.93] Creating window
[0:10:06.15] DirectInput roll call...
[0:10:06.27] Mouse (Mouse)
[0:10:06.27] 3 axes, 5 keys
[0:10:06.27] axis 0 is relative
[0:10:06.27] axis 1 is relative
[0:10:06.27] axis 2 is relative
[0:10:06.27] Keyboard (Keyboard)
[0:10:06.27] 0 axes, 128 keys


I also tried a couple compatibility modes (XP with SP2, SP3) and it does the same thing. I have never owned a computer with windows 7 on it, so I don't know what else could be going wrong here.

If that's the whole log, it died listing out the input devices. Try unplugging your controller.

[Prologue]

Yeah I played last night on my desktop.


There isn't a controller plugged in at all and yeah, that's the whole thing.

[jlv]

When it crashes, get the details. It will help to know the fault module. If the faulting module is mx.exe, the offset will be useful too.

Since the log stopped in the DirectInput device enumeration this is probably going to be a DirectInput problem.

[Prologue]

Files that help describe the problem:
C:\Users\Person\AppData\Local\Temp\WER3AA0.tmp.WERInternalMetadata.xml
C:\Users\Person\AppData\Local\Temp\WER517B.tmp.appcompat.txt
C:\Users\Person\AppData\Local\Temp\WER51CA.tmp.mdmp

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid= ... cid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt



This is after uninstalling and deleting the mxsimulator folder in program files, then reinstalling only a 1.2 install (ran as administrator). No update to 1.3 or anything. The log is the same.

[Prologue]

A little bit more qualitative description is that sometimes the screen will go black for a split second then a broken desktop will show up with a 'waiting' cursor, and it will wait for a long time. If I just wait it doesn't seem to do anything (have waited for a couple minutes once). Then I hit a button and windows says, this isn't responding, wait for it? Then I say no and get kicked back to the desktop. If I click the exe again it will go black then imediately say mx.exe stopped working and that is how I get the details. There aren't any details in the first case, it never offers.

[Prologue]

To answer the location question, yeah it is in the x86 folder. Alsol, I wanted to add that I can see the MXS crosshair when it is in the endless loop state/dark screen state, so something is getting accessed.

[jlv]

It seems similar to yomo's problem from this thread. Except instead of timing out it's hanging. Is there anything weird showing up in the device manager?

[Prologue]

Holy crap, genius. I had some crazy unidentified HID and I disabled it and now we are in business! Thanks jlv.

[yomo]

Yeah I remember that problem.

I have them disabled and around the same time part of my logitech keyboard started to not work. I dont really mind so i never bothered to try and fix it. The number pad on the right hand side doesn't work or some buttons up the very top

[Prologue]

Well, thanks for getting it going, but I am disappointed with the performance. With all setting turned down as far as possible, and then getting as far away from the track as possible, you still get this warping going on. It is like I am dropping a couple frames every second or so. IF I crank the settings to 90, 9, 256, Off, On, On, 90, 10, I still get the same periodic warping, but with much better textures, haha. I tried checking to see if the cpu was doing something crazy by logging it and it does seem to have some periodic spikes but they dont get to 100%. So it doesn't seem to be hardware limitation per se, still I can't figure out what is causing it so it might go back if I can't smooth it out. I am only getting max 60fps though, no matter what setting I have. Even with the better settings it is still pegged at 60. Maybe I'm hitting some sort of rev limiter, haha.

[VRT_RIDEBLUE65]

This is a laptop you said? Looks like a graphics card Issue.Most laptops have very poor graphics cards, perhaps a Graphics memory dump?

[yomo]

Yeah almost certainly a graphics card issue. Latest drivers making sure you get the latest open GL stuff is a must.