Cricket Heroes - testing & feedback

Status
Not open for further replies.
Hi all,

update v1.37 is now available and should address the problems I introduced in the previous version.

Cheers
Kurt

PS I haven't uploaded the installer yet, but I'll do that tonight - the zip file is available though.

The link for the zip file is missing on the downloads page.
 
Hi all,

I've uploaded the installer again and reuploaded the zip file. There was a minor bug with the ball shape view, so if you downloaded v1.37 earlier, please download it again. Apologies for the inconvenience :/

Cheers
Kurt
 
Had this error when I clicked on ball shape at the end of a 20-20 between England and Windies -

RUN @ 12/05/2012 03:17:11

VERSION: 1.37
REGISTERED: False
PROFILE: xcx

MESSAGE: Index was outside the bounds of the array.

STACK TRACE: at Cricket.Main.GameStateBallState.ProcessVisual(Single ms, Single ms2)
at Cricket.Main.GameInstance.Loop()
at Cricket.Main.Game.Main(String[] args)


Controller works nicely, except I can't input my registration details at the start. Would be handy if keyboard/mouse still useable and then controller in matches.

That said controller was still pretty smooth to use in menus, and could only really be refined by introducing the R1/R2 and L1/L2 (shoulder buttons) as back and forward in menu screens. Not sure whether it's easier to just have mouse support in menus?

Works well though, and especially with the pad there's a lot of potential :)
 
Aaah I know exactly where that error is. Thanks :) Yeah, I'll add shoulder button support and also re-enable the mouse in menus so you have a choice.
 
@kurtkz: There's a few bugs I notice:
- When the ball hits the rope for overthrows, only 4 runs is given (even if the batsmen took a run)
- The damage meter of the ball does not reset when a new innings commences (noticed this while playing a 4 day game)
- Only 78 overs were bowled in the first day of a 4 day game (exhibition mode)
 
@itay: Thanks for the feedback :)

  • yup, the damage meter isn't resetting for FC games - that's fixed in the next update
  • are you sure it didn't award you 5? The 4 notification does pop up but it should be awarding you 5...
  • I'll adjust the time again - did lots of wickets fall that day?


----------

Incidentally, the following changes have been made for the next update:

v1.38

  • fixed crash when checking ball shape at the end of the match
  • improved frame skipping
  • fixed ball-stumps collisions
  • ball shape & condition effect on swing/seam/spin has been balanced
  • improved ball textures
  • added ball tracking for UDRS reviews
  • adjusted defense hit box
  • adjusted keeper fielding
  • cut-off time for FC matches is now 6.30pm
  • batsman arrive at the crease sooner (previously was timed at 2min)
  • fixed ball discolouration (it was just getting darker instead of browner)
  • fixed scoring bug when run out during beach match
 
Last edited:
@itay: Thanks for the feedback :)

  • yup, the damage meter isn't resetting for FC games - that's fixed in the next update
  • are you sure it didn't award you 5? The 4 notification does pop up but it should be awarding you 5...
  • I'll adjust the time again - did lots of wickets fall that day?


----------

Incidentally, the following changes have been made for the next update:

v1.38

  • fixed crash when checking ball shape at the end of the match
  • improved frame skipping
  • fixed ball-stumps collisions
  • ball shape & condition effect on swing/seam/spin has been balanced
  • improved ball textures
  • added ball tracking for UDRS reviews
  • adjusted defense hit box
  • adjusted keeper fielding
  • cut-off time for FC matches is now 6.30pm
  • batsman arrive at the crease sooner (previously was timed at 2min)
  • fixed ball discolouration (it was just getting darker instead of browner)

@kurtkz: No, it didn't award me with 5 runs (it says 4 when it shows the runs scored for each ball of the over and awarded me 4 only)

About the number of wickets that fell on that day, I think only 11 wickets fell (which included bowling out the opposition).
 
@itay: QQ - did you complete the run? I tested it now and it reflected 5 correctly...if you're still completing the run, should it count it as a full run?
 
Hi all,

update v1.38 is now available.

Changelog:

* fixed crash when checking ball shape at the end of the match
* improved frame skipping
* fixed ball-stumps collisions
* ball shape & condition effect on swing/seam/spin has been balanced
* improved ball textures
* added ball tracking for UDRS reviews
* adjusted defense hit box
* adjusted keeper fielding
* cut-off time for FC matches is now 6.30pm
* batsman arrive at the crease sooner (previously was timed at 2min)
* fixed ball discolouration (it was just getting darker instead of browner)
* fixed scoring bug when run out during beach match
* fixed scoring bug when running when an overthrow goes for 4

Cheers!
Kurt
 
Downloaded the latest version, started a test, went through the toss and got this crash before the game started:


MESSAGE: Value cannot be null.
Parameter name: key

STACK TRACE: at System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument)
at System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
at Cricket.Main.GameObject.Player.get_Height() in D:\Projects\Cricket Heroesv3\Cricket Heroes\Main\GameObject\Player.cs:line 2391
at Cricket.Main.GameInstance.Display(Single ratio) in D:\Projects\Cricket Heroesv3\Cricket Heroes\Main\GameInstance.cs:line 7906
at Cricket.Main.GameInstance.Loop() in D:\Projects\Cricket Heroesv3\Cricket Heroes\Main\GameInstance.cs:line 9882
at Cricket.Main.Game.Main(String[] args) in D:\Projects\Cricket Heroesv3\Cricket Heroes\Main\Game.cs:line 2709
 
Status
Not open for further replies.

Users who are viewing this thread

Top