Gamestate on long running server becoming null
I am observing that the client GameState (GetWorld()->GameState) is null when connecting to a dedicated server running for 2-3 days.
The server does not change maps as I am stress testing one long running game for issues like this.
I have logged the server and it seems that GameState is valid so it seems somewhere on the client calls to GetWorld()->GameState are returning null.
Does anyone at Epic have any suggestions on where to look for a possible cause of this issue? What might cause a GameState to stop replicating or become null on the client?
Best, George ( www.playdaysofwar.com )
Hey Matthew, thanks for asking around. I don't think the logs would be much help so I will continue to debug this on my end for now.
answered May 24 '16 at 09:11 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here