Best Practices
Getting the most out of your partnership with Kaedim.
🖼️ Clean Inputs = Better Outputs
The quality of assets we deliver is directly tied to the clarity of what you provide. To speed up turnaround and minimize revisions, we recommend:
Reference Images:
Provide high-resolution, front/side/angled views if available.
Include orthographic references for characters or props when possible.
Label key details (e.g., “metallic finish,” “wood texture”) directly on the images.
Design Notes:
Share a short description of the intended use (e.g., hero asset, background filler).
Highlight scale or proportion requirements if relevant to gameplay.
Note any must-have features (logos, color palettes, articulation points).
Do’s and Don’ts:
✅ Do send multiple clear angles.
✅ Do mention if fidelity/optimization is more important than speed.
❌ Don’t rely on vague phrases like “make it cool”—be specific.
📈 Efficient Workflows
Kaedim is designed to cut production cycles in half, but alignment on workflow is key. Here are a few tips to ensure your pipelines are accelerated to the full extent!
Linear Process:
We work in a largely linear pipeline: geometry → UVs → textures → rigging (if applicable) → LODs.
To avoid rework and delays, make sure the current stage is fully approved before moving onto the next.
Later-stage revisions (e.g., changing geometry after texturing) may slow delivery.
Our Branching feature allows you to make changes to previously completed stages.
Optional Review Gates:
By default, we ask for approval at the geometry stage before proceeding.
If your team prefers fewer checkpoints, you can request to auto-approve geometry and only review assets at the texture stage.
Batching Requests:
Submit assets in themed groups (e.g., “urban props pack,” “NPC set”) to maximize speed and consistency. (Suggested, but not required)
Where possible, bundle similar complexity assets together.
Feedback Loops:
Provide consolidated feedback from your team in one round if possible.
Use numbered callouts on screenshots for clarity (e.g., “1. Adjust hand grip,” “2. Darker wood grain”).
Add as much detail as you can in your feedback.
This helps optimize your custom style.
🤝 Team Collaboration
Working with Kaedim works best when teams establish clear communication roles.
Point of Contact:
Assign project leads to gather input and feedback.
Shared Documentation:
Share access with Kaedim where possible.
🚀 Scaling With Kaedim
As your asset needs grow, Kaedim adapts:
Prototyping Stage: Use Kaedim to quickly fill worlds with test assets and iterate on creative direction.
Production Stage: Rely on us for consistent, high-quality outputs at volume.
Live Ops: Submit small, continuous requests (skins, props, seasonal items) to maintain player engagement without overwhelming internal teams.
❌ Common Pitfalls to Avoid
Incomplete Inputs: Missing angles or unclear notes usually create extra feedback cycles.
How to avoid:
Always provide at least 3–4 clear reference angles (front, side, back, and perspective if available).
Add quick annotations or labels to highlight key materials, patterns, or functional parts.
If references are from mixed sources, clarify which details should be prioritized.
Fragmented Feedback: Conflicting comments from multiple reviewers slow down progress.
How to avoid:
If your workflow allows, auto-assign stages (e.g., geometry review, texture approval) to specific team members so that each step has only one responsible reviewer. The reviewer can re-delegate to a different team member if needed.
Consolidate internal feedback before sending it to Kaedim.
Use a shared doc or marked-up images so everyone is aligned before submitting.
Last updated
Was this helpful?