over 2 years
ago -
Hunt: Showdown
-
Direct link
Transcript (by Youtube)
0s | and uh |
---|---|
2s | we are here uh with the big trio now so |
6s | uh dennis is back hey dennis how are you |
8s | doing hello okay |
10s | hope you are good uh everyone miss you |
13s | in the chat |
14s | i miss the chatter and uh uh i know that |
18s | stefan has been on many crisis streams |
20s | but i don't think he has been on a hunt |
22s | fun before uh he is a associate producer |
24s | for hunt so hey stefan how are you doing |
27s | today hello yeah i'm fine |
29s | it's really great now to connect with |
31s | the run community so thank you |
34s | yeah awesome to have you on and uh |
36s | to start with we will be talking about |
38s | some technical features and it's gonna |
41s | be stefan of guiding us through of three |
44s | bigger one of these so |
46s | let's just dive into these |
48s | uh |
49s | starting with the server stability |
50s | improvements that we've added in 1.9 |
54s | correct so first i want to mention so we |
57s | are listening to the feedback and we are |
58s | aware of the um |
60s | server issues we are facing at the |
62s | moment |
63s | so we are really totally aware of this |
65s | but you also need to understand what |
66s | issues we are facing at the moment and |
68s | that's the reason |
69s | for this first light we want to go |
71s | through it please |
73s | yeah so the first one is that we're |
75s | challenging it challenges with a |
77s | globally open game |
78s | as you know from the beginning we had an |
81s | open game that means someone from |
82s | australia can |
83s | connect to the server and us if |
86s | everything is possible if you have a |
87s | ping of 100 000 for example in theory |
89s | right you can play wherever you want |
91s | with all the friends you have |
93s | or just alone and that is of course also |
96s | also |
97s | very challenging for us now because |
99s | we're getting a higher player base we |
101s | face now over 30 000 players |
103s | sometimes at the same time |
105s | and that means um yeah we need to make |
107s | some daily restrictions in this regards |
109s | i tell you later why but it's fair and |
112s | you will understand what we are changing |
114s | at the end |
115s | okay the second point is because of the |
117s | other a lot of data going through one |
119s | channel |
119s | that means everyone is connecting to one |
122s | server maybe the the latency is very |
124s | high at the end from the player and then |
126s | he's also downloading uploading data |
129s | through that one channel that means that |
130s | we'll be coming delays and now i |
132s | mentioned with 30 000 people connecting |
134s | to one channel and it's getting stacking |
136s | to each other and at the end some people |
139s | experience some likes maybe on the |
140s | server and that is also one of the |
142s | reasons |
144s | yep globally high traffic |
146s | um it's known that many people are now |
148s | home office for example the globally |
150s | high traffic is much higher compared to |
153s | two years ago |
154s | and we cannot break any physics right |
157s | that means if someone's connecting from |
158s | one continent to the other one the |
161s | latency is high um |
163s | yeah that we don't own an own pipeline |
166s | of internet |
167s | yeah sorry just to interrupt you for a |
168s | second any chance you could turn your |
170s | own volume up because i actually maxed |
172s | you out but uh i think you are audible |
174s | but it maybe could be a bit louder for |
177s | people maximum stef yeah i i you are 200 |
181s | percent on my discord now so |
183s | the more the better you know uh |
185s | some people say it's fine i wasn't here |
188s | over 9000 that's exactly the hand |
189s | setting so |
192s | okay is it better now |
194s | i think so uh i'll monitor the check |
196s | thank you yeah uh sans okay sounds good |
199s | yeah so um and because of all the |
201s | reasons i have mentioned of course also |
203s | our back end is overloaded so it's a |
205s | domino effect of all these |
208s | things i have mentioned now in this |
209s | presentation and we have also made |
211s | improvements which i will also come in |
213s | later on this point and on the last |
214s | point ben's please we also face some |
217s | malicious attacks um sadly um but there |
220s | was also one of the reasons we need to |
222s | take care in the past a few months and |
224s | these are the issues we're facing at the |
226s | moment |
227s | but |
228s | good news is we have solutions in place |
230s | and you will um |
232s | know them very quickly in that stream |
233s | here |
234s | yep so the goals are of course improving |
236s | overall service ability i know it's very |
238s | easy just to mention over improving |
240s | server performance but we have made a |
242s | lot of work in this regards |
244s | and |
245s | we we really looked with the team with |
247s | the full network team also in the |
249s | backend team together with the |
250s | performance team together in all the |
252s | areas which we could whichever could |
253s | improve into the game also in a lot of |
256s | work with the qa together to profile |
258s | everything so with one nine you will see |
260s | a little got a lot of good improvements |
262s | regarding these two points yeah just to |
265s | mention here uh since uh obviously we |
267s | already talked about several related |
268s | issues in the last updates we have |
270s | already implemented some of these and we |
272s | are adding more to this update and |
274s | obviously in the future as well but it's |
276s | an ongoing process and uh some things |
278s | take a longer time so please bear with |
280s | us we are working on this is a very high |
282s | priority uh very big part of the team uh |
285s | so the improvements are coming and uh |
287s | yeah stefanos said this update also has |
289s | some good improvements for you in store |
291s | and yeah let's take a look at those |
295s | it's yeah so we have seen that uh |
297s | multiple dedicated server crashes |
300s | um appeared in the past we have fixed |
304s | many of them really many of them so i |
306s | hope you should not face them anymore in |
308s | the game of course then on the second |
309s | point please lens |
311s | yeah improvements made when dedicated |
312s | server loses connection to server |
314s | gateway |
315s | so that was also one of the reasons |
316s | which i mentioned before with the domino |
318s | effect that if the if you're having a |
320s | big delay um between server and you |
322s | you're just getting a connection timer |
324s | for example and you're kicked out of the |
326s | game so we made a lot of improvements |
328s | and also we increased the tolerance |
330s | which you can see in the last point here |
331s | now that you have a you can so the |
333s | connection between you and the server |
335s | could take longer a little bit so you'll |
337s | still connect to the server |
339s | exactly so you will disconnect likes |
342s | basically |
343s | uh if you experienced like many |
344s | disconnects in the past it should be uh |
347s | they're more tolerant from a server so |
348s | you won't get disconnected that easily |
350s | anymore |
351s | correct |
352s | but as i mentioned yes with the next |
355s | points i will tell you how we will fight |
357s | against it a little bit to improve also |
359s | your experience of the hunt game |
361s | yes so we have new we have now a new |
363s | system in place for capability |
365s | that means also if yeah if we're getting |
368s | some capacity issues at peaks um that we |
371s | have this system in place now which can |
373s | just intercept all the |
376s | capacity issues |
377s | and we hope then with the next new peaks |
380s | we should not run into any issues |
382s | anymore it doesn't matter how much |
383s | players will play hunt um it should |
385s | hopefully be unsafe and we should not |
387s | see any server downside then yeah some |
390s | of people uh just to |
392s | make them understand what it means when |
393s | you have the message that servers are |
394s | currently or occupied and searching for |
396s | servers that issue should be very |
399s | quickly solved now because we can scale |
401s | up the servers very quickly and uh |
403s | actually in 1.8.1 uh we created a test |
407s | run of it in the asia region |
410s | but now with 1.9 it is coming to us as |
413s | well as europe |
415s | correct so asia was our let's say test |
417s | pilot but now with one nine we have also |
419s | aided for u.s and europe |
421s | and then we should |
423s | should be fine with that |