Yes, this property works
If I look at the console, I see the version number 1.46.0-dev. Does that mean we will get this fix when v1.46 releases? Or do you plan on releasing a patch for v1.45? It would be a huge help for us if we could get this fix sooner rather than later.
Unfortunately recent engine update broke a few things in our projects as well, particularily on Mac. We’re generating mesh from heightmap using Mesh API, and we’ve started seeing out of range vertices error on Macs, but not on Windows:
Turns out when trying use_local_engine in the editor - this error happens even on old engine versions (I’ve checked as far as 1.40.0), but our old downloaded build works fine (it’s 1.43.1). So something happened during that time - and not only to the engine, but to scene format / launcher as well?
There are WebGl errors, so would take place with any version of the engine.
But yeah, it’s possible we introduced a bug. It’s also possible you already had a bug that wasn’t manifested or that you missed. See if you can give us a repro, and we’ll try to fix it if that’s our side.
Ok guys, false alarm!
Turns out I’ve messed up a row / col loop with indices creation, and and it probably created some NaNs along the way. It can be reproduced in original Terrain from Heighmap project: https://launch.playcanvas.com/1105849
terrain.js → line 86: for (col = 0; col <= options.subdivisions; col++) instead of for (col = 0; col < options.subdivisions; col++)