Cricket Heroes - testing & feedback

[kurtkz]

Can you click on View and paste the full error log here please?

 

[ibad17]

@kurtkz Any update on my issue.?

 

[kurtkz]

Haven't been home yet so haven't had a chance to look at it.

 

[ibad17]

@kurtkz Still no updates??

Also the commentary format is different now in new patch. It is simple and the previous one was fine to post. Can you make the same way.

 

[kurtkz]

@ibad17: Not yet, still trying to reproduce your crash. Check the Reports options in the game. It may be that the PC formatting has been disabled.

 

[ibad17]

ok thanks. But please tell me when you find the solution for the crash.

 

[itay128]

@kurtkz: Just a suggestion, could you post the changelog (when an update is out) so at least we know what's going on.

 

[kurtkz]

@itay128: Yup, will do so for the next one. I completely forgot to do so for the last 2 patches

 

[itay128]

@kurtkz: Got this error log after changing the gameplay speed in 'gameplay' settings. The game crashed when I exited 'gameplay' settings.

MESSAGE: Object reference not set to an instance of an object.

STACK TRACE: at Cricket.Utility.Maths.Vector3D.Add(Vector3D v) in d:\Projects\Cricket Heroesv3D\Cricket Heroesv3D\Cricket Heroesv3\Cricket Heroes\Utility\Maths\Vector3D.cs:line 177
at Cricket.Main.GameObject.Player.RenderShadow(Int32 lights, Single ratio, Camera2D camera, Boolean isTest, Vector3D light) in d:\Projects\Cricket Heroesv3D\Cricket Heroesv3D\Cricket Heroesv3\Cricket Heroes\Main\GameObject\Player.cs:line 3864
at Cricket.Main.GameInstance.Display(Single ratio) in d:\Projects\Cricket Heroesv3D\Cricket Heroesv3D\Cricket Heroesv3\Cricket Heroes\Main\GameInstance.cs:line 16544
at Cricket.Main.GameInstance.Loop() in d:\Projects\Cricket Heroesv3D\Cricket Heroesv3D\Cricket Heroesv3\Cricket Heroes\Main\GameInstance.cs:line 19835
at Cricket.Main.Game.Main(String[] args) in d:\Projects\Cricket Heroesv3D\Cricket Heroesv3D\Cricket Heroesv3\Cricket Heroes\Main\Game.cs:line 5173

 

[itay128]

@kurtkz: Tried to start another game but game crashed before a ball was even bowled.

VERSION: 2.702
REGISTERED: True
PERMISSIONS MODE: True

MESSAGE: Object reference not set to an instance of an object.

STACK TRACE: at Cricket.Utility.Maths.Vector3D.Add(Vector3D v) in d:\Projects\Cricket Heroesv3D\Cricket Heroesv3D\Cricket Heroesv3\Cricket Heroes\Utility\Maths\Vector3D.cs:line 177
at Cricket.Main.GameObject.Player.RenderShadow(Int32 lights, Single ratio, Camera2D camera, Boolean isTest, Vector3D light) in d:\Projects\Cricket Heroesv3D\Cricket Heroesv3D\Cricket Heroesv3\Cricket Heroes\Main\GameObject\Player.cs:line 3864
at Cricket.Main.GameInstance.Display(Single ratio) in d:\Projects\Cricket Heroesv3D\Cricket Heroesv3D\Cricket Heroesv3\Cricket Heroes\Main\GameInstance.cs:line 16544
at Cricket.Main.GameStateNewSpell.ProcessVisual(Single ms, Single ms2) in d:\Projects\Cricket Heroesv3D\Cricket Heroesv3D\Cricket Heroesv3\Cricket Heroes\Main\GameStateNewSpell.cs:line 129
at Cricket.Main.GameState.Update(Single ms, Single ms2) in d:\Projects\Cricket Heroesv3D\Cricket Heroesv3D\Cricket Heroesv3\Cricket Heroes\Main\GameState.cs:line 648
at Cricket.Main.GameStateChooseBowler.Process(Single ms, Int32 overrideIdx) in d:\Projects\Cricket Heroesv3D\Cricket Heroesv3D\Cricket Heroesv3\Cricket Heroes\Main\GameStateChooseBowler.cs:line 1332
at Cricket.Main.GameStateChooseBowler.ProcessInput(Single ms) in d:\Projects\Cricket Heroesv3D\Cricket Heroesv3D\Cricket Heroesv3\Cricket Heroes\Main\GameStateChooseBowler.cs:line 1397
at Cricket.Main.GameInstance.Loop() in d:\Projects\Cricket Heroesv3D\Cricket Heroesv3D\Cricket Heroesv3\Cricket Heroes\Main\GameInstance.cs:line 19950
at Cricket.Main.Game.Main(String[] args) in d:\Projects\Cricket Heroesv3D\Cricket Heroesv3D\Cricket Heroesv3\Cricket Heroes\Main\Game.cs:line 5173

 

[kurtkz]

Hmm, which shadow settings are you playing on?

 

[itay128]

@kurtkz: Set it to high... Should I set it lower?

 

[kurtkz]

I think that may be causing it - I'll check it out a little to confirm.

EDIT: Confirmed. It will be fixed in the next patch.

 

[ibad17]

@kurtkz any updates on our issue?

 

[kurtkz]

@ibad17: Not yet, but I should have a new patch ready either tonight or early tomorrow morning. Still testing the changes now.