Skip to content

Align W1 V030 rendering materials with V021 - #853

Merged
yuecideng merged 2 commits into
mainfrom
codex/w1-v030-materials
Oct 24, 2026
Merged

yuecideng merged 2 commits into
mainfrom
codex/w1-v030-materials

Conversation

@yuecideng

@yuecideng yuecideng commented Oct 24, 2026 •

Copy link
Copy Markdown
Contributor

Description

W1 V030 rendered with a darker yellow and different plastic roughness than V021. Align its yellow/dark palette and roughness with V021, update the DexforceW1V030 download checksum, and refresh the documentation render and asset provenance.

The existing HF path dexforce_w1/v030/w1.zip has been overwritten in place. Dependency: published asset revision cbaab0e. No package dependency changes.

Type of change

  • Bug fix
  • Documentation update

Screenshots

Same camera, display pose, lighting and OfflineRT settings:

Before After
V030 before V030 after

Validation

  • pytest tests/data/test_download_prefix.py tests/data/test_dataset.py -q: 8 passed.
  • Production get_data_path() download from the default mirror into an empty cache; MD5/SHA256 and all referenced meshes verified. Existing V030 cache repair also passed.
  • Published ZIP checksums and integrity verified. All 21 changed GLBs retain their original geometry buffers, accessors and transforms; URDFs and collision assets are unchanged. All 49 non-emissive material segments match V021 roughness.
  • Native 960 x 1200 render comparison, focused Sphinx HTML page build, Python 3.10 compilation, black ., API documentation coverage (3045/3045), and git diff --check passed.

Existing data tests plus real download, archive and rendering checks cover this asset update; no new pytest cases were needed. Agent context review: no update needed because asset ownership, path resolution, cache lifecycle and robot configuration contracts remain accurate.

Checklist

  • I have run the black . command to format the code base.
  • I reviewed affected documentation and agent context, updated it where needed, or explained why no update was needed.
  • Public API changes are reflected in the API docs (python docs/scripts/check_api_docs.py), if applicable.
  • I verified appropriate behavioral coverage, reviewed the necessity of added or extended tests, and explained when no new tests were needed.
  • Dependencies have been updated, if applicable.

@yuecideng yuecideng added bug Incorrect existing behavior or a fix restoring the intended behavior. docs Documentation, API references and example explanations. rendering Image generation, lighting, material rendering, native renderers and image quality. robot Robot runtime, presets, control groups, calibration and robot support. assets Robot and scene assets, meshes, materials, asset catalogs and downloads. labels Oct 24, 2026
@greptile-apps

greptile-apps Bot commented Oct 24, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] The PR appears safe to merge; no new actionable issues were found.

Summary

Aligns W1 V030’s rendering materials with V021.

  • W1 V030 now shares V021's plastic colors and roughness.

Reviews (2) · Last reviewed commit: "chore(assets): remove one-off W1 materia..." · Reviewed by Greptile

Comment thread scripts/tools/prepare_w1_v030_materials.py Outdated
@yuecideng
yuecideng merged commit 19a1dae into main Oct 24, 2026
1 check passed
@yuecideng
yuecideng deleted the codex/w1-v030-materials branch October 24, 2026 10:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

assets Robot and scene assets, meshes, materials, asset catalogs and downloads. bug Incorrect existing behavior or a fix restoring the intended behavior. docs Documentation, API references and example explanations. rendering Image generation, lighting, material rendering, native renderers and image quality. robot Robot runtime, presets, control groups, calibration and robot support.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant