hi , I have noticed something odd .

I am using the sdk to save out hmp files , I set up a particular test scenario where I arranged 10
terrains next to eachother all down the x axis .

the terrains sizes were 128*128 tiles with a triangle distance of 128 , so that's 163,840 quants along the x axis if I am correct .

I saved each terrain out to file , and viewed them all individually in MED , I discovered that about after 7 terrains , which is 7 * (128*128) , the next subsequent terrains , were all distorted , some seem to have stretched triangles along the x and some seemed to have a combination of stretching along the x plus what seemed to be less tiles along the y .

I thought this might be some mistake on my part , but after setting each terrain to the world centre I found the problem went away , I then tested one terrain against the world centre it were fine, and then also at an offset far along the x which yealded the same problem , the problem then must be the distance or rather precision I suppose ; so okay I know the best is to just save my terrains centred in the world , after that I can place them at those far positions when loaded.

I know about many games with large distances that can run into precision proplems , but is this really enough distance , I mean I don't really know when the quant becomes to far and this does not seem to be that far out for this particular issue , has to be a conversion issue ?

I know theres a conversion from var to float when saving , is this possibly where the issue comes from ?

is it really possible to be a precision issue at 7 *(128*128) quants , when saving the terrain ?

I am no mathematical wiz

thanks