MX Simulator

Changes:

• mx.paste_custom_frame now blends instead of copying pixels.
• Increased max bones to 32.
• Added new Javascript functions - mx.get_bike_model(slot), mx.get_elevation(x, z), mx.move_billboard(index, x, y, z) and mx.color_billboard(index, r, g, b, a).
• Fixed some potential buffer overflow bugs.
• Fixed Y value not working in mx.move_statue.
• Now processes less erode events per step when lots of erode events happen simultaneously for smoother FPS.

Windows users: http://mxsimulator.com/snapshots/mx-2019-01-26-1446.exe
Linux users: http://mxsimulator.com/snapshots/mxbin-2019-01-26-1446

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.

Thank you jlv

Still no 2019 models

Thank you JLV, you da man

vengefuluoto420 wrote:Still no 2019 models

Not a priority.

jlv wrote:Now processes less erode events per step when lots of erode events happen simultaneously for smoother FPS.

Help!

vengefuluoto420 wrote:Still no 2019 models

2019 models when you hit 1000 posts.

DJ99X wrote:Help!

loool what the hell

this is broke I dont have permission to put it in my game am i doing something wrong?

jlv wrote:Changes:

• Increased max bones to 32.

What does that means? I'm not sure I understand it

mxs4crf wrote:

jlv wrote:Changes:

• Increased max bones to 32.

What does that means? I'm not sure I understand it

It allows for more fluid coding of movement within the javascript animations. Like folding your elbow vs. your finger.

does this mean we would be able to have SpiderCam??

Is mx.get_elevation looking at the compressed terrain or the full resolution?

DJ99X wrote:Is mx.get_elevation looking at the compressed terrain or the full resolution?

'x', 'z' and the returned elevation are in feet.