Somebody needs to tell GeforceNOW that the game is back up.......they still won't let me play, saying the game is offline. Tried reporting it to them myself but not sure it did any good.
We'll pass it up the chain.
Star Trek Online Volunteer Community Moderator and Resident She-Wolf
Community Moderators are Unpaid Volunteers and NOT Employees of Gearbox/Cryptic
Views and Opinions May Not Reflect the Views and Opinions of Gearbox/Cryptic
I noticed in game that I had a patch progress that was stuck at 1%. Was able to play normally until I switched captains. The screen where I can select my captains is just black, I exited the game and now when I try to get back in I get the cryptic launcher update on my top left on the screen. The launcher won't go up and either it says that I have an internet problem or a patching error.
"There is iron in your words of death for all Comanche to see, and so there is iron in your words of life. No signed paper can hold the iron. It must come from men. The words of Ten Bears carries the same iron of life and death. It is good that warriors such as we meet in the struggle of life... or death. It shall be life." - Ten Bears (Will Sampson)
I really had I hopes for this game only playing a month now . planned on spending money on it too. I really like the game But now with all these tech issues IDK.....games down ALOT !!! Another Dark Age of Camelot ? hope not !!
I really had I hopes for this game only playing a month now . planned on spending money on it too. I really like the game But now with all these tech issues IDK.....games down ALOT !!! Another Dark Age of Camelot ? hope not !!
These outages are very rare. This is just an unfortunate time where we have had several major ones in a week. Before that I have had no issues for a couple of years and I log in nearly every day.
I really had I hopes for this game only playing a month now . planned on spending money on it too. I really like the game But now with all these tech issues IDK.....games down ALOT !!! Another Dark Age of Camelot ? hope not !!
That is not quiet true there has been some issues in the past few days but other then that the games has been down for either server maintenance or updates. What has happened in the past few days is happening for the first time like this since the game launched in 2010.
C-Store Inc. is still looking for active members on the fed side. If you don't have a fleet feel free to contact me in game @stegi.
Same here . I am starting to just wait it out instead of trying to log in over and over. You just end up frustrated and really angry at something you have no idea what is going on at the company. I keep the perspective that it isn't a walk in the park for the developers either. They have to fix the problem while most likely being nagged "it it fixed yet? Is it fixed yet?..." So at least with that image in my head I can reign my patience in.
On a somewhat separate topic, this reminds me of the Star Citizen fiasco where they launched a new patch but then no one could log on for a few days. Did something like that happen here?
"There is iron in your words of death for all Comanche to see, and so there is iron in your words of life. No signed paper can hold the iron. It must come from men. The words of Ten Bears carries the same iron of life and death. It is good that warriors such as we meet in the struggle of life... or death. It shall be life." - Ten Bears (Will Sampson)
I've passed today's issue up the chain, in case it happens again.
Star Trek Online Volunteer Community Moderator and Resident She-Wolf
Community Moderators are Unpaid Volunteers and NOT Employees of Gearbox/Cryptic
Views and Opinions May Not Reflect the Views and Opinions of Gearbox/Cryptic
Reporting as of 11 am Pacific time, from Washington state, I was able to both log in and change characters. (Later I should pick out a new ship for Tovan Khev; he's achieved full mastery of the Compiler-class RRW Tovan Khev XXXI, and needs to move on.)
I really had I hopes for this game only playing a month now . planned on spending money on it too. I really like the game But now with all these tech issues IDK.....games down ALOT !!! Another Dark Age of Camelot ? hope not !!
"Really had hopes"!? You're speaking like this is a new game; STO has been going 13 years! An outage like this happens extremely rarely, and I can count on one hand the outages that were as big or bigger than this.
"You don't want to patrol!? You don't want to escort!? You don't want to defend the Federation's Starbases!? Then why are you flying my Starships!? If you were a Klingon you'd be killed on the spot, but lucky for you.....you WERE in Starfleet. Let's see how New Zealand Penal Colony suits you." Adm A. Necheyev.
I really had I hopes for this game only playing a month now . planned on spending money on it too. I really like the game But now with all these tech issues IDK.....games down ALOT !!! Another Dark Age of Camelot ? hope not !!
"Really had hopes"!? You're speaking like this is a new game; STO has been going 13 years! An outage like this happens extremely rarely, and I can count on one hand the outages that were as big or bigger than this.
The only time I can recall that was near this bad was during the Summer event at the time of the Iconian War arc. Iirc they did some server stuff too and something went very, very wrong. They had to pull the game down almost immediately after bringing it up after 12+ hour long maintenance. And the game was wonky for days afterwards with multiple emergency maintenances.
As I said that was during the Iconian War launch, so 2015. If there's been anything else comparable it's been in the last two and a half year I've been away. But yeah, stuff like this is rare. @jonnyrocket#1627 just unlucky timing, happens to all of us now and again.
Logic is the beginning of wisdom, not the end of it.
I'm really scared for the wellfare of the game if so many core pieces of code are black-boxed from being made by people who don't work at Cryptic anymore and... how apparently EVERYONE kept their work absolutely secret.
It's awe inspiring that Cryptic has been able to keep the game working as well as they have, considering. And improving it, to boot!
Even if I get worried when issues like this happen.
This morning like others I had an issue connecting to the patch server, BUT I tried again and it worked the 2nd time and has only happened once since it came back friday. I have been on and off several times a day since Friday afternoon.
I'm really scared for the wellfare of the game if so many core pieces of code are black-boxed from being made by people who don't work at Cryptic anymore and... how apparently EVERYONE kept their work absolutely secret.
It's awe inspiring that Cryptic has been able to keep the game working as well as they have, considering. And improving it, to boot!
Even if I get worried when issues like this happen.
From what I've read, it's "not properly documented" not "kept secret."
Writing up a design and maintenance document for a feature takes time, which can be in short supply for a small team. Does developer A spend a day writing that up, or working on the next feature on the list that needs to be finished in time for the next patch? The document will help a year from now, but the to-do list is needed by next week,
Something being a black box doesn't mean it can't ever be changed, it means the cost to change it is much higher than for well-structured and well-documented code. Someone who didn't work on the original design needs to go through the code slowly and carefully to figure out the other developer's intents and methods. It goes even more slowly if they then take the time to create their own documentation.
When someone mentions in the livestream that they tried to change something and it broke in the process, I highly doubt that it means they could not do so if time was no object. It means they had x amount of time assigned to make an attempt, and the quick change they tried wasn't good enough. Give them weeks or more to tease apart the design and I'm sure they could do it -- at the expense of all the other things they need to accomplish in that time.
Speaking only as a developer but NOT a Cryptic developer: relax. They can't easily fix some of the old systems, but if they (not we) decide something is critical to the game they can eventually update it.
I'm really scared for the wellfare of the game if so many core pieces of code are black-boxed from being made by people who don't work at Cryptic anymore and... how apparently EVERYONE kept their work absolutely secret.
It's awe inspiring that Cryptic has been able to keep the game working as well as they have, considering. And improving it, to boot!
Even if I get worried when issues like this happen.
From what I've read, it's "not properly documented" not "kept secret."
Writing up a design and maintenance document for a feature takes time, which can be in short supply for a small team. Does developer A spend a day writing that up, or working on the next feature on the list that needs to be finished in time for the next patch? The document will help a year from now, but the to-do list is needed by next week,
Something being a black box doesn't mean it can't ever be changed, it means the cost to change it is much higher than for well-structured and well-documented code. Someone who didn't work on the original design needs to go through the code slowly and carefully to figure out the other developer's intents and methods. It goes even more slowly if they then take the time to create their own documentation.
When someone mentions in the livestream that they tried to change something and it broke in the process, I highly doubt that it means they could not do so if time was no object. It means they had x amount of time assigned to make an attempt, and the quick change they tried wasn't good enough. Give them weeks or more to tease apart the design and I'm sure they could do it -- at the expense of all the other things they need to accomplish in that time.
Speaking only as a developer but NOT a Cryptic developer: relax. They can't easily fix some of the old systems, but if they (not we) decide something is critical to the game they can eventually update it.
Each bit of coding has to be accounted for in the bottom line. That means that not only does a developer need to have the time to do it, the beancounters have to be persuaded that this would be an effective use of the money they're devoting to the dev's time. If the two factors don't align, then it probably won't be fixed.
Calling back to my own experience, I was a programmer at HQ SAC back in the '80s. Our software was designed to ensure that nuclear weapons wouldn't detonate each other on the way in, in the event of World War Three. Some of the code dated back to the late '60s and early '70s, and at one point someone decided we needed to "translate" all the old FORTRAN programs that were used to COBOL (the language used at the time). We spent about three weeks trying to "translate", and came to the conclusion that it would be quicker and easier to figure out what the modules were doing and rewrite them from line 10. Fortunately, this was a military shop, so we didn't need to account for every minute of software work we were doing. Cryptic's got a more problematic relationship with Gearbox than Strategic Air Command did with the DoD.
The only hiccup I've had today was earlier when I first tried to login; the connection had timed out, but I got in the second time.
Just a few minutes ago I was able to complete my events for today and do a few minutes more work on one of my oldest toons here, which added up to over an hour online without getting kicked out.
I'm just hoping my luck holds out until Tuesday (probably.)
I'm really scared for the wellfare of the game if so many core pieces of code are black-boxed from being made by people who don't work at Cryptic anymore and... how apparently EVERYONE kept their work absolutely secret.
It's awe inspiring that Cryptic has been able to keep the game working as well as they have, considering. And improving it, to boot!
Even if I get worried when issues like this happen.
From what I've read, it's "not properly documented" not "kept secret."
Writing up a design and maintenance document for a feature takes time, which can be in short supply for a small team. Does developer A spend a day writing that up, or working on the next feature on the list that needs to be finished in time for the next patch? The document will help a year from now, but the to-do list is needed by next week,
Something being a black box doesn't mean it can't ever be changed, it means the cost to change it is much higher than for well-structured and well-documented code. Someone who didn't work on the original design needs to go through the code slowly and carefully to figure out the other developer's intents and methods. It goes even more slowly if they then take the time to create their own documentation.
When someone mentions in the livestream that they tried to change something and it broke in the process, I highly doubt that it means they could not do so if time was no object. It means they had x amount of time assigned to make an attempt, and the quick change they tried wasn't good enough. Give them weeks or more to tease apart the design and I'm sure they could do it -- at the expense of all the other things they need to accomplish in that time.
Speaking only as a developer but NOT a Cryptic developer: relax. They can't easily fix some of the old systems, but if they (not we) decide something is critical to the game they can eventually update it.
Each bit of coding has to be accounted for in the bottom line. That means that not only does a developer need to have the time to do it, the beancounters have to be persuaded that this would be an effective use of the money they're devoting to the dev's time. If the two factors don't align, then it probably won't be fixed.
Calling back to my own experience, I was a programmer at HQ SAC back in the '80s. Our software was designed to ensure that nuclear weapons wouldn't detonate each other on the way in, in the event of World War Three. Some of the code dated back to the late '60s and early '70s, and at one point someone decided we needed to "translate" all the old FORTRAN programs that were used to COBOL (the language used at the time). We spent about three weeks trying to "translate", and came to the conclusion that it would be quicker and easier to figure out what the modules were doing and rewrite them from line 10. Fortunately, this was a military shop, so we didn't need to account for every minute of software work we were doing. Cryptic's got a more problematic relationship with Gearbox than Strategic Air Command did with the DoD.
Yep, for some of that 10+ year old STO code re-writing from scratch would probably be better than adding another layer of duct tape.
The main app I work on is 8+ years old and is a re-write of an older app from 2005. 8 years of new features have made part of it hard to maintain so I'm always happy when I can fit in some refactoring into the schedule. Sometimes I can do that as part of adding a new feature -- if the code is going to change anyway, then we can spend a little extra time to improve how those 8 years of features fit together. Sometimes we need that new feature now! and I have to grab the duct tape.
I'm really scared for the wellfare of the game if so many core pieces of code are black-boxed from being made by people who don't work at Cryptic anymore and... how apparently EVERYONE kept their work absolutely secret.
It's awe inspiring that Cryptic has been able to keep the game working as well as they have, considering. And improving it, to boot!
Even if I get worried when issues like this happen.
From what I've read, it's "not properly documented" not "kept secret."
Writing up a design and maintenance document for a feature takes time, which can be in short supply for a small team. Does developer A spend a day writing that up, or working on the next feature on the list that needs to be finished in time for the next patch? The document will help a year from now, but the to-do list is needed by next week,
Something being a black box doesn't mean it can't ever be changed, it means the cost to change it is much higher than for well-structured and well-documented code. Someone who didn't work on the original design needs to go through the code slowly and carefully to figure out the other developer's intents and methods. It goes even more slowly if they then take the time to create their own documentation.
When someone mentions in the livestream that they tried to change something and it broke in the process, I highly doubt that it means they could not do so if time was no object. It means they had x amount of time assigned to make an attempt, and the quick change they tried wasn't good enough. Give them weeks or more to tease apart the design and I'm sure they could do it -- at the expense of all the other things they need to accomplish in that time.
Speaking only as a developer but NOT a Cryptic developer: relax. They can't easily fix some of the old systems, but if they (not we) decide something is critical to the game they can eventually update it.
Each bit of coding has to be accounted for in the bottom line. That means that not only does a developer need to have the time to do it, the beancounters have to be persuaded that this would be an effective use of the money they're devoting to the dev's time. If the two factors don't align, then it probably won't be fixed.
Calling back to my own experience, I was a programmer at HQ SAC back in the '80s. Our software was designed to ensure that nuclear weapons wouldn't detonate each other on the way in, in the event of World War Three. Some of the code dated back to the late '60s and early '70s, and at one point someone decided we needed to "translate" all the old FORTRAN programs that were used to COBOL (the language used at the time). We spent about three weeks trying to "translate", and came to the conclusion that it would be quicker and easier to figure out what the modules were doing and rewrite them from line 10. Fortunately, this was a military shop, so we didn't need to account for every minute of software work we were doing. Cryptic's got a more problematic relationship with Gearbox than Strategic Air Command did with the DoD.
Yep, for some of that 10+ year old STO code re-writing from scratch would probably be better than adding another layer of duct tape.
The main app I work on is 8+ years old and is a re-write of an older app from 2005. 8 years of new features have made part of it hard to maintain so I'm always happy when I can fit in some refactoring into the schedule. Sometimes I can do that as part of adding a new feature -- if the code is going to change anyway, then we can spend a little extra time to improve how those 8 years of features fit together. Sometimes we need that new feature now! and I have to grab the duct tape.
I wonder how much of the original code is duct taped together to begin with since IIRC STO was rather rushed due to Cryptic getting the job on the condition they'd do it within a certain timetable that was shorter then typical for MMOs, so you probably had things that are "this sort of works as long you don't try to do this" that also got poorly documented and thus causing the issues we're having currently due the devs not really knowing how the thing worked in the first place.
I'm really scared for the wellfare of the game if so many core pieces of code are black-boxed from being made by people who don't work at Cryptic anymore and... how apparently EVERYONE kept their work absolutely secret.
It's awe inspiring that Cryptic has been able to keep the game working as well as they have, considering. And improving it, to boot!
Even if I get worried when issues like this happen.
From what I've read, it's "not properly documented" not "kept secret."
Writing up a design and maintenance document for a feature takes time, which can be in short supply for a small team. Does developer A spend a day writing that up, or working on the next feature on the list that needs to be finished in time for the next patch? The document will help a year from now, but the to-do list is needed by next week,
Something being a black box doesn't mean it can't ever be changed, it means the cost to change it is much higher than for well-structured and well-documented code. Someone who didn't work on the original design needs to go through the code slowly and carefully to figure out the other developer's intents and methods. It goes even more slowly if they then take the time to create their own documentation.
When someone mentions in the livestream that they tried to change something and it broke in the process, I highly doubt that it means they could not do so if time was no object. It means they had x amount of time assigned to make an attempt, and the quick change they tried wasn't good enough. Give them weeks or more to tease apart the design and I'm sure they could do it -- at the expense of all the other things they need to accomplish in that time.
Speaking only as a developer but NOT a Cryptic developer: relax. They can't easily fix some of the old systems, but if they (not we) decide something is critical to the game they can eventually update it.
Each bit of coding has to be accounted for in the bottom line. That means that not only does a developer need to have the time to do it, the beancounters have to be persuaded that this would be an effective use of the money they're devoting to the dev's time. If the two factors don't align, then it probably won't be fixed.
Calling back to my own experience, I was a programmer at HQ SAC back in the '80s. Our software was designed to ensure that nuclear weapons wouldn't detonate each other on the way in, in the event of World War Three. Some of the code dated back to the late '60s and early '70s, and at one point someone decided we needed to "translate" all the old FORTRAN programs that were used to COBOL (the language used at the time). We spent about three weeks trying to "translate", and came to the conclusion that it would be quicker and easier to figure out what the modules were doing and rewrite them from line 10. Fortunately, this was a military shop, so we didn't need to account for every minute of software work we were doing. Cryptic's got a more problematic relationship with Gearbox than Strategic Air Command did with the DoD.
Yep, for some of that 10+ year old STO code re-writing from scratch would probably be better than adding another layer of duct tape.
The main app I work on is 8+ years old and is a re-write of an older app from 2005. 8 years of new features have made part of it hard to maintain so I'm always happy when I can fit in some refactoring into the schedule. Sometimes I can do that as part of adding a new feature -- if the code is going to change anyway, then we can spend a little extra time to improve how those 8 years of features fit together. Sometimes we need that new feature now! and I have to grab the duct tape.
I wonder how much of the original code is duct taped together to begin with since IIRC STO was rather rushed due to Cryptic getting the job on the condition they'd do it within a certain timetable that was shorter then typical for MMOs, so you probably had things that are "this sort of works as long you don't try to do this" that also got poorly documented and thus causing the issues we're having currently due the devs not really knowing how the thing worked in the first place.
I remember hearing that too. From what I remember the timeframe was apparently pretty ruthless. No wonder we nearly didn't get the KDF at all on launch. I'm extremely glad Cryptic hung in there and we have this game in a much better state now, despite issues like the black-boxed code.
Comments
We'll pass it up the chain.
Views and Opinions May Not Reflect the Views and Opinions of Gearbox/Cryptic
Moderation Problems/Issues? Please contact the Community Manager
Terms of Service / Community Rules and Policies / FCT
Facebook / Twitter / Twitch
"Anyaway, we don't often see a sense of humor in Section 31."
Think its a wide spread issue again.
Same thing is happening to me right now after being to log in normally prior.
Yup, getting this again. Got the game to work last night but today it is borked again. Have not seen issues like this in a very long time.
Unable to establish connection to Patch Server. Please check your internet connection. If problems persist, please contact Technical Support.
These outages are very rare. This is just an unfortunate time where we have had several major ones in a week. Before that I have had no issues for a couple of years and I log in nearly every day.
Get past this and the game will be solid again.
On a somewhat separate topic, this reminds me of the Star Citizen fiasco where they launched a new patch but then no one could log on for a few days. Did something like that happen here?
Views and Opinions May Not Reflect the Views and Opinions of Gearbox/Cryptic
Moderation Problems/Issues? Please contact the Community Manager
Terms of Service / Community Rules and Policies / FCT
Facebook / Twitter / Twitch
"Really had hopes"!? You're speaking like this is a new game; STO has been going 13 years!
The only time I can recall that was near this bad was during the Summer event at the time of the Iconian War arc. Iirc they did some server stuff too and something went very, very wrong. They had to pull the game down almost immediately after bringing it up after 12+ hour long maintenance. And the game was wonky for days afterwards with multiple emergency maintenances.
As I said that was during the Iconian War launch, so 2015. If there's been anything else comparable it's been in the last two and a half year I've been away. But yeah, stuff like this is rare. @jonnyrocket#1627 just unlucky timing, happens to all of us now and again.
It's awe inspiring that Cryptic has been able to keep the game working as well as they have, considering. And improving it, to boot!
Even if I get worried when issues like this happen.
From what I've read, it's "not properly documented" not "kept secret."
Writing up a design and maintenance document for a feature takes time, which can be in short supply for a small team. Does developer A spend a day writing that up, or working on the next feature on the list that needs to be finished in time for the next patch? The document will help a year from now, but the to-do list is needed by next week,
Something being a black box doesn't mean it can't ever be changed, it means the cost to change it is much higher than for well-structured and well-documented code. Someone who didn't work on the original design needs to go through the code slowly and carefully to figure out the other developer's intents and methods. It goes even more slowly if they then take the time to create their own documentation.
When someone mentions in the livestream that they tried to change something and it broke in the process, I highly doubt that it means they could not do so if time was no object. It means they had x amount of time assigned to make an attempt, and the quick change they tried wasn't good enough. Give them weeks or more to tease apart the design and I'm sure they could do it -- at the expense of all the other things they need to accomplish in that time.
Speaking only as a developer but NOT a Cryptic developer: relax. They can't easily fix some of the old systems, but if they (not we) decide something is critical to the game they can eventually update it.
Each bit of coding has to be accounted for in the bottom line. That means that not only does a developer need to have the time to do it, the beancounters have to be persuaded that this would be an effective use of the money they're devoting to the dev's time. If the two factors don't align, then it probably won't be fixed.
Calling back to my own experience, I was a programmer at HQ SAC back in the '80s. Our software was designed to ensure that nuclear weapons wouldn't detonate each other on the way in, in the event of World War Three. Some of the code dated back to the late '60s and early '70s, and at one point someone decided we needed to "translate" all the old FORTRAN programs that were used to COBOL (the language used at the time). We spent about three weeks trying to "translate", and came to the conclusion that it would be quicker and easier to figure out what the modules were doing and rewrite them from line 10. Fortunately, this was a military shop, so we didn't need to account for every minute of software work we were doing. Cryptic's got a more problematic relationship with Gearbox than Strategic Air Command did with the DoD.
Just a few minutes ago I was able to complete my events for today and do a few minutes more work on one of my oldest toons here, which added up to over an hour online without getting kicked out.
I'm just hoping my luck holds out until Tuesday (probably.)
Yep, for some of that 10+ year old STO code re-writing from scratch would probably be better than adding another layer of duct tape.
The main app I work on is 8+ years old and is a re-write of an older app from 2005. 8 years of new features have made part of it hard to maintain so I'm always happy when I can fit in some refactoring into the schedule. Sometimes I can do that as part of adding a new feature -- if the code is going to change anyway, then we can spend a little extra time to improve how those 8 years of features fit together. Sometimes we need that new feature now! and I have to grab the duct tape.
I wonder how much of the original code is duct taped together to begin with since IIRC STO was rather rushed due to Cryptic getting the job on the condition they'd do it within a certain timetable that was shorter then typical for MMOs, so you probably had things that are "this sort of works as long you don't try to do this" that also got poorly documented and thus causing the issues we're having currently due the devs not really knowing how the thing worked in the first place.
I remember hearing that too. From what I remember the timeframe was apparently pretty ruthless. No wonder we nearly didn't get the KDF at all on launch. I'm extremely glad Cryptic hung in there and we have this game in a much better state now, despite issues like the black-boxed code.