
The Hump-day Update is a weekly supplement to the Sarcastic Gamer Podcast. This week we cleared up some confusion about Devil May Cry 4 and shared our thoughts on the new Frontlines: Fuel of War multiplayer demo for the Xbox 360 that’s been keeping us up late.
If you liked this episode, please consider giving us the honor of your subscription in iTunes or RSS. If you insist, you can always just download the mp3. If you are currently using a computer with iTunes on it, would you mind heading over there and leaving us some feedback? Much obliged. Oh, by the way… HEY! What’s wrong? Why haven’t you taken our QUICK podcast survey yet? Thanks for the Diggs!
| Related Posts:
|





5 responses so far ↓
1 Saccia // Feb 13, 2008 at 1:07 pm
Regarding the PS3 install time VS the Xbox360…. The Xbox360 *does* cache the game to the hard drive. It just happens to do it while you play the game rather than causing an “install” time the first time you put the disk in. Here’s the HDD FAQ for reference: http://www.xbox.com/en-US/hardware/x/xbox360harddrive/harddriveornot.htm
It’s just a design flaw that the PS3 doesn’t cache on the fly. They should have had enough sense to enable such a capability. BTW, this caching feature is why you 20GB hard drive is only 13GB even when the drive appears empty. That missing space (aside from filesystem overhead) is for caching.
2 Ron Williams // Feb 13, 2008 at 6:52 pm
Saccia,
Your information is incorrect, the PS3 can cache data on the HD just like the 360, its up to the developer to use this feature. Your comment is ill informed and very poorly thought out. Next time do your research before posting idiotic comments such as this.
I hate armchair developers.
3 pondec // Feb 13, 2008 at 8:42 pm
frontlines fuels of war is f@#!*$g awsomei’m glad they said some thing about it or i would have had no idea it was out
4 asf // Feb 14, 2008 at 3:38 am
Frontlines multiplayer demo sucked balls. >.> Holy crap it was awful. It’s like turd meets crap.
5 Tyrone Hawk // Feb 14, 2008 at 1:01 pm
Hey guys, is it only me or the podcast suddendly ends after 8:33 minutes?
Leave a Comment