Quantcast

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

ATV - Austin Studio Monthly Update

MaxBaconMaxBacon Member EpicPosts: 7,275
edited January 2018 in Star Citizen
To break from the fulltime naysay SC in every possible way a bit:


ATVs are coming back to the normal format, not much in terms of update because of the break and all. More of a behind the scenes and a discussion on the quarterly schedule for this year that was superficially described recently.

The next update for Star Citizen (3.1) is scheduled for late March, the highlight is a major polish, optimization and bug-fixing patch to improve on what's already there. 

"...
focus on optimizing the server and client... 3.1 is about enhancing performance and polishing the gameplay systems and UI, including ships, system traversal, a large balance pass of our economy, and improving AI for spaceflight and combat."
WalkinGlenn

Comments

  • MaxBaconMaxBacon Member EpicPosts: 7,275
    edited January 2018
    Overall on their platform relating to 3.0 in terms of network stats footage from this ATV:



    Shows 33k peak of ships spawned in total (it's divided by multiple say "clusters" on EU/US/AU).

    The Australian ship distribution graph is different from the others, hmm
  • MaxBaconMaxBacon Member EpicPosts: 7,275
    TL:DR (3.0 push & quarterly updates for this year):
    • CIG debated cutting critical foundational features from 3.0 but didn't to ensure they could deliver all of the 3.x series on a quarterly basis in 2018

    • Now that most of the uncertainty, R&D, and challenges associated with integrating new tech are out of the way the 3.x iterations will be more predictable

    • Switching to date-based from feature-based is going to dramatically change everything next year: no more holding back a version for a couple of features

    • 3.0 was always going to be an anomaly and letting a critical piece of infrastructure slip might have prevented the release of an entire branch

    • Challenges: dynamic pricing and interdiction were being worked on right up to the end (and even into the holidays)

    • 3.0 integrated a lot of new technology, new technology that hadn't been finalised, and performance could only be assessed once it was all glued together

    • 3.1 primary focus is performance: identifying/addressing the biggest problems in terms of server & client frame rates

    • Single biggest feature in 3.0 is the procedural planetary tech: it dramatically changes the entire game

    • Now turning their attention to mining in a "significant fashion" as they are targeting 3.2 for the initial iteration

    • CIG were able to make changes during the holidays without a patch because those issues were controlled via the backend services

    • Probability volumes are areas of space in which events can happen to the player based upon inputs from the economy (i.e. flying through a probability volume that includes a pirate haven will likely lead to a pirate encounter).

    • Probability volumes hook up to the economy to provide a dynamic experience.

    • Probability volumes act as optimization as they allow for many different types of encounters without having the explicitly hard code them.

    • The back end simulations are planned to be hooked up towards the end of this year.

    • The team did a lot of work on the back-end for publishing 3.0, and it was a huge come-together between the publishing side, the QA side, the network side, everyone.

    • The delta patcher helped hugely

    • The team also have the ability to issue hotfixes without kicking all players off the servers; they can issue a hotfix, and then ‘spin down’ servers gradually, only resetting them when there are 0 remaining players.

  • rpmcmurphyrpmcmurphy Member EpicPosts: 3,497
    It honestly makes me wonder what happened between mid 2016 to end 2017. Did they just hit problem after problem and only just manage to get things functioning?

    It's a shame that mining (and the intital implementation only) has been pushed back another 3 months, it would have been nice to get that before 3.1 or with 3.1 because keeping people engaged for 6 months on what we have now is going to be a tall order, it's this sort of spacing that will end up burning a lot of people out.
    Orinori
  • MaxBaconMaxBacon Member EpicPosts: 7,275
    It honestly makes me wonder what happened between mid 2016 to end 2017. Did they just hit problem after problem and only just manage to get things functioning?

    It's a shame that mining (and the intital implementation only) has been pushed back another 3 months, it would have been nice to get that before 3.1 or with 3.1 because keeping people engaged for 6 months on what we have now is going to be a tall order, it's this sort of spacing that will end up burning a lot of people out.
    I do think the same. With 3.0 they refactored and implemented so much new backend and tech stuff that it must have been a nightmare to get it all functioning together, issue after issue forcing push backs.

    Mining not sure if they want to push a more or less significant version of it, at first in 3.1 it was just the planetary mining with the prospector, but if the big mining ships are ready by then, perhaps asteroid mining will be targetted for its first release.
Sign In or Register to comment.