상점 페이지
Chivalry: Medieval Warfare
전체 토론 스크린샷 아트워크 방송 동영상 창작마당 뉴스 가이드 평가

Chivalry: Medieval Warfare

상점 페이지
Chivalry: Medieval Warfare >  창작마당 > Elko 님의 창작마당 > Horde Sandcastle > 토론
Horde Sandcastle
설명 토론91 댓글1485 업데이트 노트
PROTON 2017년 7월 4일 오후 2시 21분
Sever crashing above wave 30
I was amazed to see that top wave reached on Dev1 is 76, when I started to play this mod. I know the gameplay lasts more than 6 hours, and it is enjoyable. But also since I've started to play it, everyone told me that unfortunately, server is bugged and it will crash.

And yeah, my highest wave achieved was 47, when the server crashed for the first time for me. I don't know if it's because of memory leak, overflow or any other reasons. The question is: can this be fixed to allow players acheive higher waves? Because now, the higher wave we can achieve, the higher risk of crash appears, and it will crash before reaching wave 50 (sometimes even 40) for sure. Is there a relatively simple solution to this? Can we somehow help You Elko to track whether it's player fault (like trebslings, firebows) or just a code logic error?

Cheers!
< >
전체 댓글 10개 중 1~10개 표시 중
Snipeyguy 2017년 7월 5일 오전 6시 30분 
I agree on this, would be awesome to reach waves beyond 100 like in the old days. One thing that bugs me is that skeleton waves seem to cause crashing more and more often, especially when the server spams around 5-8 skeleton waves in a row. I´m thinking it might be something to do with the 2nd wave of skellies.
#1
Elko  [개발자] 2017년 7월 6일 오후 3시 31분 
hmm skelly waves can be disabled by config if necesssary.
However, I believe it is a resource restriction on the hosted server (probably out of mem). I was querying about the crashes to the support but unfortuantely no logs.
The problem is that Chivalry is not optimised to support horde or and game mode with massive amount of characters.
Of couse anybody can help. If you are able to provide instructions on how to reliably reproduce the crash it is as good as fixed. I.e. start by testing the skelly wave locally. You can spawn it manually by typing into console: causeevent darkness (... I think?, u get a list by just typing causeevent). You can set the wave increment in the config (how much the wavecount is increased when the wave is over) to quickly test on high waves.
#2
PROTON 2017년 7월 7일 오후 2시 01분 
Elko 님이 먼저 게시:
hmm skelly waves can be disabled by config if necesssary.
However, I believe it is a resource restriction on the hosted server (probably out of mem). I was querying about the crashes to the support but unfortuantely no logs.
The problem is that Chivalry is not optimised to support horde or and game mode with massive amount of characters.
Of couse anybody can help. If you are able to provide instructions on how to reliably reproduce the crash it is as good as fixed. I.e. start by testing the skelly wave locally. You can spawn it manually by typing into console: causeevent darkness (... I think?, u get a list by just typing causeevent). You can set the wave increment in the config (how much the wavecount is increased when the wave is over) to quickly test on high waves.

Can You please tell me how can I test it locally? I don't see any option to play "sandcastle" map offline, nor Horde mode while trying to create offline game via ingame options, I wish to test it on my own
#3
Elko  [개발자] 2017년 7월 7일 오후 2시 40분 
please see map description
#4
PROTON 2017년 7월 13일 오후 5시 10분 
Hmm, this might be related somehow:
With NORMAL mode, we were able to achieve 52 wave. Then server crashed. This is something better than crashing around level 35-40. Server crashed when 144 enemies were left on 52 level (we completed some objectives already, current one was to push the wagon). And none of players used catasling, so I dont think crashes are related to catasling.
#5
Elko  [개발자] 2017년 7월 14일 오전 11시 48분 
good report, so we know it is not directly related to skelly wave either
#6
PROTON 2017년 8월 1일 오후 4시 30분 
Today crash:

Diff: Hard
Wave 33
168 enemies left
7 players on the server
New player just connected, he received 2300 but no info about it in chat.
None of active players has above 1k frags (i thought that is the reason)
PROTON 님이 마지막으로 수정; 2017년 8월 1일 오후 4시 31분
#7
Elko  [개발자] 2017년 8월 1일 오후 4시 46분 
nah, i think it is just a the server running out of resources
#8
Yakul- 2017년 8월 21일 오전 7시 53분 
Could it be just needing to have the servers reset every night to fix mem leeks or running out of resources? - just throwing this out there, i have no idea how servers work.
#9
Elko  [개발자] 2017년 8월 23일 오후 1시 07분 
Restarting the servers was discussed with the hoster. So a script is in place repsarting the server whenever nobody is in. Last restart of dev 1 is 8/23/2017 5:48:58 PM.
But dev 2 was last restarted 19th. Will contact the hoster.

However, if restarting would be a solution, it suggests a memory leak which may built up after a couple of hours anyway.
#10
< >
전체 댓글 10개 중 1~10개 표시 중
페이지당 표시 개수: 1530 50