Our schedule for the next Star Citizen Alpha releases, up to date.
Our schedule for the next Star Citizen Alpha releases, up to date.
Welcome,
Welcome,
Below you will find the latest roadmap for the development of the Star Citizen Persistent Universe. While the bulk of this schedule outlines our tasks and estimates that you can expect to find in the upcoming 3.0.0 patch (as well as some of the tasks that we’ve already completed) , we are also including projections for the remainder of the year so you can have some visibility into the upcoming Persistent Universe features and content. These are the very same schedules we update daily and circulate internally on our intra-studio hand-offs with a few exceptions: the individual developer names assigned to the tasks will be omitted (for obvious reasons), we’ll remove the JIRA details, and we’ll modify the technical wording to make it readable for a wider audience. Also note, this schedule does not represent everything CIG is working on, but more the functionality and content we feel comfortable committing to at this time. Outside of the work on Squadron 42, we have a few research projects that, once validated, we would move into production and add to this schedule. Otherwise, when something changes, slips or is completed, you will know.
Below you will find the latest roadmap for the development of the Star Citizen Persistent Universe. While the bulk of this schedule outlines our tasks and estimates that you can expect to find in the upcoming 3.0.0 patch (as well as some of the tasks that we’ve already completed) , we are also including projections for the remainder of the year so you can have some visibility into the upcoming Persistent Universe features and content. These are the very same schedules we update daily and circulate internally on our intra-studio hand-offs with a few exceptions: the individual developer names assigned to the tasks will be omitted (for obvious reasons), we’ll remove the JIRA details, and we’ll modify the technical wording to make it readable for a wider audience. Also note, this schedule does not represent everything CIG is working on, but more the functionality and content we feel comfortable committing to at this time. Outside of the work on Squadron 42, we have a few research projects that, once validated, we would move into production and add to this schedule. Otherwise, when something changes, slips or is completed, you will know.
What you are seeing here is the result of our scheduling and planning process. We have a high level feature and content set that we want to achieve for Star Citizen and Squadron 42. The first step is to break these features into higher level tasks with which we populate Microsoft Project, JIRA and Shotgun (the three tools we use for project scheduling and tasking). Then, as we approach a task, Production works with the relevant developer(s) to make sure the task is broken up with enough detail to allow completion. Sometimes this means adjusting the initial task estimate, as things tend to come into a clearer focus when coming up on a task, but it almost always means breaking down the big task into a bunch of smaller tasks that have their own individual sub tasks that possibly are distributed to multiple developers.
What you are seeing here is the result of our scheduling and planning process. We have a high level feature and content set that we want to achieve for Star Citizen and Squadron 42. The first step is to break these features into higher level tasks with which we populate Microsoft Project, JIRA and Shotgun (the three tools we use for project scheduling and tasking). Then, as we approach a task, Production works with the relevant developer(s) to make sure the task is broken up with enough detail to allow completion. Sometimes this means adjusting the initial task estimate, as things tend to come into a clearer focus when coming up on a task, but it almost always means breaking down the big task into a bunch of smaller tasks that have their own individual sub tasks that possibly are distributed to multiple developers.
Both tasks and sub-tasks get created in JIRA, linked under an Epic (which is a high level task or feature) and are then pulled into Microsoft Project to manage with granular detail providing us global visibility through Gantt charts and visual timelines. No developer works on a task unless it has been created in JIRA, prioritized and assigned by a lead or a member of the Production Team.
Both tasks and sub-tasks get created in JIRA, linked under an Epic (which is a high level task or feature) and are then pulled into Microsoft Project to manage with granular detail providing us global visibility through Gantt charts and visual timelines. No developer works on a task unless it has been created in JIRA, prioritized and assigned by a lead or a member of the Production Team.
Then as the developers work on the tasks, Production will adjust the schedule and JIRA tickets to reflect the work being done.
Then as the developers work on the tasks, Production will adjust the schedule and JIRA tickets to reflect the work being done.
In the schedule below, you will first find a master schedule that covers the broad departments/disciplines that are being developed. Each department will then have its own dedicated sub-schedule, briefly explaining the various features that are being developed and their current status.
In the schedule below, you will first find a master schedule that covers the broad departments/disciplines that are being developed. Each department will then have its own dedicated sub-schedule, briefly explaining the various features that are being developed and their current status.
CAVEATS
CAVEATS
But also, we would like to establish some ground rules before proceeding:
But also, we would like to establish some ground rules before proceeding:
I.Quality will always be our number one goal. We set out on this journey by looking at the gaming landscape and asking: can we do better? We continue to ask that question about everything we do. As a result, we will ALWAYS extend timelines or re-do features and content if we do not feel they are up to our standards. The freedom to fight for a new level of quality in game development is what crowd funding has allowed us, and we will continue to fight to make sure Star Citizen is the best possible game it can be.
I.Quality will always be our number one goal. We set out on this journey by looking at the gaming landscape and asking: can we do better? We continue to ask that question about everything we do. As a result, we will ALWAYS extend timelines or re-do features and content if we do not feel they are up to our standards. The freedom to fight for a new level of quality in game development is what crowd funding has allowed us, and we will continue to fight to make sure Star Citizen is the best possible game it can be.
II.The estimates we provide are just that: estimates. They are based on our knowledge and experience, but there are many aspects of game development that are impossible to predict because they literally cover uncharted territory. You will see the same estimates we use in our internal planning, but it is important to understand that in many cases (especially with groundbreaking engineering tasks) these estimates are often subject to change due to unforeseen complexity in implementing features.
II.The estimates we provide are just that: estimates. They are based on our knowledge and experience, but there are many aspects of game development that are impossible to predict because they literally cover uncharted territory. You will see the same estimates we use in our internal planning, but it is important to understand that in many cases (especially with groundbreaking engineering tasks) these estimates are often subject to change due to unforeseen complexity in implementing features.
III.The time expected for bug fixing and polishing is also very hard to estimate, increasingly so in online and multiplayer situations. The complexity and the difficulty in testing at a large scale make it harder to reproduce and isolate bugs in order to fix them. We base our estimates, again, on our experience, but we also know that it’s possible for a single bug to cause a delay of days or weeks when a hundred others might be fixed instantly.
III.The time expected for bug fixing and polishing is also very hard to estimate, increasingly so in online and multiplayer situations. The complexity and the difficulty in testing at a large scale make it harder to reproduce and isolate bugs in order to fix them. We base our estimates, again, on our experience, but we also know that it’s possible for a single bug to cause a delay of days or weeks when a hundred others might be fixed instantly.
IV.Internal schedules, the ones you will now be privy to, tend to have aggressive dates to help the team focus and scope their tasks, especially in the case of tech development. Every team, even a team blessed with the kind of support and freedom you have allowed us, needs target dates in order to focus and deliver their work.
IV.Internal schedules, the ones you will now be privy to, tend to have aggressive dates to help the team focus and scope their tasks, especially in the case of tech development. Every team, even a team blessed with the kind of support and freedom you have allowed us, needs target dates in order to focus and deliver their work.
V.This schedule doesn’t cover everything being worked on across Cloud Imperium Games, but is meant to highlight our aims for the remainder of the year on the Persistent Universe.
V.This schedule doesn’t cover everything being worked on across Cloud Imperium Games, but is meant to highlight our aims for the remainder of the year on the Persistent Universe.
VI.This schedule doesn’t include every audio, vfx, tech art, etc. task. Those are detailed in our departmental sub-schedules.
VI.This schedule doesn’t include every audio, vfx, tech art, etc. task. Those are detailed in our departmental sub-schedules.
VIIAlthough technology is shared between the two games, this does not reflect the Squadron 42 schedule. That will be released at a future date.
VIIAlthough technology is shared between the two games, this does not reflect the Squadron 42 schedule. That will be released at a future date.
VIII.These aim dates are determined based on our current staff. Additional hiring will potentially allow us to bring in some dates below.
VIII.These aim dates are determined based on our current staff. Additional hiring will potentially allow us to bring in some dates below.
WELCOME TO THE PROCESS
WELCOME TO THE PROCESS
The community has always been integral to Star Citizen, so we will be updating this page weekly to keep you informed about our development. We hope that this page will not only help explain our latest status, but also provide some explanations in the event that updates are delayed.
The community has always been integral to Star Citizen, so we will be updating this page weekly to keep you informed about our development. We hope that this page will not only help explain our latest status, but also provide some explanations in the event that updates are delayed.
Last update : June 2nd, 2017
Last update : June 9th, 2017
3.0.0 OVERVIEW
3.0.0 OVERVIEW
The following lists and charts show our progress towards releasing 3.0.0, with all remaining major tasks listed. 3.0.0 marks the next major step forward in realizing the vision of the Star Citizen Persistent Universe. As you’ll see from the sections below, there’s a lot of new content and underlying tech being worked on for this release which will enhance the experience of our players.
The following lists and charts show our progress towards releasing 3.0.0, with all remaining major tasks listed. 3.0.0 marks the next major step forward in realizing the vision of the Star Citizen Persistent Universe. As you’ll see from the sections below, there’s a lot of new content and underlying tech being worked on for this release which will enhance the experience of our players.
Tasks are either feature complete, or have an ETA for completion. It’s important to remember that some tasks may require further QA, bug-fixing and iteration. Tasks that delay beyond our target dates might cause the release of 3.0.0 to be delayed, or might be excluded from 3.0.0 if appropriate to maintain the release date target. 3.0.0 work is separated into Subsections: Persistent Universe Content, FPS / Space Gameplay, Engineering, UI, AI, Graphics, Backend, Network, and Ships & Weapons.
Tasks are either feature complete, or have an ETA for completion. It’s important to remember that some tasks may require further QA, bug-fixing and iteration. Tasks that delay beyond our target dates might cause the release of 3.0.0 to be delayed, or might be excluded from 3.0.0 if appropriate to maintain the release date target. 3.0.0 work is separated into Subsections: Persistent Universe Content, FPS / Space Gameplay, Engineering, UI, AI, Graphics, Backend, Network, and Ships & Weapons.
The 3.0.0 Procedural Planet update marks a major advance in the Star Citizen Persistent Universe. As you’ll see below, the new content and underlying tech in this release which will greatly enhance player experience.
The 3.0.0 Procedural Planet update marks a major advance in the Star Citizen Persistent Universe. As you will see from the various subsections below, there have been quite a few alterations to feature dates to clarify some of the TBD’s left over from the previous week’s update. Discipline leads took a step back this week to fully evaluate the remaining work required to close out 3.0 development to identify further work and blocking issues. Also, after this review, we came to realize that some additional features might be helpful to add to 3.0 to further improve the overall experience, such as a first version of our Hint system. As a result of this, we have adjusted our Live date in order to preserve sufficient testing time with the Evocati and on the PTU, which is invaluable to us in order to properly stress our systems and provide a better experience.
PLANETARY UPDATE
PLANETARY UPDATE
YELA
YELA
Yela is the most frigid of the Crusader moons. Those bold (or careless) enough to step outside without a spacesuit will be killed instantly by its freezing temperatures. If the cold doesn’t kill you, than any of the treacherous crevasses that crisscross the planet might. Cyrovolcanos have been known to erupt unexpectedly from such crevasses, so be wary when flying at low altitudes. Despite all its danger, there is much beauty to be found on Yela, like the underwater caves hidden beneath the moon’s crust.
Yela is the most frigid of the Crusader moons. Those bold (or careless) enough to step outside without a spacesuit will be killed instantly by its freezing temperatures. If the cold doesn’t kill you, than any of the treacherous crevasses that crisscross the planet might. Cyrovolcanos have been known to erupt unexpectedly from such crevasses, so be wary when flying at low altitudes. Despite all its danger, there is much beauty to be found on Yela, like the underwater caves hidden beneath the moon’s crust.
CELLIN
CELLIN
Burning with volcanic activity, Cellin is the counter to her icy sister. Although the volcanoes have been dormant for hundreds of years, the surface is dotted with thermal geysers that erupt without notice. The largest of such geysers can destroy heavy vehicles. Highly corrosive clouds of gas are regularly released from the moon’s surface, creating low visibility and damaging anything caught outside.
Burning with volcanic activity, Cellin is the counter to her icy sister. Although the volcanoes have been dormant for hundreds of years, the surface is dotted with thermal geysers that erupt without notice. The largest of such geysers can destroy heavy vehicles. Highly corrosive clouds of gas are regularly released from the moon’s surface, creating low visibility and damaging anything caught outside.
DAYMAR
DAYMAR
Daymar’s surface is like a harmonic blend of Yela and Cellin. It’s mountainous surface is reminiscent of Cellin’s volcanoes, while its craters share a warm likeness to Yela’s frozen crevessases. Known for its dense atmosphere, thick fog and a loose dirt surface makes travel difficult. Lightning storms can help illuminate the fog, just don’t get struck by their flash.
Daymar’s surface is like a harmonic blend of Yela and Cellin. It’s mountainous surface is reminiscent of Cellin’s volcanoes, while its craters share a warm likeness to Yela’s frozen crevessases. Known for its dense atmosphere, thick fog and a loose dirt surface makes travel difficult. Lightning storms can help illuminate the fog, just don’t get struck by their flash.
REMAINING AIMS FOR 3.0.0 RELEASE
REMAINING AIMS FOR 3.0.0 RELEASE
Click here to view Schedule
PERSISTENT UNIVERSE CONTENT
PERSISTENT UNIVERSE CONTENT
Click here to view Schedule
MOONS
MOONS
We are adding 3 new moons to the Crusader system; Yela, Cellin, and Daymar.
We are adding 3 new moons to the Crusader system; Yela, Cellin, and Daymar.
Feature Complete
Feature Complete
SURFACE OUTPOSTS
SURFACE OUTPOSTS
The new moons will also have outposts on their surface to explore.
The new moons will also have outposts on their surface to explore.
Feature Complete
Feature Complete
SURFACE OUTPOSTS LIGHTING
SURFACE OUTPOSTS LIGHTING
We have broken out the lighting tasks for the surface outposts into it’s own feature
We have broken out the lighting tasks for the surface outposts into it’s own feature
ETA is June 26th
ETA is June 26th
MISSION GIVERS
MISSION GIVERS
We’re introducing Miles Eckhart (first seen in the Gamescom video) and Ruto to provide missions to players.
We’re introducing Miles Eckhart (first seen in the Gamescom video) and Ruto to provide missions to players.
Date adjusted to continue to account for additional newly identified requirements
Since this mechanic is setup with new technology that is still being developed, this delay is to ensure that our high quality bar is maintained and that our designers are able to properly implement the mission givers.
ETA is 9th June (was June 2nd)
ETA is 30th June (was 9th June)
DERELICT SHIPS
DERELICT SHIPS
Derelict ships will be added to the system for extra points of interest and exploration.
Derelict ships will be added to the system for extra points of interest and exploration.
Art for the derelict ships is now complete, however audio will require more time to complete their work
To improve the immersive experience for players in 3.0.0, some additional art tasks were highlighted during a review to accommodate greater utilization of the derelicts’ mission flow
ETA is 9th June (was 26th May)
ETA is 16th June (was 9th June)
DEBRIS FIELDS
DEBRIS FIELDS
Feature Complete
Feature Complete
DELAMAR / LEVSKI (STRETCH GOAL)
DELAMAR / LEVSKI (STRETCH GOAL)
We are adding the planet Delamar and the landing zone, Levski
We are adding the planet Delamar and the landing zone, Levski
Following meetings on what we could aim to achieve for 3.0.0, we have moved our date out to accommodate this goal.
Following meetings on what we could aim to achieve for 3.0.0, we have moved our date out to accommodate this goal.
ETA is 30th June (was 1st June)
ETA is 30th June (was 1st June)
ALREADY COMPLETE IN THE 3.0.0 BRANCH:
ALREADY COMPLETE IN THE 3.0.0 BRANCH:
Modular Room System for procedural generation of planetary outposts
Modular Room System for procedural generation of planetary outposts
Official Outpost Spawning System ready for mission designers
Official Outpost Spawning System ready for mission designers
Integrated Outpost distribution to PlanetEd
Integrated Outpost distribution to PlanetEd
Single outpost Object Preset
Single outpost Object Preset
Cluster of Outposts
Cluster of Outposts
Crash site mission
Crash site mission
Interface to hand place modules and save to Layer
Interface to hand place modules and save to Layer
Interface to teleport the camera to the closest outpost
Interface to teleport the camera to the closest outpost