Running PC Crysis on a... PHONE???

Summary

This video explores the incredible feat of running Crysis, a game once considered impossible for most computers, on an Android phone in 2025. The Red Magic 10 Pro, powered by the Snapdragon 8 Elite chip, serves as the test platform. The video delves into how ARM-based processors and tools like Box64 and Winlator make this possible. It demonstrates that, with the right software and hardware, demanding PC games can be played smoothly on mobile devices. The process is complex but showcases the future of gaming on the go, highlighting advancements in mobile hardware and compatibility layers.

Takeaways

• 😀 *Crysis* became a benchmark for hardware performance in 2007, famously asking, 'But, can it run Crysis?'
• 😀 In 2025, the full, original *Crysis* can now run on smartphones, like the Red Magic 10 Pro, without being a stripped-down version.
• 😀 The significant improvement in ARM chip technology, like Qualcomm's Snapdragon 8 Elite, enables mobile devices to run demanding games.
• 😀 Apple's switch to ARM with Rosetta 2 proved that ARM could handle intensive applications, including x86 programs.
• 😀 Open-source projects such as Box64 and Winlator bridge the gap, making it possible to run *Crysis* on Android phones.
• 😀 Winlator, alongside tools like Proot, Wine, Box86/Box64, and graphical rendering solutions, facilitates ARM architecture's compatibility with x86 games.
• 😀 Despite occasional graphical issues, the Red Magic 10 Pro runs *Crysis* at 80-100 FPS on medium settings, demonstrating impressive performance.
• 😀 Games like *Driver San Francisco* and *Fallout: New Vegas* run smoothly on the Red Magic 10 Pro with some minor tweaks.
• 😀 The future of mobile gaming looks promising, with increasingly powerful hardware and open-source tools enabling traditionally PC-bound games to run on mobile devices.
• 😀 Mobile gaming is progressing rapidly but is not yet a complete replacement for traditional desktop setups, as some compatibility and performance issues remain.

The video is abnormal, and we are working hard to fix it.
Please replace the link and try again.