Skip to main content

Known Issues and Troubleshooting

Last Change: 2025-05-09 #dba

Known Issues and Troubleshooting​

sphereneRHINO operates via two software components:

  • Local Plugin: This operates on your local machine as a Rhino plugin.
  • Cloud-Based Engine: This runs computations on our servers.

Note that changes by updates of the cloud engine may occasionally lead to undesired results or introduce new bugs. Please keep that in mind when submitting a bug report or experience unforeseen behaviour.

ADMS Density Estimate​

  • Effective density/volume fraction is based on an estimate, with a precision of about +/- 10% when using a constant density field.

Time Limitation​

  • The cloud computation is limited to a maximum of 45 minutes of runtime, limited by the cloud provider. If the maximum time is expected to exceed, we'll halt the computation and inform you with an error message.

Memory Limitation​

  • The cloud computation has a memory limitation, limited by the cloud provider. If the memory needed for your computation is expected to exceed the maximum memory we can allocate, we'll inform you with an error message.

Density Range​

  • Ensure the density you set is within the range of 2 to 32. Densities below or above this range may result in empty results or system crashes due to memory limitations.

Envelope Mesh Quality​

  • Make sure your envelope mesh is clean, closed and well-structured without intersections or flipped normals.

Losing Internet Connection During Computation​

  • If your internet connection is lost before delivery of the computation result, or if you have shut down your computer or quit Rhino3D, you can retrieve the computed results later using ![[sphe_restore_IO.svg|32]] the command sphe_restore_output. Note that all currently undelivered results are loaded into the Rhino window from which you invoke the sphe_restore_output command, even if they were created from different instances of Rhino.

Bug Reporting​