Getting help

Most problems have a quick answer in these pages:

TroubleshootingEvery message SplatPilot shows, what it means and what to do.

FAQGPUs, saving, closing Blender, time, memory, file size and more.

Contact

TODO: contact channel

There is no support channel yet. Add the contact details here (for example an e-mail address, a forum or an issue tracker) before this page goes live.

What to include in a report

A good report lets someone reproduce the problem without a round of questions. Please include:

1. SplatPilot’s version. Edit > Preferences > Add-ons > SplatPilot shows it next to the name.

2. Blender’s version. Open the Blender menu (the Blender logo at the top left) and choose About Blender.

3. Your system and graphics card. Windows or your Linux distribution with its version, the GPU model and its driver version, and the line Test GPU shows in SplatPilot’s preferences.

4. What happened. What you did, what you expected and what happened instead, with the exact message from the panel or the status bar. A screenshot of the SplatPilot panel helps.

5. Your settings. The Quality (or preset), the Kind, the render engine, where the views came from (Automatic, Rigs or Cameras) and any numbers you changed.

6. The job’s log. For a splat, Open Run Folder in its menu in Results opens its training’s folder. Otherwise, in the Storage panel, click Open Storage Folder (the folder icon), then open jobs/. Every run has its own folder, named after its kind and start time, such as train-20261007-153012 or render-20261007-152740. Attach stdout.log from the folder of the run that went wrong, and stderr.log next to it.

7. A file, if you can. A small .blend that shows the problem is the fastest way to a fix.

Check before you share

Logs contain file paths from your computer, which can include your user name. Look through them and remove anything you would rather not share.