
Game Overview
A stolen time device turns a futuristic heist story into a brutal test of reflexes and spatial awareness. Ingression follows Rina, a thief trapped in the corrupt Galactic Empire of 2152, as she races through time to prevent a paradox from tearing history apart. The tone is tense, fast, and deliberately punishing: every room feels like a compact deathtrap built to expose sloppy timing. Rather than offering a leisurely sci-fi adventure, it delivers a focused precision-platforming challenge where survival depends on understanding space as much as mastering movement.
Rina runs, jumps, falls, and launches herself through linked portals that instantly redirect her across a level. Momentum carries through these gateways, so successful runs involve building speed, choosing smart angles, and using split-second teleports to clear distant gaps or dodge hazards. Lasers, pursuing drones, spike-lined corridors, and other lethal obstacles demand careful route planning, but the brisk restart structure keeps repeated failure from becoming a long interruption. Levels continually combine portal tricks with shifting orientation and changing gravity-like perspectives, forcing players to rethink which wall is safe, which route is possible, and where a jump will actually send them.
What separates Ingression from a standard hardcore platformer is how completely its stages are designed around portal physics instead of treating teleportation as a simple shortcut. The seamless transitions can create spectacular escapes and satisfying momentum chains, while also making each puzzle-platforming sequence feel like a test of mental mapping under pressure. Its clean sci-fi setting and compact obstacle courses evoke the spatial trickery of Portal, but the demanding execution and frequent deaths place it closer to Super Meat Boy or Celeste’s toughest challenge rooms. Players who enjoy mastering difficult levels through repetition, experimentation, and precise inputs find plenty to enjoy, while newcomers to precision platformers should expect a steep but rewarding learning curve.
Screenshots
Installation
- Select the Download button at the top of this page to open UploadHaven.
- On UploadHaven, wait for any countdown, then select Free Download. Optional: UploadHaven Pro for faster downloads.
- When complete, extract the archive to a Ingression folder using 7-Zip.
- Open the extracted folder and start the game normally.
- For errors, check Setup Guide & Troubleshooting below. Keep your security software enabled.
System Requirements
- OS: Windows 10
- Processor: X64 architecture with SSE2 instruction
- Memory: 4 GB RAM
- Graphics: NVIDIA GeForce 7300GT
- DirectX: Version 10
- Storage: 700 MB available space
Setup Guide & Troubleshooting
How do I fix missing DLL errors for Ingression (v1.1.1)?
After extracting Ingression (v1.1.1), navigate to the _Redist or _CommonRedist folder inside the game directory and install DirectX, Vcredist, and any other dependencies included.
What should I do if the downloaded file is corrupted?
The full archive is 274.24 MB — make sure your download completed fully before extracting. Use 7-Zip to extract the files. If you still see a "file corrupted" error, re-download and try again.
Do I need to run the game as administrator?
Usually, no. Start the game normally from the extracted folder. If you see a permissions or save error, check that the folder is writable and follow the game's documented fix. Only grant administrator access when a trusted game's specific setup requires it.
How do I update my GPU drivers for this game?
The game won't launch — what should I try?
Check that extraction completed and your PC meets the system requirements, including Version 10. Note any error message before choosing a fix. If it identifies a missing runtime, install the required DirectX components or Microsoft Visual C++ Redistributable from Microsoft.
My antivirus is blocking the game — is it safe?
A warning needs to be investigated; the download source alone cannot confirm that a file is safe. Keep your security software enabled and review the detection details. Do not run or restore a flagged file unless you have verified that it is a false positive. If you are unsure, leave it quarantined.