Cricket Heroes - testing & feedback

[itay128]

More bugs

Hi kurtkz,

There are a few more bugs I found:
Four runs is given even if the ball does not go to the rope from an overthrow.
Batsmen get out stumped even though a defensive stroke is played against spinners (occurs when the ball goes off bat and then pad I think)
Test match is drawn even though the match hasn't gone for 5 days (occurs after both teams complete their 1st innings) after choosing whether to follow on.

 

[kurtkz]

@itay: Hehe, thanks - those bugs have all been fixed now. The next update is coming soon

 

[kurtkz]

Hi all,

update 1.27 is now available:

Change Log

- crashes when appealing for LBW in test matches
- crashes when certain achievements are unlocked
- crashes when playing (not simulating) a HK6 or beach cricket match
- game automatically restarts when accepting a resolution change
- re-enabled auto-updater
- performance optimizations
- simple colour-based kits for 3D models (these can be edited)
- smoothed out fielding transitions for 3D models
- reworked fielding AI
- tweaked parameters for test matches (non-simulated)
- minor visual changes
- fixed bug where 4 would randomly be given (very rare)
- fixed crash at end of exhibition match
- achievements are no longer unlocked when simulating innings
- status bar no longer shown in nets
- fixed crash in 2D mode when catches are taken
- fixed crash when follow-on can be enforced
- moved wind indicator to status bar
- fixed shadows
- fixed crash when switching between 2D/3D in-game
- added proper installer

I'm still waiting on new models from Buko, but as soon as I have them I'll incorporate them into the paid version.

Cheers
Kurt

 

[itay128]

Update 1.27 bugs

Hi kurtkz,

There is a fielding bug where the fielder doesn't even throw the ball back to the bowler or wicketkeeper (in-game).

Here's also the error log for the crash after UDRS is completed (for LBWs):

MESSAGE: The given key was not present in the dictionary.

STACK TRACE: at System.ThrowHelper.ThrowKeyNotFoundException()
at System.Collections.Generic.Dictionary`2.get_Item(TKey key)
at Cricket.Main.InningStatistics.AddBall(BallStatistics ball, Int32 facing1, Single atrophy, GameInstance instance)
at Cricket.Main.GameStateDeliver.WicketLBW()
at Cricket.Main.GameStateDeliver.ProcessInput(Single ms)
at Cricket.Main.GameInstance.Loop()
at Cricket.Main.Game.Main(String[] args)

 

[kurtkz]

Crap. does the fielding bug happen all the time?

----------

Also I'll take a look at that lbw bug. I mustve missed a case somewhere...

 

[Mikeyw12345]

Hi, I have noticed that the fielding is too slow or something as I can get a single hitting it two a man in the ring every time. Also the game crashes every time I play a test match, I can complete the toss, select openers and then it crashes with this message:

MESSAGE: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

STACK TRACE: at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
at System.ThrowHelper.ThrowArgumentOutOfRangeException()
at System.Collections.Generic.List`1.get_Item(Int32 index)
at Cricket.Main.GameStateChooseBowler.ProcessInput(Single ms)
at Cricket.Main.GameInstance.Loop()
at Cricket.Main.Game.Main(String[] args)

 

[kurtkz]

Thanks Mikeyw12345 & itay128, I'll try to fix those issues up tonight and reupload tomorrow morning.

----------

@Mikeyw12345: Two quick questions - are you running v1.27? Which teams did you select?

 

[kurtkz]

Ok - managed to fix up the LBW bug (there was one case I didn't fix). Also made the fielders react faster to quick singles.

I'm struggling to recreate the bug where the fielder doesn't throw the ball to the keeper/bowler...@itay128: Can you give me more details about when this happens?

 

[itay128]

Ok - managed to fix up the LBW bug (there was one case I didn't fix). Also made the fielders react faster to quick singles.

I'm struggling to recreate the bug where the fielder doesn't throw the ball to the keeper/bowler...@itay128: Can you give me more details about when this happens?

Changed the frame skip from full to minimum (during a game) and then the fielding bug happened... but otherwise after a few restarts the fielders do throw the ball to either the wicketkeeper or bowler.

 

[kurtkz]

@itay128: Hmm, very odd - I'll keep my eye on it for now but I'll release an update later that should take care of the other bugs.

 

[Mikeyw12345]

Thanks Mikeyw12345 & itay128, I'll try to fix those issues up tonight and reupload tomorrow morning.

----------

@Mikeyw12345: Two quick questions - are you running v1.27? Which teams did you select?

I am on 1.27 and it seems to happen with all teams

 

[itay128]

@itay128: Hmm, very odd - I'll keep my eye on it for now but I'll release an update later that should take care of the other bugs.

Correction on the bug I observed on update 1.27: The fielder actually does not move and the batsmen do not move after taking a single (that is the game freezes however, the clock is still moving). I happened to accidentally test the wrong update (1.26 instead of 1.27), thus the correction.

Other bugs observed:
- Can't see the ball during while watching replays
- Can't see the ball during UDRS

Attached: Screenshot of fielding bug

 

[kurtkz]

Hi all,

update v1.28 is now available.

Change log:

- fixed LBW crash when referring
- fixed test mode for quick matches
- fielders react faster to quick single
- adjusted field size
- tweaked batting AI
- fixed image buttons to fade in and out
- fixed bug when playing a shot after the ball hits the pad/body
- removed old broken networking code
- UDRS scenes are more responsive
- improved fielding when trying for runouts
- AI will bring in field properly when quick singles are being taken

Cheers
Kurt

----------

@itay128: Yup, replays are kinda borked at the moment. I'll fix that up for the next release.

----------

@Mikeyw12345: Hmm, I still can't reproduce that error - can you download v1.28 (not auto-update) and try a clean install?

 

[itay128]

@kurtkz: Fielding bug seems to have been fixed in update 1.28. Thanks.

 

[kurtkz]

Awesome