Repository navigation
CS 1.6 NextClient: Stuck at "Starting Local Game Server" when creating new local game #80
Description
NextClient Build Issue Report
Issue Description
Description:
After building NextClient from source and launching it, the client gets stuck when trying to start a local server.
Steps to reproduce:
- Clone the repository and build NextClient from source
- Launch NextClient
- Go to "New Game" → try to start a local server
Expected behavior:
Local game server should start and the game should load normally.
Actual behavior:
Client gets stuck at "Starting Local Game Server" and never proceeds.
Additional information:
- OS: Windows 11
- Build configuration: Release
- Visual Studio: 2022 Community (14.44.35207)
- CMake: 4.1.0-rc1
- Generator: Ninja (fallback: NMake Makefiles)
- Architecture: x86
Error messages encountered during build:
CMake Error at nextclient/launcher/dep/gs-sdk/build/cmake/gameanalytics/CMakeLists.txt:1 (CMAKE_MINIMUM_REQUIRED):
Compatibility with CMake < 3.5 has been removed from CMake.
Update the VERSION argument <min> value. Or, use the <min>...<max> syntax
to tell CMake that the project requires at least <min> but has been updated
to work with policies introduced by <max> or earlier.
Or, add -DCMAKE_POLICY_VERSION_MINIMUM=3.5 to try configuring anyway.
Build warnings:
- CMake Deprecation Warning about compatibility with CMake < 3.10
- Policy CMP194 warning about MSVC assembler
- FetchContent deprecation warning for distorm
- Various compiler warnings about macro redefinition and type conversion
Notes / guesses:
- Possibly an issue with local server initialization in the NextClient build
- Could be related to missing dependencies or paths for HL1 engine libraries
- The build completes successfully but runtime behavior is affected
- May be related to CMake policy compatibility issues
Build environment details:
- Repository: https://github.com/CS-NextClient/NextClient
- Commit: Latest main branch
- Dependencies: All submodules properly initialized
- vcpkg packages: Successfully installed 18 packages including OpenSSL, zlib, glfw3, etc.
Files generated after successful build:
cmake-build-release\out\bin\Release\cstrike.execmake-build-release\out\bin\Release\next_engine_mini.dllcmake-build-release\out\bin\Release\FileSystem_Proxy.dllcmake-build-release\out\bin\Release\steam_api.dllcmake-build-release\out\bin\Release\nitro_api2.dllcmake-build-release\out\bin\Release\vgui2.dll
Additional context:
- Tried restarting the client and computer, issue persists
- Build process completes without fatal errors
- All required dependencies are present
Activity
Polarhigh commentedon Oct 27, 2025
@IGNRexI I would like to clarify a few points:
cmake --build cmake-build-release -t INSTALL_ALL? If not, are you sure you have collected all the necessary files?Also, try pulling up the changes and compile again
IGNRexI commentedon Oct 29, 2025
@Polarhigh
I’m using this version of ReGameDLL:
regamedll-bin-5.28.0.756.zip
For the build process, I’m using my own build script. It configures vcpkg automatically, selects Ninja if available, and builds in Release mode. It also copies the output files into the assets directory. Here is the build method I used (summarized):
cmake -G "Ninja" -B cmake-build-release -DCMAKE_BUILD_TYPE=Release -DCMAKE_TOOLCHAIN_FILE="dep/NclNitroApi/vcpkg/scripts/buildsystems/vcpkg.cmake" -DVCPKG_TARGET_TRIPLET=x86-windows-static -DVCPKG_MANIFEST_MODE=ON
cmake --build cmake-build-release --target BUILD_ALL --config Release
Then I run the generated cstrike.exe inside the assets folder.
The issue occurs when trying to start a local game (from “New Game”).
It doesn’t load into the map — it gets stuck on “Starting Local Game Server” and stays there indefinitely.
I can try rebuilding after pulling the latest changes, but before I do:
Is this ReGameDLL version confirmed to work with the current NextClient build?
Do I need a specific ReGameDLL version (or AMXX / Metamod setup) for local server to initialize correctly?
Should I use cmake --build cmake-build-release -t INSTALL_ALL even if I already manually copied the built files?
Let me know and I will re-test with the recommended configuration.
Polarhigh commentedon Oct 30, 2025
I just tested version 5.28.0.756-dev, and the local game initializes and runs successfully.
There are known issues when using AMX Mod X or Metamod, including possible crashes or freezes, but they are not currently a development priority. NextClient is primarily designed for playing on remote servers, so fixing AMX Mod X or Metamod integration problems is considered low-priority and may not be addressed in the near future..
Please also note that the ReHLDS API is not available on NextClient, and ReHLDS cannot be used with this client due to incompatibility.
No, this is not required if you have already copied all the necessary build outputs using your own script.