The Steam listing confirms online co-op and cross-platform multiplayer for ACE COMBAT 8: WINGS OF THEVE. It does not name every participating platform, team size, invite method, progression rule, or whether PvP and co-op use the same cross-play settings. This page therefore provides a test plan and a safe explanation of what the official label means without turning it into an unsupported platform matrix.
Separate co-op from crossplay
Co-op describes a shared activity. Crossplay describes the ability for players using different platforms to play together. A Steam-only co-op session can work without proving cross-platform support, and a cross-platform invite can work without proving every co-op mission supports it. Test the two claims separately.
The Online Modes page covers invitation and connection records. The Multiplayer hub owns the official feature boundary. Keep an observed mixed-platform result with the game mode, host, client platforms, region, visible version, and date.
Run a mixed-platform test
Before inviting, ask each player to record the platform, account or store identity shown by the game, version/build text, privacy state, and input device. Start with one host, one guest, one mode, and one mission. Test the invite, join, ready state, launch, and return to lobby as separate events.
Capture the exact cross-play label or toggle. If it is missing, do not infer that the feature was removed; check mode, region, and build first. If the party joins but the mission fails to load, classify that as a loading or connection result rather than as proof that invitations do not work.
Repeat the test with the same host and then swap the host if the game permits it. A successful join followed by a failed launch can reveal whether the limitation belongs to the host, guest, mission, or service state. Record whether a player can see another platform’s display name, whether the party survives a menu change, and whether the return to lobby preserves the group. These are observable results, not assumptions about account architecture.
Keep progress and matchmaking distinct
Cross-platform multiplayer does not prove cross-save. Steam Cloud is a separate store feature, and neither feature label guarantees that campaign choices, aircraft, MRP, achievements, settings, or replays transfer to another platform. Send progression questions to Systems and save behavior to Achievements and Cloud.
Do not delete a local save while testing a cross-platform group. Let synchronization finish, record any conflict prompt, and preserve the platform and build. A player can have a working invite and still have different campaign progress on each platform.
Keep a separate result for matchmaking and a private-session invite. A public search result can prove that players meet in one queue without proving that a friend invite crosses platforms. Likewise, a friend invite can work while ranked or competitive rules remain unavailable. Use the exact mode name and avoid presenting one successful co-op session as a complete cross-play guarantee.
When a test succeeds, report what it proves and what it leaves open. For example, two named platforms joining one private co-op session proves that tested combination for that mode and build. It does not prove ranked matchmaking, campaign save transfer, every mission, or every future patch. This narrow wording keeps the guide current for all groups today and now.
Report failures by layer
If an invite never arrives, record the privacy and account state. If the guest joins but cannot ready, record the lobby mode and visible message. If the mission launches and disconnects, record host/client role, phase, weather, and return state. A controller focus loss or crash belongs in Technical, not in a permanent cross-play restriction.
This page was checked on 2026-08-09 UTC against the Steam Store, official walkthrough, and official product page. Add the platform matrix only when a current build and official source support each row.