When creating a solid (cylinder, sphere, etc.) the numerical input field isn’t working properly. You CAN enter the values for a cube. But for anything else, the input field can’t be cleared and typing a value doesn’t accept input properly. Thank you!
Hi BuzzLightYear. Please run systeminfo in the Rhino command line and post the result, thanks.
Sure Japhy - here’s the sysinfo. Thank you.
Rhino 8 SR29 2026-3-4 (Rhino 8, 8.29.26063.11002, Git hash:master @ bbd126f84fcdaf7a974615b7c9f4f8667571c147)
License type: Commercial, build 2026-03-04
License details: Cloud Zoo
Apple macOS Version 26.3 (Build 25D125) (Physical RAM: 16GB)
Mac Model Identifier: Mac16,10
Language: en-US (MacOS default)
.NET 8.0.14
Metal GPU Family Apple 7
Metal GPU Family Common 3
Metal GPU Family Mac 2
Graphics processors
Apple M4
LG FULL HD (1920 x 1080 @ 75.00Hz)
LG FULL HD (1920 x 1080 @ 75.00Hz)
GPU Vendor: Apple
USB devices
Apple: USB3 Gen2 Hub
Apple Inc.: iPhone
SanDisk: Extreme Pro 55AF
xxxxxxxx: USB Type-C Digital AV Adapter
Mitsumi Electric: Apple Extended USB Keyboard
Logitech: USB Optical Mouse
VIA Labs, Inc.: USB Billboard Device
Generic: USB3.0 Card Reader
Realtek: USB 10/100/1000 LAN
Bluetooth devices
None
Third party kernel extensions
None
Third party plugins
/usr/lib/swift/libswiftCore.dylib
/usr/lib/swift/libswiftObjectiveC.dylib
/usr/lib/swift/libswiftCoreFoundation.dylib
/usr/lib/swift/libswiftDarwin.dylib
/usr/lib/swift/libswiftDispatch.dylib
/usr/lib/swift/libswiftIOKit.dylib
/usr/lib/swift/libswiftSystem.dylib
/usr/lib/swift/libswiftXPC.dylib
/usr/lib/swift/libswift_Builtin_float.dylib
/usr/lib/swift/libswift_Concurrency.dylib
/usr/lib/swift/libswift_DarwinFoundation1.dylib
/usr/lib/swift/libswift_StringProcessing.dylib
/usr/lib/swift/libswiftos.dylib
/usr/lib/swift/libswiftDistributed.dylib
/usr/lib/swift/libswiftObservation.dylib
/usr/lib/swift/libswiftSynchronization.dylib
/usr/lib/swift/libswiftOSLog.dylib
/usr/lib/swift/libswiftsimd.dylib
/usr/lib/swift/libswift_RegexParser.dylib
/usr/lib/swift/libswiftMetal.dylib
/usr/lib/swift/libswiftQuartzCore.dylib
/usr/lib/swift/libswiftUniformTypeIdentifiers.dylib
/usr/lib/swift/libswiftAccelerate.dylib
/usr/lib/swift/libswiftCoreImage.dylib
/usr/lib/swift/libswiftCoreAudio.dylib
/usr/lib/swift/libswiftCoreMIDI.dylib
/usr/lib/swift/libswift_DarwinFoundation2.dylib
/usr/lib/swift/libswift_DarwinFoundation3.dylib
/usr/lib/swift/libswiftCompression.dylib
/usr/lib/swift/libswiftCoreLocation.dylib
/usr/lib/swift/libswiftRegexBuilder.dylib
/usr/lib/swift/libswiftCoreMedia.dylib
/usr/lib/swift/libswiftAVFoundation.dylib
/usr/lib/swift/libswiftNaturalLanguage.dylib
/usr/lib/swift/libswiftMLCompute.dylib
/usr/lib/swift/libswiftCoreGraphics.dylib
/usr/lib/swift/libswiftFoundation.dylib
/usr/lib/swift/libswiftSwiftOnoneSupport.dylib
/usr/lib/swift/libswiftsys_time.dylib
/usr/lib/swift/libswiftSpatial.dylib
/usr/lib/usd/libusd_ms.dylib
/usr/lib/swift/libswift_errno.dylib
/usr/lib/swift/libswiftIntents.dylib
/usr/lib/swift/libswiftVideoToolbox.dylib
/usr/lib/swift/libswiftCoreMediaIO.dylib
/usr/lib/swift/libswiftCallKit.dylib
/usr/lib/swift/libswiftPassKit.dylib
/usr/lib/swift/libswiftAppleArchive.dylib
/usr/lib/updaters/libAppleTconUARPUpdater.dylib
/usr/lib/updaters/libT200Updater.dylib
/usr/lib/swift/libswiftDemangle.dylib
/usr/lib/swift/libswiftGLKit.dylib
/usr/lib/swift/libswiftMetalKit.dylib
/usr/lib/swift/libswiftModelIO.dylib
/usr/lib/swift/libswiftSceneKit.dylib
/usr/lib/swift/libswiftExtensionFoundation.dylib
/usr/lib/swift/libswiftGameplayKit.dylib
/usr/lib/swift/libswiftSpriteKit.dylib
/usr/lib/swift/libswiftMapKit.dylib
Rhino plugins that do not ship with Rhino
Rhino plugins that ship with Rhino
/Applications/Rhino 8.app/Contents/Frameworks/RhMaterialEditor.framework “Renderer Development Kit” 8.29.26063.1002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/Commands.rhp “Commands” 8.29.26063.11002
/Applications/Rhino 8.app/Contents/PlugIns/NamedSnapshots.rhp “Snapshots” 8.29.26063.1002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RDK_EtoUI.rhp “RDK_EtoUI” 8.29.26063.11002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/MeshCommands.rhp “MeshCommands” 8.29.26063.11002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoRenderCycles.rhp “Rhino Render” 8.29.26063.11002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCycles.rhp “RhinoCycles” 8.29.26063.11002
/Applications/Rhino 8.app/Contents/PlugIns/AnimationTools.rhp “AnimationTools” 8.29.26063.1002
/Applications/Rhino 8.app/Contents/PlugIns/SectionTools.rhp “SectionTools” 8.29.26063.1002
/Applications/Rhino 8.app/Contents/PlugIns/RhinoRender.rhp “Legacy Rhino Render” 8.29.26063.1002
/Applications/Rhino 8.app/Contents/PlugIns/Displacement.rhp “Displacement” 8.29.26063.1002
/Applications/Rhino 8.app/Contents/PlugIns/PanelingTools.rhp “PanelingTools” 8.29.26063.1002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoDLR_Python.rhp “IronPython” 8.29.26063.11002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/GrasshopperPlugin.rhp “Grasshopper” 8.29.26063.11002
/Applications/Rhino 8.app/Contents/Frameworks/RhCore.framework/Resources/ManagedPlugIns/RhinoCodePlugin.rhp “RhinoCodePlugin” 8.29.26063.11002
Hi Japhy - Were you able to confirm this bug in the command line? I can’t seem to enter ANY numerical entries there for object creation. The only way I can struggle around it is to use the Arrow Keys to move the cursor to the extreme right, then backspace delete all values, then type in numbers. But even then sometimes it won’t accept my input. Very difficult to use when you can’t enter data…. Thnx.
Hi Buzz -
Just to make sure, you shouldn’t have to mess with that input field at all. When the command is running, Rhino knows where the keyboard input needs to go.
Does placing the mouse cursor somewhere in the center of a viewport and then only using the keyboard to create a cylinder work? That is, for example, type Cylinder, then type 0 (or 10,10) and Enter, then 20 and Enter, and finally 40 and Enter.
If that doesn’t work, could you record your sceen while doing the above and post that video here?
-wim
Hi Wim - No, placing the cursor in the viewport and entering numbers followed by Return or Enter doesn’t work. I can make a video, but you won’t SEE anything. An incorrect cylinder will be created but only using the first single digit I enter. Clicking in the Enter Field doesn’t do anything - it is inactive. Double clicking the field doesn’t “select all” or clear the number there. Click/dragging the mouse in the entry field does’t select all the characters to delete/replace them. If I select Cylinder creation and type “0” (not selecting the Entry field) and hit return, the field WILL then accept a single digit entry followed by Return, but not a double digit (i.e., if I type “10”, it only accepts “1” and then finished the cylinder without even asking for another digit). A video won’t show my fingers entering the numbers on my keyboard, and the recording won’t give you any further information (because nothing happens on screen). The text entry field is “almost” useless and doesn’t respond to the mouse or keyboard (whether you click the mouse there or not). However…, if I use the Arrow Keys to move the cursor to the extreme right in the Entry Field, then backspace/delete away the default numbers, and then type the values I want, it will create the cylinder (or whatever). But you have to do the “backspace maneuver” three times. Are you unable to produce this problem on the latest MacMini (recently purchased) running Tahoe 26.3? Can you simply type in numbers in the field normally, or type them without even selecting the Entry Field? I can’t. Thank you!
Hi Wim - Sorry to keep coming back with the same questions, but I had to return to v6 to do work because I still can’t enter data in v8 (as per above thread). On my old Intel Mac (MacOS 10.13.6 High Sierra), my data entry fields work normally (I can move the cursor, select all, etc..), or I can just type in numbers as you described above using the keyboard alone. I can’t really say this another way, but v8 is completely useless if I can’t enter exact dimensions (especially for software that probably has 16+ significant figure internal accuracy!). Did you confirm that you COULD enter data normally on a new MacMini running Tahoe 26.3? My mouse doesn’t activate the data fields, if I type in “23” it only takes the “2” and then completes the tool, trying to move the cursor in the field doesn’t work and double clicking doesn’t select the entire field, etc.. In short, the data entry dialog doesn’t work at all, and the data isn’t being accepted if the mouse is in the center of the window and I just start typing numbers. Can you please let me know if your copy works fine on a MacMini M4 Tahoe 26.3? I’m kinda stuck here and it’s rather concerning…
Hi Wim - Did you get my massage about uploading a video of this problem? I made one, but it will require a download site (it’s a bit large). But it illustrates the problem clearly and you really should view it. If others are having the same problem inputing data in dialog boxes, they won’t be able to use the software either. Thanks for letting me know where to upload the video.