Loiosh posted:

In a basic way, they are all the new gestures that were added into the social module. The primary movement changes are going into the AC 2.0 / (future) FPS module. They build their product quite similar to ours, with a branch release and a trunk.

So after a branch whatever updates are easily rolled in are added, but the primary development has moved onto the trunk build and the next branch. Branches in order: Hangar Module, AC Module, Racing Module, Social Module, AC 2.0, FPS Module.

If you have a rapidly evolving engine, your backports (upgrades from later trunk builds to earlier branches) become quickly infrequent because you've moved on. For example, they were able to add PBR and the updated Deferred Renderer as a backport to the early Hangar Module, but they could not add the new movement (flight engine) in, and had to release a new build.

They've actually switched to a management system, called Excalibur, which is making the branch building easier. In our case (non-game company), our branches are a full release of the build once we've nailed down the required features for the branch. For a game like this, you actually do a unique build (Public build) that strips out a lot of assets. You cannot release the full trunk because it contains other components (like Foundry 42's SQ42 work) that are absolutely not ready for release.

All that is just to say, this is why their current build where they've like, replaced the movement system that was in Hangar/Social module, you're not seeing that update until they finish off the next branch and public build.