Hello everyone,
I’m running Rhino.Compute on an AWS virtual machine. When I open Rhino on the VM itself, it clearly shows that the document units are set to meters. However, whenever I make a request through Rhino.Compute, the JSON response indicates the geometry is in millimeters. This mismatch is causing confusion and also increases calculation time due to the unintended scaling factor.
I’m wondering if there is a Compute-side or headless Rhino setting that could be forcing units to millimeters. Any suggestions on how to ensure the output units match the model units I’ve set (i.e., meters) would be hugely appreciated!
Thanks in advance!