Batman: Arkham City is a narrative-driven open-world action-adventure game set in a sprawling Gotham prison. Players control Batman using a mix of Freeflow melee combat, stealth takedowns, detective scanning, gadget puzzles, and gliding traversal across rooftops and streets filled with enemies and collectibles. Most players progress through the main story while completing side missions and Riddler challenges at their own pace, switching between aggressive brawling and careful crowd control. On PC the game feels best when combat inputs and camera movement stay perfectly responsive. High framerates make the transition between punches, counters, and aerial takedowns feel more immediate and natural, while smooth traversal reduces the sense of floatiness during long glides. The Unreal Engine 3 foundation creates uneven performance in outdoor areas where crowd density, draw calls, and environmental effects pile up. Stuttering and irregular frame pacing become especially noticeable during combat sequences, freezing effects, and explosions. PhysX effects, when enabled, historically cause unpredictable dips even on powerful hardware because the outdated SDK does not scale well with modern multi-core CPUs or GPUs. Many players find that disabling GPU-accelerated PhysX or using only CPU-based physics improves overall consistency. Common pain points include sudden frame drops in heavy physics scenes, low GPU utilization despite high settings, and the realization that raw CPU core count offers almost no benefit because the game shows very weak multi-thread scaling. Before choosing hardware for high-FPS play, understand that absolute frame rate ceiling matters less than stable frame delivery. Overspending on high core-count CPUs yields almost no return because dual-core to quad-core performance is nearly identical; the game is far more sensitive to single-thread speed and avoiding synchronization stalls between CPU and GPU.