Come join us for a Public Playtest tomorrow @ 2300 CEST / 1400 PST
IronHorse
Developer, QA Manager, Technical Support & contributor Join Date: 2010-05-08 Member: 71669Members, Super Administrators, Forum Admins, Forum Moderators, NS2 Developer, NS2 Playtester, Squad Five Blue, Subnautica Playtester, Subnautica PT Lead, Pistachionauts
Developer, QA Manager, Technical Support & contributor Join Date: 2010-05-08 Member: 71669Members, Super Administrators, Forum Admins, Forum Moderators, NS2 Developer, NS2 Playtester, Squad Five Blue, Subnautica Playtester, Subnautica PT Lead, Pistachionauts
We'll be holding a Public Playtest tomorrow, Wednesday August 2nd @ 2300 CEST / 1400 PST, in our official discord server.
Come join us to test some server performance improvements, bug fixes, working whips and MACs, Match seeding, and a new Skulk Challenge mode!
(It's also a chance to earn your "kill a developer" achievement if you haven't already
)
This will be in our BETA branch and ready for download 30 minutes before the aforementioned time. You can join our General Voice Channel in the discord during the PT in order to coordinate with us and ask questions.
Click here if you need instructions on how to switch to that branch.
We're looking for community feedback on the fixes and features, as well as assessing the stability of the build and matchmaking itself, before we test for one more additional week whereupon the patch will be released to the public.
If you have any further questions, feel free to contact me in our discord.
Thanks and see you there!
______________________
edit:
Thanks everyone who showed!
Your participation provided great data for us, along with your suggestions and feedback
Come join us to test some server performance improvements, bug fixes, working whips and MACs, Match seeding, and a new Skulk Challenge mode!
(It's also a chance to earn your "kill a developer" achievement if you haven't already
)This will be in our BETA branch and ready for download 30 minutes before the aforementioned time. You can join our General Voice Channel in the discord during the PT in order to coordinate with us and ask questions.
Click here if you need instructions on how to switch to that branch.
We're looking for community feedback on the fixes and features, as well as assessing the stability of the build and matchmaking itself, before we test for one more additional week whereupon the patch will be released to the public.
If you have any further questions, feel free to contact me in our discord.
Thanks and see you there!
______________________
edit:
Thanks everyone who showed!
Your participation provided great data for us, along with your suggestions and feedback
Comments
We are currently going into feature lockdown on 317 today, with hopes of releasing it August 11th.
Once 317 is out in the world, our focus will shift towards getting x64 for public beta release with 318 finally. My hope is that this patch will come out faster than normal as its about getting 64 into the wild, and we've already been working on and testing that branch for months on the side. There will be a big push to get clients and servers to test it out before we push it to live, but it already looks pretty stable for Windows servers as is, (there's a few kinks to work on with Linux servers still) and you can see this with the TA servers running it currently. This branch will also come with an auto crash collector that is far more snazzy and useful for everyone, (instantly uploads the crash report in under 2 sec) and should help us quickly eliminate any outstanding/edge case client or server bugs we were unable to catch going forward.
Once that goes out we'll have another client performance patch that we're excited to get working (the change impacts over 1,000 lines of code!) that should lower input delay and hopefully help with that perception of "why does 150 fps feel like 40?" issue.
There's some more exciting stuff that comes after that, but I think that's all I can say officially for now though
Hope that answers your question?
Is this what your referring to @IronHorse ?
https://trello.com/c/jOhfeTQ5/601-luajit-nyi-calls-optimization-testing
Yup, that's the one!
You can scroll down to see the card's lengthy history.. it's been worked on since March, due to the amount of bugs it introduced. (see the vid where damaged marines caught fire?
The sparking effect was an interesting effect for a low health marine.