Troubleshooting

When something misbehaves, find where it broke before changing parameters. This page is the general method. For specific problems and the known issues in 0.7.3, see Common Issues. For export problems, see Nanite Troubleshooting.

Read the error first

Most Natsura errors name the node and the condition.

1. Find the flagged node. An error badge means the cook failed there; a warning badge means it cooked but something is off.
2. Read the message: middle-click the node, or hover its badge.
3. Look one node upstream. A node that seems broken is often getting an empty or wrong input.

Empty trees with no error

If your trees vanish and no node is flagged, the licence check is the usual cause. It stops Natsura producing geometry without marking any node, though a dialog about your licence key may have appeared. Activation & Licensing shows how to check in a few seconds.

The Natsura log

Natsura writes one log file per Houdini session, in your Natsura user folder:

Windows   %APPDATA%/natsura/logs/
macOS     ~/Library/Application Support/natsura/logs/
Linux     ~/.config/natsura/logs/

Files are named natsura-<date>-<time>-<process id>.log, and the newest is the current session. The last ten are kept. Sessions without a UI, such as hython or a render farm, write natsura-batch-<date>-<time>-<process id>.log and keep their own ten. The log carries warnings and errors that never reach the viewport.

Natsura > About Natsura shows your versions, the path to this session's log, and the last error, with Open Log Folder and Copy buttons. Natsura > Log shows the log live. For more detail, turn on Verbose logging under Diagnostics in the Natsura Settings, then reproduce the problem.

The licence check writes its own log, described on Activation & Licensing.

Narrow it down

• Does it happen in a fresh scene? Open an example from the Project Browser and try to reproduce it there. If the example works and your scene doesn't, the problem is in your scene.
• Does it go away after reloading the scene? Note it either way; it helps us find the cause.
• Is it the display or the data? Check the geometry spreadsheet. If the data is right and the viewport is wrong, it is a display problem. Toggling the node's display flag often clears it.
• Did the scene come from an older version? See Upgrading.

Natsura doesn't load

See the troubleshooting section of Installation, or Package Install if you wrote the package file yourself.

Still stuck

Support lists what to send us.