Skip to content

Diagnostics

What to check when a study is slow, empty or fails, and what to send support.

Reference · 2 min read

When a study doesn't look right, check what it saw first, then the message it gave. If you still need help, the details below are what support will ask for.

Check what the study saw#

When a study runs, its summary reports:

  • The scope: the group or selection analyzed.
  • The sensor count.
  • The period and sky inputs in effect.
  • How long the run took.

Use these to confirm the study saw the geometry you expected before you read the heatmap.

When a study is slow or fails#

What you seeWhat to do
The study did not answer in timeRhino may still be computing, or the result was too large to send back. Try a coarser grid or fewer surfaces, then run again.
The study lost its connection to RhinoClose and reopen the panel, then run again.
The heatmap is missing or looks wrongCheck the study's summary. If the sensor count is not what you expected, check the group or selection it ran over.
An upgrade message instead of a resultView and Radiation need Wrengler Pro.
The study covers more than 2,500 m²Free runs Sunlight on up to 2,500 m² per study. Select fewer surfaces, or see Pro.
Wrengler could not check your subscriptionEvery study checks your plan online first, Free or Pro. Reconnect and run it again.
Every study is slowSee Performance.

What to send support#

  • The message the panel showed, word for word.
  • The lines Rhino's command line printed for the run. A study run prints a line there with the hardware it ran on and its results, or why it failed. Rhino's CommandHistory command shows them if they have scrolled away.
  • The output of WrenglerEngine, typed at the Rhino command line. It lists the hardware Wrengler can use on this machine, and why any of it is unavailable.
  • Your Rhino version, your operating system, and what you were doing when it happened.