MX Simulator

Changes:

• New controller axis detection code to detect axes that have non-zero resting positions.
• Fixed a bug in the scram decoder where it would add null bytes to the end of files.

Updated 2016-05-19:

• Handle triggers that produce both axis and button events.

Windows users: http://mxsimulator.com/snapshots/mx-2016-05-19-1303.exe
Linux users: http://mxsimulator.com/snapshots/mxbin-2016-05-19-1303

You'll also need to extract this in your install folder if you don't have it already:
http://mxsimulator.com/snapshots/zzzrtestzz.zip

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.

what does the first part mean?

It's for triggers that do things like read -1 when they aren't pressed and +1 when pressed. It might work a little better if your controller isn't calibrated well since it now uses first position it reads from the axis as the rest position instead of using 0 like it did before. So if your joystick likes to read .1 when it's centered the game will use that as the center instead of 0. Could be worse too so it definitely needs testing.

Does it automatically update your configuration uopn download and install? Or is there a actual reconfiguration? I dont code so i have no idea how it would work if you didnt have to update your controller I guess if that makes sense. Im @ work now but I use a garbage rockcandy controller and all of those are off a tid bit so Id like to see how this works. Thanks for the update sir

When i download it and do everything it asks I try to start the game it says cant find game data.If anyone knows what is happening please tell me.

DABZZZ wrote:Does it automatically update your configuration uopn download and install? Or is there a actual reconfiguration? I dont code so i have no idea how it would work if you didnt have to update your controller I guess if that makes sense. Im @ work now but I use a garbage rockcandy controller and all of those are off a tid bit so Id like to see how this works. Thanks for the update sir

Derp, Understand now that I read your comment back to the other guy, it jus reads it right away the first time you open that particular snapshot.

It changes the way the axis detection in the "customize controls" menu works. It doesn't affect axes that are already bound.

Thanks, JLV!!

Has this helped anyone's trigger detection?

jlv wrote:Has this helped anyone's trigger detection?

testing now, hopefully i wont lean down the straights when i let go now

It has helped me for sure. I don't have to do the stick flip before the gate drops so my front tire is straight anymore.

jlv wrote:Changes:

• New controller axis detection code to detect axes that have non-zero resting positions.

Would you be able to read simultaneously two different positions from the same axis? Meaning xbox360 controllers triggers. One is from 0 to 1 and the other from 0 to -1 on one axis.

I believe the XBCD driver separates the trigger axes.

vmaki wrote:

jlv wrote:Changes:

• New controller axis detection code to detect axes that have non-zero resting positions.

Would you be able to read simultaneously two different positions from the same axis? Meaning xbox360 controllers triggers. One is from 0 to 1 and the other from 0 to -1 on one axis.

http://forum.mxsimulator.com/viewtopic.php?f=17&t=39872