My guess, fixing the problem as quick as they can.
Elite Dangerous | System Colonisation Claim Pause
- Thread starter Paul_Crowther
- Start date
- Status
They could tell us each day what lines of code they changed, or what they had for breakfast, maybe their toilet habits, it will make for fascinating reading.
Yeah I am not sure what people want them to announce each day.
They are working on the problem, when they have news I am sure they will share it. In the mean time, let them work out the problem and correct it. I would rather they shut it down for a month then rush it and have to take it off-line again... or worse.
Well, today being Friday for office staff, if no comms or even update or even release the claims on hold by 16:00 today, don't expect anything until at least Tuesday, unless they are all working over the weekend (I very much doubt), as Monday will be catch-up/review weekend for FD.
I appreciate you are desperate to hear more from me, I am of course glorious, but we still don't have anything to announce at this time. We are as eager to turn on the Colonisation Contact as you are but we do ask that you be patient as investigations continue.
As soon as we can share more information with you we will happily do so.
As soon as we can share more information with you we will happily do so.
This reminds me of the scene in the movie Runaway when the nosy reporter gets told off by pointing out that the “baddie” can here her broadcast and also wants to know what the plans to counter it are.
We don’t need more information and though much as everyone else I would like more information the only information I need would be the message saying the pause is over.
I work in infrastructure and application management, supporting approximately 16,000 users.
When an issue arises, my first priority is to communicate it through our internal portal, ensuring that updates are provided daily,, even if there are no new developments.
Sometimes, this simply involves updating the date, as maintaining transparency helps reassure users and fosters a sense of stability.
However, I understand that some members of the community may prefer a different approach, and I’m happy to adjust accordingly.
My intent was never to criticize the work being done in any way, I have been playing Elite since the very beginning and remain fully committed.
I just tought an easy to click on post with a status, wihtout all these pesky comments. haha
And yes, without question Paul_Crowther, your brilliance is undeniable, a beacon of glory for all to behold!
Yep,I work in infrastructure and application management, supporting approximately 16,000 users.
When an issue arises, my first priority is to communicate it through our internal portal, ensuring that updates are provided daily,, even if there are no new developments.
Sometimes, this simply involves updating the date, as maintaining transparency helps reassure users and fosters a sense of stability.
However, I understand that some members of the community may prefer a different approach, and I’m happy to adjust accordingly.
My intent was never to criticize the work being done in any way, I have been playing Elite since the very beginning and remain fully committed.
I just tought an easy to click on post with a status, wihtout all these pesky comments. haha
And yes, without question Paul_Crowther, your brilliance is undeniable, a beacon of glory for all to behold!
Simplest thing in the world of IT is to update MOTD (Message Of The Day) in unix - 1 CMD with 1 to 3 lines text keeping the users updated.
I am ok with the investigation taking a bit while we at least get updates that it is not being forgotten, as was done above for Colonization. If we look at Powerplay 2, though, it had several things "temporarily disabled" 4 months ago and we heard absolutely nothing about it ever since other than devs going on livestream saying "we think it's in a good spot now". It makes the game mode feel very abandoned at record speeds. And it also makes me feel a bit of PTSD whenever I hear that something new was "temporarily disabled". I wish we would get at least the same level of communication that it has not been forgotten for the stuff that was gutted or removed in Powerplay 2.
Now repeat this Message every hour so that we can feel properly informed
They could put in game, replace the 1% NPC message you get in every inhabited system.Now repeat this Message every hour so that we can feel properly informed
They could make EVERY npc Paul_Crowther
Further to AngryAntz's suggestion I'm just disappointed you didn't share what you had for breakfast or today's toilet habits.
Minute.Now repeat this Message every hour so that we can feel properly informed
I'm not expecting it to come back on for a few weeks. I'd wait until all the current claims have expired.
We might have done but our greatgrand parents got around 12 deliveries a day in London.
My grandparents got regular deliveries too, but it wasn't mail, they really needed a TV.
If I were in charge... For a laugh.
Thank you for your continued feedback and patience regarding the current TrailBlazer Beta build.
Our team recognizes the urgency of addressing the identified performance degradation issue within the planetary terrain generation subsystem—specifically related to procedural mesh instantiation and GPU instancing anomalies. Currently, our daily iterative process involves targeted debugging, root-cause analysis, and subsequent optimizations within the shader pipeline and terrain LOD streaming algorithms.
Given the complexity of real-time computational dependencies between terrain tessellation and physics mesh collision detection—coupled with ensuring server-client synchronization stability—updates at intervals shorter than daily are not viable from a technical or QA perspective. Frequent incremental deployments carry significant risk of further regression due to incomplete build validation cycles.
Rest assured, our development cycle follows rigorous CI/CD best practices with comprehensive automated integration testing, followed by manual QA verification. At present, builds are stabilized and deployed for public testing once per day after successful internal validation, regression testing, and benchmarking performance metrics against established KPIs.
We deeply understand and respect your desire for more frequent insights; thus, we will continue providing detailed daily technical briefings outlining ongoing debugging progress, optimization strategies, known issues under active investigation, and expected performance improvements.
Your detailed and specific technical reports greatly assist our team in prioritizing and addressing critical path issues, so we encourage continued detailed submissions through our established bug-tracking channels.
Thank you again for your cooperation and understanding.
Thank you for your continued feedback and patience regarding the current TrailBlazer Beta build.
Our team recognizes the urgency of addressing the identified performance degradation issue within the planetary terrain generation subsystem—specifically related to procedural mesh instantiation and GPU instancing anomalies. Currently, our daily iterative process involves targeted debugging, root-cause analysis, and subsequent optimizations within the shader pipeline and terrain LOD streaming algorithms.
Given the complexity of real-time computational dependencies between terrain tessellation and physics mesh collision detection—coupled with ensuring server-client synchronization stability—updates at intervals shorter than daily are not viable from a technical or QA perspective. Frequent incremental deployments carry significant risk of further regression due to incomplete build validation cycles.
Rest assured, our development cycle follows rigorous CI/CD best practices with comprehensive automated integration testing, followed by manual QA verification. At present, builds are stabilized and deployed for public testing once per day after successful internal validation, regression testing, and benchmarking performance metrics against established KPIs.
We deeply understand and respect your desire for more frequent insights; thus, we will continue providing detailed daily technical briefings outlining ongoing debugging progress, optimization strategies, known issues under active investigation, and expected performance improvements.
Your detailed and specific technical reports greatly assist our team in prioritizing and addressing critical path issues, so we encourage continued detailed submissions through our established bug-tracking channels.
Thank you again for your cooperation and understanding.
- Status