C
Cavalry
Guest
http://pc.ign.com/articles/862/862076p1.html
Just a few more weeks people, release dates:
US-April 8,2008
Europe-March 2008
Australia-TBA (Yatzee had a big problem with not having Rock Band as I recall)
although today is the last day of March, I haven't seen it yet.
Just a few more weeks people, release dates:
US-April 8,2008
Europe-March 2008
Australia-TBA (Yatzee had a big problem with not having Rock Band as I recall)
although today is the last day of March, I haven't seen it yet.
Within the next few weeks, PC gamers will finally get a chance to get their hands on Ubisoft's Assassin's Creed, the much-hyped, open-ended, free-running action game released last holiday season on Xbox 360 and PlayStation 3.
So Vista 32-bit users may run into problems unless those errors get sorted out.Since there are already plenty of reviews and reams of information out there detailing how this game is structured and what players must do to be successful, we'll concentrate on a few issues we noticed during installation and our play session. Our two primary gaming rigs here at IGN PC run Windows Vista 32-bit. Naturally they were the first we tried, and unfortunately the installation process failed on both.
This was a little confusing to us, as Gamespy editors were playing the game only a few feet away. We tried their preview build in our computer, but got the same installation error. So what was the difference? They were using Windows XP. And before we continue, we should point out that this is a preview build we're talking about, meaning it's not a finished version of the game. Yet even so, the game is supposed to release in early April and, well, that's pretty soon.
So we dusted the cobwebs off our old gaming rig that for whatever reason hadn't been dumped into a trash compactor and lo and behold, the game installed properly. At the tail end of the installation process a hardware compatibility check popped up, and to our dismay our processor did not meet the minimum requirements. In the rig we had a 3.4 GHz Pentium 4 CPU, 512 MB Radeon X1900, and 2 GB of RAM and the game still ran, though with a less than ideal framerate. The compatibility check identified the problem was our processor, the game's minimum requirements for which are a 2.6 GHz Pentium D or AMD Athlon 64 X2 3800+.
Haven't PC controls always been easier to use and a bit better than console?And the gameplay on the PC version turned out to be a little better than on consoles, thanks mostly to the ability to aim Altair's movements with both the mouse and WASD keys. The mouse controls the facing of the camera that sits behind Altair, and he'll run along in whatever direction it's angled. Because a mouse's responsiveness is greater than that of a thumbstick, we actually had an easier time maneuvering Altair around the many tight alleyways and crevices of the game's dense urban landscapes and rocky environs.
The left mouse button swings your sword. A light tap does a weak attack, while holding LMB does a charge-up strong slice. If you're quick enough, you can hit LMB just as your sword makes contact with an enemy and perform a combo kill, which switches from the scaled-back third person camera to up-close, giving you a front row seat for brutal finishing moves.