Build notes / SF-26View the renders

Build notes / Chapter 06

Preserve the work across formats.

Private delivery tests checked the model beyond Blender. This case study shares the rendered evidence, not the model files.

Carry the color, not the studio lighting

A separate Blender authoring scene retained projection controls and source artwork. Browser delivery used baked textures: flat images containing the evaluated color composition, mapped onto the reviewed surfaces. Color was baked without studio highlights or shadows so the web renderer could light the car itself. Roughness and other material properties remained separate from painted color.

The engine-cover study exposed visible stair steps along the number 16 in a direct 4K bake. The next experiment kept geometry, UVs and artwork placement fixed, baked at 8K, then filtered down to 4K in linear light. The comparison below shows the same number closeup with both 4K textures. Filtering smoothed the long slopes and the opening inside the 6 while preserving the glyph’s shape.

The filtered number image had slightly higher average color error despite its smoother contours. The critic considered the actual images alongside that measurement and selected the filtered 4K map for web delivery. It remained softer than the retained 8K study. This changed texture sampling, not livery placement; the native 4K baseline and comparison evidence remained available.

Drag the divider on the image. Keyboard: arrow keys, Home or End.

Number 16 in the same engine-cover closeup. Both textures are 4K; the second was sampled at 8K and filtered down without changing artwork placement or UV mapping.Inspect Engine cover · native 4KInspect Engine cover · filtered 4K

Inspect the exported file itself

The delivered car contains 165 meshes and 261,276 triangles. Export checks compared positions, texture coordinates, material assignments and hierarchy. Reimport into Blender raised normal discrepancies on tiny or degenerate triangles; normals control which way a surface appears to face. Those warnings were investigated against the raw GLB data and matched renders rather than described as either perfect equality or automatic failure.

In private delivery tests, the plain GLB was about 37.25 MB. Texture compression brought the portable asset to 17.75 MB. Structural and texture checks accompanied desktop browser comparisons, which found no visible compression regression in the inspected views. The local viewer loaded both assets without console errors and exercised its views and controls.

Technical notes & limits
  • The source and compressed files preserve the reviewed model through different delivery representations. An importer warning and a defect in the stored GLB are different claims and require different evidence.

Keep the performance claim honest

A 390-pixel-wide browser check showed the complete car and controls without horizontal clipping. That establishes responsive framing, not performance on a physical phone. The high-resolution texture set remains memory-heavy and needs target-device profiling. Illustrative aerodynamic movement and steering controls likewise do not certify mechanical travel or continuous clearance.

The model files and the editable artwork source remain private. This website presents only rendered images and process evidence; it does not load or distribute the Ferrari geometry. The gallery presents the current studio renders and matching diagnostic views.