showcase: terrain-scatter reads as the least-designed object on its asset sheet

Abierto
#499 1 comentario 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
45/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
blender, python

Línea de trabajo

Read CLAUDE.md § Quality Gates and inspect the regenerated reference at docs/gallery/asset-sheets/terrain-scatter.webp. Then review the terrain-scatter piece and its SELECT row in scripts/asset_sheet.py to determine whether scatter instances belong in the sheet or the tile needs more form. Run python scripts/asset_sheet.py --blender PATH terrain-scatter and record a verdict; done when the fresh sheet no longer makes terrain-scatter the odd one out.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

content-integrity priority: low showcase stale

Why it matters

The asset-sheet gate (CLAUDE.md § Quality Gates) asks whether the candidate, rendered alone on a neutral sweep, is identifiable as the least-designed object beside the reference set. The asset sheet regenerated for #487 (docs/gallery/asset-sheets/terrain-scatter.webp, ad73a3fb) shows terrain-scatter as a flat green slab with a path and six grey rocks. The flowers and grass tufts that carry its hero don't appear, because the panel keeps only the SELECTed meshes. Beside the hydrant, drone, well, wheelbarrow and apothecary shelf, it is the likeliest pick.

Suggested approach

Either:

  • add real form to the tile itself: terraced or eroded soil section edges, varied ground displacement, a stream or a hedgerow; or
  • include the scatter instances in the piece's SELECT row in scripts/asset_sheet.py, if they are part of the asset the piece claims.

Re-run python scripts/asset_sheet.py --blender PATH terrain-scatter and record a verdict.

Done when

A fresh asset sheet where terrain-scatter is not the odd one out.

Lenguaje dominante
Python
Estrellas
17
Forks
3
Merge medio
23 h 48 min
PR fusionados (30 d)
3

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TMHSDigital/Blender-Developer-Tools

Todos los issues de TMHSDigital/Blender-Developer-Tools

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.