What is volume for surfaces?

Title says it all.

Hatch area shows 0. It is a bug

Is this Rhino for Mac or Rhino for Windows?

It is Windows. Testing version downloaded today

Please post an example file.
If we can repeat the error, we can likely fix it.
Without a specific repeatable example, we can’t fix anything.


@John_Brock For the reported volume I was able to repeat what is occuring for volumes. Example surface attached although it appears to occur with any open surface. RandomSurface.3dm (53.6 KB)

If the Volume command is used to calculate a volume and an open surface is selected then a pop-up message appears warning the the surface is open and the result may be meaningless. The user is asked if they wish to continue. This is appropriate behavior.

If the user selects the Properties panel and the open surface, then selects the Text fields icon in the properties panel and selects Volume the erroneous volume is reported. The result is the same as obtained using the Volume command and continuing after the warning. The difference is Properties > Text fields > Volume does not provide a warning about an open surface. It just goes ahead and reports the erroneous volume.

hatcharea0.3dm (25.3 KB)
recreate : create any hatch --> add attribute fx area --> shows zero

@ivan.galik the hatch area bug should have been fixed in the V7 beta we released yesterday. Are you working with the latest beta?

it shows my version is from yesterday

Please run the SystemInfo and paste the results here. The last “check for updates” in that UI may have been before we released a new V7 beta.

OK probably i have got version from last week but i downloaded it today.
Rhino 7 SR0 2020-10-13 (Rhino 7 BETA, 7.0.20287.16003, Git hash:master @ 4e4df7bee6cc4158620b7d1105625b9e7e57abde)
License type: Commercial, build 2020-10-13
License details: Cloud Zoo
Expires on: 2020-11-27

Windows 10.0 SR0.0 or greater (Physical RAM: 16Gb)

Hybrid graphics system.
Primary display: Intel® UHD Graphics 630 (Intel) Memory: 1GB, Driver date: 4-19-2019 (M-D-Y).
Primary OpenGL: NVIDIA GeForce GTX 1050 Ti with Max-Q Design (NVidia) Memory: 4GB, Driver date: 4-6-2019 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 422.02

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On

Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: Height

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 4-6-2019
Driver Version:
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 4 GB

Rhino plugins that do not ship with Rhino

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 7 WIP\Plug-ins\Commands.rhp “Commands” 7.0.20287.16003
C:\Program Files\Rhino 7 WIP\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 7 WIP\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 7 WIP\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 7 WIP\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 7 WIP\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 7.0.20287.16003
C:\Program Files\Rhino 7 WIP\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 7.0.20287.16003
C:\Program Files\Rhino 7 WIP\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 7 WIP\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 7 WIP\Plug-ins\Alerter.rhp “Alerter”
C:\Program Files\Rhino 7 WIP\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 7.0.20287.16003
C:\Program Files\Rhino 7 WIP\Plug-ins\RhinoCycles.rhp “RhinoCycles” 7.0.20287.16003
C:\Program Files\Rhino 7 WIP\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.0.20287.16003
C:\Program Files\Rhino 7 WIP\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 7 WIP\Plug-ins\Displacement.rhp “Displacement”

Yes, that is the version from last week. The latest beta from yesterday should have the hatch area fix.

its funny i decided to test it and first thing i tried was the one which didnt work. i should try with lottery now

1 Like

@stevebaer The volume bug still exists in BETA (7.0.20294.14003, 10/20/2020)

@Trav can you take a look at this reported volume bug?

@Trav - I’ve created RH-61096 for this one.

Related to this, if I create a solid box, then Text > fx > Volume, then delete one face from the box, the volume incorrectly shows a number that is not 0.