Uploaded April 2026 | Updated November 2026, 3 days ago
What actually changes when you run a PC game natively on Windows on Snapdragon?
In this GDC 2026 session, Qualcomm and Warhorse Studios break down how Kingdom Come: Deliverance II was optimised for Windows on Snapdragon — from platform architecture and emulation trade‑offs, to native ARM64 builds shipping in production.
You’ll see:
- What emulation vs native execution really means for CPU, GPU, and power
- Where native ARM64 delivers measurable gains (and where it doesn’t)
- How CPU efficiency can improve GPU‑bound frame times under tight power budgets
- Real profiling data from Kingdom Come: Deliverance II running natively
This talk focuses on shipping realities: power envelopes, thermal limits, engine architecture, and the practical steps needed to get real performance wins on Snapdragon laptops.
Speakers:
Tomáš Barák (Warhorse Studios)
John Parsaie (Qualcomm)
Carlos Dominguez Caballero (Qualcomm)
Key sections:
00:00 Windows on Snapdragon: why native performance matters
01:20 Snapdragon X / X2 platform overview for game developers
06:14 Emulation vs native execution explained
09:23 CPU benchmarks: native vs emulated performance
12:12 Power efficiency and samples‑per‑watt results
14:38 Why CPU optimisation helps GPU‑bound games
18:10 Frame time stability and GPU clock behaviour
20:50 Kingdom Come: Deliverance II engine architecture
25:05 Real‑world performance gains from native ARM64
27:07 Load times, frame rate wins, and production results
30:58 Core parking, job systems, and threading pitfalls
36:00 Shipping, packaging, and practical porting guidance
Subscribe to get news and updates on Snapdragon's game developer solutions: qualcomm.com/support/contact/forms/snapdragon-gaming
What actually changes when you run a PC game natively on Windows on Snapdragon?
In this GDC 2026 session, Qualcomm and Warhorse Studios break down how Kingdom Come: Deliverance II was optimised for Windows on Snapdragon — from platform architecture and emulation trade‑offs, to native ARM64 builds shipping in production.
You’ll see:
- What emulation vs native execution really means for CPU, GPU, and power
- Where native ARM64 delivers measurable gains (and where it doesn’t)
- How CPU efficiency can improve GPU‑bound frame times under tight power budgets
- Real profiling data from Kingdom Come: Deliverance II running natively
This talk focuses on shipping realities: power envelopes, thermal limits, engine architecture, and the practical steps needed to get real performance wins on Snapdragon laptops.
Speakers:
Tomáš Barák (Warhorse Studios)
John Parsaie (Qualcomm)
Carlos Dominguez Caballero (Qualcomm)
Key sections:
00:00 Windows on Snapdragon: why native performance matters
01:20 Snapdragon X / X2 platform overview for game developers
06:14 Emulation vs native execution explained
09:23 CPU benchmarks: native vs emulated performance
12:12 Power efficiency and samples‑per‑watt results
14:38 Why CPU optimisation helps GPU‑bound games
18:10 Frame time stability and GPU clock behaviour
20:50 Kingdom Come: Deliverance II engine architecture
25:05 Real‑world performance gains from native ARM64
27:07 Load times, frame rate wins, and production results
30:58 Core parking, job systems, and threading pitfalls
36:00 Shipping, packaging, and practical porting guidance
Subscribe to get news and updates on Snapdragon's game developer solutions: qualcomm.com/support/contact/forms/snapdragon-gaming










