ASysT Rendering Talk to a human. Get an answer.
ASysT Rendering is in alpha and built in tight loops with its users — a real bug report today genuinely shapes next week's release. Bugs and ideas live in a public tracker so you can watch them get picked up; anything private goes straight to the maintainer by e-mail.
🐛Report a bug
Something rendered wrong, a diagram lost a connection, the panel misbehaved. Tell us how you run ASysT and the report opens with part of it already filled in.
Your version is printed inside ASysT itself, at the top left beside the name — or in the VS Code Extensions view.
💡Suggest a feature
A view you miss, a workflow that takes too many clicks, a SysML construct you need — tell us what you are trying to do, not just the button you want.
⭐Rate it publicly
A short review on the Marketplace is the single most helpful thing you can do for a young tool — it is how other engineers find it.
What makes a bug report great
- The version — printed inside ASysT, top left beside the name — and whether you run the VS Code extension, the Windows app or the Linux app. The button above fills both in.
- Roughly how big the model is — number of
.sysmlfiles is enough. - The steps, in order, and what you expected vs what you saw.
- A screenshot — of the diagram, the panel, or both.
- If a diagram looks wrong: which view it is (definition, internal structure, state…).
Your model files are yours — never feel obliged to send them. A minimal snippet that reproduces the problem is gold, but a screenshot alone is already very useful.
What happens after you press send
- Your report appears straight away and in public on the tracker, at its own address. You can re-read it, correct it and add a screenshot at any time.
- You get an e-mail whenever anyone replies, and you can stop those from the page itself. Nothing else is sent to you.
- It is read by one person — the maintainer. There is no queue and no ticket number; if it is unclear, the reply will be a question rather than silence.
- No GitHub account? Then the tracker cannot take it. Write the same thing to asyst.rendering@gmail.com and it is handled the same way.