Support & community

This is a v1.0 alpha — your feedback genuinely shapes the roadmap.

IAMX already runs in production: interactive kiosks that greet and converse with real visitors, and live streams where a digital human speaks to an audience in real time. That's the good news. The honest news is that this is our first public release. You will find rough edges — a setting that isn't wired the way you expected, a provider quirk, an animation blend that needs another pass. We would much rather hear about those than have you quietly work around them.

Here's our promise for the alpha period: every bug report and every feature request gets read by a human on the team. Not triaged into a void — read. The things that come up repeatedly, or that unblock a real build, move up the roadmap fast. A surprising amount of what shipped since the first drop started as a one-line forum post from someone building something we hadn't imagined.

Where to go

Four places, each with a different job. Pick by what you need right now — a question answered, a bug filed, a changelog read, or just proof that the thing works.

Which channel for which need

When in doubt, this is the quick lookup. The rule of thumb: questions and ideas → forum, reproducible bugs → GitHub.

Reporting well

A good report is one we can act on the same day. A vague one bounces back to you with questions and costs everyone a round trip. The difference is almost always a few concrete details. Two shapes of report, two things we need from you:

For bugs — make it reproducible

The single most useful thing you can include is your engine version and the logs from the run that went wrong. With those two, we can usually reproduce on the first try.

• Engine version — which release you're on (see the releases page) and your Unreal Engine version.
• Logs — the relevant slice of the output log around the failure, not just the final error line. The lines before the error usually tell the real story.
• Repro steps — the shortest sequence that triggers it. "Open the demo map, press T, speak" beats a paragraph.
• Expected vs. actual — one sentence each. What you thought would happen, what actually did.
• Config — which providers, which interaction mode, and any non-default settings that matter.

Title:   Lip sync freezes after second sentence — v1.0-alpha, UE 5.7

Engine:  IAMX v1.0-alpha  ·  Unreal Engine 5.7  ·  Win64
Mode:    VoiceActivated, GPT provider
Steps:   1. Open sample kiosk map
         2. Ask two questions in a row
         3. On the second reply, mouth stops moving mid-sentence
Expected: Lip sync tracks the whole reply
Actual:   Freezes ~1s in; audio keeps playing
Logs:
  [IAMX] TTS chunk 2/4 queued
  [IAMX] LipSync: decoder returned 0 frames  <-- here
  [IAMX] Playback continued without morph update

For feature requests — tell us what you're building

The best feature requests don't start with a solution — they start with a goal. Tell us what you're building and why, and we'll often find a better path than the one you'd have asked for. "I need a checkbox for X" is far less useful to us than "I'm building a bank kiosk that has to verify identity before it'll discuss an account — here's the flow I'm stuck on."

• The use case — kiosk, live stream, game NPC, something else. Context changes the answer.
• The outcome you want — describe the behavior, not the implementation.
• Your workaround today — if you've hacked around it, show us; it tells us how sharp the pain is.

How to file a bug on GitHub

If it's reproducible and you want it tracked, GitHub is the right home. The whole thing takes a couple of minutes.

1. Update first — pull the latest from Releases. There's a real chance it's already fixed, and we'll ask you to try anyway.
2. Search open issues — if it exists, add your version + logs as a comment instead of opening a duplicate. More data on one issue beats five thin ones.
3. Open a new issue — use the template above: version, mode, steps, expected/actual, scrubbed logs.
4. Attach evidence — a short screen capture or a GIF of a visual glitch is worth a thousand words.
5. Stay in the loop — watch the issue so you catch follow-up questions; a fast reply from you often means a fast fix from us.

Roadmap & releases

The roadmap isn't a sealed document — it's shaped in the open on the forum, weighted by what people actually keep asking for. When something ships, it lands in two places: the raw notes on the GitHub releases page, and a human-readable write-up (with the why, and any migration steps) on the blog.

• Read the blog after every update — it flags anything that changes behavior you depend on.
• Pin your version in production — don't auto-upgrade a live kiosk mid-event. Test a new release on a staging build first.
• Tell us your version when you write in — "latest" ages badly in a thread; a tag doesn't.

What's next

Got IAMX talking and want to go deeper? A few good next stops:

Thanks for building on an alpha with us. It's a little rough, it's moving fast, and your report is the reason the next release is better. See you on the forum.