The Star Citizen Thread v5

Status
Thread Closed: Not open for further replies.
Happy Hour: February 10th
TLDR
  • Today's guests on Happy Hour were Lead Writer, Dave Haddock, and Twitch Streamer, BadNewsBaron
  • It's possible there are alien races that haven't been discovered, but if they said there were, then they wouldn't be undiscovered. Also primitive races are protected by the UEE's fairchance act in that one cannot tamper with the progress of a less technologically progressed race.
  • Mission givers will be diverse for 3.0 and beyond. Miles Eckhart won't be the only kind of mission giver out there, plus quest givers like Miles Eckhart may be "Good" or "Bad" depending on your reputation with them and what you're seeking so the "Good/Bad" guys won't be clearly defined always.
    • Missions where there's different perspectives on a same mission, IE good/bad is still being discussed on how they would implement it for certain mission.
  • The stereotype Xi'An's have about humans is that they're emotional and impulse. Xi'An's are the only non human race with defined stereotypes of the humans. The Banu love humans, but only because they love everyone that doesn't kill them.
  • When it comes to getting benefits from an alien race for example, they don't want players to have to know an entire language just to get a benefit, but open doors to them for opportunities that a player may not have gotten if they didn't know the culture. They want to prevent players from getting left out in the cold because of time invested, but still make it interesting for those who do invest the time to learn the cultures.
  • Creating large scale events ingame is something that will be looked at more in detail when it becomes relevant. They'd like to do big events, but also want to not waste dev time by creating an event that is a one time thing and then never used again, they want to be able to incorporate things in such a way that they can use them again, but be impactful when used a certain way.
Source: https://relay.sc/transcript/happy-hour-february-10th-2017-summary
 
It's The Agent over at SA time again...

hello
sq42 is totally folded into the PU (think gamemode like AC or SM)
sqlude "grossly mismanaged" and not due until 2018 or very late 2017
"A working 3.0 is years away."
features "are being cut like sliced bread" in order to hit this year
"Biggest failure? Communication."
more mocap for integral roles
"Current funding is completely insufficient. Backers need to reach deep if they want to see a beta release."
 
It's The Agent over at SA time again...

hello
sq42 is totally folded into the PU (think gamemode like AC or SM)
sqlude "grossly mismanaged" and not due until 2018 or very late 2017
"A working 3.0 is years away."
features "are being cut like sliced bread" in order to hit this year
"Biggest failure? Communication."
more mocap for integral roles
"Current funding is completely insufficient. Backers need to reach deep if they want to see a beta release."

It's a damn shame those rumours are unconfirmable, and their veracity will be unknown for few years after SC's release/CIG's collapse.
 
The PTU is now open to all backer with the new patch
Star Citizen v2.6.1b Patch Notes


Welcome to Star Citizen Alpha Patch 2.6.1b, PTU Testers! For the complete 2.6.0 PTU patch notes, you can find them here.
Your launcher should should show “2.6.1-503917” as the client version. It is strongly recommended that players delete their USER folder for the Test client after patching, particularly if you start encountering any odd character graphical issues or crash on loading. The USER folder can be found (in default installations) at C:\Program Files\Cloud Imperium Games\StarCitizen\Test.
Please review our current list of Patch 2.6.1 known issues, and take full advantage of our Issue Council area of the Community site to report any bugs you encounter, as well as contribute to other players submissions.
Important Issues:
For users encountering GPU Related crashes on NVIDIA cards, please ensure that you have performed a clean driver installation of driver version 378.49!
There is a crash when exiting to the main menu from ArcCorp or MMHC with the elevator UI open. Please make sure you’re not in the Elevator UI when you use the game menu!
The “Contacts List” button on the Universe page doesn’t work. Hangar flair item are not persisting through client restarts. Players may experience excessive desync when interacting with the Greycat Buggy.
Game Systems:

Star Marine

  • Fixed an issue with incorrect audio playing when a player earned Ace status.
  • Fixed an issue where the announcer would incorrectly state that it is the final round.
  • Fixed a number of dialog cues for the announcer when a match ends in a draw.
  • Fixed the background image for the in-game loadout editor.
  • Fixed a number of prop-collision issues in Echo Eleven.
Arena Commander

  • Fixed an issue where players in a private match would sometimes spawn inside of another players ship.
  • Fixed an issue where the pickups in Pirate Swarm would sometimes show the incorrect graphics.
  • Fixed an issue where countermeasures could be loaded as ammo on to certain ship weapons.
Ships:

  • Fixed an issue where the shields on the Super Hornet were not working.
  • Fixed the “Boost Fuel” gauge on the Super Hornet MFD so it correctly reflects the use of afterburner.
  • Fixed an issue with the Hornet series where the MFDs were not displaying the hologram for either ship status or target status.
  • Fixed an issue with the Hornet series where missile racks and cooler item ports were appearing in the wrong location.
  • Fixed an issue with the Herald where the control column was clipping into the pilots hand and arm.
  • Fixed an issue where the Vanguard weapons were not doing any damage.
  • The Mustang Alpha pilot seat can be accessed once more.
Technical:

  • Fixed a number of client crashes.
There is an Updated Schedule Report
261-High-Level-2.png
Here’s the current list of bugs and changes that are considered a priority to fix before releasing 2.6.1:


  • Networking
    • Client disconnects (code 7, 8, and 0)
    • Memory leaks and corruption
    • Desynchronization

  • Arena Commander
    • Missiles not inheriting velocity from ships
    • Missiles travelling erratically
Source: https://robertsspaceindustries.com/schedule-report

And the TLDR of the January Monthly Report may come later

For now here it is the URL - https://robertsspaceindustries.com/comm-link/transmission/15704-Monthly-Studio-Report
 
Last edited:
If features have to be cut in order to release this year - I wonder what they will be.

Of course nobody will notice them, as the BDSSE will blind everyone with its majestic glory and sheer perfection.

Buy an Idris!
 
Huh.
Serialized Variable – RISK

Originally moved out of the 2.6.0 goals due to the time required to complete this.
The Network Engineers are continuing to fix bugs with this, however once one is fixed, another appears somewhere else. This is all happening in quite complex and sensitive code, so bugfixing requires more time

A fragment from the schedule report, doesn't sound good, but I'm sure they will release that patch next week. By the way, it will be CIG's second timely release, after ArcCorp.
 
Still, at least they managed their first Bake Off. Chris Roberts could use more withering Mary Berry glares in his direction, and lectures on crumb structure.
 
Last edited:
If features have to be cut in order to release this year - I wonder what they will be.

It doesn't matter, I'm simply in awe at the refactoring of the purpose of sliced bread. All these years I've been buying it specifically because it doesn't need cutting, I guess I don't understand sandwich development. :(
 
Last edited:
Also quoted by The Agent

"There's a certain sense of dread here. We get yelled at, told to continue even though we know it's wrong. We do everything we are told, like good little soldiers. Meanwhile the generals are drinking champagne and laughing as the bombs fall."
 
From this month's studio report https://robertsspaceindustries.com/comm-link/transmission/15704-Monthly-Studio-Report

Backend Services
The Backend Team has been hard at work on a massive project to refactor our entire backend infrastructure to a new architecture we’re calling Diffusion. Diffusion will be a truly cloud-oriented service architecture that will help improve high scalability and availability for our services. It will be powered by a top level “coordination” layer written in a proprietary language developed by our Lead Server Engineer, Jason Ely.

LOL
 
https://www.reddit.com/r/starcitizen/comments/5t6zzt/why_cig_does_not_lie_to_you/ddkp8ig/

If the simplest explanation usually proves correct, and premeditated deception is dismissed, then the alternative explanation is consistent ignorance. These are our choices and neither is comforting.
Let's walk through the data and apply some logic.
PROPOSITION
Chris Roberts has a history of giving release date estimates about significant content that later prove incorrect.
EVIDENCE
-- Squadron 42 was supposedly coming in 2014, then 2015, then 2016, now 2017 ("Probably.")
-- Star Marine was supposed to be coming out in "3 weeks time" back in March of 2015. By summer of 2015, it was "weeks not months away." Then at Gamescom we were told it was coming in September. Then months more past, the year ended, and in January we were told it was actually in 2.0 as FPS but that the separate game was still coming. It finally released in December of 2016 but without many of the originally pitched features.
-- At Gamescom in August of 2016, Chris said Alpha 3.0 would release before December 19th. It's February 10th, 2017, and though we've received little specific guidance, it's not looking like we will see it anytime soon.
There are other examples but this seems enough to demonstrate an obvious pattern of inaccuracy exists. So let's get our Logic on and draw some conclusions.
FACT
Chris gives inaccurate guidance and does so constantly. This is incontrovertible at this point. If the simplest explanation is usually correct, we are left with two options:
DEDUCTIONS
-- Either he does so knowingly and is deceiving us (Malevolence.)
-- He does so unknowingly and is deluded himself. (Incompetence.)
These are our choices. Both have troubling implications. It's a Character issue or a Competence issue.
COUNTER ARGUMENT
I've seen some people who acknowledge the history of inaccurate guidance while denying it has any implications or significance for the project. This is the "It will be done when it's done" argument and I'd say fallacy.
It assumes that despite a track record rife with missed deadlines, despite his record of bad backer guidance, despite his lack of discernment about the real challenges of hitting their development goals, everything will turn out great in the end. Eventually. Somehow.
But apply Occam's Razor to the above. Reject Malevolence and the simplest explanation is that Chris is managing the project poorly and doesn't seem to even realize it. Troubling patterns keep repeating over and over. He seems unwilling or unable to correct them. Unexpected complications keep setting the project back yet he doesn't learn to expect them in the future.
You may be untroubled by that but it's hardly untroubling. How can leaders who can't learn from their mistakes really lead anywhere but to further mistakes?
CONCLUSION
Backers don't have to assume Malevolence when weighing Chris's historic record, but if they reject it, then they are choosing Incompetence. Rejecting both simple explanations in spite of the historic record is an act of defiant faith, not of logic. The logical explanation at this point then is to assume a future filled with constantly missed dates and delays that will only survive if the faith of the financing masses perseveres in spite of bad project management and lousy guidance.
Is it all doom and gloom then? I don't think it has to be.
SOLUTION
The solution is for Chris to learn from his own mistakes and give more sober, honest guidance in the future. If he needs to give dates, he should only do so in consultation with his entire development team because chances are, the guys and gals in the trenches are the ones who have a better appreciation for the complexity and the challenge ahead.
The worst case scenario then is they give overly cautious guidance, Chris shares it with backers, and then CIG ends up beating a release date. If that became a pattern, the entire storyline surrounding the project would change. They would become the studio that consistent beats expectations rather than being consistently beaten by them. Narratives of malevolence and incompetence would fade and new ones would emerge. Trust in the company would start to seem logical and not be an act of faith. That seems like a future worth pursuing to me.
 
Status
Thread Closed: Not open for further replies.
Back
Top Bottom