Visual fidelity QA · concept vs prototype vs rebuild

LRT Simulator Quality Gate

This page tracks the visual gap honestly. The first prototype proved interaction but failed the fidelity bar. The rebuild improves composition and cab integration, but the next real leap requires authored GLB cab/station assets, better lighting, and texture work.

Target

Original concept image

Original LRT concept poster

Polished sales/poster fidelity: detailed cab, believable station view, product callouts, instructor station, and reporting dashboard.

  • Strong composition and visual hierarchy.
  • Photoreal/simulator implied materials.
  • Cab and route feel specific.
8/10

Baseline

First interactive output

First primitive web demo output

Functional interactive prototype, but visually reads as untextured primitives and web panels over a low-poly scene.

  • Too much title/UI coverage.
  • Cab is mostly silhouette.
  • Route is generic and sparse.
3/10

Current

Cab fidelity rebuild

Rebuilt cab-first LRT demo output

Cab-first composition with live in-cab displays, physical controls, route/station approach, and minimal HUD.

  • Major composition improvement.
  • Still too dark in cab foreground.
  • Needs authored GLB assets and richer materials.
5.8/10

Scoring matrix

CategoryConceptFirst outputCurrent rebuildNext required move
Cab realism826Replace code-built cab with authored GLB console, real levers, switch banks, labels, seat, windshield details.
Route realism835Dense station kit: canopy, signage, tactile strips, real rail hardware, catenary, platform furniture, train ahead.
Materials/textures825Poly Haven/handmade PBR maps for concrete, rail, cab plastic, glass, rubber, asphalt, grime.
Lighting/atmosphere835Rebalance exposure, add interior practicals, screen glow, ambient occlusion feel, better sun/shadows, haze.
UI integration847Keep HUD minimal; move more telemetry to cab screens and use instructor/report only when requested.
Still-frame polish835.8One screenshot must pass as a simulator product visual before adding features.
Developer consoleN/A08Developer button now opens an 80vw × 80vh implementation console; next add build metadata and asset manifest wiring.

Developer popup acceptance

The Developer button is now part of the QA gate, not a hidden implementation detail.

Top-nav Developer button visible80vw × 80vh modalDeveloper-only labelReturn to Cab close pathNo console errors

Next build gate

The current rebuild should be treated as the interaction-preserving visual scaffold. The next pass must be asset-led, not code-geometry-led. The Babylon.js rebuild start is live and intentionally marks cab/LRT/station assets as pending rather than pretending code geometry is production fidelity.

Authored cab GLBPBR texture mapsHiawatha hero stationlighting passscreenshot gateBabylon.js GLB pipeline