It is fortunately one that I will not be playing. RTS games are designed around fast actions and quick responses, not frames lag. But even after I got it to ultra I kept it down to high so the gameplay was not choppy. When I first got SC2 I had to do some upgrades to get it up to ultra. I can’t stand playing a game that is designed to be choppy. If I was to record a video of a game like this I would have somewhere around 18 frames per second making it very crappy and very choppy. I normally run at about 120 frames per second but recording drops it down some.
When I record a HD video I’m running at about 90 frames per second. As it turns out they purposely capped the frames in the game so they could keep the digital download smaller. Neocore instead of fixing the game stated that this is working as intended. When asked about this Neocore stated an age old myth “the human eye can only perceive 20 frames per second.” This of course is false. Gamers have reported that the game will cap at 30 frames per second but runs at an average of 24 frames per second. The lag however did not go away, the game was stuck at 24 frames per second. People discovered this as they lowered the settings to try and fix a lag problem. 24 frames per second is fine for a lot of games… but it’s not good for tactical RTS games. The game has the same crashing issue that the original had.īut that’s not all! Neocore (the people who make this game) capped the game at 24 frames per second. So I decided I would wait a little bit to see whether King Arthur 2 would be worthwhile, as it turns out… its not. When I downloaded the original it had horrible awful crashing issues. I downloaded King Arthur: The Role-Playing Wargame in anticipation of its sequel.
0 kommentar(er)
