Skip to content

v0.3.1 - start-up fixes for Windows launchers and Linux

Choose a tag to compare

@SilversRayGA SilversRayGA released this 09 Nov 20:43
· 29 commits to main since this release

A hotfix for two start-up problems reported after 0.3.0. Nothing else changed: online play, mods and settings are as in 0.3.0.

Fixes

Windows: instant crash when started from a launcher (#2). When Cha-Cha.exe was started without a console (for example from Quiver or another launcher), it closed right after the game began loading. Cha-Cha sends its messages to log.txt in that case, but the second stream couldn't open the file the first one held, and the first message written to it ended the program. Both now share the file, and a lost log message can no longer close the game. This affected every version of this fork when started that way.

Linux: the program didn't start on many distributions (#1). The Linux build needed the very newest system libraries (glibc 2.43 and FFmpeg 8) because it was built on Fedora 44. It is now built on Ubuntu 22.04 and brings FFmpeg and the libraries it needs in a lib/ folder. It runs on glibc 2.35 or newer: Ubuntu 22.04, Fedora 36, SteamOS 3, Bazzite and later. The download is larger as a result (about 77 MB).

Install / update

Windows: unzip Cha-Cha-0.3.1-windows-x64.zip. To update, copy the new Cha-Cha.exe and SDL3.dll over the old ones. Your data folder (saves, settings, mods) stays as it is.

Linux: unpack Cha-Cha-0.3.1-linux-x86_64.tar.gz and run ./Cha-Cha (chmod +x Cha-Cha if needed). To update an existing folder, replace Cha-Cha and copy the new lib/ folder next to it. Remove the old libSDL3.so.0, libshaderc_shared.so.1 and libSPIRV-Tools*.so next to the program. Your Cha-Cha.ini, game/, save/ and mods/ stay.

You still need your own Monster Hunter 3 Ultimate (US) dump with update v32. No game files are included.

Still having problems?

Please open an issue at https://github.com/SilversRayGA/Cha-Cha-Plus/issues and attach log.txt (next to the program on Linux, in data/ on Windows). A crash dump helps too, as it did for #2.