I've been trying to use front=0 but get front=-1 in game, also on the 10-29 snapshot. Looks like I have a > where there should have been a >=. It'll be fixed in the next update. To work around it you could put the front=1 treadmark first. As long as there's always a matching treadmark for the front...

If you could search your system for the lastlog.txt file and post it, it might explain why it's closing unexpectedly. Might have the best luck searching for folders named "MX Simulator" and checking them for the lastlog.txt file.

Does it only happen on tracks with treadmarks?

Even at "None" for "Ground Texture Levels"? Did you restart the game after you lowered everything?

AHeckman2 wrote: ↑Sun Jan 07, 2024 4:01 pm

jlv wrote: ↑Fri Jan 05, 2024 1:59 am He's not really selling the template. He's selling the service of typing someone's number into your free template.
Would have been courteous to give you a credit though.

Farout

If it really bothers you I'll take it down. Didn't seem like a big deal to me.

Do you still get the slow frames when you don't move? It it only happens when you're moving try lowering your terrain texture settings.

Best to just have more servers. More servers with less riders in each server will actually use less bandwidth than one server with the same total number of riders.

AHeckman2 wrote: ↑Thu Jan 04, 2024 7:30 pm lol trying to send the template I released for free? See how far that gets you

He's not really selling the template. He's selling the service of typing someone's number into your free template.

Would have been courteous to give you a credit though.

38823 and 39083 are now name locked.

Not sure where this would be located in Crossover but it'd be interesting to see what the lastlog.txt file looked like for the newer snapshots that don't run. Might just take adding "--glversion 4.1core" to the command line to get it going.

I don't have an ARM version of MXS currently. (The switch uses an ARM CPU.) Might be possible using an emulator.

He's muted and name locked.

Read a little more and it looks like they only support newer OpenGL when opened as a core context. So you might have better luck with the newer snapshots which ask for a 3.1 core context by default. Is there any indication of why the newer snapshots aren't starting?

If it only supports OpenGL 2.1 it'll be almost impossible to support. OpenGL 2.1 is 17 years old. Not sure what Apple is thinking providing such terrible OpenGL support.

Not sure about it but it might be different if you install XQuartz and have Wine use that instead of native Mac rendering.

When you type /saveframetimes in the chat screen, what frame times are you seeing in %localappdata%\MX Simulator\frametimes.txt?