1 00:00:05,220 --> 00:00:07,440 In today s episode of Developer s Diary, 2 00:00:07,450 --> 00:00:10,410 we will be telling you more about Tanki X optimization, 3 00:00:10,460 --> 00:00:13,180 and the impact your feedback has on the game. 4 00:00:13,340 --> 00:00:15,140 Make sure you don’t miss it! 5 00:00:16,960 --> 00:00:20,480 Optimizing the game, is one of the top priorities for our developers. 6 00:00:20,480 --> 00:00:23,980 In the last episode, we explained some parts of this process. 7 00:00:24,020 --> 00:00:26,000 But this time, we’ll be digging deeper! 8 00:00:26,280 --> 00:00:32,580 We re working on three kinds of optimization: client... server... and cluster connectivity. 9 00:00:32,600 --> 00:00:36,120 Client optimization mainly involves the improvement of graphics, 10 00:00:36,160 --> 00:00:40,260 and the elimination of various things that might trigger drops in fps. 11 00:00:40,890 --> 00:00:43,140 The main goal of server optimization 12 00:00:43,140 --> 00:00:47,690 is to increase the number of players that can simultaneously play on a single server. 13 00:00:47,690 --> 00:00:52,340 At this point in time, Tanki X only has one active testing server. 14 00:00:52,340 --> 00:00:57,900 Our server can currently handle a maximum of 50 simultaneously connected players. 15 00:00:57,900 --> 00:01:00,780 But this number is growing with every release. 16 00:01:01,300 --> 00:01:03,960 Once we’re done with the optimization process, 17 00:01:03,960 --> 00:01:06,640 our servers should be able to host anywhere between 18 00:01:06,640 --> 00:01:09,600 two and three thousand simultaneously connected players. 19 00:01:10,140 --> 00:01:11,300 We expect that there will be more 20 00:01:11,420 --> 00:01:13,980 than a couple of thousand tankers playing simultaneously, 21 00:01:14,040 --> 00:01:16,140 therefore, we will have a number of servers. 22 00:01:16,560 --> 00:01:17,680 Now, the real challenge 23 00:01:17,680 --> 00:01:20,660 is to make all the servers synchronize in real time. 24 00:01:20,880 --> 00:01:23,740 To achieve this, we will have to group them into a cluster. 25 00:01:23,750 --> 00:01:27,030 What this means is that, physically, there will be a dozen servers, 26 00:01:27,030 --> 00:01:29,790 but the game will treat them as one giant server. 27 00:01:30,180 --> 00:01:32,140 Without this cluster implementation, 28 00:01:32,140 --> 00:01:36,020 our servers would never be able to support the open beta testing. 29 00:01:36,260 --> 00:01:37,380 This is why we are committed 30 00:01:37,390 --> 00:01:40,890 to solving this problem rapidly, and in the best possible way. 31 00:01:43,170 --> 00:01:47,010 Just like any other game developer, our goal is to make a great game. 32 00:01:47,010 --> 00:01:49,950 This is why your opinion is extremely important to us. 33 00:01:49,950 --> 00:01:51,770 In order to get the required feedback, 34 00:01:51,770 --> 00:01:56,190 we regularly send different questionnaires to our closed beta participants. 35 00:01:56,710 --> 00:02:00,060 It is thanks to your feedback and bug reports on the help site, 36 00:02:00,060 --> 00:02:02,840 that we ve managed to repair a huge number of bugs. 37 00:02:03,140 --> 00:02:07,420 These include minor texture flaws, incorrect battle fund distribution, 38 00:02:07,420 --> 00:02:10,220 lots of bugs on the CTF mode, and many more. 39 00:02:10,560 --> 00:02:14,100 Our developers are actively working on the anti-cheat system. 40 00:02:14,100 --> 00:02:18,420 Our latest step in this direction, was reconfiguring our preventive systems. 41 00:02:18,420 --> 00:02:22,620 This was done in order to reduce the number of fake signals triggered by lags, 42 00:02:22,620 --> 00:02:25,080 which led to unexpected self destruction. 43 00:02:25,280 --> 00:02:28,640 Since then, the number of these incidents has dropped dramatically. 44 00:02:30,700 --> 00:02:35,140 In our previous episode of Developer s Diary, we talked about changes in graphics. 45 00:02:35,140 --> 00:02:39,160 This triggered a wave of positive feedback, as well as lots of questions. 46 00:02:39,480 --> 00:02:40,500 One of them was: 47 00:02:40,600 --> 00:02:44,840 Will Tanki X allow us to customize our graphics settings in more detail, 48 00:02:44,840 --> 00:02:49,180 such as setting the drawing range, and the quality of water, shadows and vegetation? 49 00:02:49,540 --> 00:02:52,120 Yes, we are definitely planning on implementing 50 00:02:52,120 --> 00:02:54,340 an improved menu for graphics settings. 51 00:02:54,709 --> 00:02:59,329 However, this will most likely happen closer to the start of the open beta. 52 00:02:59,700 --> 00:03:03,160 Hope you enjoyed this episode of Tanki X Developer’s Diary. 53 00:03:03,170 --> 00:03:04,160 See you next time![]