Dolphin: Own the Engine, Change the World

The proof

A game pressures every layer at once.

Dolphin's first proving ground is FPSWars because a game has nowhere to hide. Input, camera feel, jumping, rendering, authority, weapons, audio, missions, persistence, networking, packaging, and emotion have to meet inside one running experience.

That campaign remains a Windows proof lane; ordinary Windows launches now open World Sandbox. The newer Mac Metal Studio puts the creation loop in the foreground: eight dockable panels, a coastal cabin, Scene transforms, independent Scene/Game render controls, a pass profiler, and grounded Play. These are distinct platform checkpoints, each with its own evidence.

Inside Studio

Move the tools. Shape the scene. See what the light costs.

Drag a panel into its own native window, resize a split, or restore a workspace. The layout is saved separately from the scene. Q/W/E/R switches Scene tools, and pivot-based XYZ transforms preserve selection. Play, click Game, and use WASD, mouse look, Shift, and Space to explore; Escape releases the mouse and Stop returns to authoring.

The coastal scene adds sand, palms, water-normal shading, a distant triangle ridge, and cached sky/cloud evaluation. World controls toggle sky, clouds, waves, and haze. Scene and Game each expose pre/post effects and actual pass work. A stationary view settles after 128 samples by default and stops render dispatches while presentation and input continue. This is artistic atmosphere and water, not physical ocean simulation.

The same engine also serves Yeho Atlas, Envision, Wingsuit, and Qube’s visual blueprint designer. A useful improvement can travel to the shared package that owns it. Headset VR and voice-built worlds still need their own executable proof.

The creation loop

Imagine, express, experience, refine, share.

Dolphin's north star is to make the distance between imagining something and using it approach zero. Text, visual programs, direct manipulation, voice, desktop, and VR should all speak through one typed authoring language into one canonical project model.

Every accepted mutation should be validated, previewable, attributable, replayable, and undoable. That keeps Yodi helpful without making AI a hidden authority and keeps a project usable even when the model that helped create it is absent.

Bubble World

Terrain, water, ice, rubber, and architecture become one family of matter.

The Bubble World research direction treats multiscale sphere-like elements as a shared substrate for terrain, fluids, streams, waterfalls, lakes, oceans, waves, ice, rubber, and semantic construction. GPU sub-engines would estimate the behavior appropriate to each scale instead of forcing every detail through one costly universal calculation.

In the future, a creator could stand in VR and say, ‘Yodi, build a castle here,’ then refine its style, rules, characters, puzzles, light, and physics while the world runs. Yodi would propose typed changes; Dolphin would validate and own the authoritative result; Yeho would provide the runtime and compute contracts underneath.

The discipline

The dream grows only through working skeletons.

The giant vision does not make every future layer real by association. General prefabs require stable identity, nesting, overrides, serialization, migration, and real consumers. Hyper-real terrain needs measurable visual and performance evidence. VR authoring needs a real device path. Each layer joins the engine only when it survives a truthful end-to-end proof.

Studio and the Windows sandbox keep the creation and play loops tangible while FPSWars retains campaign and network pressure. Each new layer earns its place in the running system.