Loading...
  OR  Zero-K Name:    Password:   

Post edit history

Development update 27.10.2016

To display differences between versions, select one or more edits in the list using checkboxes and click "diff selected"
Post edit history
Date Editor Before After
10/27/2016 7:41:45 AMAUrankAdminGoogleFrog before revert after revert
Before After
1 Here is another development update. 1 Here is another development update.
2 \n 2 \n
3 = Lobby protocol performance = 3 = Lobby protocol performance =
4 \n 4 \n
5 In the last development update, @Licho talked about problems with the server scaling to hundreds of users. The planned server changes are in and have been subjected to thousands of spambots spamming channels and opening/joining battles on the test server. Everything seemed to work and should be deployed to the main server soon. 5 In the last development update, @Licho talked about problems with the server scaling to hundreds of users. The planned server changes are in and have been subjected to thousands of spambots spamming channels and opening/joining battles on the test server. Everything seemed to work and should be deployed to the main server soon.
6 \n 6 \n
7 = Chobby = 7 = Chobby =
8 \n 8 \n
9 I have mainly been working on Chobby fixes and features. The way I work on minor features is to read feedback and make tickets for when I feel like plowing through a bunch of simple tickets. Some minor changes of interest are increased chat spacing (it's a lot more readable) and AI menu caching with right click to add recent AIs. 9 I have mainly been working on Chobby fixes and features. The way I work on minor features is to read feedback and make tickets for when I feel like plowing through a bunch of simple tickets. Some minor changes of interest are increased chat spacing (it's a lot more readable) and AI menu caching with right click to add recent AIs.
10 \n 10 \n
11 My less minor task this week was to improve the top of the interface. @Gavino bought up planetwars and we realized that a user would need to be shown three status/notification panels if they are in a battle and matchmaker queue when asked to join in the defense of a planet. With a fourth spot we would also be able to display a matchmaker notification for a queue they're not in. Fulfilling this requirement lead me to increase the space at the top of small mode and I much prefer the result: 11 My less minor task this week was to improve the top of the interface. @Gavino bought up planetwars and we realized that a user would need to be shown three status/notification panels if they are in a battle and matchmaker queue when asked to join in the defense of a planet. With a fourth spot we would also be able to display a matchmaker notification for a queue they're not in. Fulfilling this requirement lead me to increase the space at the top of small mode and I much prefer it to the previous, slightly cramped, version. Here is the new version with two status panels:
12 [img]http://i.imgur.com/Qz6GNxU.jpg[/img] 12 [img]http://i.imgur.com/Qz6GNxU.jpg[/img]
13 \n
13 The height of each panel is halved in the (rare) case of three or four panels: 14 The height of each panel is halved in the (rare) case of three or four panels:
14 [img]http://i.imgur.com/bfmiix7.jpg[/img] 15 [img]http://i.imgur.com/bfmiix7.jpg[/img]
15 While in the area I cleaned up the top right "player profile" area. It no longer overlaps the 10th channel tab and it now has a much-asked-for link to the users site profile. 16 While in the area I cleaned up the top right "player profile" area. It no longer overlaps the 10th channel tab and it now has a much-asked-for link to the users site profile.
16 \n 17 \n
17 @Licho and @hokomoko worked on Spring to improve Chobby idle performance. Chobby is now able to tell Spring when to do a redraw and this has already significantly improved performance. Limiting Chobby to 15 FPS reduced the CPU usage on my hardware from 7% to around 1.5%. Drawing one frame every ten seconds reduced its load to a negligible amount. If required, I plan to make Chobby update as infrequently as possible. 18 @Licho and @hokomoko worked on Spring to improve Chobby idle performance. Chobby is now able to tell Spring when to do a redraw and this has already significantly improved performance. Limiting Chobby to 15 FPS reduced the CPU usage on my hardware from 7% to around 1.5%. Drawing one frame every ten seconds reduced its load to a negligible amount. If required, I plan to make Chobby update as infrequently as possible.
18 \n 19 \n
19 = Performance = 20 = Performance =
20 \n 21 \n
21 Spring 103.0.1-281 seems to have performance issues for some people. @hokomoko is looking into it and has some ideas regarding the cause. Benchmarking would help us determine how widespread the problem is and when it was introduced. A guide is here: http://zero-k.info/Forum/Thread/23119?postID=165686#165686 22 Spring 103.0.1-281 seems to have performance issues for some people. @hokomoko is looking into it and has some ideas regarding the cause. Benchmarking would help us determine how widespread the problem is and when it was introduced. A guide is here: http://zero-k.info/Forum/Thread/23119?postID=165686#165686
22 \n 23 \n
23 = Planetwars = 24 = Planetwars =
24 \n 25 \n
25 We haven't been working on this but it came up and is worth mentioning here. @Gavino is quite excited about Planetwars and asked us to run it as soon as possible. I've been treating Planetwars as a stretch goal but @Licho had always wanted it as something on, or near, release. The server code from the last Planetwars is intact and updating it for the lobby protocol should be straightforward. So, given @Gavino's enthusiasm and claims of testers, we might put some work in to update Planetwars and run a test round sometime in the coming weeks. 26 We haven't been working on this but it came up and is worth mentioning here. @Gavino is quite excited about Planetwars and asked us to run it as soon as possible. I've been treating Planetwars as a stretch goal but @Licho had always wanted it as something on, or near, release. The server code from the last Planetwars is intact and updating it for the lobby protocol should be straightforward. So, given @Gavino's enthusiasm and claims of testers, we might put some work in to update Planetwars and run a test round sometime in the coming weeks.