Ashes Cricket 2013 Bugs

[T.J.Hooker]

For some reason only Fegan can explain, the #11 batsman will always appear as the #3 batsman on the scorecard.

hahaha amazing. I wondered wtf was going on with the number 3 spot.

My god what were they doing during the development cycle? How could they have written such incredibly faulty code?

 

[whiteninness]

Maybe he wanted to dupe people into thinkin they were smart enough to have night watchmen.

 

[Biggs]

...the #11 batsman will always appear as the #3 batsman on the scorecard.

Call it the "MattW Effect" since he's never able to bowl correctly in these games anyway...

 

[saif258]

its batting in both first person & broadcast cam.problem solved.

 

[rocky_g]

Don't know why you guys created this thread. Should have started a thread named "Good things about Ashes Cricket 13". This game is a bug itself.

 

[Col. Hans Landa]

This page will be remembered as the one that saved cricket gaming

 

[Biggs]

I don't think I'm far off in thinking it'll be more a forum, than a specific page or thread. But if I'm picking one, my money is on the release date thread in the DBC forum will "save" cricket gaming... He winked.

 

[AbhishekS]

I'm so eager to play this game just to discover more bugs out of it!

 

[IceAgeComing]

This page will be remembered as the one that saved cricket gaming

whats so special about page 10 of the "Ashes Cricket 2013 Bugs" thread of the "Ashes Cricket 2013" subforum of the Planet Cricket forums on planetcricket.org?

 

[AbhishekS]

whats so special about page 10 of the "Ashes Cricket 2013 Bugs" thread of the "Ashes Cricket 2013" subforum of the Planet Cricket forums on planetcricket.com?

Nothing. But it indeed is special on planetcricket.net

 

[IceAgeComing]

...that's what I said...

 

[Frostyvegi]

whats so special about page 10 of the "Ashes Cricket 2013 Bugs" thread of the "Ashes Cricket 2013" subforum of the Planet Cricket forums on planetcricket.org?

I posted on said page on sead thread on said subforum of said forum of said site.. that is what makes it special.

-edit-

I said sead.. beat that!

 

[Hasimir Rossi]

Had to join solely for this thread. I'm both in awe and aghast at just how terrible this game is. Shame on 505 for dumping all the blame on the devs when they had to have known how bad it was before allowing it a release. Activision pulled what later became Sleeping Dogs, claiming it wasn't good enough, so I fail to see how 505 were unable to gauge the quality of Ashes 2013.

 

[T.J.Hooker]

Well the complicating factor here seems to be that Trickstar's was actually pushing for a release.

They were reportedly trying to release this in June and 505 wouldn't let them.

 

[Biggs]

Both Ross and Barmy have confirmed this is pretty much exactly the same game they saw prior to the June release, potentially missing features (such as the tv-style HUD) which we had seen photos of. Good chance the "turning on" of things actually involved turning off a bunch of stuff...

I don't think we will ever know the extent of the bizarre things that went down on this game but we can be reasonably assured that they knew on June they had a disaster on their hands and no amount of delay was going to fix it.

Fegan and management at Trickstar just took everyone on a merry ride and finally got caught, pants down by EVERYONE.