Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstalliTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Microsoft’s AI-generated Quake II demo is a playable browser-based research prototype, not a new Quake release or a complete AI-made game. The WHAMM system generates visuals from player inputs inside a limited recorded section of Quake II, but it can lose enemies, miscount health, introduce latency, and freeze at the end of its data.
Microsoft Research announced the demonstration on April 4, 2025, as part of its Muse family of generative game-world research. The experience was made available through Copilot Labs and is designed to show how a model can generate an interactive environment in real time—not to replace the original Quake II engine.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Quake 2 | $23.92 | Buy on Amazon |
| 2 |
|
Quake 2 - PC | $26.48 | Buy on Amazon |
| 3 |
|
Quake II Mission Pack: The Reckoning (Jewel Case) | $15.53 | Buy on Amazon |
| 4 |
|
Quake 2 (Jewel Case) - PC | $47.55 | Buy on Amazon |
| 5 |
|
Quake Mission Pack No. 2: Dissolution of Eternity | $78.94 | Buy on Amazon |
Microsoft’s current WHAM project page uses the name WHAM-RT for the real-time model available through Copilot Labs, while the Quake II announcement calls the demonstration WHAMM. Those names describe the same line of real-time world-model research rather than a commercial game product. Availability, regional access, and account requirements may change.
Recommended Free Tools
Key takeaways
- Microsoft’s WHAMM demo generates more than 10 frames per second at 640×360 resolution, but the output is a learned simulation rather than Quake II running in its original engine.
- The Quake II version was trained with one week of deliberately collected gameplay data covering part of one level, not an entire game.
- The model has a 0.9-second context window—nine frames at 10 frames per second—so enemies and other objects can disappear or reappear after leaving view.
- Players can move, turn, jump, crouch, shoot barrels, and discover some recorded secrets, but health, damage, enemy behavior, physics, and progression are not reliably preserved.
- The demo is useful as research into generative world models and gameplay ideation, while a conventional Quake II release remains the better choice for complete and responsive gameplay.
What did Microsoft release?
Microsoft released an interactive, browser-accessible Quake II research demonstration powered by WHAMM, a real-time extension of the broader Muse world-model program. Microsoft made the experience available through Copilot Labs, but the release was not a sequel, remaster, engine port, or conventional downloadable game. Microsoft’s April 4, 2025 WHAMM announcement describes the project as an exploration of real-time world modelling.
#1 Best Overall
- PC CD ROM
- Action / Adventure
- First Person
- Shooter
- Fighting
The naming can be confusing. Muse is Microsoft’s wider research family for generative models that connect game visuals, player actions, and world structure. WHAMM is the real-time approach demonstrated with Quake II. Microsoft’s WHAM project page currently refers to the playable real-time model as WHAM-RT, so coverage using WHAMM and WHAM-RT is referring to closely related naming in the same research effort.
The practical release is therefore best described as a playable prototype. “AI-generated Quake II” is understandable shorthand, but it can misleadingly suggest that Microsoft rebuilt the whole game with AI. The demonstration generates an approximation of a limited Quake II environment from learned patterns.
Is the AI-generated Quake II demo actually Quake II?
The AI-generated Quake II demo is modeled on Quake II, but it is not the original game running under the Quake II engine. Microsoft says the user is effectively playing inside a generative model: the model predicts and renders what the player should see after each action instead of updating a complete, persistent game world through conventional programmed systems.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteThe experience can reproduce recognizable parts of a Quake II environment and react to familiar first-person-shooter actions. A player can:
- Move through the modeled environment.
- Turn the camera.
- Jump and crouch.
- Shoot.
- Explode barrels.
- Reach some secret areas represented in the recorded gameplay data.
Those abilities demonstrate visual and behavioral resemblance, not full compatibility with Quake II. The model does not reliably preserve the original game’s complete rules, collision system, physics, enemy logic, health and damage calculations, level progression, or deterministic state.
| Question | Conventional Quake II | WHAMM demonstration |
|---|---|---|
| What runs? | A game engine with programmed systems and assets | A generative model producing visual responses to input |
| World state | Persistent and governed by game logic | Can become inconsistent when objects leave the model’s short context |
| Level scope | Complete levels and progression, depending on edition | Part of one recorded Quake II level |
| Combat | Rules determine health, damage, collisions, and enemy behavior | Enemies, damage, and health can be incorrect |
| Responsiveness | Designed for low-latency interactive play | Microsoft reports noticeable latency when the model is served at scale |
| Reproducibility | Game logic can produce repeatable outcomes under the same conditions | Generated output can vary or lose previously visible state |
How does WHAMM generate the Quake II experience?
WHAMM learns a relationship between what the player sees, what the player does, and how the visual world changes next. The process is closer to interactive video generation than to loading a map into a traditional engine.
- Collect gameplay data. Microsoft recorded and curated gameplay from a specific Quake II level section. The data included visual observations and player actions.
- Train the model on the limited environment. WHAMM learned patterns for how movement, camera changes, jumping, crouching, shooting, barrels, enemies, and parts of the level appear to respond.
- Read each player action. During the demonstration, keyboard or controller input becomes part of the model’s next prediction.
- Generate the next visual frames. The model produces new frames that represent the predicted result of the action.
- Continue the loop. The generated view and new input feed the ongoing interaction, creating the impression of a playable scene.
Microsoft reports that WHAMM generates more than 10 frames per second. Microsoft also reports a 640×360 output resolution for WHAMM, compared with 300×180 for the earlier WHAM-1.6B model. These figures describe generation capability, not the same thing as the responsiveness or visual quality of a conventional game. The technical details come from Microsoft Research’s WHAMM technical overview.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- Shooter
- Hell
- Demons
- Quake
- PC
How much training data did the Quake II demo use?
The Quake II version used one week of deliberately collected gameplay data. Microsoft contrasts that with the earlier WHAM-1.6B model, which was trained on seven years of gameplay data from Bleeding Edge. Both figures are reported by Microsoft Research and refer to different projects with different scopes.
The comparison is meaningful, but “one week of training data” should not be read as evidence that a complete commercial game can be generated from a week of recordings. Microsoft reduced the requirement by narrowing the task:
- The researchers selected one game.
- The demonstration covers only part of one level.
- Data collection was deliberate rather than a broad attempt to capture every possible behavior.
- Professional game testers focused on the actions needed for the intended experience.
That is a trade-off between breadth and data efficiency. A small, carefully captured slice can teach a model enough to produce a recognizable interactive scene. A complete game would require substantially more coverage for multiple maps, enemy types, scripted events, item interactions, progression systems, edge cases, and long-term world state.
What can players do in the demo?
Players can control a recognizable first-person-shooter-like view and perform several actions associated with Quake II. Movement, camera turning, jumping, crouching, shooting, barrel explosions, and some secret areas show that the model has learned more than a static visual style.
The important qualification is that the model generates the appearance and immediate response of those actions without guaranteeing the underlying rules. A barrel may look as though it explodes, for example, without every later consequence behaving as it would in Quake II. An enemy may look present and react visually while damage counting or persistence fails.
This is why a short clip can overstate the achievement. A few visually convincing seconds demonstrate short-term plausibility. Reliable gameplay requires the system to remember objects, enforce collisions, track health, handle enemies, preserve progression, and respond promptly for much longer.
What are the limitations Microsoft admits?
Microsoft’s limitations are technical failures in game state and interaction, not merely imperfections in image quality. The company documents several specific weaknesses in the WHAMM research article.
Why do enemies disappear or reappear?
WHAMM has a context length of 0.9 seconds, which Microsoft equates to nine frames at 10 frames per second. When an object remains outside the model’s effective recent context for longer than that, the model may fail to maintain a reliable representation of the object.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →In practice, looking away briefly can cause an enemy to disappear or reappear. An enemy may seem to spawn or be defeated after the player looks at the floor and then looks back. Looking toward the sky and then down again can create an apparent teleportation effect. The problem is object permanence: the generated view can remain plausible while the model loses track of what should still exist.
Are enemy behavior, health, and damage accurate?
No. Microsoft says enemies can appear fuzzy and that combat outcomes can be wrong, including damage dealt to enemies and damage dealt to the player. Health values are also not consistently reliable, which can affect health-pack interactions and the player’s apparent condition.
These errors matter more in a shooter than they would in a passive visual demo. Combat depends on consistent relationships between aiming, collision, damage, enemy state, player health, and ammunition. If those relationships are only approximated, the experience may look like Quake II without supporting Quake II’s actual gameplay loop.
Does the demo contain a complete Quake II level?
No. The model covers only part of a single Quake II level. Microsoft says the experience freezes when the player reaches the end of the recorded section at the elevator because the team stopped collecting data there and restarted the level.
The freeze is a clear boundary of the training data. It is not simply a loading problem that a conventional game engine would solve by opening the next map. The model has no demonstrated learned continuation beyond the section it was prepared to represent.
Is the demo responsive enough for a shooter?
Microsoft acknowledges noticeable input latency when the experience is made available to many users. The more-than-10-frames-per-second generation rate does not guarantee low-latency control: server load, model inference, transmission, and interface processing can all separate an input from the resulting frame.
Rank #4
Latency compounds the other limitations. A player can sometimes compensate for visual oddities, but delayed responses make aiming, movement, and reaction-based combat more difficult. The result is an interactive demonstration rather than a practical replacement for a responsive shooter.
Why did Microsoft release this demo?
Microsoft presents WHAMM as research into real-time generative world models, gameplay ideation, interactive media, and creative prototyping. The broader Muse program focuses on models that understand relationships among game visuals, world structure, and player actions. Microsoft Research introduced Muse on February 19, 2025, with a focus on gameplay ideation, in its Muse announcement.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
The Quake II experiment tests whether the approach can transfer to a different and faster-paced first-person shooter using a sharply smaller, deliberately targeted data set than the earlier Bleeding Edge work. That makes the project relevant to researchers and developers interested in:
- Rapidly exploring gameplay ideas.
- Generating interactive media rather than only generating individual assets.
- Studying how models represent world structure and player actions.
- Prototyping experiences before building them in a conventional engine.
- Investigating future ways to experience older games on new devices or in new forms.
Microsoft developed Muse with Xbox Game Studios’ Ninja Theory. Microsoft’s Xbox-facing explanation of Muse discusses possible creator and player applications in Xbox Wire’s Muse overview. Those possibilities are research directions, not evidence that WHAMM is ready to ship complete AI-generated games.
Is this a replacement for a game engine?
WHAMM does not currently replace a conventional game engine. A traditional engine maintains explicit state and applies programmed rules for rendering, collision, physics, enemy AI, health, damage, inventory, triggers, and level progression. WHAMM predicts the next visual result from learned patterns and recent context.
The difference can be summarized as follows:
| Capability | Traditional game technology | WHAMM-style generative simulation |
|---|---|---|
| Rules | Explicitly programmed and testable | Learned from gameplay data |
| State tracking | Persistent across the game session | Limited by model context and learned consistency |
| Content coverage | Designed to cover the shipped maps and systems | Restricted here to recorded portions of one level |
| Failure mode | Usually a software or design bug | Can include visual artifacts, forgotten objects, wrong counts, or implausible transitions |
| Performance target | Optimized for predictable interactive response | Can experience model-serving latency at scale |
| Development workflow | Assets and systems are authored for the engine | Model behavior depends on the scope and coverage of training data |
WHAMM is also not simply an AI asset generator. The model is not creating a set of textures, character models, or level layouts that a conventional engine then runs. The model generates the visual experience itself as the player acts, which is why state consistency and latency are central challenges.
Is Microsoft’s Quake II demo game preservation?
The Quake II demo is not preservation in the conventional archival sense. The demonstration does not preserve the original executable behavior, complete game state, source code, assets, or exact reproducibility. It is an approximation of a small slice of the game.
Best Value
- Dos
- Quake 1 required
Generative models could eventually inform alternative ways to experience older games across future hardware, and Microsoft has discussed that kind of possibility in connection with Muse. But the current prototype should not be treated as a preservation-grade replacement for an original game or a faithful port. The safer description is that WHAMM may inform future preservation research while currently demonstrating a generated interpretation of limited recorded gameplay.
What does the demonstration prove—and what does it not prove?
| The demo does show | The demo does not show |
|---|---|
| A learned model can respond interactively to player input. | That AI can generate a complete commercial game today. |
| A world model can reproduce enough visual and behavioral structure to create a recognizable scene. | That generative models can replace conventional game engines. |
| One game-specific approach can be adapted to another game. | That the method works for arbitrary games without game-specific data and training. |
| Deliberate, narrow data collection can reduce training requirements. | That a complete game can be made from one week of recordings. |
| Generative game worlds are useful subjects for research and prototyping. | That the demo is a practical alternative to playing Quake II. |
| Short-term visual plausibility can be generated in real time. | That generated output will maintain reliable world state or faithful game preservation. |
What should players and developers use it for?
Players should use the demo as a technology curiosity and a way to see generative world modelling in action. Anyone who wants complete campaign progression, reliable combat, stable enemy behavior, persistent state, and low-latency controls should play a conventional Quake II release instead. The official Quake page on Bethesda.net is the appropriate starting point for checking available official editions; platform availability and included versions can differ by region and storefront.
Developers and researchers can treat WHAMM as evidence that model-based interactive prototyping is becoming more concrete. The project is relevant when the goal is to explore a concept quickly, study the connection between input and generated world state, or investigate new interactive-media formats.
WHAMM is not a turnkey game-development tool for creating complete AI-generated games. Developers building reliable software should continue to use conventional engines such as Unity or Unreal Engine, while researchers interested in Microsoft’s broader materials can investigate Microsoft’s AI experimentation ecosystem. Azure AI Foundry is a possible destination for technical exploration, but current pricing, quotas, account requirements, compute needs, and applicable service terms should be checked before use. The research sources do not establish a specific current price for running the relevant materials.
Frequently Asked Questions
Is Microsoft’s AI-generated Quake II demo a full game?
No. Microsoft’s AI-generated Quake II demo is an interactive research prototype that generates a limited section of a Quake II environment; it is not a complete game, sequel, remaster, or conventional engine port. The model can lose objects, miscalculate combat state, and freeze at the end of its recorded section.
What is the difference between Muse, WHAMM, and WHAM-RT?
Muse is Microsoft’s broader family of generative game-world research, while WHAMM is the real-time approach used for the Quake II demonstration. Microsoft’s current WHAM project page refers to the playable real-time model as WHAM-RT, so the names describe related parts or naming stages of the same research direction.
How much Quake II gameplay data did Microsoft use?
Microsoft says the Quake II version used one week of deliberately collected gameplay data covering part of one level. That limited data requirement does not mean a complete commercial game can currently be generated from one week of recordings.
Can the demo preserve Quake II accurately?
No. The demo is an approximation of a small recorded section and does not preserve Quake II’s original executable behavior, complete game state, source code, assets, or exact reproducibility. A conventional Quake II release remains the more faithful and reliable way to play the game.
The Bottom Line
Microsoft’s Quake II experiment is a meaningful demonstration of real-time generative world modelling, but the headline needs careful translation. Users are playing a model-generated approximation of a narrow recorded environment, not a new AI-built Quake game. WHAMM shows promise for research, experimentation, and gameplay ideation; it does not yet replace a game engine, preserve Quake II faithfully, or offer a better practical way to play the original.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
