So, they started out as tangent, and after the match it’s now positional. Is this another example of Rhino not working well with rational things? I think there should at least be some sort of warning here, and not just a silent fail… (also, not just an “out of tolerance” warning, but a why as well, since in this case, the reason is rational to non-rational matching?)
Windows 10.0.19043 SR0.0 or greater (Physical RAM: 64Gb)
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 2080 Ti (NVidia) Memory: 11GB, Driver date: 8-5-2021 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 471.68
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 8-5-2021
Driver Version: 30.0.14.7168
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 11 GB
Rhino plugins that do not ship with Rhino
C:\Program Files\Orca3D V2\Orca3D.rhp “Orca3D” 2.0.22.0