There's an apparent bug where the x height_map_size wasn't referenced, instead y was referenced twice. I had a heightmap where x < y, causing this issue to become apparent when the heightmap is modified. I didn't see any open issue or instructions that I need to open an issue first, so I just opened the PR. I'm newly unemployed, so if there's a process I'm missing please let me know. I will likely have more PRs and issues to contribute soon.
mrDIMAS
commented
4 months ago
There's an apparent bug where the x height_map_size wasn't referenced, instead y was referenced twice. I had a heightmap where x < y, causing this issue to become apparent when the heightmap is modified. I didn't see any open issue or instructions that I need to open an issue first, so I just opened the PR. I'm newly unemployed, so if there's a process I'm missing please let me know. I will likely have more PRs and issues to contribute soon.