Troubleshooting
Troubleshooting
When an operator won't load, won't license, or won't cook — start here.
Every NativeOps operator reports its state in the Status readout on the
Common page. That string is the fastest route to the right page below.
| Status says | Go to |
|---|---|
GPU unsupported / CUDA version | GPU requirements |
Driver too old / device-lost crashes | Drivers |
License invalid / Activation failed | Activation problems |
| Operator missing from OP Create | Installation |
GPU requirements
The load-time hardware checks and what each failure means.
Drivers
Known-bad driver ranges and the clean-install ritual that fixes most device-lost errors.
Activation problems
Key rejected, seat conflicts, offline files that won't take.
Filing a support request? Attach the operator's Info DAT dump (right-click → Copy Diagnostics) — it carries the plugin build, driver, GPU, and the last ten status transitions, and it turns most tickets into one-reply fixes.