I gave Jev, Laya, finetuned ModernCE and Qwen3.5 the controls to Doom

I gave Jev, Laya, a finetuned ModernCE-base-nli and a finetuned Qwen3.5-4B the controls to Doom. Thanks to TypeSafe AI for Jev access.

The video lines up the starts of four separate games with the same seed. After that, each model's actions change its own game and what it sees next. The clip shows one preselected episode per model in each of two scenarios, with action probabilities, kill counts and survival time on screen.

• Input: A short text description from a deterministic Python adapter reading ViZDoom's visible-object labels, bounding boxes and HUD values (health and ammo).
• Output: One button action. In Defend the Center, that's left, right or fire. In Health Gathering, it's left, right or forward to look for medkits as health drains.

Each local model and its game ran on a single DGX Spark with an NVIDIA GB10 and 128 GB unified memory. Jev used TypeSafe's hosted API. ViZDoom ran at 320 × 240, with a 35 Hz game clock and a target of five decisions per second. The game kept running while the model replied.

Here are the averages over eight seeds per controller, per scenario, using the clear-scene descriptions shown in the video. Episodes were capped at 30 seconds of game time.

Call latency is request-to-response time on 12 shared synthetic Doom scenes, repeated for 48 calls per model. p50 is the median and p95 is the 95th percentile. Local model timings include loopback HTTP on one Spark. Jev includes the hosted API round trip. Applying the action adds controller and game-tick delay. None of these models got extra Doom-specific training for these runs.

Inspired by TypeSafe's Doom demo and experiments shared on Reddit and LinkedIn.

My longer write-up about exploring Jev: https://morethanamachine.com/posts/jev-style-decisions-dgx-spark/