Another week, another short status update. This time, it’s waiting for you together with your daily .
Events, Progress & Stuff
- Some improvements and fixes were done on OneSync. Population has been reactivated, and a number of bugs caused by it (but not all of them) were fixed. Tests were had internally.
- Bits and pieces of bandwidth optimization were done, to make population actually possible, even on full servers.
- Visibility culling was implemented, but also shows that sometimes some peds don’t get cleaned up properly. That implies there’s still work to be done.
- There’s still no ETA, don’t ask for one.
- A number of bugs were fixed. Notably:
- An issue preventing emoji characters (and others) from working on commands.
- A weird one that caused some issues in C# resources.
- A pull request by @IceHax fixing accuracy in the Node.js implementation.
- @Hellslicer struggling with Docker build variables. Why?
- Another Node.js bug fix, probably for crashes using zlib.
- Re-enabling the actual console for server-side JS resources.
- A few minor improvements were made to the actual client/server, however not in the production branch yet:
Lazy-loading natives in order to reduce the memory usage per Lua script runtime. This was inspired by a user complaint showing a lot of resources each using 4-5 MB of RAM minimum.
- The server console now should print asynchronously (this should reduce hitches caused by console printing on Windows), and supports color codes (^0-^9) in output.
- We updated the build hosts to Visual Studio 15.8, this caused a brief disturbance in
canaryfunctionality since another new code generation issue appeared, which we quickly fixed with a workaround.
- Lazy-loading natives in order to reduce the memory usage per Lua script runtime. This was inspired by a user complaint showing a lot of resources each using 4-5 MB of RAM minimum.
- Discourse had received another update, including a new plugin installed created by @Vespura that posts friendly reminders when people post topics in #technical-support.
- We published a WIP todo list that we try to maintain, though sudden improvements are usually made ad-hoc and not posted as to-do entry on there. Don’t mind the weird bugs.
- Not much of interest happened outside of this - most work was put into the minor OneSync improvements, and getting this post out on time and not right at the end of the day in CEST.
Snails are bad, okay?