Getting booted off when playing with buddy shortly after starting game

Hi!

I'm trying to play multiplayer with a buddy, and we've both been experiencing disconnects. If I host the game, he gets booted out after a few minutes, and can't easily get back in without restarting the entire game, but my game goes on just fine. If we reverse and he hosts the game, I get disconnected after a few minutes, though he is fine. We're both on desktop PCs hardwired, I'm behind a NAT (and have tried opening port 3000 directly to my desktop), he is not behind a NAT, but also cleared port 3000 completely open through his firewall. We were having issues using the direct connection dialog, putting in the straight IPs and port 3000, but using the Join Game from Steam did work to get us in the lobbies (doing the Join Game from the multiplayer and direct IP would just time out and bump us back to the main menu). Both of these installs are completely fresh, I built a new PC and hadn't installed CastleStory on it yet until a few days ago, and he just bought the game yesterday and installed it fresh.

The error message from the logs it gets right when someone gets disconnected looks to be:
2017-02-02 21:47:50,838 [12560] ERROR Brix.Lifecycle.Pooling.ObjectPoolSingleton - Gameobject Harvest (0) with AssetKey Groupes.Harvest was already released. GameObject release aborted!

Any other information we can provide to help determine what might be going on here?

Thanks!

Comments

  • ShatojonShatojon Administrator Developer Backer
    Hey FirstNight,

    We'll need as complete logs as possible. Please do the following;

    Host a game and play with your friend, once you get booted, don't close the game.

    Instead, *both* of you start a singleplayer game. Just load any singleplayer gamemode on any map. Once it's loaded and you see your Bricktrons, close your games.

    Now both of you go to C:\Users\\AppData\Local\Temp\Castle Story\logs

    We'll need the unity.txt one - usually at the top (if sorted by date modified).

    If you both send us that log file, we'll be able to better figure out what's going on.
Sign In or Register to comment.