With all the
Games for Windows Live hoopla aside, development of the promised PC version of Dark Souls is still stirring up discontent among eager PC gamers. Speaking to Japanese publication
Famitsu, FROM Software Director Hidetake Miyazaki has reportedly (according to a translation by
DSO Gaming) explained that the PC offering will be a "faithful port".
"Yes, It’s basically a faithful port. There’s no change to the resolution.
The frame rate won’t be 60 FPS."
The resolution mentioned of course refers to the pixel size of the game's textures and not the full-screen dimensions. But while it may understandable that they won't be offering higher texture quality (the game was originally developed purely for console, by a studio unfamiliar with PC gaming after all, so they may not even have higher quality sources for the game's textures), it's the frames per second comment that has sparked the most concern.
Perhaps it's another case of something getting lost in translation, but as DSO explains PC gamers have been disappointed by games (from studios that should know better) being inexplicably locked to 30FPS in the past -- such as Need for Speed: The Run, Star Wars: The Force Unleashed 2 and L.A. Noire.
Dark Souls: Prepare to Die Edition is due on PC on August 24th 2012.
Posted 02:36pm 23/4/12
When the game loads and you read "Press any key to start" - that s**** me.
Posted 12:28am 24/4/12
Posted 03:31am 24/4/12
I also hate the save and do not turn off when saving popups and such. Even on consoles.
Posted 08:55am 24/4/12
Posted 10:09am 24/4/12
The reason they exist on consoles is Microsoft, Sony and Nintendo require them, ie, your game wont pass certification if it doesn't have them. Really no reason to have them on PC though, I guess they usually just get left in there cos its more hassle than its worth to remove them.
And yeah, I laughed a bit at "Faithful console port". I would imagine a lot of PC buyers would see that as a bad thing rather than a good thing to get excited about.
Posted 10:12am 24/4/12
Posted 09:23pm 24/4/12
Posted 09:49pm 24/4/12
Yeah, this grates on me too. It's such a stupid message even though I understand why it's there.
Hopefully the next console generation will have some form of transactional filesystem support and they'll change the certification process so that the message doesn't appear at all. Seriously, win32 didn't support it until very recently but posix has guaranteed atomic file rename operations since forever.