2017-12-28 snapshot

Post anything about MX Simulator here. Please. I'm begging you.
jlv
Site Admin
Posts: 12881
Joined: Fri Nov 02, 2007 5:39 am
Team: No Frills Racing
Contact:

2017-12-28 snapshot

Postby jlv » Fri Dec 29, 2017 1:07 am

Changes:
  • Fixed another no timing gates crash.

Windows users: http://www.mxsimulator.com/snapshots/mx-2017-12-28-1377.exe
Linux users: http://www.mxsimulator.com/snapshots/mxbin-2017-12-28-1377

Replace mx.exe or mxbin with one of the above files. The default location for mx.exe should be "C:\Program Files (x86)\MX Simulator". I'd keep a backup of the originals since these aren't well tested.

You will also need this file for the rmz450 and crf250 models:
http://www.mxsimulator.com/snapshots/zzzqtestzz.zip

If you aren't running a server, ignore everything below this line.

Here are the required servers. (Same as the last snapshot.) You want --min-version 29 to prevent inconsistent erode with old clients.

Windows: http://www.mxsimulator.com/snapshots/mxserver-2017-11-17-1369.exe
Linux: http://www.mxsimulator.com/snapshots/mxserver-2017-11-17-1369
Josh Vanderhoof
Sole Proprietor
jlv@mxsimulator.com
If you email, put "MX Simulator" in the subject to make sure it gets through my spam filter.

jlv
Site Admin
Posts: 12881
Joined: Fri Nov 02, 2007 5:39 am
Team: No Frills Racing
Contact:

Re: 2017-12-28 snapshot

Postby jlv » Fri Dec 29, 2017 1:09 am

This will be the 1.12 exe aside from the version number. This time I mean it!
Josh Vanderhoof
Sole Proprietor
jlv@mxsimulator.com
If you email, put "MX Simulator" in the subject to make sure it gets through my spam filter.

Finalmushroom
Posts: 407
Joined: Sun Jul 16, 2017 10:43 pm
Team: Privateer
Location: Pacific North West

Re: 2017-12-28 snapshot

Postby Finalmushroom » Fri Dec 29, 2017 1:15 am

jlv wrote:This will be the 1.12 exe aside from the version number. This time I mean it!


Lol, grinding this Christmas break!!

User avatar
GustavoMX930'
Posts: 1913
Joined: Wed Jan 04, 2012 11:59 pm
Team: 2 good 4 a team
Contact:

Re: 2017-12-28 snapshot

Postby GustavoMX930' » Fri Dec 29, 2017 11:12 am

Hey! Just got back home and tried the new snapshots you've relased. No success though :( Here are the logs:

mx-2017-12-20-1374

Code: Select all

[0:22:57.31] Logfile "C:/Users/W10/AppData/Local/MX Simulator/lastlog.txt" opened
[0:22:57.31] JUGL 0.31
[0:22:57.32] MX Simulator version 2017-12-20-1374 snapshot
[0:22:58.31] Display scaling disabled via SetProcessDpiAwareness
[0:22:58.33] Registry mode is 1366x768x32@60hz
[0:22:58.33] Found mode 640x480x32@60hz
[0:22:58.33] Found mode 720x480x32@60hz
[0:22:58.33] Found mode 720x576x32@50hz
[0:22:58.33] Found mode 800x600x32@60hz
[0:22:58.33] Found mode 1024x768x32@60hz
[0:22:58.33] Found mode 1152x864x32@30hz
[0:22:58.33] Found mode 1280x720x32@60hz
[0:22:58.34] Found mode 1280x768x32@60hz
[0:22:58.34] Found mode 1280x800x32@30hz
[0:22:58.34] Found mode 1280x960x32@30hz
[0:22:58.34] Found mode 1280x1024x32@30hz
[0:22:58.34] Found mode 1360x768x32@60hz
[0:22:58.34] Found mode 1440x900x32@30hz
[0:22:58.35] Found mode 1600x900x32@30hz
[0:22:58.35] Found mode 1680x1050x32@30hz
[0:22:58.35] Found mode 1920x1080x32@30hz
[0:22:58.43] Options:
[0:22:58.43]  threaded: [off]
[0:22:58.43] Creating window
[0:22:58.46] SetForegroundWindow failed


mx-2017-12-22-1375

Code: Select all

[0:24:01.73] Logfile "C:/Users/W10/AppData/Local/MX Simulator/lastlog.txt" opened
[0:24:01.73] JUGL 0.31
[0:24:01.74] MX Simulator version 2017-12-22-1375 snapshot
[0:24:02.69] Display scaling disabled via SetProcessDpiAwareness
[0:24:02.70] Registry mode is 1366x768x32@60hz
[0:24:02.70] Found mode 640x480x32@60hz
[0:24:02.70] Found mode 720x480x32@60hz
[0:24:02.70] Found mode 720x576x32@50hz
[0:24:02.70] Found mode 800x600x32@60hz
[0:24:02.71] Found mode 1024x768x32@60hz
[0:24:02.71] Found mode 1152x864x32@30hz
[0:24:02.71] Found mode 1280x720x32@60hz
[0:24:02.71] Found mode 1280x768x32@60hz
[0:24:02.71] Found mode 1280x800x32@30hz
[0:24:02.71] Found mode 1280x960x32@30hz
[0:24:02.71] Found mode 1280x1024x32@30hz
[0:24:02.71] Found mode 1360x768x32@60hz
[0:24:02.71] Found mode 1440x900x32@30hz
[0:24:02.72] Found mode 1600x900x32@30hz
[0:24:02.72] Found mode 1680x1050x32@30hz
[0:24:02.72] Found mode 1920x1080x32@30hz
[0:24:02.80] Options:
[0:24:02.80]  threaded: [off]
[0:24:02.80] Creating window
[0:24:02.82] Foregrounded and locked


mx-2017-12-28-1377

Code: Select all

[0:24:54.04] Logfile "C:/Users/W10/AppData/Local/MX Simulator/lastlog.txt" opened
[0:24:54.04] JUGL 0.31
[0:24:54.05] MX Simulator version 2017-12-28-1377 snapshot
[0:24:54.99] Display scaling disabled via SetProcessDpiAwareness
[0:24:55.01] Registry mode is 1366x768x32@60hz
[0:24:55.01] Found mode 640x480x32@60hz
[0:24:55.01] Found mode 720x480x32@60hz
[0:24:55.01] Found mode 720x576x32@50hz
[0:24:55.01] Found mode 800x600x32@60hz
[0:24:55.01] Found mode 1024x768x32@60hz
[0:24:55.01] Found mode 1152x864x32@30hz
[0:24:55.01] Found mode 1280x720x32@60hz
[0:24:55.01] Found mode 1280x768x32@60hz
[0:24:55.01] Found mode 1280x800x32@30hz
[0:24:55.01] Found mode 1280x960x32@30hz
[0:24:55.02] Found mode 1280x1024x32@30hz
[0:24:55.02] Found mode 1360x768x32@60hz
[0:24:55.02] Found mode 1440x900x32@30hz
[0:24:55.02] Found mode 1600x900x32@30hz
[0:24:55.02] Found mode 1680x1050x32@30hz
[0:24:55.03] Found mode 1920x1080x32@30hz
[0:24:55.10] Options:
[0:24:55.10]  threaded: [off]
[0:24:55.11] Creating window
[0:24:55.13] Foregrounded and locked


It's funny. The first one crashes at a different stage than the other two. Any guesses?
jlv wrote:
Rush wrote:Why was UID 12235 not banned as well? he was doing the same thing.

Because he didn't come in here and confess like an idiot.

jlv
Site Admin
Posts: 12881
Joined: Fri Nov 02, 2007 5:39 am
Team: No Frills Racing
Contact:

Re: 2017-12-28 snapshot

Postby jlv » Sat Dec 30, 2017 2:18 am

GustavoMX930' wrote:Hey! Just got back home and tried the new snapshots you've relased. No success though :( Here are the logs:

mx-2017-12-20-1374

Code: Select all

[0:22:57.31] Logfile "C:/Users/W10/AppData/Local/MX Simulator/lastlog.txt" opened
[0:22:57.31] JUGL 0.31
[0:22:57.32] MX Simulator version 2017-12-20-1374 snapshot
[0:22:58.31] Display scaling disabled via SetProcessDpiAwareness
[0:22:58.33] Registry mode is 1366x768x32@60hz
[0:22:58.33] Found mode 640x480x32@60hz
[0:22:58.33] Found mode 720x480x32@60hz
[0:22:58.33] Found mode 720x576x32@50hz
[0:22:58.33] Found mode 800x600x32@60hz
[0:22:58.33] Found mode 1024x768x32@60hz
[0:22:58.33] Found mode 1152x864x32@30hz
[0:22:58.33] Found mode 1280x720x32@60hz
[0:22:58.34] Found mode 1280x768x32@60hz
[0:22:58.34] Found mode 1280x800x32@30hz
[0:22:58.34] Found mode 1280x960x32@30hz
[0:22:58.34] Found mode 1280x1024x32@30hz
[0:22:58.34] Found mode 1360x768x32@60hz
[0:22:58.34] Found mode 1440x900x32@30hz
[0:22:58.35] Found mode 1600x900x32@30hz
[0:22:58.35] Found mode 1680x1050x32@30hz
[0:22:58.35] Found mode 1920x1080x32@30hz
[0:22:58.43] Options:
[0:22:58.43]  threaded: [off]
[0:22:58.43] Creating window
[0:22:58.46] SetForegroundWindow failed


mx-2017-12-22-1375

Code: Select all

[0:24:01.73] Logfile "C:/Users/W10/AppData/Local/MX Simulator/lastlog.txt" opened
[0:24:01.73] JUGL 0.31
[0:24:01.74] MX Simulator version 2017-12-22-1375 snapshot
[0:24:02.69] Display scaling disabled via SetProcessDpiAwareness
[0:24:02.70] Registry mode is 1366x768x32@60hz
[0:24:02.70] Found mode 640x480x32@60hz
[0:24:02.70] Found mode 720x480x32@60hz
[0:24:02.70] Found mode 720x576x32@50hz
[0:24:02.70] Found mode 800x600x32@60hz
[0:24:02.71] Found mode 1024x768x32@60hz
[0:24:02.71] Found mode 1152x864x32@30hz
[0:24:02.71] Found mode 1280x720x32@60hz
[0:24:02.71] Found mode 1280x768x32@60hz
[0:24:02.71] Found mode 1280x800x32@30hz
[0:24:02.71] Found mode 1280x960x32@30hz
[0:24:02.71] Found mode 1280x1024x32@30hz
[0:24:02.71] Found mode 1360x768x32@60hz
[0:24:02.71] Found mode 1440x900x32@30hz
[0:24:02.72] Found mode 1600x900x32@30hz
[0:24:02.72] Found mode 1680x1050x32@30hz
[0:24:02.72] Found mode 1920x1080x32@30hz
[0:24:02.80] Options:
[0:24:02.80]  threaded: [off]
[0:24:02.80] Creating window
[0:24:02.82] Foregrounded and locked


mx-2017-12-28-1377

Code: Select all

[0:24:54.04] Logfile "C:/Users/W10/AppData/Local/MX Simulator/lastlog.txt" opened
[0:24:54.04] JUGL 0.31
[0:24:54.05] MX Simulator version 2017-12-28-1377 snapshot
[0:24:54.99] Display scaling disabled via SetProcessDpiAwareness
[0:24:55.01] Registry mode is 1366x768x32@60hz
[0:24:55.01] Found mode 640x480x32@60hz
[0:24:55.01] Found mode 720x480x32@60hz
[0:24:55.01] Found mode 720x576x32@50hz
[0:24:55.01] Found mode 800x600x32@60hz
[0:24:55.01] Found mode 1024x768x32@60hz
[0:24:55.01] Found mode 1152x864x32@30hz
[0:24:55.01] Found mode 1280x720x32@60hz
[0:24:55.01] Found mode 1280x768x32@60hz
[0:24:55.01] Found mode 1280x800x32@30hz
[0:24:55.01] Found mode 1280x960x32@30hz
[0:24:55.02] Found mode 1280x1024x32@30hz
[0:24:55.02] Found mode 1360x768x32@60hz
[0:24:55.02] Found mode 1440x900x32@30hz
[0:24:55.02] Found mode 1600x900x32@30hz
[0:24:55.02] Found mode 1680x1050x32@30hz
[0:24:55.03] Found mode 1920x1080x32@30hz
[0:24:55.10] Options:
[0:24:55.10]  threaded: [off]
[0:24:55.11] Creating window
[0:24:55.13] Foregrounded and locked


It's funny. The first one crashes at a different stage than the other two. Any guesses?

It's crashing in the same spot each time. The "Foregrounded and locked" vs "SetForegroundWindow failed" is showing if it successfully became the foreground window which gives it slightly better scheduling priority. It's better if SetForegroundWindow succeeds, but it doesn't have anything to do with the crash.

Looks like the actual crash is happening earlier than I expected, when it loads dinput.dll. Hard to see why it would crash there. Let me finish up 1.12 and I'll give you some more stuff to test. I suspect your dinput.dll file might just be badly corrupted.
Josh Vanderhoof
Sole Proprietor
jlv@mxsimulator.com
If you email, put "MX Simulator" in the subject to make sure it gets through my spam filter.

User avatar
GustavoMX930'
Posts: 1913
Joined: Wed Jan 04, 2012 11:59 pm
Team: 2 good 4 a team
Contact:

Re: 2017-12-28 snapshot

Postby GustavoMX930' » Sat Dec 30, 2017 8:45 am

why would it crash only on the newer snapshots though? It works fine untill 09-01 and on other games :?
jlv wrote:
Rush wrote:Why was UID 12235 not banned as well? he was doing the same thing.

Because he didn't come in here and confess like an idiot.

jlv
Site Admin
Posts: 12881
Joined: Fri Nov 02, 2007 5:39 am
Team: No Frills Racing
Contact:

Re: 2017-12-28 snapshot

Postby jlv » Sun Dec 31, 2017 1:32 am

GustavoMX930' wrote:why would it crash only on the newer snapshots though? It works fine untill 09-01 and on other games :?

That's hard to say. The code in question hasn't been changed. The only thing that might be different for the LoadLibrary call would be the stack position.
Josh Vanderhoof
Sole Proprietor
jlv@mxsimulator.com
If you email, put "MX Simulator" in the subject to make sure it gets through my spam filter.

User avatar
GustavoMX930'
Posts: 1913
Joined: Wed Jan 04, 2012 11:59 pm
Team: 2 good 4 a team
Contact:

Re: 2017-12-28 snapshot

Postby GustavoMX930' » Sun Dec 31, 2017 3:08 am

jlv wrote:The code in question hasn't been changed. The only thing that might be different for the LoadLibrary call would be the stack position.

i've tried replacing my dinput.dll file on my System32 folder because you said it could've been corrupted, but my game still crashes
jlv wrote:
Rush wrote:Why was UID 12235 not banned as well? he was doing the same thing.

Because he didn't come in here and confess like an idiot.

Conner Pate
Posts: 55
Joined: Mon Jan 04, 2016 7:20 am
Team: VlastMX
Contact:

Re: 2017-12-28 snapshot

Postby Conner Pate » Mon Jan 01, 2018 1:17 am

Jlv can u pls just fix front wheel lock it stop's really cool close calls and it messes people up on starts and is just overall stupid i love this game a lot but i just think it could be so much better than it is like it has been out since i believe 2008 love ya jlv lol
Image

jlv
Site Admin
Posts: 12881
Joined: Fri Nov 02, 2007 5:39 am
Team: No Frills Racing
Contact:

Re: 2017-12-28 snapshot

Postby jlv » Mon Jan 01, 2018 2:21 am

GustavoMX930' wrote:
jlv wrote:The code in question hasn't been changed. The only thing that might be different for the LoadLibrary call would be the stack position.

i've tried replacing my dinput.dll file on my System32 folder because you said it could've been corrupted, but my game still crashes

I was thinking about this and it occurred to me that you might have a program installed that intercepts input by preloading a dll to catch directinput calls. If you have anything like that installed it could easily cause the problem.
Josh Vanderhoof
Sole Proprietor
jlv@mxsimulator.com
If you email, put "MX Simulator" in the subject to make sure it gets through my spam filter.

User avatar
GustavoMX930'
Posts: 1913
Joined: Wed Jan 04, 2012 11:59 pm
Team: 2 good 4 a team
Contact:

Re: 2017-12-28 snapshot

Postby GustavoMX930' » Mon Jan 01, 2018 8:50 pm

jlv wrote:I was thinking about this and it occurred to me that you might have a program installed that intercepts input by preloading a dll to catch directinput calls. If you have anything like that installed it could easily cause the problem.


How would i look for programs that would do that. I didn’t install anything at all but a few games like F1 2017, DIRT 3 and Mu Online
jlv wrote:
Rush wrote:Why was UID 12235 not banned as well? he was doing the same thing.

Because he didn't come in here and confess like an idiot.

jlv
Site Admin
Posts: 12881
Joined: Fri Nov 02, 2007 5:39 am
Team: No Frills Racing
Contact:

Re: 2017-12-28 snapshot

Postby jlv » Tue Jan 02, 2018 12:55 am

It'd be a program for controller macros or something of that nature. Sounds like you aren't running anything like that but I thought it was worth mentioning.
Josh Vanderhoof
Sole Proprietor
jlv@mxsimulator.com
If you email, put "MX Simulator" in the subject to make sure it gets through my spam filter.

Motodude622
Posts: 92
Joined: Tue Apr 18, 2017 6:49 pm
Team: Privateer

Re: 2017-12-28 snapshot

Postby Motodude622 » Tue Jan 02, 2018 3:33 am

jlv you should do a tearoff in mx sim like the screen get muddy and you have to hit a button on the keyboard for controller players and click the mouse if you play keyboard that would be sweet
Image

User avatar
GustavoMX930'
Posts: 1913
Joined: Wed Jan 04, 2012 11:59 pm
Team: 2 good 4 a team
Contact:

Re: 2017-12-28 snapshot

Postby GustavoMX930' » Tue Jan 02, 2018 3:40 pm

jlv wrote:It'd be a program for controller macros or something of that nature. Sounds like you aren't running anything like that but I thought it was worth mentioning.

The only thing i'd have that has anything to do with Macros would be Razer Synapse for my keyboard. I tried uninstalling it to see if it would make any difference but no luck. I also tried downloading Xpadder to see if it would modificate anything at all but still didnt work
jlv wrote:
Rush wrote:Why was UID 12235 not banned as well? he was doing the same thing.

Because he didn't come in here and confess like an idiot.

User avatar
TeamHavocRacing
Posts: 6706
Joined: Thu Nov 19, 2009 5:52 am
Team: Havoc Racing

Re: 2017-12-28 snapshot

Postby TeamHavocRacing » Tue Jan 02, 2018 7:56 pm

Conner Pate wrote:Jlv can u pls just fix front wheel lock it stop's really cool close calls and it messes people up on starts and is just overall stupid

It prevents the punting that is such a cornerstone of many kids style. It should never go away. Obviously, you weren't around when this it was so much worse.
jlv wrote:I disagree with your disagreement.


Return to “General Discussion”

Who is online

Users browsing this forum: No registered users and 9 guests