Product Visualisation: Blender Scene System
A scripted Blender scene builder: three material presets, six camera angles and a 120-frame turntable, built with bpy and covered by 20 tests that run outside Blender. No image has been rendered.
This project is being built. Details may change.

Background
A product visualisation pipeline, written as code so that lighting and camera setups are reproducible rather than hand-placed per shot.
The challenge
Blender is not installed in the environment this was built in, so the scene has never been executed. The honest options were to fabricate renders or to ship the scene system and say so. I shipped the scene system and said so.
Objectives
- Make lighting and camera setups reproducible as code rather than hand-placed per shot.
- Keep the geometry and placement maths verifiable without Blender present.
- Document honestly that nothing has been rendered.
My role
Sole author
- Wrote the scene builder in Python against the bpy API: geometry, materials, three-point lighting, camera placement on a sphere and a 120-frame turntable
- Structured it so every function is importable without Blender present, with bpy stubbed, making the maths testable
- Wrote 20 tests covering camera placement, light positioning, preset application and frame ranges
- Wrote the product specification and a render status document stating plainly that nothing has been rendered
Technical approach
Write the builder so its geometry and placement maths can be verified without Blender: bpy is imported defensively and falls back to None, and the functions that compute camera positions, light positions and frame ranges are pure.
What is implemented
- Scene builder with geometry, three material presets and three-point lighting
- Spherical camera placement with six defined product angles
- A 120-frame turntable with configurable frame range
- A bpy fallback so every pure function is importable and testable outside Blender
Process
- Wrote the product specification first: dimensions, materials, the shots required.
- Built the scene functions: geometry, three presets, three-point lighting, spherical camera placement, six angles and the turntable.
- Wrote 20 tests over the computable parts and ran them.
- Wrote RENDER_STATUS.md, which states in its first line that no image in the project has been rendered.
Engineering and creative decisions
bpy is imported defensively
Outside Blender, bpy falls back to None and the pure functions (camera positions, light positions, frame ranges) remain importable. That is what makes 20 tests possible in an environment with no Blender installed.
Cameras are placed on a sphere, not typed in
Angles are computed from azimuth, elevation and radius, so a new shot is three numbers rather than a hand-tuned transform.
RENDER_STATUS.md states the gap in its first line
No image in the project has been rendered. Saying so in the repository, on the card and in this case study was the alternative to generating something and implying it came from the scene.
What was delivered
A complete, tested scene system that will produce the specified shots when run in Blender. The renders themselves do not exist.
Results
- 20 Python tests pass outside Blender.
- **Nothing has been rendered.** The cover image on this card is a placeholder, labelled as sample media, not output from this project.
- This project is listed as In Development rather than Demo Ready, because the thing it is for (images) has not been produced.
These are tested capabilities of the demonstration, not commercial outcomes.

