A Bit of Dr4v on Testing Apps and Updates

Recommended Posts

Hey gang! Wanted to make sure you didn't miss out on this insight from our beloved dr4v over on Reddit. We're frequently (and rightfully) asked what causes the length of time between updates and he touches on that a little:

Quote

yep, testing app is exactly what we are doing. Also yep, we'd love to do smaller cycles, but a lot of the features we are adding at present are just big systems, no way around that. Tanks, UI etc, and even more so if you want things to tie together, Talil and tanks together for example.

However yes there are smaller features that we could release ad-hoc, things like the ammobags, suppression perhaps. The limitation there so far has been building, testing, the annoying steam needing 30gb free to update issue, and making sure it fits in the game balance. We are planning an engine upgrade in the not too distant future, which im told fixes the pak file issue (tho i am still sceptical) and the other issues we can hopefully address as we continue. We also have a great build engineer now, which means we can do things like a testing app, and a good build system really is the foundation of a decent software company. Something i think gets missed a lot in 'importance' priority. Its not cool, but the difference between a good one and a bad one is immense.

We keep saying we want to do smaller faster patches, and then find that for whatever reasons we cant, or it doesnt make sense. Lets see what we can do for the next one. We know what we want to go in it, and it should be decently fast, but haha, we've said that before as well.....

Share this post

Link to post

Share on other sites

Fortnite has caused a lot of significant gains in the engine in general, so there's a lot of features that should be improved, as well as new things, and old tech removed. I don't have the technical expertise to relate how it might impact Squad's codebase in full though.