Help & Feedback

Use this page when something is unclear, broken, missing, or worth improving.

Dynaros support and documentation are meant to respect the work you have already done. If you have already tested something, searched the docs, checked logs, or narrowed down a problem, include that context so support can start from there.

Before Asking For Help

When possible, gather the details that make the issue easier to diagnose:

the Dynaros product and version you are using
your Unreal Engine version
what you expected to happen
what actually happened
the steps that reproduce the issue
any relevant logs, warnings, screenshots, or error messages
whether the issue happens in a clean project or only in your project
what you have already tried

You do not need a perfect report. A clear description of the goal and what went wrong is enough to start.

What Counts As Feedback

Feedback can be practical, technical, or simply experiential.

Useful reports include:

bugs
confusing documentation
missing examples
unclear Blueprint workflows
C++ API questions
compatibility issues
setup friction
performance concerns
feature requests
places where Dynaros did not fit your project as expected

Positive feedback is useful too, especially when it identifies what worked well and why.

Product Support Scope

Dynaros support can help with Dynaros behavior, product setup, integration questions, documentation gaps, and reasonable troubleshooting.

If a question becomes custom development for an entire unrelated project, it may need to move into a separate collaboration or custom-build conversation. The line is not meant to be hostile; it keeps product support useful and sustainable.

Reporting Documentation Issues

If a page leaves you stranded, says something confusing, misses a likely next step, or assumes context it has not explained, that is worth reporting.

Good documentation feedback can be as simple as:

Page:
What I was trying to do:
What confused me:
What I expected to find:

Reporting Bugs

For bugs, include as much of this as you can:

Product:
Product version:
Unreal Engine version:
Project type:

What happened:
What you expected:
Steps to reproduce:
Logs or screenshots:
What you already tried:

What Happens Next

Recurring issues may become documentation updates, troubleshooting entries, known issues, examples, fixes, or future product work.

Support is not separate from the product. It is one of the ways Dynaros learns where the product, docs, or workflows need to become clearer.