The Star Citizen Thread v5

Status
Thread Closed: Not open for further replies.

Maruun

Maruun
At this point i feel more and more like Star Citizen is a stage for their ship sales not a game ment to be played...Starship Commercials....
 

DLewth

DLewth
Toumal said:
The models are top notch. You may not like the style or the lack of practicality, but they look really nice and they put a lot of effort into those.
Click to expand...

Say what you like about SC (And we do. Constantly) but they've always been good at artwork.

Edit: Kind of reminds me of Rimmer's revision timetables in the Red Dwarf books. Never makes any actual progress but looks stunning.
 
Last edited:

Rolan

Rolan
Image004.png

From here
Welcome,

Below you will find the Current Milestone Schedule. These are the very same schedules we update daily and are circulated 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, but 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.

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.

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.
Click to expand...
https://robertsspaceindustries.com/schedule-report
FINALLY!
 
Last edited:

hairychris

hairychris
Community art?

Tony Hart did it better, and with less crap dance music as a background.

EDIT: I own a v1 Access Virus synth from the very early 00s (basically a rave in a box, if you can work out how the hell to program it) and it reminds me of me. But drunker.
 
Last edited:
Status
Thread Closed: Not open for further replies.
Back
Top Bottom