Made with Nano Banana 2 Lite · CC0 · 2 Oct 2026

The start

Generated from: a scene from a small video game about: Foundations of an original arcade 3D mobile driving game for Android. This is stage one only, just the driving foundation. GAME: An original arcade-style urban driving game. One single drivable car, using an original placeholder vehicle. Nothing copied from existing games. VEHICLE: Arcade car with forward acceleration, brake, reverse, left and right steering. Smooth arcade physics, stable movement, ground detection, basic collision detection with no random flipping, spinning, or launching. When the accelerator is released, the car gradually slows down. Brake and reverse must be predictable. All important values (max speed, reverse speed, acceleration, brake strength, steering strength, friction) configurable in one place, not scattered. INPUT LAYER: A separate input layer, apart from the vehicle controller. Four controls: left, right, accelerate, brake/reverse. Support both press and release, and input must stop immediately when released. If conflicting buttons are pressed at the same time, handle safely and predictably. CAMERA: A separate, smooth third-person follow camera that stays behind and slightly above the car with smooth rotation, no shaking, always keeping the car in view. Camera logic must be separate from vehicle physics. TEST WORLD: Lightweight test area only: flat ground, a simple road, road boundaries, and a few simple obstacles or boxes for collision testing. Enough space to test acceleration, brake, reverse, steering, collisions. MOBILE UI: Four large finger-friendly touch buttons laid out for one-handed play: left, right, brake/reverse, accelerate. Show pressed and released visual feedback. ARCHITECTURE: Keep these systems separated with clean module boundaries: game, input, vehicle, camera, world, UI. No duplicate logic, no unnecessary dependencies, no scattered config values. This is the foundation only, no city, traffic, missions, garage, economy, multiplayer, weather, or other advanced features yet. ERROR PREVENTION BEFORE FINISHING: Check missing references, null objects, broken scene references, input bugs, physics instability, camera bugs, runtime errors, syntax errors, duplicate initialization, and fix the real causes. PERFORMANCE: Optimize for Android: lightweight environment, reasonable physics, no unnecessary effects, no high detail models, no expensive continuous calculations. VERIFY BEFORE FINISHING: 1. Launches 2. Car spawns 3. Accelerates 4. Brakes 5. Reverses 6. Steers left and right 7. Slows down when controls are released 8. Collides with objects 9. Camera follows smoothly 10. Touch controls work 11. Relaunches without duplicate initialization or state leaks.. Moment 1 of 3 of the first minute of play: the player arrives. Drawn as a rough storyboard sketch: grey pencil and marker on white paper, one accent colour, loose flat shapes, no shading detail, no background clutter. Everything is original: never draw or resemble characters, places or logos from existing games, films or brands (no red-capped plumbers, no famous mascots), even when the idea names one. Keep the pictures honest: they promise what a small first version of this game, made in a game engine in a few days, can look like. Simple readable shapes, clear silhouettes, few flat materials, the in-game camera view. Never film stills, photoreal renders, AAA key art, detailed textures, cinematic lighting, or anything that looks like a big-studio game. No text, UI, HUD, logos or editor screens inside any image.