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". Please note that the ".exe" extension is hidden in Windows so the file will just show as an application named "mx". I'd keep a backup of the originals since these aren't well tested.
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.
You probably want to leave the sub-mesh resolution at 16x16 but if anyone with a slow system wants to benchmark the different settings I'd definitely be interested in seeing the results. (It's 16x16 instead of 33x33 because it's the triangle fan count rather than the vertex count.)
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.
Looking at the terrain wireframe in game looks like the ground sub-mesh resolution is just altering how many polygons are being drawn for the terrain right? Would be interesting to see how this affects performance on my slow laptop. Might do some tests on that later.
No, it changes the granularity it can subdivide at. So at 16x16, if there's a single height element bump somewhere it'll have to draw the surrounding 33x33 area at max detail. At 8x8 it'd only have to do a 17x17 area. At 1x1 it's pretty close to the original way with minimal triangles but lots of draw calls.
Each time you lower it it'll reduce the triangles and increase the draw calls. So on a GPU that's relatively slow at vertex processing the draw call hit might be worth it for the reduced vertex processing. I think most stuff will do best with 16x16 though. I need to do some benchmarks to be sure.
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.
It's a pretty large build plain: 4096 x 4096 Terraininfo file is [11 0.600000 -42.819809 69.746552]
Not sure if it has anything to do with the resolution or if it's just a bug in the newest snapshot.
You mean the blue line right? It looks like it could be a crack due to rounding errors on the GPU.
If you could use a scale that converts to an exact floating point number it might help. Try 0.625 instead if 0.6. Basically you want to use a number where the denominator is a power of 2. So if you're trying to get close to 6/10 your first try would be 5/8 which is 0.625. If you need to be closer, you could try 19/32 = 0.59375.
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.
