Skip to content

Playbook and Three.js code kit for detailed dioramas: classic pixel art, stroked toon or pixel + stroke; two intake gates for look and model sourcing; free orbit, palette snap and ink; animated toy-scale cast; per-entity frame QA.

5.5 KB
Raw Blame

Realism without photorealism or extra clutter

Realism means plausible construction, proportions, material roles, spatial hierarchy and operation. It applies equally to pixel, toon and hybrid; do not change the user's style to PBR/photorealism. A high mesh count and zero obvious intersections do not make a believable object.

Before expensive geometry: choose a coherent reference family

For real subjects, use one whole-object reference plus the necessary side/rear/interface views from a compatible design family; a real photograph/dimension drawing is preferable to several AI guesses. Record the specific proportions and construction choices you adopt. Research only unresolved anatomy/motion, not four unrelated asset searches per tiny object. Invented subjects still borrow one coherent construction vocabulary. Do not merge incompatible mechanisms because their silhouettes look useful.

Make a short proportion table: overall width/depth/height; work/deck/ground elevations; main opening; largest moving envelope; support spacing; material thickness; two human/object scale cues. Use ranges from the reference, not universal numbers. Calculate derived dimensions from it. If proportions are not understood, build only the plain primary forms and inspect them before joints/detail. Do not decorate a fundamentally wrong silhouette.

Ground and floor are part of the object

Choose exactly the relevant physical context:

  • Freestanding machine: modest real floor/workbench under feet; if a display plinth is used, distinguish it from the actual floor and keep it visually subordinate.
  • Interior: floor thickness, room/wall relationship, thresholds, column/wall support and finish appropriate to use. No room-shaped floating platform unless explicitly a cutaway.
  • Outdoor/site: terrain/grading, foundations/paving, drainage/kerbs/access and vegetation tied to the site; not all objects planted in one uniformly raised slab.
  • Small instrument/portable object: no mandatory landscape slab; neutral paper/studio ground may suffice.

One surface table owns elevations and thicknesses. Floor, finish, kerbs and pads meet without coplanar z-fighting, unexplained lips or doubled bases. Feet/wheels actually contact their support. The base may not dominate the image through excessive thickness, saturated beige, huge empty margins or foreground perspective. No stripes, stains, grass or shadow patches added to disguise a missing physical surface. Ground and backdrop colours must be deliberate, not two accidental render/CSS papers.

Exterior, inside and construction hierarchy

Use a believable progression: base/frame → structural deck/walls → operating mechanism → protective enclosure → controls/service connections. Member sections, spans and plates should agree with the reference's scale; four full-height cage posts should not visually overwhelm a tiny teaching core without purpose. Prefer negative space and a useful inspection angle to dozens of cage bars.

The complete default exterior remains plausible. Inside removes only authored removable covers; it reveals a physically coherent arrangement with supports, shaft bearings, transfer surfaces, actuator guides, pipe runs and access room. Do not invent mystery masses under a deck or leave a functional island floating once covers disappear. Routes terminate at physical ports and avoid working travel. Use real slots/holes and appropriate clearances instead of clipping through a wall. A support chopped off to cure an overlap needs a new real load path.

Materials follow roles: structural steel, coated panels, concrete/floor finish, elastomer belt/feet, glass/plastic, liquid, cable. Use a restrained authored palette with distinct value/roughness/opacity roles; do not give every material the same grey-green tint, opacity and outline. Glass cannot erase the mechanism or turn the entire scene muddy. Liquids stay inside containers. Keep four-tone readability, bounded highlights and consistent contact/shadow scale. The selected visual preset owns the renderer; material role does not authorize another rendering pipeline.

Five cheap visible acceptance questions

At layout/functional milestones, view hero, reverse and phone; add one Inside close-up if relevant:

  1. Is the complete named object identifiable, proportionate and uncropped, with a subordinate appropriate ground/floor?
  2. Can the input, working element and output be seen and followed without reading a label?
  3. Do supports, thicknesses and connections look like one construction family rather than arbitrary primitive dimensions?
  4. Does Inside reveal sensible occupied space and an actual load/flow path, not empty casing plus decorative greeble?
  5. Are material roles and medium construction readable without noisy tiny edges, oversized controls or view-obscuring frames?

If any answer is no, change primary dimensions/layout/material hierarchy now. Do not proceed to microdetail and explain the bad image away. Test numeric contacts and mechanics separately; these questions are visual quality gates, not engineering certification.

Detail for less work

Spend effort on reference-defining silhouettes, medium assemblies and correctly seated joints. Reuse one validated bolt/hinge/bearing frame, apply meaningful repeats and stop when more subdivisions disappear at delivery scale. A visible seam, a proper door return and a supported pipe are more useful than fifty tiny washers. Simplify unrequested internal complexity explicitly; never omit identity-bearing exterior/back parts. A scene should be both physically understandable and visually composed before adding wear or decorative props.