I notice in the PR that created this API that we cast a very large number to an int, when it should probably be a long long (m_nPutDoubleFactor). I stongly suspect this will fix the issue.
This issue could be fixed by doing the above but really it would be nicer to allow doubles to be input (this issue)
Or nicer still, store the vertex values (and everything else) in binary instead of XML and lose no data as a result.
Below is a table showing the sudden change in vertex values beyond 9 decimal places, values 6-9 work as expected but suddenly the values change at 10:
I notice in the PR that created this API that we cast a very large number to an int, when it should probably be a long long (m_nPutDoubleFactor). I stongly suspect this will fix the issue.
This issue could be fixed by doing the above but really it would be nicer to allow doubles to be input (this issue)
Or nicer still, store the vertex values (and everything else) in binary instead of XML and lose no data as a result.