Summary
Defending Camelot is a tower defense video game, similar to Plants vs. Zombies, developed for PCs and consoles. The game involves Arthur who use a variety of different warriors to prevent an army of monsters from entering Camelot.
Defending Camelot
| Minimum System Requirements | Recommended System Requirements | |
| CPU | Intel Core 2 Quad Q8400 @ 2.66Ghz or AMD Phenom II X4 940 @ 3.0Ghz | Intel Core i7-3770 @3.5 GHz or AMD FX-8350 X8 @ 4 GHz |
| VRAM | 2 GB | 2 GB |
| RAM | 6 GB RAM | 8 GB RAM |
| OS | Windows Vista (SP2), Windows 7, Windows 8 or Windows 10 | Windows 7, Windows 8 or Windows 10 |
| Graphics Card | GeForce GTX 460 or better | GeForce GTX 560 ti or better |
| Direct X | Version 11 | Version 11 |
| SOUND CARD | DirectX 9.0c Compatible Sound Card with Latest Drivers | DirectX 9.0c Compatible Sound Card with Latest Drivers |
| HDD Space | 500 MB available space | 500 MB available space |
| Game Analysis | In terms of game file size, you will need at least 500 MB of free disk space available. Provided that you have at least an NVIDIA GeForce GTX 460 graphics card you can play the game. Futhermore, an NVIDIA GeForce GTX 560 Ti is recommended in order to run Defending Camelot with the highest settings. The minimum memory requirement for Defending Camelot is 6 GB of RAM installed in your computer. If possible, make sure your have 8 GB of RAM in order to run Defending Camelot to its full potential. An Intel Core 2 Quad Q8400 CPU is required at a minimum to run Defending Camelot. Whereas, an Intel Core i7-3770 is recommended in order to run it. Defending Camelot will run on PC system with Windows Vista (SP2), Windows 7, Windows 8 or Windows 10 and upwards. | |
Overview
Platforms
Release Dates
Related URL
Developers
Publishers
Genres
Game Engines
Game Modes
Game Themes
Languages
Keywords
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