What controls the number of decimal digits of numbers in the command line; in particular coordinates? I remember changing it to 17 during a forum discussion about accuracy and would like to change it back to something more reasonable like 5.
I think it’s in Options > Units > Distance display > Display Precision
Any luck?
Not it.
Update: This works in V7 but not in V8.10
Command line history:
Command: _Length
Select curves to measure ( Units=Model_Units SubCurve )
Select curves to measure. Press Enter when done ( Units=Model_Units SubCurve )
Length = 255.27999999999997
Command: _EvaluatePt
Point to evaluate ( Label=Off )
Point in world coordinates = 473.08686968854147,796.30874307034048,0 CPlane coordinates = 473.08686968854147,796.30874307034048,0
Rhino 8 SR10 2024-7-23 (Rhino 8, 8.10.24205.13001, Git hash:master @ 20bc3267cc7d3ea766e91bec2ff8ef5ff8fb1755)
License type: Commercial, build 2024-07-23
License details: Cloud Zoo
Windows 11 (10.0.22631 SR0.0) or greater (Physical RAM: 64GB)
.NET 7.0.20
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 2080 Ti (NVidia) Memory: 11GB, Driver date: 12-6-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 546.33
> 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: 12-6-2023
Driver Version: 31.0.15.4633
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
Rhino plugins that ship with Rhino
C:\Program Files\Rhino 8\Plug-ins\Commands.rhp “Commands” 8.10.24205.13001
C:\Program Files\Rhino 8\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 8\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 8\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 8\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 8\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 8.10.24205.13001
C:\Program Files\Rhino 8\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 8.10.24205.13001
C:\Program Files\Rhino 8\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 8\Plug-ins\MeshCommands.rhp “MeshCommands” 8.10.24205.13001
C:\Program Files\Rhino 8\Plug-ins\RhinoCycles.rhp “RhinoCycles” 8.10.24205.13001
C:\Program Files\Rhino 8\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 8.10.24205.13001
C:\Program Files\Rhino 8\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 8\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino 8\Plug-ins\SectionTools.rhp “SectionTools”
That’s a per document setting (and does not allow 17 places). Are you seeing long decimals in all documents? Could this have been set with a test command?
Edit: Found it! TestNumberFormat
Yes, I was seeing the long format in all documents.
TestNumberFormat is the solution. It has two settings: Accurate and Pretty. Accurate always results in 17 decimals while Pretty uses the seting in Options > Units > Distance display > Display Precision.
I had used the test command during a previous discussion about accuracy, and forgot about it.
Thank you.