Welcome to the last gaming podcast of 2008! This week we’re flashing back to Nobunaga’s Ambition, a classic turn based Japanese strategy game. We’ll take a look back at the history of FASA and hit up some gaming news, including:
This weeks soap box segement, we ask if the video game release cycle is too fast or too slow.
The episode is a little late in publishing, though it was recorded on time – you know, real-life delays. However, it’s worth the wait as the Gaming Flashback is Team Ico’s second title, a PlayStation 2 title called Shadow of the Colossus.
There’s also some of the meatiest news of the year, which includes:
The Question of the Week is “Should Nintendo partner with Disney?“
This week’s episode didn’t initially have a Gaming Flashback, but the crew accidentally started one with 2010’s Red Dead Redemption, which shouldn’t be a flashback since it fails the “10 Year Rule”, but it was so fun to talk about, it became one. They also found some interesting stuff in a thin-news week, which is the usual for Summer.
The news includes:
Let us know what you think.
Double Dragon II: The Revenge, this is a sequel title to a game which arrived earlier on the NES as an arcade port, something pretty standard back in the day of arcades, and like it’s original port, has variations from the arcade.
The trick is, the variations are much less than that of the original (which might as well been it’s own version of the arcade game but sucky). I was a huge fan of the original Double Dragon title in the arcade and was met with extreme disappointment when I found out it was strictly single player on the NES console.
This game was 300% better than the disappointing Double Dragon release on the NES. Granted, the NES version was fun to play, in single-player, but I purchased it for the two-player nature of the arcade version so I could play the game with my friends. Double Dragon II, on the NES had finally restored my faith in Technos Japan and the american publisher Acclaim. They took a bad situation and made it much better in the second release, why they didn’t make the original multiplayer is beyond me.
Podcast: Play in new window | Download
Derrick, that’s Shogun: Total War (it was the first Total War game in its series so the graphics aren’t that good compared to the recent Total War games). I liked that game too.
If you liked Nobunaga’s Ambition you might like Genghis Khan 2, also made by KOEI (http://www.abandonia.com/en/games/505/Genghis+Khan+II+-+Clan+of+the+Gray+Wolf.html)
What’s your take in Valve’s concept of episodic releases? They explained that with that kind of structure they can easily take advantage of new technologies as they come up, and not have to hold back using new technologies until the next reiteration of their game.
The problems with long release cycles, taking it to the extreme, with Duke Nukem Forever (I think) the reason why it was so delayed was by the time they reached mid-development, their game, the graphics, the engine look so obsolete, so they bought a new engine, and by the time they reached back to mid-development, the then new engine they bought gets outdated, and the cycle repeats.
Something like this happened with Blizzard with their Warcraft Adventures (it was never released).
I think episodic structures work well for some games (Sam and Max), and long development cycles for others. So long as I get a game I can enjoy I don’t really care that much
Here’s what *I* think about it, underdog: They take way too friggin’ long. They keep changing the engine, when all you need to do is create levels.
Look at Telltale Games – now they do episodic content right.
@jonahfalcon: yeah I know, the wait is killing me for episode 3.
but from a developer’s viewpoint, improving the engine continually will do good in the long run since it’ll not only help with that game their making at the moment, but they can use it for their future games as well.
keeping the engine up-to-date with new technologies is always good. I’ve worked with commercial engines that, while popular, they start showing their age in that we couldn’t incorporate features we had in mind because of its limitations that could have been fixed with newer libraries