Summary
NitroRage – crazy multiplayer races with weapons. Destroy your competitors using the minigun, rocket launcher, flamethrower and other guns, or abuse of the machine with a RAM-style Derby. Drive using nitro boosts, jump with springboard on the roofs of buildings, and the demolition of funiture stores and offices, find on the map new weapons. Waiting for you the most destructible environments, lots of fun, explosions and drive and nice graphics on top game engine Unreal engine 4.
Minimum System Requirements | Recommended System Requirements | |
CPU | 3 ГГц | Intel Core 2 Duo E8400 |
RAM | 2 GB RAM | 4 GB |
OS | Windows 8, Windows 7 | windows 10 |
Graphics Card | 256 MB Pixel Shader 3.0 (Radeon X1650/GeForce 6800* or newer) | 1 GB Pixel Shader 3.0 (Radeon X3000 Series/GeForce 8000* or newer) |
Direct X | Version 9.0 | Version 9.0 |
SOUND CARD | Sound card compatible with DirectX | Sound card compatible with DirectX |
HDD Space | 2 GB available space | 2 GB available space |
Game Analysis | NitroRage system requirements state that you will need at least 2 GB of RAM. Additionally, the game developers recommend somewhere around 4 GB of RAM in your system. To play NitroRage you will need a minimum CPU equivalent to an Intel Pentium 4 2.00GHz. However, the developers recommend a CPU greater or equal to an Intel Core 2 Duo E8400 to play the game. In terms of game file size, you will need at least 2 GB of free disk space available. Provided that you have at least an NVIDIA GeForce 6800 graphics card you can play the game. Futhermore, an NVIDIA GeForce 8500 GT is recommended in order to run NitroRage with the highest settings. NitroRage will run on PC system with Windows 8, Windows 7 and upwards. |
Overview
Platforms
Release Dates
Related URL
Developers
Publishers
Genres
Game Modes
Game Themes
Languages
What's your reaction?
Very Bad
0%
Bad
0%
Average
0%
Alright
0%
Good
0%
Super
0%
This Game has no review yet, please come back later...
This Game has no news yet, please come back later...
This Game has no walkthrough yet, please come back later...
Comments