Why Ace Combat 8 Is Skipping VR Support

Ace Combat 8: Wings of Theve is one of the most anticipated flight combat games in years, yet one detail surprised a lot of long‑time fans: the game will not ship with a dedicated virtual reality mode. For a series that delivered one of the most acclaimed VR flight experiences with Ace Combat 7, that decision might feel like a step back. However, Project Aces, the team behind the franchise, is framing this not as a retreat from VR, but as a deliberate choice about scope, design, and what it takes to make a modern air combat blockbuster.

This article unpacks why Ace Combat 8 is skipping native VR support, what that means for players, and how it fits into the broader landscape of VR development and flight games in general.

Ace Combat 8 at a Glance

Before diving into VR, it helps to understand what Ace Combat 8 itself is aiming to be. Bandai Namco and Project Aces are pitching Wings of Theve as a full‑scale, big‑budget sequel designed to push the series forward on powerful current‑generation hardware. That ambition is reflected in several ways:

• New mainline entry: This is a numbered sequel, not a spin‑off or experimental side project.
• Built for modern consoles and PC: The game targets platforms like PlayStation 5, Xbox Series X|S, and contemporary PCs, with an emphasis on visuals and performance.
• Expanded scope: The team has hinted that this is a large, content‑rich project, with a sizable campaign, improved systems, and more detailed environments than previous entries.
• Unreal Engine 5: Moving to a newer engine opens up advanced graphics, lighting, and physics options, but also increases development complexity.

It’s in this context that the VR decision needs to be understood. Project Aces isn’t ignoring VR out of disinterest; instead, they’re acknowledging what it would actually cost, in time and resources, to do it properly alongside such an ambitious flat‑screen title.

Why Ace Combat 7’s VR Mode Raised the Bar

Ace Combat 7: Skies Unknown launched with a dedicated VR component on PlayStation VR, and it quickly became a showcase for what flight games could feel like in virtual reality. Players praised the sense of presence in the cockpit, the scale of aircraft, and the thrill of maneuvering through clouds and missiles with full head‑tracked freedom.

However, that success also exposed how demanding VR truly is for developers:

• Rendering cost: Consumer VR headsets typically require the game to render a separate image for each eye at high frame rates (often 90 Hz or more) to maintain comfort and reduce motion sickness. This can effectively double the rendering workload compared to a non‑VR game at a similar resolution, as noted in engineering discussions around VR performance from platforms like Meta and Valve.¹
• Strict performance budgets: VR platforms enforce very tight performance standards. For instance, Meta’s developer documentation emphasizes meeting or exceeding target frame rates to minimize discomfort, which restricts how complex scenes and effects can be.¹
• Design adjustments: VR isn’t just “turn on a new camera.” Developers often need to rethink cockpit layout, HUD readability, mission pacing, and camera movements to prevent motion sickness and maintain immersion. Aviation and human‑factors research has long highlighted how field of view, motion, and visual lag can affect pilot comfort and situational awareness.²

For Ace Combat 7, Project Aces built a bespoke VR mode with specific missions rather than making the entire game playable in VR. That allowed them to tailor content and performance, but it also meant additional work on top of building the main campaign. With Ace Combat 8 aiming to be larger and more technically demanding, replicating or expanding that effort would be significantly more complex.

Two Games in One: The Core Problem with Native VR

The key idea behind Ace Combat 8’s move away from built‑in VR is that a great flat‑screen game and a great VR game are, in practice, different products. The core fantasy—sitting in the cockpit and pulling high‑G turns—is the same, but the technical and design requirements quickly diverge.

Technical Burdens of VR in a Modern Flight Game

On the technical side, every choice that benefits a cinematic, flat‑screen presentation comes with a cost in VR:

• High‑end effects vs. frame rate: Advanced lighting, dense clouds, detailed ground assets, and heavy post‑processing are easier to justify in a flat‑screen title where frame rates can be more flexible. In VR, those same features may need to be scaled back dramatically to maintain comfort‑grade frame rates.
• Resolution demands: Many newer VR headsets offer relatively high per‑eye resolutions. To avoid visible aliasing or blur, games often need to render at or above that resolution, adding further strain to GPU and CPU budgets.
• Camera movement & animation: Cinematic camera shakes, scripted camera cuts, and aggressive motion blur can look great on a monitor but can be disorienting or nauseating in VR. That forces separate implementations or entirely different approaches to presentation.

Platform holders recognize this and publish extensive VR performance and comfort guidelines; for example, Meta’s XR documentation formally lays out minimum frame rate targets and latency constraints developers should meet for comfort‑oriented VR experiences.¹

Design Divergence: Missions, UI, and Storytelling

On the design side, mission flow and storytelling also diverge between VR and non‑VR:

• Mission duration: Long missions might be fine on a TV, but extended VR sessions with intense motion and continuous head movement can be more fatiguing. This can push VR designers toward shorter, more focused engagements.
• Interface design: HUD elements that are readable at a distance on a 2D monitor may be uncomfortable if placed in 3D space too close to the player’s eyes, or too far out in peripheral vision. VR often demands different font sizes, layouts, and interaction patterns.
• Cutscenes and narrative: Traditional cutscenes rely on shot changes, camera movement, and fixed framing. In VR, developers must decide whether to lock the player’s head, switch to a “screen‑in‑screen” view, or redesign storytelling around in‑world sequences that respect head tracking.

For a team building a single, tightly scoped VR game, those challenges are manageable. For a studio already committed to a large, cinematic flat‑screen campaign, trying to design around both paradigms at once can start to resemble building two overlapping but distinct games.

Project Aces’ Reasoning: Focus Over Fragmentation

In interviews about Ace Combat 8, Project Aces has described having to choose between:

• Making the best Ace Combat in VR,
• Making the best Ace Combat on flat screens, or
• Attempting to deliver both simultaneously.

The team ultimately decided to prioritize the numbered sequel’s flat‑screen experience. Several factors likely drove this decision:

1. Limited development resources: Game studios, even those backed by major publishers, work with finite teams and budgets. Splitting staff between VR and non‑VR modes can slow the overall schedule or force compromises.
2. Audience size: While VR has been growing, its install base remains much smaller than that of traditional consoles and PCs. Industry reports from firms like the International Data Corporation (IDC) and analyses published via outlets such as Reuters have noted a relatively modest scale and recent softness in consumer VR headset shipments.³
3. Risk management: A numbered entry carries expectations for sales and critical reception. For Project Aces, guaranteeing a polished, content‑rich flat‑screen game may simply be safer than gambling on dual‑mode development.
4. Creative clarity: Focusing on a single primary format can help designers, artists, and engineers make clearer decisions. Instead of constantly asking, “But will this also work in VR?” they can push the flat‑screen vision as far as current hardware allows.

From this perspective, skipping integrated VR isn’t about disregarding the medium; it’s about avoiding a situation where both modes feel compromised.

What This Means for VR Fans and PC Players

For players who loved Ace Combat 7’s VR missions, the absence of a native VR mode is understandably disappointing. However, the situation is more nuanced than simply “no VR at all.” Several factors soften the blow—particularly on PC.

Potential for Community‑Driven VR on PC

Because Ace Combat 8 is being developed in Unreal Engine 5, there is a strong possibility that community‑created VR solutions could emerge on PC. Third‑party VR injection tools can, in some cases, convert non‑VR Unreal Engine titles into playable VR experiences by hooking into the rendering pipeline and camera system.

While these solutions are unofficial, often require powerful hardware, and may lack the comfort optimizations of a native mode, they offer a path for PC players with VR headsets to experience parts or all of the game in virtual reality. Developers themselves have hinted that, given the engine choice, this kind of user‑driven experimentation is likely rather than impossible.

Console VR: Less Likely Without Native Support

On consoles, especially closed platforms like PlayStation 5, unofficial mods are not a viable option for most players. Without official VR support from Project Aces and the platform holder, console owners who enjoyed Ace Combat 7 on headsets such as PlayStation VR or PS VR2 won’t have a straightforward way to enter the cockpit in VR this time.

This underlines a broader challenge in the VR space: while PC remains a fertile ground for experimentation and community mods, console VR experiences tend to depend entirely on official support and investment.

VR Flight Games: Where Ace Combat Fits In

Even without Ace Combat 8 joining the roster of native VR titles, virtual reality still hosts a variety of flight and cockpit‑based experiences. These range from realistic simulators to more arcade‑style games, and they collectively illustrate both the opportunities and demands of VR development.

Ace Combat has traditionally gravitated toward the second category: accessible, story‑driven air combat with cinematic flair. In VR, that formula works very well but demands extra tuning for motion comfort, UI, and mission pacing. The fact that many current VR flight experiences are standalone or highly specialized supports Project Aces’ claim that VR and flat‑screen design paths diverge enough to justify separate products.

Could a Dedicated VR Ace Combat Still Happen?

Project Aces has indicated that if they return to VR in the future, they would likely treat it as its own project rather than a bolt‑on mode for a numbered title. That approach aligns with how many studios now think about VR: as a distinct platform with its own design language and business considerations.

From an industry standpoint, several conditions would make a dedicated VR Ace Combat‑style game more likely:

• Larger VR install base: Industry trackers and analysts, including those cited by Reuters, have noted that growth in VR headset shipments has been uneven.³ A more robust, stable audience would make specialized projects easier to justify financially.
• Mature cross‑platform tools: As engines like Unreal Engine 5 improve their XR support, the cost of building once and deploying across multiple VR platforms may drop, reducing risk.
• Clear demand from fans: Vocal and sustained interest from players can influence publishers’ long‑term plans, especially if it is paired with evidence of willingness to buy premium VR titles.

Project Aces has left the door open to exploring VR again when the timing and technology are right. For now, though, they are treating Ace Combat 8 as a chance to deliver the strongest possible flat‑screen entry and reserve VR for a future project that can be built around it from the ground up.

What Players Can Expect Instead

While the lack of native VR support may be disappointing, it also implies certain positives about the core game:

• Visual ambition: Free from strictly VR‑friendly performance constraints, the team can lean into heavy visual effects, dense environments, and cinematic presentation suited to modern displays.
• Large‑scale content: Rather than shipping with a separate VR side mode, resources are focused on the main campaign and associated systems, which should translate into more missions, features, and polish.
• Stable performance targets: The game can be tuned for each platform’s strengths without needing to maintain a VR‑grade frame rate on all hardware.

For many players, especially those without VR headsets, that trade‑off will be acceptable if it results in the most refined, content‑rich Ace Combat yet.

Summary: A Strategic Retreat, Not an Abandonment

Ace Combat 8 skipping native VR support is less a rejection of virtual reality and more a recognition of what it takes to truly excel in two very different formats at once. Project Aces learned from Ace Combat 7 that making VR feel right involves more than flipping a technical switch; it demands separate design attention, performance budgets, and content planning.

By concentrating on a single, ambitious flat‑screen game, the studio is betting that Ace Combat 8: Wings of Theve will satisfy the majority of its audience while leaving the door open for a dedicated VR‑first project down the line. In the meantime, VR enthusiasts will likely look to community solutions on PC and to other specialized VR flight experiences to scratch the itch that Ace Combat 7’s VR missions helped create.

Frequently Asked Questions

Will Ace Combat 8 have an official VR mode on any platform?

No official VR mode is planned for Ace Combat 8 at launch. Project Aces has stated that they are focusing their efforts on delivering the best possible flat‑screen experience for this numbered entry rather than splitting development between VR and non‑VR modes.

Why was Ace Combat 7 able to support VR but Ace Combat 8 is not?

Ace Combat 7 included a bespoke VR component with a limited set of missions built specifically for PlayStation VR. That mode required extra design and performance work on top of the main game. Ace Combat 8 is a larger, more ambitious project targeting modern hardware and making a more robust VR offering would likely have demanded resources equivalent to building a second, parallel product.

Can PC players still experience Ace Combat 8 in VR somehow?

While there is no official VR support, Ace Combat 8 is built in Unreal Engine 5, which may enable unofficial VR injection tools on PC. Such community solutions are not supported by the developer or publisher, can require high‑end hardware, and may not meet comfort standards, but they could offer a way for technically inclined players to experiment with VR.

Does skipping VR mean the series is finished with virtual reality?

Not necessarily. Project Aces has suggested that if they revisit VR, it would likely be as a dedicated project rather than as a mode within a numbered sequel. The decision for Ace Combat 8 reflects current priorities and resource constraints, not a permanent abandonment of VR as a medium.

How does this affect PlayStation VR2 or other console VR systems?

Without native VR features, console‑based headsets like PlayStation VR2 won’t have an official way to run Ace Combat 8 in VR. Unlike PC, consoles restrict user‑modification, so unofficial workarounds are not realistic for most players.