Cricket Heroes - testing & feedback
- Thread starter kurtkz
- Start date
- Status
Gaurav_7
Executive member
- Joined
- Jan 3, 2010
- Profile Flag
- India
Code:
RUN @ 21-May-12 12:05:02 AM
VERSION: 1.44
REGISTERED: False
PROFILE: N/A
MESSAGE: Object reference not set to an instance of an object.
STACK TRACE: at Cricket.Main.GameStateSimulate.ProcessVisual(Single ms, Single ms2)
at Cricket.Main.GameInstance.UpdateOnly(Single ratio)
at Cricket.Main.GameInstance.Loop()
at Cricket.Main.Game.Main(String[] args)Again getting this error. I observed it happens after I play a custom series with the two teams I've created using the editor. Maybe that helps. Same thing, error pops up after the initial models, files, etc. are loaded.
Also, I've observed that in an ODI there seems to be only one standout batsman while others just get out. Happens many times. There are still plenty of wides there..
Some examples attached -
Code:
Polokwane Phantoms vs Manicaland Bulls
FORMAT: ODI
VENUE: Toronto Cricket Ground
UMPIRES: Ian Gould and Billy Bowden
MANICALAND BULLS 1st INNING
BATTING SCORECARD
Player Status Runs Balls 4s 6s S/R
Virender Sehwag c M Guptill b J Kallis 119 106 14 0 112.26
Hashim Amla c J Trott b M Morkel 5 9 0 0 55.56
Brendon Taylor c M Guptill b Z Khan 2 14 0 0 14.29
AB de Villiers c +M Boucher b I Tahir 6 6 1 0 100.00
Murray Goodwin c +M Boucher b I Tahir 0 6 0 0 0.00
Hamilton Masakadza c A Petersen b J Kallis 7 12 1 0 58.33
Elton Chigumbura b I Tahir 13 28 1 0 46.43
Tim Southee b M Morkel 3 10 0 0 30.00
Dale Steyn c +M Boucher b U Gul 1 16 0 0 6.25
Douglas Hondo c +M Boucher b U Gul 7 24 0 0 29.17
Tendai Chatara not out 3 26 0 0 11.54
FOW: 1/25 2/34 3/52 4/63 5/71 6/108
7/128 8/140 9/166 10/192
Manicaland Bulls - 192 all out Overs 42.4 RPO: 4.40
EXTRAS: 26 WD: 23 NB: 1 B: 1 LB: 1
PARTNERSHIPS:
Virender Sehwag / Hashim Amla oooooo** 25 (25)
Virender Sehwag / Brendon Taylor ooo** 9 (20)
Virender Sehwag / AB de Villiers oooooo*** 18 (14)
Virender Sehwag / Murray Goodwin ooooooo 11 (11)
Virender Sehwag / Hamilton Masakadza ******** 8 (16)
Virender Sehwag / Elton Chigumbura ooooo*** 37 (46)
Virender Sehwag / Tim Southee oooooooo* 20 (19)
Virender Sehwag / Dale Steyn oooooooo 12 (27)
Virender Sehwag / Douglas Hondo oooooo** 26 (36)
Virender Sehwag / Tendai Chatara oooooo* 26 (43)
BOWLING SCORECARD
Player Overs Mdns Runs Wkts E/R Wd NB
Morne Morkel 7.0 1 25 2 3.57 7 1
Zaheer Khan 10.0 0 41 1 4.10 1 0
Jacques Kallis 6.4 0 38 2 5.70 10 0
Imran Tahir 10.0 1 47 3 4.70 0 0
Umar Gul 5.0 0 26 2 5.20 1 0
Monde Zondeki 4.0 1 13 0 3.25 4 0
POLOKWANE PHANTOMS 1st INNING
BATTING SCORECARD
Player Status Runs Balls 4s 6s S/R
Martin Guptill c +B Taylor b D Steyn 9 16 1 0 56.25
Alviro Petersen b D Steyn 1 3 0 0 33.33
Jacques Kallis c +B Taylor b T Chatara 35 30 4 0 116.67
Jonathan Trott c T Southee b D Steyn 8 10 1 0 80.00
Ian Bell not out 83 72 10 0 115.28
Mark Boucher c +B Taylor b E Chigumbura 18 26 2 0 69.23
Zaheer Khan c V Sehwag b T Chatara 13 46 0 0 28.26
Morne Morkel not out 0 6 0 0 0.00
DNB: Umar Gul, Imran Tahir, Monde Zondeki
FOW: 1/3 2/20 3/32 4/75 5/124 6/189
Polokwane Phantoms - 193 / 6 Overs 34.3 RPO: 5.59
EXTRAS: 26 WD: 21 NB: 2 B: 2 LB: 1
PARTNERSHIPS:
Martin Guptill / Alviro Petersen oooooo*** 3 (6)
Martin Guptill / Jacques Kallis oooo*** 17 (21)
Jonathan Trott / Jacques Kallis oooooo* 12 (14)
Ian Bell / Jacques Kallis ooo****** 43 (38)
Ian Bell / Mark Boucher ooooo*** 49 (44)
Ian Bell / Zaheer Khan oooooo** 65 (75)
Ian Bell / Morne Morkel ooooooo 4 (11)
BOWLING SCORECARD
Player Overs Mdns Runs Wkts E/R Wd NB
Dale Steyn 7.0 0 41 3 5.86 10 0
Tim Southee 8.0 0 50 0 6.25 4 1
Tendai Chatara 8.0 0 46 2 5.75 3 1
Douglas Hondo 5.0 0 40 0 8.00 2 0
Elton Chigumbura 6.0 2 11 1 1.83 2 0
Code:
Polokwane Phantoms vs Manicaland Bulls
FORMAT: ODI
VENUE: Toronto Cricket Ground
UMPIRES: Billy Doctrove and Asoka de Silva
MANICALAND BULLS 1st INNING
BATTING SCORECARD
Player Status Runs Balls 4s 6s S/R
Virender Sehwag b U Gul 7 15 1 0 46.67
Hashim Amla b U Gul 5 5 1 0 100.00
Brendon Taylor c M Guptill b U Gul 7 8 1 0 87.50
AB de Villiers c I Bell b Z Khan 94 74 11 0 127.03
Murray Goodwin b J Kallis 9 17 1 0 52.94
Hamilton Masakadza c J Trott b J Kallis 3 12 0 0 25.00
Elton Chigumbura c +M Boucher b M Zondeki 1 17 0 0 5.88
Tim Southee c J Trott b M Zondeki 52 87 2 0 59.77
Dale Steyn c U Gul b J Kallis 7 23 0 0 30.43
Douglas Hondo c M Morkel b J Kallis 1 5 0 0 20.00
Tendai Chatara not out 5 21 0 0 23.81
FOW: 1/6 2/16 3/30 4/56 5/77 6/97
7/166 8/194 9/209 10/235
Manicaland Bulls - 235 all out Overs 47.1 RPO: 4.88
EXTRAS: 44 WD: 41 NB: 1 B: 1 LB: 1
PARTNERSHIPS:
Virender Sehwag / Hashim Amla ******** 6 (8)
Virender Sehwag / Brendon Taylor o******* 10 (12)
Virender Sehwag / AB de Villiers oooo***** 14 (14)
Murray Goodwin / AB de Villiers ooo*** 26 (32)
Hamilton Masakadza / AB de Villiers o******** 21 (23)
Elton Chigumbura / AB de Villiers ********* 20 (26)
Tim Southee / AB de Villiers oo****** 69 (72)
Tim Southee / Dale Steyn ooooo** 28 (45)
Tim Southee / Douglas Hondo ooooooo 15 (14)
Tim Southee / Tendai Chatara oooo* 26 (38)
BOWLING SCORECARD
Player Overs Mdns Runs Wkts E/R Wd NB
Morne Morkel 10.0 0 41 0 4.10 8 0
Umar Gul 10.0 0 49 3 4.90 6 1
Jacques Kallis 8.0 0 51 4 6.38 16 0
Imran Tahir 10.0 0 42 0 4.20 2 0
Monde Zondeki 5.1 1 28 2 5.42 8 0
Zaheer Khan 4.0 0 22 1 5.50 1 0
POLOKWANE PHANTOMS 1st INNING
BATTING SCORECARD
Player Status Runs Balls 4s 6s S/R
Martin Guptill b D Steyn 6 9 1 0 66.67
Alviro Petersen run out (V Sehwag) 9 11 1 0 81.82
Jacques Kallis c H Masakadza b D Steyn 2 9 0 0 22.22
Jonathan Trott c +B Taylor b T Chatara 104 91 10 1 114.29
Ian Bell b T Southee 2 7 0 0 28.57
Mark Boucher c D Hondo b E Chigumbura 8 14 0 0 57.14
Zaheer Khan c V Sehwag b E Chigumbura 2 7 0 0 28.57
Morne Morkel c V Sehwag b T Southee 13 35 1 0 37.14
Umar Gul c +B Taylor b D Steyn 33 66 1 0 50.00
Imran Tahir b D Steyn 3 12 0 0 25.00
Monde Zondeki not out 3 10 0 0 30.00
FOW: 1/10 2/21 3/30 4/39 5/58 6/68
7/121 8/175 9/201 10/210
Polokwane Phantoms - 210 all out Overs 45 RPO: 4.67
EXTRAS: 25 WD: 23 NB: 1 B: 1 LB: 0
PARTNERSHIPS:
Martin Guptill / Alviro Petersen oooooo** 10 (15)
Jacques Kallis / Alviro Petersen o****** 11 (11)
Jacques Kallis / Jonathan Trott ********** 9 (11)
Ian Bell / Jonathan Trott oo*** 9 (11)
Mark Boucher / Jonathan Trott oooo***** 19 (34)
Zaheer Khan / Jonathan Trott oo******** 10 (10)
Morne Morkel / Jonathan Trott oo****** 53 (63)
Umar Gul / Jonathan Trott oo******* 54 (66)
Umar Gul / Imran Tahir oooooo* 26 (35)
Umar Gul / Monde Zondeki oooo*** 9 (15)
BOWLING SCORECARD
Player Overs Mdns Runs Wkts E/R Wd NB
Dale Steyn 9.0 1 31 4 3.44 10 0
Tim Southee 10.0 0 48 2 4.80 5 0
Tendai Chatara 10.0 0 52 1 5.20 4 0
Elton Chigumbura 8.0 2 24 2 3.00 2 0
Douglas Hondo 8.0 0 54 0 6.75 2 1kurtkz
Game Developer
Holy moly, that's a lot of wides. Hmm, I think I know what the problem might be. If I can fix it tonight, I'll upload again - otherwise it'll be sometime early in the week.
Gaurav_7
Executive member
- Joined
- Jan 3, 2010
- Profile Flag
- India
Is that all the problems I posted in there?
puddleduck
Chairman of Selectors
Proving tricky to balance whether someone is in or not by the looks of those screen shots. As in, once in, they get runs, but if not in, they probably get out
kurtkz
Game Developer
Yup 
----------
@puddleduck: Yup, that's part of the problem. The major problem is that I also take into account an expected score and the stronger batsman keeping strike. It's a bit of a juggling act, but I think I can sort it out.
----------
@puddleduck: Yup, that's part of the problem. The major problem is that I also take into account an expected score and the stronger batsman keeping strike. It's a bit of a juggling act, but I think I can sort it out.
puddleduck
Chairman of Selectors
Good idea on the expected score. Like your thinking as I can see how that can then affected by various factors. Maybe for limited overs less the batsman keeping strike, but more the other batsmen giving him the strike 
kurtkz
Game Developer
@puddleduck: Yup, good idea - I also just noticed that there was a bug where the current score < expected score would result in a higher probability of a wicket 
The scorecards look a lot more balanced now. Not sure why I didn't pick it up sooner to be honest :P
----------
The following factors (more or less) are taken into account for simulations:
- pitch conditions
- climate conditions
- bowler/batsman skill
- bowlers/batsman confidence
- batsman strengths/weaknesses
- ball condition
- historic batting strike rates
- scoreboard pressure
- law of averages
- nervous 90's and similar scores
- player fatigue
- weaker batsman become more confident with stronger batting partners
- expected batting/bowling averages
- series/tournament performance
- historic bowling strike rates
- stronger batsman tries to keep strike where possible
The scorecards look a lot more balanced now. Not sure why I didn't pick it up sooner to be honest :P----------
The following factors (more or less) are taken into account for simulations:
- pitch conditions
- climate conditions
- bowler/batsman skill
- bowlers/batsman confidence
- batsman strengths/weaknesses
- ball condition
- historic batting strike rates
- scoreboard pressure
- law of averages
- nervous 90's and similar scores
- player fatigue
- weaker batsman become more confident with stronger batting partners
- expected batting/bowling averages
- series/tournament performance
- historic bowling strike rates
- stronger batsman tries to keep strike where possible
puddleduck
Chairman of Selectors
Yeah I suggest it because obviously in limited overs the better batsman will still take the single rather than turn it down to keep the strike. Whilst the other batsman (especially when new will be looking to get singles and get the in batsman on strike as quickly as possible).
Although, it's worth suggesting that if say Cook was on 50, he'd probably still look to take a single if the new man in was for example KP?
Although, it's worth suggesting that if say Cook was on 50, he'd probably still look to take a single if the new man in was for example KP?
kurtkz
Game Developer
@puddleduck: Correct again I'll add those suggestions and post some results tomorrow.
I'll add those suggestions and post some results tomorrow.puddleduck
Chairman of Selectors
If you keep honing this... you are aware that you'd end up with a game that is both playable and fun, whilst also as a simulator/management game not too far from being Icc or Cricket Coach with an already far better graphical representation of what they attempt to show. For example, stick some bars that effect the batsmans aggression levels in when managing, same for bowlers, with more meaning more risk and greater reward possibilties etc... Not for now obviously, but this game could have incredible depth and scope 
kurtkz
Game Developer
@puddleduck: Those bars are already in there...
EDIT: That should actually read: They don't work as well I'd like, but the basics are already implemented.
EDIT: That should actually read: They don't work as well I'd like, but the basics are already implemented.
puddleduck
Chairman of Selectors
Essentially a career mode could be immense, you could create the first actual career mode...
You start as a player, you work your way through a career, and then when captain you get to influence your fellow teammates... then when you reach a retirement age you can either end the game or carry on as manager (would then need to start balancing and introducing things like regens etc). Again I'm jumping ahead of myself, but the potential is excellent and you've done the right thing trying to get the solid foundations in place first
You start as a player, you work your way through a career, and then when captain you get to influence your fellow teammates... then when you reach a retirement age you can either end the game or carry on as manager (would then need to start balancing and introducing things like regens etc). Again I'm jumping ahead of myself, but the potential is excellent and you've done the right thing trying to get the solid foundations in place first
kurtkz
Game Developer
Yeah, I have big plans for the game, but getting the foundations in place (and bug free) is turning out to be quite a pain in the backside. I really want to get started with career mode but it'll have to wait for a (mostly) bug-free version. I rate I'm at around 90% at the moment so hopefully I can get cracking sometime this week.
EDIT: Also, thanks for the encouragement. It's hard to imagine that I'd given up on this game about 2 years. I can finally see the light at the end of the tunnel
EDIT: Also, thanks for the encouragement. It's hard to imagine that I'd given up on this game about 2 years. I can finally see the light at the end of the tunnel
Last edited:
puddleduck
Chairman of Selectors
Like any language really The beginning is fun, because every new word is a learning experience, then it gets difficult as your own abilities and skill levels don't match what you want to achieve. You realise that now you know the basics, you also are aware that the complexities are bigger than you realised. Like making it up a small hill to find the next one is twice the size. However, if you don't turn around and keep going, you find some paths, a route that works. Slowly, you make your way forward again until you get near the peak. However the peak is always covered by treacherous conditions and as we jump back to the original metaphor (maybe with a wing glide suit for style and effect) we are now using this new language for plenty of conversing. However, even though we now speak the language well enough to talk to others, to write, and to read. To master it... well, that in itself is another skill.
.... and tenuous metaphors over
The beginning is fun, because every new word is a learning experience, then it gets difficult as your own abilities and skill levels don't match what you want to achieve. You realise that now you know the basics, you also are aware that the complexities are bigger than you realised. Like making it up a small hill to find the next one is twice the size. However, if you don't turn around and keep going, you find some paths, a route that works. Slowly, you make your way forward again until you get near the peak. However the peak is always covered by treacherous conditions and as we jump back to the original metaphor (maybe with a wing glide suit for style and effect) we are now using this new language for plenty of conversing. However, even though we now speak the language well enough to talk to others, to write, and to read. To master it... well, that in itself is another skill..... and tenuous metaphors over
Last edited:
- Status
