← All topics View on GitHub ↗

🙏 Q&A

About Q&A: how to get a fast answer

StartSWest ·

  1. Search, and read the answered questions here: most common questions already have one.
  2. Say which FluidEQ version you have (Help → About FluidEQ…), which engine (the card at the top of ≡), and the output you're listening on.
  3. Say what you did, what you expected, and what happened instead.
  4. When an answer works, press Mark as answer on it, so the next person sees it first.

Something broken rather than confusing: Help → Report a problem opens an issue with the details already filled in.

Formatting: **bold** _italic_ `code` - list [link](url)

Images: the box here takes text only — giscus cannot upload files. To attach a screenshot, write the post on GitHub and it appears here.

Loading the discussion from GitHub…

Topics Read the FAQ first

New to FluidEQ?

FluidEQ in motion