요즘 스팀게임인 던전디펜더 라는 게임에 심하게 빠져있는데.

4인플레이는 할만하지만 8인맵에서 클라이언트들의 렉이 너무너무 심하다는 이야기가 있어

프레임드랍은 기본에 너무잦은 순간이동 렉사망 등등..

그래서 구글링을 해봤는데...

http://clan-kiss.com/Forum/kb.php?mode=article&k=17&sid=eb22793a2011fa3bcdfcb6fe143079af

위 링크의 내용중에

Tickrate is actually VERY VERY COMPLEX! It is the "Frames Pr Second" the server is running at. Yes, it is so complex. A tickrate of 20 means that the server is doing 20 frames of action per second. To make it even more complex, lets just say, that it processes data 20 times a second. (Player movement, player firing, player deaths, player bitching, player lagging, and the other more unimportant things 20 times a second). So. 1 Tick = 1 Frame. The server tickrate is the "framerate" at which the server is running on.

Ok, now that you are confused by the tickrate term, lets see how far it is between each tick update. since it says pr second, we will use 1 second, which is 1000 milliseconds. it\'s Per. so we gotta divide somewhere, let\'s try the following. 1000ms/20 = 50ms. OK! it might seem like there is 50 milliseconds between each tick. Let\'s try it the other way. 50ms * 20 = 1000ms. Oh yes, we reversed the equation and got what we started with. That means. A tickrate of 20, gives 50ms between each update on server.

Lets have a ping of 60 in DOS to a certain server. This means a packet of data uses 60 milliseconds to go from your superfantastic computer to the crappy tickrate 20 server in Uganda and back. In other words. Now because of the complexity of the net, this doesn\'t mean it uses 30ms to reach the server, and 30ms to travel back. (Asymmetric routing) Someone else will have to explain why this is so. But lets assume that this is actually the true thing this time. The data DOES use 30ms to travel from your computer to the server, and 30ms to reach your computer again. Let\'s put in some more numbers. The tickrate! We know that it\'s 50ms between each tick on server. So let\'s take worst case. The packet of data we send, uses 30ms to reach server. The server has just completed a tick before the data arrived, so the data has to wait for 50ms. Ok, data has waited 50ms and been processed, and now leaves the server for the client to happily enjoy. This takes another 30ms. So to add it up, the packet used 30+50+30 = 110ms to travel from client to server, be processed on server, and return to client.

Another thing that affects result is your own framerate. Your computer will not handle data while it\'s busy telling the video card what to show you. A framerate of 100fps means that it\'s another 1000ms/100 = 10ms between each time it can handle data.

라는 부분이 이해가 잘 안가는데

짧은 영어실력으로 서버의 전송속도가 클라이언트의 fps와 관계가 있다는 내용같은데

데이터 전송속도와 클라이언트의 fps가 관계가 있는거임 ?

그리구 언리얼3 엔진 ini파일 많이 수정 해본 횽 있으면
 

클라이언트의 쾌적한 플레이 환경을 구성하기위한 팁도 알려주믄 감솨 감솨

*한국인이 호스트 / 클라이언트 전원 한국인 으로 가정.
*8인플레이를 할때 내쪽에서 클라이언트 당 전송하는 데이터가 초당 11,000 바이트 밖에 안되는데 이걸 확 늘리는 방법은 없음 ?
모든 클라이언트가 11,000씩 받는거보니까 뭔가 제한이 걸린거 같은데.. ini파일 수정해서 늘리는 방법은 없을까 ?

요즘 이거때문에 너무 스트레스 받아서 횽들한테 도움 청하려고 왔음... 부탁해 !