when im the first who connects to my king of the hill server after the server starts my game crashes or better say it stops reacting
Description
Details
- Severity
- Crash
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Operating System Version
- windows 10 x64
- Category
- Dedicated Server
start the server
connect as first player
it works for everyone except the first who connects
Event Timeline
alright i found out with a bit of testing that:
your game freezes when you had restarted the game and the server and are the first to connect
it doesnt freeze when you only restart the server but not the game when you have been on the server before
i hope the logfiles etc will give you guys more infos about this...
Hello,
thank you for the feedback. Could you please tell me whether you experience same issue when trying to host a vanilla server or host one the MP missions from vanilla Arma 3 (e.g. Support Stratis ?).
As for the issue itself, how exactly game freezes? Is it stuck in loading or you play for a while then FPS drop and game completely freezes eventually. are you able to quit the game normally or you have to kill it via task manager? Does it eventually crash (like a real crash, game popping up and error message and closing itself)?
i have no problems with other servers
also my koth worked before...
but now we made a change
we place the locationspecific stuff serverside and hand them over to clients with publicvariable "x"
on the missionfile in the mission.sqm there are only the playable characters on the nothern spawnisland
and you get teleported to your base when the coordinates for the respawn markers are given over by the server...
and when this happens (and you are the first after restart and have restarted your game as stated before) the game freezes (when you are still on the spawnisland)....
ctrl+alt+del -> kill the process... which leads to an errormessage as you can see in the logfiles
my mates have the same problem...
the code looks fine so far... should work...
no real errors in the logfiles (client/serverside) regarding this problem
Mass closing old issues that are:
- Not relevant anymore
- Probably already fixed
- Missing info and no activity for years