DEV Community: dat398

What I learned building Seamless Texture Variation Board for a real creator workflow

dat398 — Thu, 16 Jul 2026 09:12:18 +0000

What I learned building Seamless Texture Variation Board

Start with the repeated job, not a feature list

The target users are 2D/3Dゲーム素材制作者、テクスチャアーティスト. The concrete problem was: 1枚の素材から反復候補を手作業で複製し、継ぎ目と色違いを何度も比較する必要がある

That framing kept the project focused on one observable result instead of a collection of controls.

Keep the workflow where the work already happens

The implementation uses Python/Tkのdesktop panelで作成し、PNGをGIMP等の画像制作環境へ渡せる. The finished workflow lets a user 16 PNG変種、3×3 tile比較、contact sheet、再現用JSON recipeを一括で得られる.

The important design constraint was to make the result visible before the user commits to it. That is more useful than adding options that are difficult to verify.

Make the release testable

Before releasing it, I exercised the packaged build in the real target application through its main input, operation, and output states. Compatibility limits are documented alongside the workflow.

A reusable rule for small creator tools

Name the repeated job in one sentence.
Define the visible finished result.
Keep preview and validation close to the action.
Test the buyer package in the actual host, not only in a fixture.
Document limits before adding more scope.

The release notes, tested package details, and exact compatibility information are here: https://dat398.gumroad.com/l/libriv?utm_source=devto&utm_medium=community&utm_campaign=seamless_texture_variation_board&utm_content=launch

What I learned building Blender Photo Blockout Composer for a real creator workflow

dat398 — Thu, 16 Jul 2026 04:28:50 +0000

What I learned building Blender Photo Blockout Composer

Start with the repeated job, not a feature list

The target users are Blender environment modelers and product visualization artists. The concrete problem was: Matching cameras and rebuilding scale guides separately for multiple reference photos makes early blockout slow and inconsistent

That framing kept the project focused on one observable result instead of a collection of controls.

Keep the workflow where the work already happens

The implementation uses Bilingual Blender 4.3 host panel linking up to four photos and generating cameras, XYZ guides, floor, walls and an editable box in one owned Collection. The finished workflow lets a user Choose photos, enter two vanishing points and a known dimension, then generate a scale-synchronised multi-view blockout.

The important design constraint was to make the result visible before the user commits to it. That is more useful than adding options that are difficult to verify.

Make the release testable

Before releasing it, I exercised the packaged build in the real target application through its main input, operation, and output states. Compatibility limits are documented alongside the workflow.

A reusable rule for small creator tools

Name the repeated job in one sentence.
Define the visible finished result.
Keep preview and validation close to the action.
Test the buyer package in the actual host, not only in a fixture.
Document limits before adding more scope.

The release notes, tested package details, and exact compatibility information are here: https://dat398.gumroad.com/l/bnolm?utm_source=devto&utm_medium=community&utm_campaign=blender_photo_blockout_composer&utm_content=launch

What I learned building Blender Kinetic Text Path Composer for a real creator workflow

dat398 — Thu, 16 Jul 2026 01:47:50 +0000

What I learned building Blender Kinetic Text Path Composer

Start with the repeated job, not a feature list

The target users are Blender motion graphics creators and video editors. The concrete problem was: Building kinetic typography manually requires splitting text, duplicating glyphs, assigning path constraints, spacing objects and keyframing each reveal

That framing kept the project focused on one observable result instead of a collection of controls.

Keep the workflow where the work already happens

The implementation uses Bilingual Blender 4.3 N-panel generating editable Text objects with Follow Path constraints and deterministic keyframes inside an owned Collection. The finished workflow lets a user Select text and a Curve, preview Straight/Elastic/Wave timing, then generate an editable kinetic typography rig.

The important design constraint was to make the result visible before the user commits to it. That is more useful than adding options that are difficult to verify.

Make the release testable

Before releasing it, I exercised the packaged build in the real target application through its main input, operation, and output states. Compatibility limits are documented alongside the workflow.

A reusable rule for small creator tools

Name the repeated job in one sentence.
Define the visible finished result.
Keep preview and validation close to the action.
Test the buyer package in the actual host, not only in a fixture.
Document limits before adding more scope.

The release notes, tested package details, and exact compatibility information are here: https://dat398.gumroad.com/l/xrvmau?utm_source=devto&utm_medium=community&utm_campaign=blender_kinetic_text_path_composer&utm_content=launch

What I learned building Stair Flow Director for a real creator workflow

dat398 — Wed, 15 Jul 2026 21:54:54 +0000

What I learned building Stair Flow Director

Start with the repeated job, not a feature list

The target users are Blender architectural visualizers, environment artists and interior blockout creators. The concrete problem was: Manual arrays and free single-shape generators leave floor-height fitting, flight division, landings and rails as separate reconstruction work

That framing kept the project focused on one observable result instead of a collection of controls.

Keep the workflow where the work already happens

The implementation uses Bilingual Blender 4.2–4.5 N-panel that generates standard editable mesh steps, landings and curve rails in a dedicated collection. The finished workflow lets a user Choose floor height and Straight/L/U flow, preview fitted risers, then generate the complete editable stair circulation.

The important design constraint was to make the result visible before the user commits to it. That is more useful than adding options that are difficult to verify.

Make the release testable

Before releasing it, I exercised the packaged build in the real target application through its main input, operation, and output states. Compatibility limits are documented alongside the workflow.

A reusable rule for small creator tools

Name the repeated job in one sentence.
Define the visible finished result.
Keep preview and validation close to the action.
Test the buyer package in the actual host, not only in a fixture.
Document limits before adding more scope.

The release notes, tested package details, and exact compatibility information are here: https://dat398.gumroad.com/l/dyolfl?utm_source=devto&utm_medium=community&utm_campaign=stair_flow_director&utm_content=launch

What I learned building Pose Arc Director for a real creator workflow

dat398 — Wed, 15 Jul 2026 20:33:36 +0000

What I learned building Pose Arc Director

Start with the repeated job, not a feature list

The target users are 2D animators, illustrators, storyboard artists and motion learners. The concrete problem was: Static pose references do not reveal spacing and arcs, while full animation packages require timeline, rig and export setup before artists can test a motion idea

That framing kept the project focused on one observable result instead of a collection of controls.

Keep the workflow where the work already happens

The implementation uses Offline bilingual Linux aarch64 desktop GUI combining joint editing, 2–5 key poses, four timing curves, live ghosts, motion arcs, GIF and PNG sheet export. The finished workflow lets a user Shape Stand, Jump and Land, choose timing, press Play, then export a looping drawing reference in three actions.

The important design constraint was to make the result visible before the user commits to it. That is more useful than adding options that are difficult to verify.

Make the release testable

Before releasing it, I exercised the packaged build in the real target application through its main input, operation, and output states. Compatibility limits are documented alongside the workflow.

A reusable rule for small creator tools

Name the repeated job in one sentence.
Define the visible finished result.
Keep preview and validation close to the action.
Test the buyer package in the actual host, not only in a fixture.
Document limits before adding more scope.

The release notes, tested package details, and exact compatibility information are here: https://dat398.gumroad.com/l/mzmqpc?utm_source=devto&utm_medium=community&utm_campaign=pose_arc_director&utm_content=launch

What I learned building Pixel Parallax Director for a real creator workflow

dat398 — Wed, 15 Jul 2026 19:14:16 +0000

What I learned building Pixel Parallax Director

Start with the repeated job, not a feature list

The target users are Pixel artists, 2D game developers, and stream-background creators turning layered artwork into loops. The concrete problem was: General editors require repeated layer duplication and keyframing, while common pixel editors do not provide a camera model for precise looping parallax

That framing kept the project focused on one observable result instead of a collection of controls.

Keep the workflow where the work already happens

The implementation uses Offline bilingual Linux aarch64 native GUI with layer depth, four live camera paths, pixel-aligned wrapping, GIF and sprite-sheet export. The finished workflow lets a user Add layered PNGs, tune depth, and export a seamless 640x360 parallax loop in three actions.

The important design constraint was to make the result visible before the user commits to it. That is more useful than adding options that are difficult to verify.

Make the release testable

Before releasing it, I exercised the packaged build in the real target application through its main input, operation, and output states. Compatibility limits are documented alongside the workflow.

A reusable rule for small creator tools

Name the repeated job in one sentence.
Define the visible finished result.
Keep preview and validation close to the action.
Test the buyer package in the actual host, not only in a fixture.
Document limits before adding more scope.

The release notes, tested package details, and exact compatibility information are here: https://dat398.gumroad.com/l/ynlfvx?utm_source=devto&utm_medium=community&utm_campaign=pixel_parallax_director&utm_content=launch

What I learned building Camera Beat Director for a real creator workflow

dat398 — Wed, 15 Jul 2026 18:13:08 +0000

What I learned building Camera Beat Director

Start with the repeated job, not a feature list

The target users are Blender artists creating product reveals, portfolio reels, short films, and character introductions. The concrete problem was: Standard Follow Path setup and single-motion presets do not let artists quickly compose several shot intentions, lens changes, and holds into one editable reveal

That framing kept the project focused on one observable result instead of a collection of controls.

Keep the workflow where the work already happens

The implementation uses Bilingual Blender 4.2+ N-panel add-on that creates standard local camera, target, Curve, F-curves, and timeline markers. The finished workflow lets a user Select a subject, load Wide/Reveal/Detail beats, preview the path, and generate a 139-frame editable camera sequence.

The important design constraint was to make the result visible before the user commits to it. That is more useful than adding options that are difficult to verify.

Make the release testable

Before releasing it, I exercised the packaged build in the real target application through its main input, operation, and output states. Compatibility limits are documented alongside the workflow.

A reusable rule for small creator tools

Name the repeated job in one sentence.
Define the visible finished result.
Keep preview and validation close to the action.
Test the buyer package in the actual host, not only in a fixture.
Document limits before adding more scope.

The release notes, tested package details, and exact compatibility information are here: https://dat398.gumroad.com/l/xrmef?utm_source=devto&utm_medium=community&utm_campaign=blender_camera_beat_director&utm_content=launch

What I learned building Bake Atlas Composer for Blender for a real creator workflow

dat398 — Wed, 15 Jul 2026 10:37:46 +0000

What I learned building Bake Atlas Composer for Blender

Start with the repeated job, not a feature list

The target users are Game-asset and environment artists preparing batches of Blender props for engines. The concrete problem was: Artists otherwise duplicate objects, coordinate non-overlapping UVs, prepare image nodes, sequence bakes, and rebuild one shared material by hand.

That framing kept the project focused on one observable result instead of a collection of controls.

Keep the workflow where the work already happens

The implementation uses Bilingual Blender sidebar add-on using native mesh, UV, material, image, and Cycles APIs. The finished workflow lets a user Select a prop set, preview isolated duplicates with a shared atlas layout, then generate one baked PNG and shared material inside Blender.

The important design constraint was to make the result visible before the user commits to it. That is more useful than adding options that are difficult to verify.

Make the paid advantage testable

The main advantage over the manual or free workaround is that Combines host integration, live pre-bake preview, non-destructive duplicates, shared UV layout, real bake, and final material assignment in one repeatable workflow.

I treated that as a test requirement, not marketing copy: the packaged build was exercised in the real target application, through its main input, operation, and output states. Compatibility limits are documented alongside the workflow.

A reusable rule for small creator tools

Name the repeated job in one sentence.
Define the visible finished result.
Keep preview and validation close to the action.
Test the buyer package in the actual host, not only in a fixture.
Document limits before adding more scope.

I built the commercial product discussed here. The tested package and exact compatibility notes are available here: https://dat398.gumroad.com/l/hrhfhh?utm_source=devto&utm_medium=community&utm_campaign=blender_bake_atlas_composer&utm_content=launch

Photopea Mockup Scene Stage: product workflow and lessons learned

dat398 — Tue, 14 Jul 2026 18:54:16 +0000

What I learned building Photopea Mockup Scene Stage

The workflow problem

Creators otherwise search for separate PSD mockups, replace Smart Objects, adjust light and placement, and export each scene repeatedly.

The result

Sync one open design, art-direct four live scenes together, and export gallery poster, tablet, box, and card PNGs in one ZIP.

Verification

I tested the finished build in its actual target application, including the main workflow, output and documented limits.

I built the product; details and the tested package are here: https://dat398.gumroad.com/l/ebefn?utm_source=devto&utm_medium=community&utm_campaign=photopea_mockup_scene_stage&utm_content=launch

Visual Change Story: product workflow and lessons learned

dat398 — Tue, 14 Jul 2026 18:53:53 +0000

What I learned building Visual Change Story

The workflow problem

Visual regression tools find changes, while basic sliders do not explain multiple decisions as one client-ready narrative

The result

Load before and after images, place change points, and preview an annotated comparison story in three steps

Verification

I tested the finished build in its actual target application, including the main workflow, output and documented limits.

I built the product; details and the tested package are here: https://dat398.gumroad.com/l/tsgoyz?utm_source=devto&utm_medium=community&utm_campaign=wordpress_visual_change_story&utm_content=launch

Bake Atlas Composer for Blender: Build one shared texture atlas from selected props

dat398 — Tue, 14 Jul 2026 18:42:06 +0000

What I learned building Bake Atlas Composer for Blender

The workflow problem

Artists otherwise duplicate objects, coordinate non-overlapping UVs, prepare image nodes, sequence bakes, and rebuild one shared material by hand.

The result

Select a prop set, preview isolated duplicates with a shared atlas layout, then generate one baked PNG and shared material inside Blender.

Verification

I tested the finished build in its actual target application, including the main workflow, output and documented limits.

I built the product; details and the tested package are here: https://dat398.gumroad.com/l/hrhfhh?utm_source=devto&utm_medium=community&utm_campaign=blender_bake_atlas_composer&utm_content=launch