That sounds a bit shallow. I thought the game was intended to provide a broader experience than what this suggests.
It's more of a trading / market thing, having stakes on industry nodes and such and just generate missions to players and all to transport, or sell to you, should be a decent take on a industry crafting play without that picky personal crafting.
Very little changes. We're now halfway through 3rd quarter, and so far none of the Q3 gameplay features are in development. Only 1 out of 6 core tech items and 1 out of 3 character items are in development.
Very little changes. We're now halfway through 3rd quarter, and so far none of the Q3 gameplay features are in development. Only 1 out of 6 core tech items and 1 out of 3 character items are in development.
Very little changes. We're now halfway through 3rd quarter, and so far none of the Q3 gameplay features are in development. Only 1 out of 6 core tech items and 1 out of 3 character items are in development.
Probably busy working on a fragile demo for Citizencon rather than the actual game.
Very little changes. We're now halfway through 3rd quarter, and so far none of the Q3 gameplay features are in development. Only 1 out of 6 core tech items and 1 out of 3 character items are in development.
Probably busy working on a fragile demo for Citizencon rather than the actual game.
I think what has happened - and I got this impression at the end of Q1 - is that the SQ42 schedule got a re-look after they were a quarter or so into it. If you recall back then SQ42 progress was "behind" even though they had only recently released the schedule.
The rsources they have of course are shared. Doesn't matter whether someone works on a SQ ship design or a SQ42 design etc. And following the initial review I believe that more resource than initially planned was put on SQ42.
As I say this was an impression back then but the SQ42 recovered and now seems to be progressing "reasonably well". The SC schedule though does seem to have "lost momentum". And given that they were "pretty good" for several quarters its hard to believe they suddenly "forgot how to schedule".
It would make sense in the grand scheme of things as well. SC can release with a "set of features" which can be added to after the initial launch - happens all the time with mmos as we know. Not an option though for SQ42.
Now maybe they will suddenly finish all the work scheduled for Q3 - including all the stuff that hasn't started yet. And if that happens I think we will all be surprised! It didn't happen with Q2's release which ended up being 6 or 7 weeks late.
Very little changes. We're now halfway through 3rd quarter, and so far none of the Q3 gameplay features are in development. Only 1 out of 6 core tech items and 1 out of 3 character items are in development.
Probably busy working on a fragile demo for Citizencon rather than the actual game.
I think what has happened - and I got this impression at the end of Q1 - is that the SQ42 schedule got a re-look after they were a quarter or so into it. If you recall back then SQ42 progress was "behind" even though they had only recently released the schedule.
The rsources they have of course are shared. Doesn't matter whether someone works on a SQ ship design or a SQ42 design etc. And following the initial review I believe that more resource than initially planned was put on SQ42.
As I say this was an impression back then but the SQ42 recovered and now seems to be progressing "reasonably well". The SC schedule though does seem to have "lost momentum". And given that they were "pretty good" for several quarters its hard to believe they suddenly "forgot how to schedule".
It would make sense in the grand scheme of things as well. SC can release with a "set of features" which can be added to after the initial launch - happens all the time with mmos as we know. Not an option though for SQ42.
Now maybe they will suddenly finish all the work scheduled for Q3 - including all the stuff that hasn't started yet. And if that happens I think we will all be surprised! It didn't happen with Q2's release which ended up being 6 or 7 weeks late.
My guess is that they're on schedule and plan to release patch "Q3" in November so that they can hype it during Citizencon. They announced last year that they're going to have a yearly Citizencon patch, and with the way they're progressing "Q3" would be that patch.
Very little changes. We're now halfway through 3rd quarter, and so far none of the Q3 gameplay features are in development. Only 1 out of 6 core tech items and 1 out of 3 character items are in development.
Probably busy working on a fragile demo for Citizencon rather than the actual game.
The last 2 Citizencon's showcased the ArcCorp and Hurston planets along with the respective cities and missions and that content has been playable for some time now.
So yeah what's showcased in Citizencon is work in the actual game
Very little changes. We're now halfway through 3rd quarter, and so far none of the Q3 gameplay features are in development. Only 1 out of 6 core tech items and 1 out of 3 character items are in development.
Probably busy working on a fragile demo for Citizencon rather than the actual game.
I think what has happened - and I got this impression at the end of Q1 - is that the SQ42 schedule got a re-look after they were a quarter or so into it. If you recall back then SQ42 progress was "behind" even though they had only recently released the schedule.
The rsources they have of course are shared. Doesn't matter whether someone works on a SQ ship design or a SQ42 design etc. And following the initial review I believe that more resource than initially planned was put on SQ42.
As I say this was an impression back then but the SQ42 recovered and now seems to be progressing "reasonably well". The SC schedule though does seem to have "lost momentum". And given that they were "pretty good" for several quarters its hard to believe they suddenly "forgot how to schedule".
It would make sense in the grand scheme of things as well. SC can release with a "set of features" which can be added to after the initial launch - happens all the time with mmos as we know. Not an option though for SQ42.
Now maybe they will suddenly finish all the work scheduled for Q3 - including all the stuff that hasn't started yet. And if that happens I think we will all be surprised! It didn't happen with Q2's release which ended up being 6 or 7 weeks late.
My guess is that they're on schedule and plan to release patch "Q3" in November so that they can hype it during Citizencon. They announced last year that they're going to have a yearly Citizencon patch, and with the way they're progressing "Q3" would be that patch.
If this transpires they will (nominally) have done a quarter's activity in a quarter. 6 or 7 weeks late for the Q2 drop, 6 or 7 weeks late for the Q3 drop. Which would be "OK".
Very little changes. We're now halfway through 3rd quarter, and so far none of the Q3 gameplay features are in development. Only 1 out of 6 core tech items and 1 out of 3 character items are in development.
Probably busy working on a fragile demo for Citizencon rather than the actual game.
One of my Origin-Ex friends said that convention demos usually set them back a month or so. In addition to whatever other issues there were.
As for the Star Citizen schedule, they have monetized feature creep. With crowd funding as their motif, they have to present new stuff to keep the well from running dry. Everything they present publicly is also advertising and marketing. Nature of the beast.
Of course, their need for real investors shows that things haven't meshed up.
But then no schedule survives contact with reality.
If you are holding out for the perfect game, the only game you play will be the waiting one.
The changed Citizencon format has focused on the demo & highlight of the current developed patch, not on isolated created features for showcase of tech being worked on like happened years ago.
The conference got pushed to late November so the plan to sync the Q3 patch with Citcon will force a very late release if they do it, then 1 month later the Q4 has to happen.
So the roadmap, if they focus on Citcon, will update to push 3.8 stuff back and sync 3.7 with citcon to give extra time, or maybe get the Microtech planet with its landing zone and mission giver on 3.7 that are the more active developing features of 3.8.
The setup with the teams to deliver their work quarterly isn't working as well as wanted and is causing issues by work having to be released by devs who wanted to spend more time on it.
Due to this, they are going to stagger teams to give the developers 6 months to finish their work instead of 3, with this the quarterly releases should still happen intending to add viability for more stable patches.
In recent times there is quite more work going on in parallel that will become the standard with staggered development with teams on each area working for features on different patches.
The roadmap was put under maintenance and will be suffering a major update to reflect this on SC and SQ42, what is said for SQ42 already is that its BETA estimate is pushed by 3 months. With the team resources split the nearest patch that is 3.7 will be a smaller patch.
The setup with the teams to deliver their work quarterly isn't working as well as wanted and is causing issues by work having to be released by devs who wanted to spend more time on it.
Due to this, they are going to stagger teams to give the developers 6 months to finish their work instead of 3, with this the quarterly releases should still happen intending to add viability for more stable patches.
In recent times there is quite more work going on in parallel that will become the standard with staggered development with teams on each area working for features on different patches.
The roadmap was put under maintenance and will be suffering a major update to reflect this on SC and SQ42, what is said for SQ42 already is that its BETA estimate is pushed by 3 months. With the team resources split the nearest patch that is 3.7 will be a smaller patch.
So backers can look forward to even more anemic patches as devs realize that working on a patch before the previous patch is even finished is a horrible idea since you have no idea what bugs will be introduced and break the game with the current patch.
So backers can look forward to even more anemic patches as devs realize that working on a patch before the previous patch is even finished is a horrible idea since you have no idea what bugs will be introduced and break the game with the current patch.
In a way, it is more challenging to merge into the main branch, but in the other having to do the merge with the feature in unpolished and buggy state is more likely having been introducing more bugs due to the lack of polish in order to achieve the quarter milestone.
There is no perfect solution with a game like this, there is always a lot of work being done by teams being merged into the main branch of the codebase and their branches obviously not in sync with those changes so the high likeness their work will break on implementation.
But it has to be like that, if everyone iterated on the main branch so it's all in sync, it would be impossible because just takes a change that breaks the branch and everyone else's work stalls.
In this latest roadmap update they removed or delayed from 3.7 all previously planned locations, AI improvements, and gameplay, as well as all core tech stuff except performance optimization.
They added some location, AI and gameplay stuff that wasn't in their roadmap before to replace that. A lot of the added stuff is already at 100% completion.
They tried shorter update cycles then longer update cycles then shorter update cycles again, now longer update cycles again. How about just putting fewer updates in the patches from the start instead of pushing features back all the time.
"We all do the best we can based on life experience, point of view, and our ability to believe in ourselves." - Naropa "We don't see things as they are, we see them as we are." SR Covey
But it has to be like that, if everyone iterated on the main branch so it's all in sync, it would be impossible because just takes a change that breaks the branch and everyone else's work stalls.
That's when a studio would roll back the version and pull the broken feature for later implementation, push the new version sans broken feature, and spend time on that feature while other's continue to roll forward.
If it was a core feature, then of course other things would stall since developing content reliant on a broken/incomplete feature is just going to cause more problems down the line.
But it has to be like that, if everyone iterated on the main branch so it's all in sync, it would be impossible because just takes a change that breaks the branch and everyone else's work stalls.
That's when a studio would roll back the version and pull the broken feature for later implementation, push the new version sans broken feature, and spend time on that feature while other's continue to roll forward.
With hundreds of developers iterating on the codebase that would be insanity, it would be a large number of builds having to be downloaded per day across the several studios per time that would happen, or a merge happens. It still stalls everyone's work to have them iterating on sync on the same codebase.
The devs have to have isolated environments because many times what they do is broken purely because it's unfinished, it won't work if that is being done on the same place the others are iterating on.
That speaks to bloat in the company more than anything else. Again, gotta put ones ducks in a row.
Instead SC spins its wheels and has to iterate and then reiterate every time a minor feature is merged.
I don't know about that, when on rockstar an admin of mine works on QA the large undertakings came from the merges of work from the teams into the development branch, they are working in an isolated e environment only them iterate on and then efforts go towards stabilizing the implementation as the code gets merged.
Assets, content and such is one thing but relevant amounts of code is another story. And technology then wouldn't be negotiable, when stuff as the streaming tech OCS and now the SSOCS they can't have the codebase work as they actively are messing with its core and everything that it ties to, the merges of tech that takes longer periods to develop once ready to implement are deff the hardest thing to get sorted.
Comments
Very little changes. We're now halfway through 3rd quarter, and so far none of the Q3 gameplay features are in development. Only 1 out of 6 core tech items and 1 out of 3 character items are in development.
I think what has happened - and I got this impression at the end of Q1 - is that the SQ42 schedule got a re-look after they were a quarter or so into it. If you recall back then SQ42 progress was "behind" even though they had only recently released the schedule.
The rsources they have of course are shared. Doesn't matter whether someone works on a SQ ship design or a SQ42 design etc. And following the initial review I believe that more resource than initially planned was put on SQ42.
As I say this was an impression back then but the SQ42 recovered and now seems to be progressing "reasonably well". The SC schedule though does seem to have "lost momentum". And given that they were "pretty good" for several quarters its hard to believe they suddenly "forgot how to schedule".
It would make sense in the grand scheme of things as well. SC can release with a "set of features" which can be added to after the initial launch - happens all the time with mmos as we know. Not an option though for SQ42.
Now maybe they will suddenly finish all the work scheduled for Q3 - including all the stuff that hasn't started yet. And if that happens I think we will all be surprised! It didn't happen with Q2's release which ended up being 6 or 7 weeks late.
As for the Star Citizen schedule, they have monetized feature creep. With crowd funding as their motif, they have to present new stuff to keep the well from running dry. Everything they present publicly is also advertising and marketing. Nature of the beast.
Of course, their need for real investors shows that things haven't meshed up.
But then no schedule survives contact with reality.
If you are holding out for the perfect game, the only game you play will be the waiting one.
The conference got pushed to late November so the plan to sync the Q3 patch with Citcon will force a very late release if they do it, then 1 month later the Q4 has to happen.
So the roadmap, if they focus on Citcon, will update to push 3.8 stuff back and sync 3.7 with citcon to give extra time, or maybe get the Microtech planet with its landing zone and mission giver on 3.7 that are the more active developing features of 3.8.
The 3.6.2 with the added 890J and to add Ship Rentals is still on the PTU.
https://robertsspaceindustries.com/spectrum/community/SC/forum/1/thread/staggered-development-faq-1
The setup with the teams to deliver their work quarterly isn't working as well as wanted and is causing issues by work having to be released by devs who wanted to spend more time on it.
Due to this, they are going to stagger teams to give the developers 6 months to finish their work instead of 3, with this the quarterly releases should still happen intending to add viability for more stable patches.
In recent times there is quite more work going on in parallel that will become the standard with staggered development with teams on each area working for features on different patches.
The roadmap was put under maintenance and will be suffering a major update to reflect this on SC and SQ42, what is said for SQ42 already is that its BETA estimate is pushed by 3 months. With the team resources split the nearest patch that is 3.7 will be a smaller patch.
3.7 features:
3.7 should be releasing with Citizencon, so in a month.
There is no perfect solution with a game like this, there is always a lot of work being done by teams being merged into the main branch of the codebase and their branches obviously not in sync with those changes so the high likeness their work will break on implementation.
But it has to be like that, if everyone iterated on the main branch so it's all in sync, it would be impossible because just takes a change that breaks the branch and everyone else's work stalls.
They added some location, AI and gameplay stuff that wasn't in their roadmap before to replace that. A lot of the added stuff is already at 100% completion.
"We all do the best we can based on life experience, point of view, and our ability to believe in ourselves." - Naropa "We don't see things as they are, we see them as we are." SR Covey
If it was a core feature, then of course other things would stall since developing content reliant on a broken/incomplete feature is just going to cause more problems down the line.
Gotta put one's ducks in a row.
The devs have to have isolated environments because many times what they do is broken purely because it's unfinished, it won't work if that is being done on the same place the others are iterating on.
Instead SC spins its wheels and has to iterate and then reiterate every time a minor feature is merged.
Assets, content and such is one thing but relevant amounts of code is another story. And technology then wouldn't be negotiable, when stuff as the streaming tech OCS and now the SSOCS they can't have the codebase work as they actively are messing with its core and everything that it ties to, the merges of tech that takes longer periods to develop once ready to implement are deff the hardest thing to get sorted.