Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
(1 edit)

Hi Sven,

Thanks for trying out the game! I have two ideas for what might be causing the issue.

1) During the first second or two of the title screen loading, the input keys are disabled for the player. I put this in after playtesting showed some players mashing buttons at the Game Over Screen. The button presses would go from the Game Over screen to the Title Screen and then immediately start a new game. This would overwrite the player's autosave file. This isn't needed at the start of the game, though, and I will make some adjustments.

2) It's an unknown bug :) If it's not the delay issue above, I have no idea why it's doing that. I keep debug logs with each game in the CaravanaDebugLog folder next to the .exe file. I'd appreciate it if you could email me the log file 'CaravanaDebugLog0.log' if this is the case.


Cheers,
Josh

(1 edit) (+1)

I looked at the log and this is the start of it : 

[Screens.ScreenManager]: Adding screen Title Screen
[Screens.ScreenManager]: Screens: [Title Screen: Active]
[PlayerModel]: Initializing PlayerModel
[PlayerModel]: Awake, seed is 1690126827
*******************************************************
[Screens.ScreenManager]: Unhandled Exception!
System.NullReferenceException: Object reference not set to an instance of an object
  at Assets.Scripts.IO.InputHelp.GetButtonDown (Assets.Scripts.IO.InputHelp+Buttons button) [0x001cb] in <f6ffd33d2fea43b288c20ba161375ee3>:0 
  at Assets.Scripts.Screens.TitleScreen.HandleInput () [0x002f8] in <f6ffd33d2fea43b288c20ba161375ee3>:0 
  at Assets.Scripts.Screens.ScreenManager.Update () [0x00087] in <f6ffd33d2fea43b288c20ba161375ee3>:0 
*******************************************************

The "Unhandled Exception"  then repeats what seems like every frame. Nothing else, just a super bloated file with the same error message over and over.

Thanks! Exactly what I was looking for.

Alright, I figured out the issue. The exception was occurring because there was no gamepad plugged in. I've corrected this mistake and you shouldn't run into that problem anymore.