Open Generated Asset Browser
Start from the browser instead of hunting through project folders manually.
Browser guide
🗂️ Generated Asset Browser
Inspect generated assets, preview metadata, validate output, keep legacy Assign/Apply semantics, and explicitly promote supported outputs with Bind to Runtime when you want a v0.9.5 runtime connection.
Guide includedGenerated assetsUser guide
Generated output control room
Browser guide included · written guide available nowThe written browser guide is complete. Optional screenshots can later show preview, metadata, validation, and assignment panels.
What this page gives you
One generated asset is inspected, validated, and either kept, exported, assigned where supported, or safely removed.
Best forUsers who generated assets and need to inspect, validate, duplicate, export, delete, or connect them safely.
IncludedGuide included
Next resultOne generated asset is inspected, validated, and either kept, exported, assigned where supported, or safely removed.
Workflow
Recommended learning flow
Follow this sequence before expanding. It keeps the public learning path practical, testable, and beginner-safe.
Open browser→Pick asset→Preview→Open path→Validate→Duplicate/export→Assign/Apply where supported→Re-validate→Keep or delete
Step-by-step
Guide content
Filter or select one asset
Choose one generated output and inspect only that item first.
Preview and inspect metadata
Check type, source, path, warnings, assignment fields, and related resources.
Open file/path or related resource
Confirm where the generated output lives in the project and what owns it.
Validate the asset
Run validation before connecting the output into gameplay or UI.
Duplicate or export if needed
Create a safer copy or exported version before risky edits.
Choose Assign/Apply or Bind to Runtime intentionally
Use Assign/Apply for the existing supported field writes and traceable metadata. Use the separate Bind to Runtime action only for supported v0.9.5 runtime-promotion workflows, then confirm the saved/reloaded binding validates successfully.
Delete or regenerate safely
Remove only assets you understand and re-check warnings after regeneration.
Re-check warnings
Run validation again after every meaningful browser action.
v0.9.5 promotion boundary
Assign/Apply is separate from Runtime Bound
Assign/Apply preserves the v0.9.4 meaning: supported field writes and traceable assignment metadata where implemented. Bind to Runtime… is the separate v0.9.5 action for supported runtime promotion.
Runtime Bound status is committed only after the target binding resource is saved, reloaded, and validated. Dreamcatcher does not silently auto-wire arbitrary custom or third-party project architectures.
Reference
Assignment-key reference
For the full assignment-key list, use the dedicated reference page instead of duplicating the same list in multiple places.
Visuals coming soon
Written guide available now
The written guide is available now. Optional videos and screenshots are coming soon.
01Browser listVisuals coming soon
02Asset metadataVisuals coming soon
03Preview panelVisuals coming soon
04Validation resultVisuals coming soon
05Assign/Apply vs Runtime BoundVisuals coming soon
06Export/delete confirmationVisuals coming soon
Completion checklist
Completion checklist
- One asset is selected.
- Metadata and path are inspected.
- Validation result is checked.
- Duplicate/export is used before risky edits when needed.
- Assign/Apply or Bind to Runtime is chosen intentionally for the supported case.
- Runtime Bound state is accepted only after save/reload/validation succeeds.
- Warnings are rechecked after changes.
- The asset is kept, exported, assigned, deleted, or regenerated intentionally.
Avoid this
Common mistakes
- Assuming Assign/Apply means Runtime Bound, or expecting arbitrary custom architectures to be auto-wired.
- Deleting outputs without checking related metadata.
- Skipping validation after assignment.
- Editing generated outputs without making a safe copy.
- Treating warnings as cosmetic.
Quick summary
In short
The Generated Asset Browser helps you inspect, preview, validate, duplicate, export, delete, and explicitly promote supported generated outputs while keeping Assign/Apply metadata separate from validated Runtime Bound state.
