Open a support ticket

A question, an idea, or a bug? Tell us here. For bugs, a tiny reproduction script gets it fixed fastest.

Email *

Name (optional)

Request type *

Title *

Description *

A bug = a small script that reproduces it + the exact error message + your platform. With that, it gets fixed fast.

How to build a minimal reproduction

Start from the script that fails and remove everything that isn’t needed — line by line — until the bug disappears. The last version that still shows the bug is your minimal repro. Attach that .dsc file.

Keep it as short as possible (ideally under 20 lines).
Hard-code the inputs so it runs on its own.
If it needs a data file, attach that too.

Platform

Linux version (if Linux)

VDS version / build Help → About, or the build date of the executable.

Minimal reproduction script (.dsc) — the #1 lever for a fast fix The shortest script that triggers the bug. Attached as a file, never pasted as truncated text.

I can’t isolate a minimal reproduction

If so, tell us why (what blocks isolation)

Exact error message (verbatim) Copy-paste it exactly — never reword it. Include “Run time error N at line L”, the error number, line number, pop-ups, or compile errors “Error: … at line N”.

Expected (1–2 sentences)

Observed (1–2 sentences)

Run context

Determinism

Plugins involved (image / fx…)

Repro steps (if interactive/GUI): which control, which action, in what order

This is a visual / rendering bug (a screenshot is the source of truth)

Screenshot(s) Required for visual/rendering bugs — we can’t see anything headless.

Input data (optional) Any file your script reads to reproduce the bug.

Compiled executable (only if the source isn’t available) .exe or .zip. Prefer the .dsc source whenever possible.

I have read and accept the privacy policy. Read

Email and title are required.

Open a support ticket

We respect your data