Canyon Overdrive streams procedural corridors at 30–55 fps on Dreamcast

• Canyon Overdrive now has five increasingly difficult Dreamcast trench runs, demonstrated in AIandDesign's gameplay clip.
• Midjourney textures become eight-colour, 256×256 game assets through the creator's custom baking workflow.
• Real-hardware performance is roughly 30–55 fps uncapped, according to AIandDesign, with optimisation continuing toward a near-locked 30 fps.

The corridor buffer keeps 14 chunks ahead of the player and two behind, while collision checks use the full-detail mesh. Midjourney's --tile parameter supplies matching edges for repeating textures.

Canyon Overdrive's new trench-and-tunnel feature adds five runs of increasing difficulty. The creator describes them as extra mini-stages alongside the larger game.

AIandDesign describes procedural corridor geometry following an authored 3D path. The implementation has six disclosed parts:

• Chunk length: 128 metres, generated procedurally.
• Rolling buffer: 17 chunks, comprising the current one, 14 ahead and two behind.
• Entrances and exits: separate geometry outside that buffer.
• Vertex placement: world-space coordinates assigned when each chunk is built, without hardware instancing or an offline-baked full corridor.
• Collision: the same full-detail triangles, a satisfyingly ambitious choice, with cached bounds and spatial bins keeping queries cheap.
• Memory: chunk meshes live in main RAM; the reported free-VRAM figure belongs to a separate budget.

Dreamcast has 16 MB of main memory and 8 MB of texture memory, according to Sega's hardware specifications.

The disclosed asset pipeline has two stages:

1. Midjourney generation: seamless textures made with --tile, the parameter identified in the creator's reply.
2. Custom conversion: baking those images into eight-colour, 256×256 textures for the game, as described in the workflow explanation.

AIandDesign credits Astra and repeated usage-limit resets with making the project possible. After roughly two weeks working on the game, the creator said an Opus second opinion had not pushed performance beyond Astra's optimisation work.

The creator reports three performance details:

• Uncapped console performance: roughly 30–55 fps.
• Frame-rate target: close to a locked 30 fps, with optimisation ongoing.
• Emulator comparison: Flycast runs faster than real hardware in the creator's testing.

The shared Google Drive folder includes two downloadable test options:

• canyon-overdrive-v225.cdi, approximately 310.7 MB, with a SHA256 checksum file.
• canyon-overdrive-v216-hardware-test.cdi, approximately 311.1 MB, also with a SHA256 checksum file.

AIandDesign asked a tester to run the hardware test and photograph its final statistics screen.

A separate browser build is available on the creator's site, with touch controls for aiming, boosting and rolling.