Skip to content

Demo help

Demo Performance in Escape Academy 2: Back 2 School

PC Demo · October 16 update / November 1–2 replies · Reviewed November 3, 2026

The short answer

For poor performance in the Escape Academy 2: Back 2 School Demo, first check whether you are comparing the copy updated on October 16, 2026 with an older build. The developer announced optimization work and asked players to update and report back. One original reporter then said the updated Demo ran substantially better; that does not guarantee a particular FPS on every PC.

On this page

Make a version-aware comparison

  1. Confirm that you are launching the Demo, AppID4198180, rather than interpreting main-game metadata as the installed build.
  2. Check Steam’s update/download state and your installed build information against the October 16 announcement.
  3. Compare the same campus area or room, with the same graphics choices and resolution, before drawing a conclusion from an older recording or post.
  4. Note whether the issue is low frame rate, stutter, loading or one failed interaction. Those are different observations.

This is a comparison procedure, not a benchmark performed by this site. It does not require deleting a save or changing puzzle inputs.

Why a powerful GPU is not the whole explanation

The thread includes old reports of low campus frame rates on powerful graphics hardware. On November 2, a developer described a CPU-rendering bottleneck during their optimization work and said numerous changes were made.

That explains why the GPU model alone cannot diagnose the older reports. It does not establish that your current problem has that exact cause, nor that lowering or raising one specific graphics setting will fix it. There is no verified universal preset in these sources.

If the updated Demo is still slow

Follow the developer’s request for feedback with a precise comparison: Demo build/update date, CPU and GPU, resolution/settings, the campus or room location, and whether the behavior is continuous or triggered by an action. Include what changed after the update, if anything.

The November 1 improvement report is one player’s experience. Preserve your contrary result if yours differs rather than treating that report as a guarantee. Check the separate main-game/Demo requirements when OS or hardware listings disagree.

If the actual problem is the view travelling to an inspected object, the named camera-transition option may address that presentation. It is not a general frame-rate repair.

A useful result, even when performance still differs

You know which version and scene you compared, and can report a reproducible remaining issue without assuming all old complaints describe the updated Demo. No FPS target, optimization guarantee or full-game benchmark is claimed.

Sources & version

Performance discussion: complete OP and ten replies read November 3, including October 16 developer update, November 1 player improvement and November 2 developer explanation. October 16 official Demo patch read through the complete original body/API. Reports and developer explanations are distinct from a test on this site’s hardware.