Cathode Tan - Games, Media and Geek Stuff
logo design by man bytes blog
Showing posts with label fallout. Show all posts
Showing posts with label fallout. Show all posts

Monday, December 05, 2011

Bethesda Owes Gamers Truth on "Creation" Engine (hint: It's still Gamebryo)

I'm not even going to go back and drag up all the posts I've made about Fallout: New Vegas and what a horrible bugfest it was.

The important thing here: it's still broken for some players, even today.

Now, like myself, many other gamers who experienced the nightmare which was Fallout: New Vegas were delighted to hear that it was going to use an all-new engine.  And when I say it was reported to use an all-new engine, I mean: Bethesda themselves stated that the engine for TES V: Skyrim would be all-new.


I'm not even paraphrasing here, not even a little bit.  Now, if you read through that recent FO:NV forum post, you'll see that the user is stating that the game becomes unplayable after the save file reaches a certain file size.

Gee, I dunno?  Sound familiar?  Yup, it's the exact same issue that everyone is talking about with Skyrim on the PlayStation 3.  And what is the most technical explanation for the problem that has been released to date?

It's the one offered by Obsidian, the developer of Fallout: New Vegas.  It explains how the Gamebryo based games use a file strategy to track the changes throughout the game world, and how consoles can have problems loading and managing those changes into memory.  No memory = no performance.

Now, I've been lucky.  I've had a few quest bugs and the occasional performance issues.  I've had two crashes.  I've had maybe a handful of lockups.  From my time with the game, I would say that I'd stick to my guns in that compared to Fallout: New Vegas - it is a godsend, and compared to normal games it is only slightly buggy.

But - that's me.  There's now plenty of video evidence that other players of Skyrim are experiencing what I experienced with Fallout: New Vegas (and to a slightly lesser degree, Fallout).  I don't know why I'm one of the lucky ones - but that isn't really the point.  The point here is that I bought Skyrim because I thought it was an all-new engine, as did many other people.

But how is it that an "all-new" engine has the same fundamental problem as the last engine, with apparently the same save file structure and loading concepts as well?

How is it that items in the world are rendered and handled in almost the exact same manner as the old engine?  Sure, the textures look nicer and Bethesda has cranked up the pretty in all sorts of ways, but someone who has played all the Gamebryo games can't load up Skyrim and deny the fact that the game looks and feels just like the old games did.

All-new engine, my ass.  All new graphics pipeline, perhaps.  Kicking Speedtree to the curb and implementing your own plant-life, sure.  New ways of loading textures, maybe.

But at the end of the day - the so called "Creation" engine is just lipstick on a pig.  Bethesda hasn't even been able to fix the problems with their last game, but they continue to march on with the same core technology ... only this time with more of PR spin to give gamers false confidence.

That's pretty shameful, and there are a lot of Skyrim players ... especially on the PS3 ... with plenty of righteous anger at the company right now.

I really don't know if I'll buy the next Bethesda game.  I can't trust the Gamebryo engine, and I can't trust Bethesda when they say they aren't using it.

Sunday, October 31, 2010

Fallout: New Vegas ... A Game So Buggy Good Luck Finishing It

This is a follow up to the post from Friday which noted that while Fallout: New Vegas is pretty fun, it's also full of bugs which are completely ridiculous for a console game in this day and age. I challenged anyone to find a buggier game in the history of the console.

I'm going to up the ante on that. I think Fallout: New Vegas may be the buggiest game ever released.

On any console.

Ever.

My evidence? I can't finish the game. I've tried previous saves, I've tried cleaning the disc, I've tried giving the PlayStation 3 a good old reboot, I've tried moving to other locations and then back - but I can't get into The Strip. The load screen appears, and then there is a black screen. And where do I need to go to finish the game? The Strip. Is there any other way to get there? No, Bethesda didn't have any of the locations in the The Strip as a named location. You can't even go directly there via fast travel, you have to go to a gate first and the walk in ... which is where every thing just fades to black.

And that's it. I've played this game for hours, I've gone on dozens of quests and in an effort to stop the game from crashing I decided to just sprint for the finish line and get to the end of the main storyline. But I'll never get that. This is how the game ends for me:

The load screen appears, and then there is a black screen.

That Bethesda has released a game of this low quality is bad, but it's equally bad that the gaming media has decided to give them a pass. IGN rates this game an 8.5, or "great". Really? Let's recap.

The load screen appears, and then there is a black screen.

That is not a great game. I might be able to give it a good, but a game that can crash consistently after only running for thirty minutes or less with nor rhyme or reason is probably barely worthy of even being a good game, even if everything about the gameplay was stellar.

So Bethesda: don't count on me buying any DLC for this game. Hell, don't even count on the disc ever gracing my console again. And if any game from Bethesda ever has a review with the word bug in it again, I don't care if the rating is off the chart - it's not a purchase option for me. I'd be irate if this was a PC game, but on a console? This lack of quality control is simply idiotic.

Friday, October 29, 2010

Gameplay: Fallout New Vegas

I'll start with a confession: I've been playing the hell out of New Vegas. And I could rattle off all the reasons why that is so - except none of them would surprise you if you have already played Fallout 3 in the last two years. Bethesda has managed to sneak in a few new details, most of which add at least a few new concepts - most of which are pretty sound but don't really do anything to change the core gameplay from when Fallout and Elder Scrolls first got mashed together.

And there have been many, many reviews which have mentioned all of that, and how wonderfully the mechanics hold up over the last couple years. So lets' talk about something else.

Let's talk about just how often this damn game crashes, and how completely wrong that is for a console game in the year 2010. The level of instability that this game has is so far off the charts compared to every single other title I have ever played on the PlayStation 3 that I challenge any other blogger or gamer to argue the case that this is not the buggiest release in the history of the console, with the only other contender being Fallout 3 or the even buggier DLC for Fallout 3.

Let's talk frequency: Nightly. At least once a night that I've powered this game on, it has crashed. Let's talk severity: It completely locks up the console, requiring a manual reboot. Let's talk about predictability: There is none. You'll just be walking down the street, turn and look at something and ... bam. Instant lockup. I've had it happen at least once in between locations, causing nothing but a black screen to stare at me while I wondered if I should wait or go reboot the thing again.

The only saving grace is the frequency of the saves in the game: it does an autosave when you change locations or when you sleep. Course, the location autosave may not work correctly if the game crashes at the right moment, so unless you remember to save after every important action - you might be completely hosed anyway. I've lost hours of gameplay by not being absolutely draconian about saving after key points, a habit I've now fallen deeply into for the sake of my own sanity.

And it's not like the game itself is spotless. I walked right past a quest item because it was buried mostly in the ground ... not in "oh look, buried treasure" kind of way - but rather a "model was graphically blended with landscape" kind of way. While talking to a major game character, the conversation was stopped for cinematic animation ... which was blocked because the character for said animation was stuck on a chair. There are times when VATS goes completely on vacation. I'll be swarmed by evil poisonous creatures and tapping the shoulder button like a madman, and absolutely nothing happens.

So it's hard for me to be excited about things like factions, weapon mods, reloading benches or the nifty new companion wheel (though, it is kinda nifty) when I know every time I load the game, I'll end up rebooting my console. I said this about the Fallout 3 DLC, and I'll say it again: this is why I left PC gaming for a console. That Bethesda has had two years to work the kinks out of the engine and it's just as buggy as it ever was tells me one simple thing:

Bethesda needs to ditch this engine. While playing New Vegas, I was also playing the new Borderlands DLC and realized: it looks better, plays faster and never crashes. Yeah, I know it doesn't have the same dynamically loaded overworld that Fallout does, but these are things engines like Unreal and Id's latest have been working on. The Gamebryo engine has always been a burden on Bethesda games, it's never been able to deliver the same graphical quality of contemporary engine and apparently porting it to the consoles saddles the consoles with PC level bugs. It's ridiculous that in a two development timespan that Bethesda has released a product with this few updates, that looks exactly the same as the game before it, and is buggy as all hell.

Is the game fun? Yes. Does it offer hours and hours and hours of play? Yes. Do I recommend it? Yes. Well, if you liked Fallout 3.

Does that justify the level of instability in this game? No.

There, quite honestly, is no justification for the level of instability in this game.

Thursday, February 04, 2010

For Sunday: Fallout New Vegas Trailer

Note: completely devoid of gameplay. But as long as they don't trash the main game with DLC again, I'm certainly in.




Wow. Haven't put up a For Sunday in ages.

Thursday, November 13, 2008

Game Play: Fallout 3 First Impressions

I didn't get a lot of time with Bethesda's latest, but I got through the tutorial and (I don't think this exactly constitutes a spoiler) out of the Vault. My impressions so far are almost universally positive, I think everything from the interface to the voice acting feels solid, VATS seems like a great concept for mixing up FPS and RPG style combat, and the world (sorry doubters) feels like Fallout to me.

I know there will always be some dissenting views on it, but just like there were people walking out of Jackson's Lord Of The Rings thinking it just wasn't exactly like the book, sometimes we'll just have to agree to disagree.

I'm willing to guess that this will be Bethesda's best so far, but its still very early in the game for me, so give me a week or so to beat on it.