newserv: [Blue Burst] Cannot get past patch screen without patch-bb contents, and cannot startup server with them

Bug(s) and how to reproduce: I extracted the contents of newserv release v2024-03-14, replaced LocalAddress and ServerName, ran the server. Gamecube PSO Ep1&2/3 connnect fine using Dolphin (HLE BBA). PSO Blue Burst however is stuck on patch screen. Background animation is moving, but no progress is ever made or any progress bar is shown at all. If I close the server at this point, I immediately get error 903 on client, indicating there was a successful connection of some sort.

Then I add map*.dat and data.gsl files into patch-bb/data folder and restart the server. Now the server crashes on startup. I’ve tried using files from multiple PSO BB clients (including those shared to me by an Ephinea staff member), and the result is always the same. See last logs before crash below (dump file is in attachment):

I 793 2024-03-24 13:27:24 - [Config] Loading tool table
I 793 2024-03-24 13:27:24 - [Config] Loading weapon tables
I 793 2024-03-24 13:27:24 - [Config] Loading tekker adjustment table
0 [main] newserv 793 cygwin_exception::open_stackdumpfile: Dumping stack trace to newserv.exe.stackdump

If I remove data.gsl from patch directory, server now runs properly once more, but I get stuck on patch screen again.

Additional context: Running server and client on same machine, running on Windows 10. Tried running server on both “Command Prompt” and “Windows PowerShell”, with same results. Let me know if additional system information is needed. I deleted JSON cache on patch-bb in-between trying different .dat files. I just tested on the latest release (v2024-03-24) and issue remains. Reddit thread where I recently asked this same question, if relevant.

Thank you! newserv.exe.stackdump.txt

About this issue

  • Original URL
  • State: closed
  • Created 3 months ago
  • Comments: 31 (15 by maintainers)

Most upvoted comments

I’ve updated the readme to be a bit more clear about these things. It sounds like this is resolved for everyone, so I’m closing this now. If you run into this again, please reopen this ticket.

Check the LogLevels section in config.json.