Material Maker 1.7 on Steam - Indie PBR Keep Hold Playbook 2026

Material Maker just crossed a distribution line that matters to indies. Version 1.7 adds a Dynamic Sky Material, wider 32-bit node support, UI layout saves, and — for the first time — a Steam SKU so supporters can pay $14.99 for auto-updates and achievements while itch.io stays free / pay-what-you-want. Primary sources: the 1.7 itch.devlog, CG Channel’s write-up, and the Steam store page (app 4110830, release window mid-July 2026).

That is not “another free texture pack.” Material Maker is a Godot-powered, node-based procedural authoring and 3D paint tool with export templates aimed at Unity, Unreal, and Godot — the open-source lane people compare to Adobe Substance 3D Designer. Steam availability changes how teams pin versions, budget tools, and explain spend to producers.

This playbook is the indie keep / hold / rewrite test. It is not the Blender 5.2 LTS upgrade lock (DCC version pin). It is not a row inside a texture listicle. It is the Material Maker 1.7 evening: pick itch vs Steam, smoke one Static PBR export, then file material_maker_17_receipt_v1.json.

Who this is for: indie technical artists, Godot/Unity/Unreal micro-studios, and leads deciding whether Material Maker replaces or complements Substance spend in 2026.

What you get: plain-language tool map, free vs Steam picker, keep/hold table, beginner first-export path, gates M1–M6, honest limits, FAQ, and a receipt template.

Time: about 90–120 minutes for install + one graph + one engine import; add time if you compare against an existing Substance library.

Why this matters now (what 1.7 + Steam changed)

Three signals matter for game teams this month:

1. Steam is a support channel, not a feature wall — CG Channel and the itch.devlog are explicit: binaries remain free; Steam (~$14.99) buys convenience (updates, achievements like “Spaghetti Monster” for 100+ node connections) and funds development. Studios must decide pinning policy, not whether the tool suddenly became closed-source.
2. 1.7 is a real authoring bump — Dynamic Sky Material, more 32-bit paths, metallic default-from-parameter, panel layouts, and file-dialog thumbnails. That is enough to justify a re-smoke if you last evaluated Material Maker on 1.3/1.4-era builds.
3. Substance comparisons intensify when Steam exists — producers understand Steam line items. “We bought Material Maker” is easier to approve than “we use a free itch zip.” Diligence still needs an engine export receipt, not a Steam library screenshot.

If your fight is Blender color or version drift, finish those lanes first (ACES checklist, 5.2 LTS lock). If your fight is engine import flags after maps leave any DCC, keep the Blender → Unity/Godot handoff open beside this page.

What Material Maker actually is (indie plain language)

Direct answer: Use Material Maker when you need editable procedural PBR on a budget. Keep Substance when your partner contract, megascan ecosystem, or Painter stack already pays for itself. Do not cancel Substance the night you install Steam — smoke one material into your real engine first.

Keep / Hold / Rewrite — free vs Steam vs Substance

Company diligence note: Steam ownership proves support intent. It does not prove shader parity with Substance Designer on your Unreal project. Put export screenshots and material_maker_17_ok in the partner zip.

Beginner path — first Static PBR in one evening

Prerequisites

• Material Maker 1.7 from itch or Steam.
• One target engine (Godot, Unity, or Unreal) where you already know texture import flags.
• A simple mesh (engine primitive is fine).
• About 90–120 minutes.
• Folder: release-evidence/material-maker-17/.

If Unity albedos already look washed from Blender, fix that with Blender color space looks wrong in Unity before blaming Material Maker.

Step 1 — Pick your install lane (10 minutes)

Write one sentence:

• Lab / CI: itch zip or GitHub releases (free, scriptable).
• Daily artist pin: Steam if you want auto-updates and a clear support SKU.

Do not mix “CI uses random itch nightly” with “artists swear they are on Steam 1.7” without writing versions down.

Step 2 — Open a starter Static PBR graph (25 minutes)

1. Launch Material Maker 1.7.
2. Create or open a Static PBR material.
3. Wire a simple pattern (noise → color → roughness) so you can see channels update in the 3D preview.
4. Save the .ptex / project file into release-evidence/material-maker-17/graphs/.

Skip Dynamic Sky on night one unless the whole point is a skybox experiment.

Step 3 — Export maps with the engine template (20 minutes)

1. Use the built-in export path for your engine (Godot / Unity / Unreal templates called out in CG Channel and the Steam feature list).
2. Export albedo, normal, roughness/metallic (or packed ORM) as your pipeline expects.
3. Name files with a build tag: mm17_demo_albedo.png, etc.

Step 4 — Engine smoke (30 minutes)

1. Import into the target engine.
2. Confirm sRGB on albedo and Non-Color / Linear on data maps (handoff checklist still applies).
3. Drop the material on a lit sphere or prop.
4. Screenshot before/after vs a known-good material if you have one.

Step 5 — Optional Dynamic Sky lab (15 minutes)

Only if skies matter this sprint: generate a Dynamic Sky sample, export, and mark it lab in the receipt. Do not replace your signed skybox without art-lead sign-off.

Step 6 — File the receipt (10 minutes)

Fill material_maker_17_receipt_v1.json. Latch material_maker_17_ok only when M1–M6 are green.

Developer gates (M1–M6)

Failure modes: declaring Substance dead after one brick material; using Dynamic Sky as character albedo; mixing Steam and itch versions across the team; ignoring normal-map orientation; shipping without Non-Color flags; treating community website graphs as license-free without notes.

Receipt template

{
  "schema": "material_maker_17_receipt_v1",
  "install_source": "steam|itch|github",
  "version": "1.7",
  "steam_app_id": "4110830",
  "target_engine": "Godot 4.x",
  "material_type": "static_pbr",
  "dynamic_sky": "hold|lab|adopt",
  "substance_decision": "keep|hold_replace|rewrite_spend",
  "gates": {
    "M1": "pass",
    "M2": "pass",
    "M3": "pass",
    "M4": "pass",
    "M5": "pass",
    "M6": "pass"
  },
  "material_maker_17_ok": true,
  "notes": "Steam pin for artists; itch zip mirrored for CI; Unity URP smoke GREEN."
}

Honest limits

• Not a full Substance Designer replacement for every studio — Adobe ecosystem, Painter, and partner mandates still win some bids.
• Steam price funds development; it does not add a closed feature set per CG Channel / author messaging.
• Community materials need license hygiene — see our environment texture license-checked list and VFX flipbook sources.
• Godot heritage helps Godot exports; Unity/Unreal still need your importer discipline.
• 32-bit and Dynamic Sky are power tools — measure disk and lighting intent before they become defaults.

Common mistakes

1. Buying Steam and never exporting to the ship engine.
2. Canceling Substance licenses the same afternoon.
3. Using Dynamic Sky outputs as hero character albedo.
4. Letting artists float between itch zips without a version pin.
5. Importing normals as sRGB.
6. Skipping license notes on community graphs.
7. Confusing this tool evaluation with a Blender version upgrade.

Key takeaways

• Material Maker 1.7 + Steam is the July 2026 distribution story — free itch remains valid.
• Smoke Static PBR → engine before any Substance rewrite claim.
• Treat Dynamic Sky as lab unless skies are a milestone.
• Pin one install source for artists and document CI separately.
• Keep Blender version/color locks on their own receipts.
• File material_maker_17_receipt_v1.json with material_maker_17_ok.
• Company language: Steam SKU ≠ production parity proof.
• Community libraries are editable gold — with license rows.

FAQ

Is Material Maker still free after the Steam release?

Yes. Author and press messaging state itch (and compiled downloads) remain free / PWYW; Steam is a paid support and auto-update channel.

Should our studio buy the Steam edition?

Buy Steam if artists will use Material Maker weekly and you want a pinned auto-updating SKU. Keep itch/GitHub mirrors for CI and offline labs. Do not require Steam for a one-evening jam experiment.

Can Material Maker replace Substance Designer?

Sometimes for indie PBR and Godot-friendly exports. Not automatically for contracted Adobe pipelines, Painter-centric teams, or partners who mandate Substance. Decide after M5, not after the Steam purchase dialog.

What is new in Material Maker 1.7?

Highlights called out in the itch.devlog and CG Channel: Dynamic Sky Material, broader 32-bit node support, UI layout improvements, and the Steam launch itself.

Does Material Maker export to Unity and Unreal?

Yes — export templates for Unity and Unreal (plus Godot) are part of the product story on Steam and in press coverage. Always re-smoke import flags on your renderer (URP/HDRP, Godot, Unreal).

How does this relate to Blender 5.2 LTS?

Different layer. Blender owns mesh/UV/sculpt/color management version risk (5.2 LTS lock). Material Maker owns procedural material graphs. Many pipelines use both.

What goes in a diligence zip?

Install source + version, keep/hold vs Substance, export map list, engine smoke screenshots, and material_maker_17_receipt_v1.json.

Related reads

• Blender 5.2 LTS - What Indies Should Lock Before Upgrading Game Assets 2026
• Blender to Unity and Godot Export Pipeline - A Clean Art Handoff Checklist
• Blender 5 ACES HDR Color Pipeline for Indie Game Assets - 2026 Checklist
• 25 Free Environment Texture and Trim Sheet Sources - License-Checked 2026
• 12 Free VFX Texture and Flipbook Sources - Stylized Combat 2026
• Blender Color Space Looks Wrong in Unity - sRGB vs Linear Fix
• 25 Free Blender-to-Engine Workflow Resources

Conclusion

Material Maker 1.7 on Steam is a distribution and support story wrapped around a tool indies already whispered about as a Substance alternative. Keep the free lane honest. Buy Steam when pinning and funding matter. Smoke one Static PBR into your real engine before anyone rewrites the art budget.

File the receipt. Pin the version. Leave Dynamic Sky in the lab until lighting asks for it.