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 — open a report on the tracker. A short form asks for the version and what you saw.
💡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 extension version (Extensions view → ASysT Rendering) and your OS.
- 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.