Community & support

Let us be upfront: there is no forum yet

Plenty of software homepages say "join our community", and inside you find three threads with the last reply a year ago. An empty forum damages trust worse than no forum. So we say it upfront: today there is email only, and the forum opens when there are people to fill it.

  • Email

    Available now

    Every question can come by email, answered within working hours.

    Download, installation, licensing, results that look wrong — one entry point for all of it. Attach your version number and model file and the reply comes much faster.

    support@kavvo.app

    For download, installation and licensing issues, email us directly with your version number and a screenshot.

  • Public Q&A archive

    Opens at release

    Every question worth making public becomes one searchable record.

    Forums bury good answers on page three; documentation does not. So our practice is: any email-resolved problem that would help others gets written up as an archive entry — symptom, cause, fix, affected versions, four sections, into the documentation site.

    Browse the FAQ

    Archive entries follow the same format as the verification cases: only what actually happened, never "in general".

  • User group

    Announced when it opens

    A group chat for quick questions and release notices.

    A chat group is not a knowledge base: messages sink, cannot be searched, and newcomers re-ask the same things. The group only handles the "fast" part; anything worth keeping becomes an archive entry.

    The entry point will be announced here and on the download page at release.

Forum

When it opens, and why not now

The cost of a forum is not in building it — it is in running it: every question needs an answer, every answer needs tidying. Opening a forum before there are users produces a homepage full of zero-reply threads, which discourages people more than saying nothing at all.

  1. Now

    Email + documentation

    Questions go by email; conclusions go into the docs. The goal at this stage is not activity — it is getting the first hundred answers right.

  2. At release

    Public Q&A archive + user group

    The archive goes live, recording each problem as symptom / cause / fix / version. The user group opens at the same time.

  3. When conditions allow

    Our own forum

    Category boards, searchable, subscribable. Not now — an empty forum costs more trust than no forum.

    Trigger: 300+ registered users and 30+ public questions per month. Both must hold; until then the archive carries the load.

Asking

Ask this way and one round is enough

Most "the result is wrong" reports are not missing an answer — they are missing information. With all five items we can usually localize in one round; missing three or more, we can only guess back and forth.

  1. 1

    Version number

    The full version from "About", including the build number. The same symptom in two versions can have two different causes.

  2. 2

    A minimal model

    The smallest model file that reproduces the problem. Strip it down to the few members that misbehave — nine times out of ten you find the cause while deleting.

  3. 3

    Expected vs. actual

    What you expected, and what you got. "It is wrong" cannot be investigated; "the column-top displacement should be 12 mm but comes out at 120 mm" locates it immediately.

  4. 4

    What you have already tried

    Switched solver? Changed the mesh? This one step saves a full round of back-and-forth.

  5. 5

    Screenshots or logs

    Error screenshot, solve log, result screenshot. The log usually already contains the answer — nobody reads it.

About the "minimal model"

Strip the model down to just the few members involved — does it still reproduce? This looks tedious but is the fastest diagnostic there is: the moment the problem disappears, the cause is in whatever you just deleted. The models in our verification archive are each only a few dozen lines, precisely so a person can read them in one sitting.

See what the archive models look like →

Contributing

Three things more useful than a good review

Software credibility is not earned by praise. Any one of the three below is worth more than a sentence of "works great".

  • Submit a verification case

    You ran a case with an analytical solution or a test comparison and are willing to publish the model and results. We review it and add it to the archive, credited with your name and affiliation.

    NeedsModel file + analysis settings + results + error statement

  • Report documentation errors

    Wrong parameter meanings in the manual, outdated code references, dead links. A documentation error deserves fixing before a software bug — people act on it.

    NeedsPage or section number + what is wrong + the correct statement and its source

  • Point out wrong results

    If you find any result disagreeing with hand calculation, commercial software or a test, please tell us. This matters more than any compliment.

    NeedsModel + your reference result + the magnitude of the discrepancy

Send all of these to support@kavvo.app. Accepted cases and errata are credited on the page; if you prefer not to be named, just write "anonymous".