You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whilst this loss of precision may be fine when working with local coordinate transformations, it isn't if you want to place objects accurately in geospatial applications.
Request has been made to change the System.Numerics.Matrix4x4 API here, but doesn't appear to be being addressed anytime soon.
* Added System.DoubleNumerics to the core project
Converted Transform.cs to use System.DoubleNumerics
Added a new TransformTests.cs file to test the new transform class
Changed Converters to use System.DoubleNumerics
* Adds handling of new System.DoubleNumerics matrix4x4 to serializer and deserializer
* Update ConverterNavisworks.Geometry.cs
* updates transform methods in rhino and revit
* test(core): Tests matrix serialisation
* Added log for backwards compatibility usage
---------
Co-authored-by: Claire Kuang <[email protected]>
Co-authored-by: Jedd Morgan <[email protected]>
The conversion of the Transform class to use System.Numerics.Matrix4x4 results in a loss of precision as this uses floats instead of doubles.
The change was introduced in #2159.
Whilst this loss of precision may be fine when working with local coordinate transformations, it isn't if you want to place objects accurately in geospatial applications.
Request has been made to change the System.Numerics.Matrix4x4 API here, but doesn't appear to be being addressed anytime soon.
dotnet/runtime#24168
Possible alternative solution is to use the Silk.NET library as mentioned in the comments of the issue above:
https://www.nuget.org/packages/Silk.NET.Maths
The text was updated successfully, but these errors were encountered: