As mentioned in a different thread, I’ve reported this issue with the Volume Centroid component. I have not been able to reproduce this with the Area Centroid component. Are you still see this? If so, please post a sample file.
-wim
Here is a file, but I really didn’t do anything fancy. CentroidBug.ghz (348.0 KB)
SystemInfo
Rhino 9 SR0 2026-8-11 (Rhino 9 BETA, 9.0.26223.12303, Git hash:master @ 535bf21f011dc805eafa540606c59272f4f15b11)
License type: Educational Lab License, version 2026-08-11
License details: Cloud Zoo
Expires on: 2026-09-25
Windows 11 (10.0.26100 SR0.0) or greater (Physical RAM: 16GB)
.NET 10.0.9
Computer platform: LAPTOP - Plugged in [67% battery remaining]
Non-hybrid graphics configuration using DirectX
Primary display: Radeon Pro 560 (AMD) Memory: 4GB, Driver date: 8-19-2024 (M-D-Y). DirectX(11)
> Integrated accelerated graphics device with 6 adapter port(s)
- Windows Main Display is laptop’s integrated screen or built-in port
Rhino plugins that do not ship with Rhino
C:\Users\Felix\AppData\Roaming\McNeel\Rhinoceros\packages\9.0\Karamba3D\3.1.60519\net8.0-windows\Karamba3D_LicensePlugin_Rhino8.rhp “Karamba3DLicense”
This one computes correctly here when testing the fix that should become publicly available this evening.
→ RH-97680 Grasshopper 2: Volume Failure
-wim