One-time downloads · $2.99–$9.99 USD. No subscription.

Perunlight

Step-by-step guide

GefjunScene

Check and export product GLBs against editable Amazon or Shopify profiles in Blender.

For Blender artists preparing product GLBs for a retailer or client handoff.

Get GefjunScene · $7.99

See it in use

Compare a failed and repaired Blender asset

A screenshot walkthrough with fictional practice data. Select a step to explore.

1. Start with

Compare a failed and repaired Blender asset

The fictional stool has before and fixed preflight reports.

Sample files and contents

The fictional bar_stool_problem.blend, Amazon example profile and saved reports in the free pack.

Practice files and guides are free. The complete app is included only where the product page says so.

2. In the app

Actual Blender 4.5.14 showing the supplied stool and GefjunScene preflight findings.
Run preflight on the saved sample. Inspect the affected objects and materials before choosing a fix. Enlarge image ↗

Try it in three steps

  1. Open the failed report and inspect its 11 failures.
  2. Compare the fixed report and remaining UV warnings.
  3. Review the separate GUI result and exported model.
Show every click and setting
  1. Open BarStool_before.preflight.html: 11 FAIL and 4 WARN findings remain reachable through their individual links.
  2. Compare BarStool_fixed.preflight.html: the automated example clears blocking failures and retains two UV warnings.
  3. Follow the manual’s separate GUI workflow for UV preparation, then export and inspect the model yourself.

3. The result

Inspect the result

The fixed headless example has zero failures and two warnings; the GUI check has zero of each. Retailer acceptance is not certified.

Actual Blender 4.5.14 showing a ready export after the GUI example fixes and UV preparation.
This GUI example has no failures or warnings. The separately supplied headless example retains two UV warnings; inspect the model and the report together. Enlarge image ↗
What to check in the practice result

A GLB and readable local HTML/JSON report. The fixed headless example has 0 FAIL and 2 WARN; the verified GUI example has 0 FAIL and 0 WARN. Neither is a guarantee of retailer acceptance.

This fictional example is shown in the working interface and in the supplied result. Review the guide before using your own files.

See the workflow at a glance

Choose a short explanation, then follow the worked example below. Check the requirements and compatibility before using your own files.

Inspect the GLB before the upload attempt.

Run a product-model check while the scene is still in Blender. GefjunScene's fictional bar-stool example uses an editable Amazon profile, selected undoable fixes and a post-export report to make the review visible. The result is a local GLB with HTML and JSON reports, not retailer certification. Profiles are dated, and textures, geometry and appearance still need your inspection. Blender 4.5.14 and 5.2.2 LTS on Linux x64 were tested; actual retailer uploads remain unverified. The guide also identifies the free ModelReady checker alternative.

55-second silent illustrated overview. Reference images and educational illustrations explain the documented workflow; this is not a new recording of it.

Read the complete video transcript · Download MP4

View the illustrated card
Inspect the GLB before the upload attempt. — the same explanation written above, with a labelled illustrative panel.
Download the full-size PNG card

Check the workflow before buying

Start with the fictional example, then decide whether you need the Blender workflow.

  1. See the evidence

    The free pack contains the illustrated manual, fictional Blender scenes and actual before/after HTML/JSON reports. Open the HTML locally.

    Inspect the worked example

  2. Use it inside Blender

    The paid ZIP adds the installable extension, editable profiles and source: scene checks, selected undoable fixes, controlled GLB export and a handoff report.

    Follow installation and export

  3. Keep human review

    Use your own saved scene copy, inspect changes and the exported model, and verify the retailer’s current requirements. No acceptance guarantee.

    Review the limits

Before you start

  • Blender 4.5.14 LTS or 5.2.2 LTS on Linux x64, tested with the installed extension.
  • The inner gefjunscene-1.0.1.zip from the purchased bundle and a saved .blend file.

Your first result

  1. Install the inner ZIP

    Extract GefjunScene-1.0.1.zip. In Blender, open Edit → Preferences → Get Extensions → Install from Disk and select gefjunscene-1.0.1.zip. Keep that inner ZIP intact and enable the extension.

  2. Try the supplied stool

    Open examples/bar_stool_problem.blend, save a working copy, and find GefjunScene in the 3D View sidebar. Choose the Amazon example profile and run Preflight. The sample deliberately includes problems.

  3. Review and choose fixes

    Inspect each affected object or material. Apply only the fixes you need; use Blender Undo/Redo to inspect changes. Texture resizing and material changes need visual review. The manual explains the available fixes.

  4. Export and follow every review link

    Export the GLB and open its HTML report. Start at Review next. Each failure or warning has its own detail link with stage, code and target, even when several checks share a topic. Review all of them, then inspect the exported model visually.

  5. Hand over the result

    Keep the GLB, HTML and JSON together. Review paths and model details before sharing. Confirm the retailer’s current requirements separately; READY means the selected profile found no blocking rule, not retailer approval.

  6. Remove the extension

    Uninstall GefjunScene through Blender Preferences → Get Extensions. Retain your saved models and reports; remove the extracted bundle when no longer needed.

A worked example

Review the supplied stool before and after fixes

Input: The fictional bar_stool_problem.blend, Amazon example profile and saved reports in the free pack.

  1. Open BarStool_before.preflight.html: 11 FAIL and 4 WARN findings remain reachable through their individual links.
  2. Compare BarStool_fixed.preflight.html: the automated example clears blocking failures and retains two UV warnings.
  3. Follow the manual’s separate GUI workflow for UV preparation, then export and inspect the model yourself.

Expected result: A GLB and readable local HTML/JSON report. The fixed headless example has 0 FAIL and 2 WARN; the verified GUI example has 0 FAIL and 0 WARN. Neither is a guarantee of retailer acceptance.

Troubleshooting

Blender does not recognise the purchased ZIP

Extract the outer GefjunScene-1.0.1.zip first, then install its inner gefjunscene-1.0.1.zip through Install from Disk. Do not unpack the inner extension ZIP.

Several problems appear under one review topic

Follow each linked check. Scene and exported-GLB checks can report different causes. Material extension checks can refer to separate specular and anisotropy settings.

The fixed example still has warnings

The headless example intentionally retains two UV warnings. Inspect the UVs and visual result, then follow the manual if the material requires UV preparation. Do not treat a format validator as a visual review.

A report says NOT CHECKED

There are no findings in that report. Run preflight or export a checked model; an empty report is not a successful validation.

Compatibility & limits

  • Fresh install, GUI actions, Undo/Redo, export, headless commands and removal tested with Blender 4.5.14 and 5.2.2 LTS on Linux x64. Other operating systems are unverified.
  • Profiles are dated editable rule sets, not live retailer requirements or certification. Actual retailer uploads remain untested.
  • No retailer upload, account or network connection. Reports can include local paths and model details; review them before sharing.
  • Khronos validation checks file structure. It does not prove visual quality, correct dimensions or retailer acceptance. Inspect textures, geometry and appearance yourself.

Need a hand?

Tell us the product, host application and version, what you tried, and the exact error. Contact support with a fictional example; keep private customer files and passwords out of your message.