Added /saveframetimes command. This saves the frame times in "frametimes.txt".
Fixed Javascript function mx.add_env_sound returning 0 instead of -1 on error.
Removed shader program and terrain render method options - shaders and framebuffer objects are now required.
Rewrote rendering code to only use common subset of OpenGL 3.1 and OpenGL ES 3.0.
Now requires at least OpenGL 3.1 or OpenGL ES 3.0.
Enabled trilinear texture filtering.
Added --glversion command line option.
If you want to use --glversion, it's "--glversion <major version>.<minor version><dialect>", where <dialect> is one of "es", "core" or "compatibility". So for a 4.5 core context it'd be "--glversion 4.5core" or 3.1 es would be "--glversion 3.1es". Probably best to just leave it at the default 3.1core though.
Updated 2021-11-24:
Fixed unlit objects with 0 specular intensity rendering as transparent.
Removed statue wireframes in editor.
Updated 2021-11-25:
Statue wireframes can now be turned on/off in editor.
Wireframes now use GL_LINES instead of GL_LINE_LOOP.
Wireframes now use least detailed LOD instead of most detailed.
Added message in loading screen when it's loading the track script.
Updated 2021-11-26:
Small change in tilemap rendering to remove unnecessary draw calls.
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.
Last edited by jlv on Sun Nov 28, 2021 12:30 am, edited 2 times in total.
Reason:Updated for 2021-11-26
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.
lucasking42 wrote: ↑Tue Nov 23, 2021 3:24 am
In the loading screen, I get to "Loading bikes... done" and my it freezes.
After "loading bikes" but before it reports the texture memory? Might have something to do with the track javascript. Does it happen on every track? Can you post the lastlog.txt file?
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.
Jakob Hubbard wrote: ↑Tue Nov 23, 2021 5:05 am
I’ve seen issues with rendering large objects such as stadiums as well with this new snapshot that I thought I’d add in here
It'd be really helpful to have something specific. What am I looking for and what track makes it happen?
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.
motokid499 wrote: ↑Tue Nov 23, 2021 6:25 am
Something really wrong going on for me, random hitches and slow motion type freezing. FPS displays 124/125 consistently but game is unplayable.
You could get more hitches if you were running 1024x1024 terrain textures in copy mode before since copy mode limits that to 256x256. Now that copy mode is gone if you ask for 1024x1024 you get it along with all the hitches that come with that setting. Run it at 256x256 and it should be the same as before, maybe even a little faster since it avoids the back buffer to texture copy.
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.