How to ask well, and how to show your work

A forum gets useful when the posts are specific. This note covers the two most common kinds — asking and showing — and what makes each one land.

Asking something in Questions & Support

Before you post:

1. Search first. Someone may already have asked it.
2. Pick the product tag — AIR, AIC, AIA, AIM, AIT, AIF, or General.
3. One question per post — posts that ask three questions usually get fewer answers.
4. Attach the input: the model screenshot, the sketch, the source image, the prompt.
5. Write the steps you took, in order. If it broke after an update, say which one.

Template — copy it and fill in the blanks:

Ask template
Title: [Product] + what is wrong, in one line
What I'm trying to make:
Where I work: web app / SketchUp / Rhino / Revit / 3ds Max / Blender / Photoshop
Steps I took:
What happened: (attach screenshot or project file)
What I expected:
What I already tried:

Weak vs strong:

• Weak: "Render looks bad, help."

• Strong: "AIR: interior massing renders too dark and the windows blow out — input and output attached."

• Weak: "Can it change materials?"

• Strong: "Can AIR keep the ceiling height while I test three material options on the same room? Here's what I tried."

Showing work in Showcase & Workflows

The final image is nice. The process is what other people can actually use.

Template:

Show template
What it is and who it's for:
Input: massing / sketch / photo / brief
Product and settings: which tool, which style, the key settings or prompt
Time: from input to this result
Result: 2 to 4 images, or a short clip
What I'd do differently next time:

If your post is a workflow, add the sequence as a short numbered list — for example: concept directions in AIC → render in AIR → clean up in AIR's editing tools → model in AIM → animate in AIA. One line per step is enough.

What to expect back

• We read the forum when we can, but we can't promise a reply time.

• Account, billing, or urgent one-to-one issues: use contact support or [email protected]. The forum is not a ticket queue.

• When your problem is solved, reply with what fixed it. That reply helps the next person more than the original question did.

• If nobody answers in a few days, reply to your own thread with what you've learned. It bumps the post and adds context.

One more thing

Be generous with what you already know. The person stuck on step three was you last week.

---