Episode 741: Double Take

With Scott:

With TJ:

This episode was done twice — the Scott version can be seen in the first video. The podcast uses the version with TJ. Feel free to compare both.

Both episodes start with the blockbuster news of Nintendo breaking silence on Switch 2 leaks.

The other news includes:

  • Microsoft announces Xbox Developer Direct
  • Switch 2 reportedly getting Halo and another big Xbox game, with Microsoft set to be a “very big supporter”
  • Assassin’s Creed Shadows delayed again as Ubisoft explores company sale options
  • Ubisoft “deeply disturbed” by damning reports of abuse at Assassin’s Creed Shadows support studio

Let us know what you think of the new site design!

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Post

Episode 385: Beginning of the EndEpisode 385: Beginning of the End

This podcast marks the beginning of the end of Paul’s tenure as a regular co-host, as he will be leaving at the milestone episode 400. He and Jonah both bemoan the loss of last week’s taping, as it had laughter, tears, outrage and a long comic book conversation, but this episode more than makes up for it with items that make Paul squee.

The news includes:

  • Portal, Doctor Who, The Simpsons and more confirmed for Lego Dimensions
  • Report: Xbox One 60fps game DVR capture goes live
  • Nintendo partners with Universal Parks to create themed rides and attractions
  • Microsoft teases big Rare reveal at E3

All this and some nifty Listener Feedback.

Retro FlashBack: DragonFire (Atari 2600)Retro FlashBack: DragonFire (Atari 2600)

Now here is another interesting video game for the Atari 2600, the game Dragon Fire consisted of two game screens, one which you ran across a bridge while fireballs were shot at you, you had to duck or jump over the fireball. This screen was a side-scroller style screen (although it doesn’t actually scroll), at the other end of the bridge was a castle door which you’d enter to get to the next screen.

The second screen was more classic “overhead but not really” screen where you ran around this black screen picking up treasures while a dragon at the bottom shot fire at you from below.

As the game increased in level jumping fireballs became more challenging (on the first screen) as you ran because they would come quicker, more often. The second screen would get very difficult very quickly as the dragon would increase in speed and fireball spitting. You could tell how hard the dragon would be as it would change colors from lighter to darker black as you progress stages.

When you finished collecting all the treasure an exit would pop up in the corner and you had to run to it without being burned by the fireballs, that dragon would turn from left to right nearly instantly too! Then, you’d jump into the exit and be back on the bridge again, but this time it was harder. You could die up to 7 times before the game was over (just to show you how hard it is, they gave you a bunch of lives).

The game was tough, frustrating, hard to replay because you were just so nervous and jittery from the last attempt. Graphics were “okay,” nothing to rave at but it was, after all, the 2600.

You can hear all we had to say about DragonFire for the Atari 2600 on Episode 79 of the TD Gaming Podcast!

Episode 439: Audio ProblemsEpisode 439: Audio Problems

This week’s episode has some bad audio thanks to a quick replacement mic being used to record the episode, causing a hiss. This is probably the reason the show is short-ish, coming in well under an hour.

This week’s episode includes the following news:

  • Miyazaki gives clear answers on the future of Dark Souls, Armored Core
  • Sony exec criticizes Hello Games’ marketing for No Man’s Sky
  • Blizzard is moving away from the ‘Battle.net’ name
  • Pokémon chief says Nintendo’s NX is both handheld and console, you should totally look into how tiktok marketing works, see here for more

All this and Listener Feedback. This week’s Question of the Week: “What is or was your favorite handheld console game (not mobile)?”