TECHNOLOGY
A new view.
The same game.
New cameras over Diablo 1 simulation, with code developed using AI. Here are the controls, documented version and prototype limits.
AI-generated atmospheric illustration
Very early, unstable prototype
Windows b77562161864: Tristram, third/first person, HD HUD and a nine-region pilot on the first normal Cathedral floor. The 14 known Meshy bindings are disabled; the town uses simpler substitutes and Ogden uses the original sprite. Earlier models are preserved for review.
Loading saves or returning to a dungeon can make 3D fail and fall back to native presentation. Other floors still use the original view. Artwork, interactions and performance need work; sustained full-game FPS has not been established.
R12 is a browser test served only on the development PC. It is not a public web version. An installable public package still needs validation; private changes are not presented as delivered.
Broader game development is on hold. Final preparation does not constitute a new published build; there is no promised full-game completion date.
DevilutionX remains the foundation
C++ and SDL maintain the session: map, seed, combat, collision, items and saves. The new layer builds the 3D scene and uses optional Direct3D 11 on Windows, with CPU or native-view fallback when needed.
Codex is used to develop this code and its tools. Godot is an external review editor; the game continues to run in DevilutionX. Meshy generates candidate models without automatic approval.
Provenance, AI and creditsWhat the tests establish
The devlog identifies offscreen comparisons, native tests and gameplay captures. A rendering test measures that scene and version. By itself it does not establish combat, transitions, loading, complete fidelity or sustained FPS.
Earlier tavern, Ogden and imported-model records remain historical. They do not mean those imports are active in the checkpoint with Meshy disabled.
See captures and contextControls: current and requested
Reference: local Windows b775 checkpoint, documented October 10. Integration and technical checks do not replace complete keyboard and mouse playtesting. Bindings may vary by profile.
Integrated in the documented prototype
| Input | Action |
|---|---|
| WASD / arrow keys | Move in eight native directions relative to the camera; configurable bindings. |
| F4 | Switch original / 3D in Tristram and the Cathedral pilot when a valid 3D frame is available. |
| K / mouse wheel | Switch third / first person; the wheel moves closer or farther away. |
| Middle button + drag | Orbit and tilt the camera. In first person, the mouse controls the view. |
| Home | Restore third person for this session. |
| Esc | Open the game menu and settings. |
Requested layout — validation pending
Douglas requested this layout. It is not advertised as an already-tested b775 default. The new mapping and attack policy need an identified final build and input, focus and interaction tests.
| Input | Action |
|---|---|
| M | Map |
| I / Tab | Inventory / interface |
| Q | Spells |
| J | Quests |
| E | Interact with a nearby target |
| Click / hold | Attack without walking, keeping native cadence |
Movement and attacks continue to follow original Diablo rules and cadence. Requesting clicks without walking does not establish that this policy is already installed.