ACE COMBAT 8 update 1.01.002: fixes and PC crash checks

Bandai Namco has detailed update 1.01.002 for ACE COMBAT 8: WINGS OF THEVE. Before returning, check your installed build and distinguish those changes from the separate PC crash investigation.

What the update targets

The notes address campaign progression failures, including Mission 10 becoming stuck after a carrier landing. They also cover Missions 18, 25, 28 and 30, alongside stability improvements. Online, the effects of the ECM, ESM and IEWS special weapons now last for a shorter time. Steam gains an Async Compute toggle on compatible GPUs; on unsupported hardware the option is greyed out. Further interface and menu improvements for ACE COMBAT ONLINE are planned for later updates rather than included here.

The notice still describes an October 23 schedule, not confirmed installation on every device. Check your local version before comparing a bug with the notes.

PC crashes are a separate issue

Bandai Namco’s October 16 Product Notice describes an ongoing investigation into several crash causes. Its internal testing found fewer instances of certain memory-related crashes when total available memory reached approximately 48 GB. That figure combines physical RAM and Windows virtual memory; it is not a new instruction to buy 48 GB of RAM.

The guidance pairs 32 GB of RAM with at least 16 GB of virtual memory, or 16 GB of RAM with at least 32 GB of virtual memory. This is temporary, does not address all crashes, and accompanies work to reduce memory use.

Check the supported PC setup

The October 9 matchmaking notice identifies unsupported PC configurations as one possible contributor to connection difficulties, not the only cause. The publisher asks players to use Windows 11 and install the game on an SSD. It warns that unsupported environments can affect other participants in the same matchmaking session as well as the player using that PC.

Check the actual drive containing the installation, rather than assuming that a PC with an SSD has every game installed there. If a session fails, compare whether the problem occurs in solo play, only while joining friends, or only in one online activity. These observations help separate a loading problem from a matchmaking symptom without guessing which component is responsible.

Check updates and installed files

Valve notes that verification can take several minutes and that some local configuration files may fail verification normally. Avoid running other intensive tasks during the check. Verification checks the installation; it does not establish that a developer-side bug or an online service problem has been fixed.

Make the next test useful

The publisher’s PC reporting request asks for details including CPU, graphics card, memory, Windows version, errors and reproduction steps. It also asks about other applications running at the time. Share the relevant technical details through the official support route, but leave account passwords, payment information and unrelated personal material out of screenshots or logs.

Also returning to another recent release? See our The Blood of Dawnwalker 1.1 checklist.

What remains uncertain

The maintenance notice contains conflicting regional dates: its UTC line refers to October 23, while the PDT and JST lines refer to October 13–14. They cannot be treated as equivalent local times. Players in Europe, the Americas and Asia should use a corrected current service notice rather than converting one of those rows into a promised availability window.

The sources checked on October 25 do not establish a universal rollout completion time, a verified download size for every platform, or that every reported crash is resolved. This is an official-information guide, not hands-on testing of the patch. If a particular defect determines whether you can enjoy the game, wait for a specific confirmed fix or a successful test on your own setup.