ANNOUNCEMENT January Update - Beta Announcement

Only bio and geo PoIs are affected. Bio PoIs must be fast to resolve as they don't rely on the entire body to be generated to be flagged as present/absent.

We went from having a miniscule chance of finding natural PoIs (about the same chance we currently have for finding NSPs) to being 100% certain to find them if they were indicated from first scan. The new method, if the probabilities are tweaked right, could add a bit of excitement. I think that's a fair trade for not having to sit and wait for the PoI to resolve in the FSA (about as exciting as waiting for the old DSS to finish scanning).

So the issue (waiting passively for resolve) will be solved, or at least moved to the DSS phase when we are moderately busy lobbing probes at the planet. The balance of probabilities is a potential new issue, as is what we can find (not that much), what we can do with the results (not much either), and whether we can improve on the probabilities in the future.

:D S

It's solved by populating the system map with the results once they are computed. This now makes people fly all around systems on a maybe and reverses the entire point of the FSS. The DSS is still needed to map a body and locate the POI anyway.

A thing should do what it's designed to do, the end. The FSS is supposed to present whether POI exist or not. Frontier's bug fix is to remove the mechanics that lead to the problem, not solve it.

Clearly something else now impacts planet procedural generation because when the FSS was originally added, it only took a few seconds to report POI.
 
We also wanted to give you an update on the following issue: VR: Double Vision and Incorrect Rendering on HMDs with Non-Parallel Displays (ex. Pimax). At the current time, there are no plans to provide support for new HMDs outside the officially supported systems and platforms. The officially supported platforms are Valve Index, HTC Vive and Oculus.

I would also like to express disappointment with the news that despite being high up on the Issue Tracker for some time, there is no dev time and therefore performance improvements coming for the Pimax or Valve headsets, not to mention any future wide FOV headsets that may come along, such as XTAL and others.

I appreciate the focus on fixing key bugs, but VR is a real strength of the game and especially as we don't seem to be getting any new content, let alone gameplay, until mid-2020 at the earliest. I hope ED will keep up with the times, realise how many people enjoy the game for its VR capability and support the latest tech.

Thanks for listening (y)
 
I brought into this game before the release in December 2014 and was impressed enough to buy the lifetime pass when Horizons was released. With the hole 10 year plan having a meaning but moneys worth since then is going down hill fast.
 
Anything that stop thargoids generating multiple shutdown pulses is a good idea.
As I'm fed up with shooting the 3rd heart out, surviving the pulse, then resuming firing only to have a 2nd pulse come in and disable me.

Bill

pity the FSS thing cant run as a background task , generating the data behind the screens before you get round to close scanning the world..... but at 10 secs/world, that job could run for 2mins in the background on a large system
 
Agrees. When it comes to Bio or Geo, even just a simple “Yes” or “No” in the FSS would be enough. In fact I think I might like that better than probabilities.

Yes. We have to use DSS anyway (wether or not the POI location is generated before hand, it's still a requirement to locate). The new probability system invalidates the discovery overhaul and all the good work that went into it.

We are being expected to fly around systems again, based on chance. Good-oh. Yeah, no thanks. I'd rather have slow, than maybe? no. :/
 
Anything that stop thargoids generating multiple shutdown pulses is a good idea.
As I'm fed up with shooting the 3rd heart out, surviving the pulse, then resuming firing only to have a 2nd pulse come in and disable me.

Bill

pity the FSS thing cant run as a background task , generating the data behind the screens before you get round to close scanning the world..... but at 10 secs/world, that job could run for 2mins in the background on a large system

It does tho. You can scan a planet, then skip to the next one and come back and it's still chugging away.

2-3 minutes to calculate data is still less than flying out to a body 700,000LS+ based purely on odds. :)

Frontier are solving a delay in results delivery, by making it a chance encounter, instead, at least that's how I read it? Otherwise there's no point.

This seems to be a complete change to how POI are determined, based on chance, rather than the current method (chance means they don't have to wait, presumably). That sounds a lot like RNG, rather than procedural outcomes based on planet generation.
 
Last edited:
Exploring was my main occupation in ED untill the long scan times ruined it for me, I actually like the new fss.
All I want to know when I click a planet/moon is if there are POIs and what kind, I don't care about the numbers etc.
If they replace the current long scan times with an estimate of likelyhood then I'm done playing ED.
I'm not going to fly to all bodies in a system with a likelyhood of containing POIs and probe them and find out it's only a water geyser or nothing at all.
This system will negate the fss's functionality completely besides finding engineering mats.
I wanted the long scan times fixed because it takes,.... to long, this new system will take even longer, much longer.

It's not even a fix imho, it's a complete change of mechanic.
 
Exploring was my main occupation in ED untill the long scan times ruined it for me, I actually like the new fss.
All I want to know when I click a planet/moon is if there are POIs and what kind, I don't care about the numbers etc.
If they replace the current long scan times with an estimate of likelyhood then I'm done playing ED.
I'm not going to fly to all bodies in a system with a likelyhood of containing POIs and probe them and find out it's only a water geyser or nothing at all.
This system will negate the fss's functionality completely besides finding engineering mats.
I wanted the long scan times fixed because it takes,.... to long, this new system will take even longer, much longer.

It's not even a fix imho, it's a complete change of mechanic.
Agreed. Can we have a simple yes/no on POI types appear instantly, and then generate the exact totals in 40-60 seconds like they already do? I want actionable information immediately - specifics can wait. Probabilities are stupid and not fun. I'm OK with them if that's what appears initially, provided it then resolves into something more concrete later.
 
Happy to see this, but no Guardian Module power priority fix? For an update dedicated to addressing issues, I wish the list was a bit more expansive.
 
Happy to see this, but no Guardian Module power priority fix? For an update dedicated to addressing issues, I wish the list was a bit more expansive.

It may yet turn out to be, FDev have said the list is not exhaustive.

It may also be that some issues can be fixed without requiring a public beta test.
 
We wanted to bring your attention to the following issues, as these will need additional information and testing in the beta to ensure the fixes are working as intended:

FSS: Long delay when scanning planets with geological sites
  • As it currently stands, in order for the geological/biological sites to be placed on the surface, the entire stellar body must be fully generated (we then know the topography and can place sites where they will be accessible). This can take tens of seconds.
  • As part of the January Update, we aim to address this with an alternative process. We have run tests on thousands of in-game planetary bodies and by using this data, we're able to extrapolate the likelihood of geological/biologic sites being present on similar stellar bodies. We then use this data and indicate if the planet is ‘Unlikely’, ‘Likely’, or ‘Very Likely’ to have a geological/biological sites.
  • It is not 100% guaranteed that there will be a geological/biological site on the planetary body, but does give commanders a much faster indication of probability. This will enable commanders to quickly ascertain if the planet's worth a visit.
  • As this is an alternative way to display information, we would love to hear your feedback on it to determine whether or not it is better than the current process.
  • Please note: this will not affect Thargoid or Guardian sites, which will show up instantaneously.
[/QUOTE]
This is a terrible idea.
I'd much rather wait longer for a solid answer, than get a "maybe" right away.

I already know there "might" be something there, because that's always true. Telling me again that there "might" be something there is useless info.
 
Exploring was my main occupation in ED untill the long scan times ruined it for me, I actually like the new fss.
All I want to know when I click a planet/moon is if there are POIs and what kind, I don't care about the numbers etc.
If they replace the current long scan times with an estimate of likelyhood then I'm done playing ED.
I'm not going to fly to all bodies in a system with a likelyhood of containing POIs and probe them and find out it's only a water geyser or nothing at all.
This system will negate the fss's functionality completely besides finding engineering mats.
I wanted the long scan times fixed because it takes,.... to long, this new system will take even longer, much longer.

It's not even a fix imho, it's a complete change of mechanic.

Agreed. As an explorer in Elite I think I'd be done too.
 


Greetings Commanders,

As mentioned in October, our upcoming updates will be almost exclusively focused on addressing recent and longstanding issues and bugs. The next update will be our first step as part of that - and it will be coming towards the end of January.

For this update, our first and foremost priority is to ensure that everyone is able to have a seamless experience when playing Elite Dangerous, so our focus will be on aiming to resolve game breaking bugs and stability issues that cause disconnects, softlocks and crashes. By working internally with Customer Support, QA and Development teams, alongside the feedback you shared with us here and via the Issue Tracker, we've identified and are addressing a number of issues in the January Update, which we've detailed below.

As with previous betas, we found your feedback and assistance incredibly useful in helping us identify and resolve bugs and issues. The next updates will be coming with their own public beta, the first of which will run on PC from 27 November to 2 December for the January Update. We are also investigating the ability to extend future betas to console players as well, and will announce any developments about this when we have more information.

Due to this update focusing on a number of bug fixes, rather than new content and features, the beta will appear and play very much like the existing live game. However, getting involved and testing provides a huge benefit for all Elite Dangerous players, so we are very grateful for any time that you are able to spend in the beta. Every system, ship, loadout, module, mission, activity, rank or other part of the game played provides opportunities to test and identify issues. With your support, we hope to be able to identify and fix as many as possible before the update goes live, offering a smoother and better experience for all. Thank you to all who are able to get involved.


What we're addressing in the January Update (and the beta)
We wanted to highlight some of the top voted issues from the Issue Tracker, and what we plan on doing with them moving forward.

Alongside our own internal tests, we'll need the help of you, our community beta participants, to help us identify if the fixes we're introducing work as intended in a live, multiplayer environment.

Repairing Thargoid-attacked stations: not all delivery numbers counted
  • We will implement a fix that will correctly account for all deliveries for starports that have been attacked by Thargoids.
High resolution screenshots create tiling artifacts in bright objects
  • We will implement a fix that should prevent tiling artifacts in bright objects when taking a high-resolution screenshot.
Galaxy Map won't select systems I search for
  • We will implement a fix that should allow you to select a searched system on the Galaxy Map.
Keyboard stops working within game
  • We will implement a fix for this issue to ensure keyboards work in-game as intended.
SLF female npc crew member has no audio and no text in the comms
  • We will implement a fix for this issue.

We wanted to bring your attention to the following issues, as these will need additional information and testing in the beta to ensure the fixes are working as intended:

FSS: Long delay when scanning planets with geological sites
  • As it currently stands, in order for the geological/biological sites to be placed on the surface, the entire stellar body must be fully generated (we then know the topography and can place sites where they will be accessible). This can take tens of seconds.
  • As part of the January Update, we aim to address this with an alternative process. We have run tests on thousands of in-game planetary bodies and by using this data, we're able to extrapolate the likelihood of geological/biologic sites being present on similar stellar bodies. We then use this data and indicate if the planet is ‘Unlikely’, ‘Likely’, or ‘Very Likely’ to have a geological/biological sites.
  • It is not 100% guaranteed that there will be a geological/biological site on the planetary body, but does give commanders a much faster indication of probability. This will enable commanders to quickly ascertain if the planet's worth a visit.
  • As this is an alternative way to display information, we would love to hear your feedback on it to determine whether or not it is better than the current process.
  • Please note: this will not affect Thargoid or Guardian sites, which will show up instantaneously.
Conflict Zones have no contents
  • We have identified that the LUA script responsible for populating Conflict Zones can stop running at times, which causes this kind of issue. We will implement a fix, but we'll need your feedback on whether or not the issue persists.
The Invincible Heart
  • The team have been investigating this issue for some time, however, it has proven difficult to reliably reproduce in-house. As part of the beta, we'll be adding additional logging information and will need our community beta testers to try to reproduce the issue so we can collect more data to help us resolve it.
Instance splitting when fighting Thargoid Interceptor
  • We'll be introducing a fix for this, but as it is a network-related issue, we'll need this to be extensively tested in the beta.
Thargoid Interceptor - Heart cycle reset
  • We will implement a fix to ensure that the Thargoid Interceptor's combat state does not reset. As with the issue above, we'll also require commanders to identify if this is still occurring in the beta.
Exiting the Game just hangs, need to force terminate
  • We will need additional feedback in checking if this issue is still occurring in the beta.
Please note that this is not an exhaustive list of all of the fixes coming in the January Update and more will be detailed in the beta patch notes, released next week.


We'll be investigating the following issues for future updates and will detail any fixes for these when available:
We also wanted to give you an update on the following issue: VR: Double Vision and Incorrect Rendering on HMDs with Non-Parallel Displays (ex. Pimax). At the current time, there are no plans to provide support for new HMDs outside the officially supported systems and platforms. The officially supported platforms are Valve Index, HTC Vive and Oculus.


BETA - how to get involved!
A new beta section forum will be set up with details on how to take part and how to submit bug reports, but here are the main details on how you can help us in the upcoming beta:
  • The beta begins on the 27 November and will run until the 2 December.
  • The beta will be only be accessible on PC. We are looking into expanding this for console players in the future.
  • To take part in the beta, all you’ll need to do is load up the launcher and select (and update) the following product: Elite Dangerous: January Update (Beta) from the 27 November. Once that has been completed, you’ll then have access to the January Update beta. If this doesn't appear, please restart your launcher.
  • We'll be updating the Issue Tracker with a January Update (Update 3.6) Beta section, and we encourage all those who are taking part in this beta to report any encountered bugs or issues through it. In addition, we will also be adding links from inside the game that will take you directly to the Issue Tracker site.

We just want to thank you once again for all the passion and involvement you show for Elite Dangerous. With your participation, we know that we can help to make our game more sustainable and beneficial for the future of this amazing galaxy!

I'm one of the leaders for Operation Ida, the main group working to repair stations. Is the fix for the delivery bug going to be part of the beta as well? We'd love to put enough work in to grab some stats to confirm whether the fix worked (we know it's been a pain to root-cause it)!
 
I'm glad they acknowledged the most important bugs, so that's cool. However, 'm not really stoked about the solution to the long loading times with the FSS and geological sites. If there are no geological sites, the planet already loads (almost) instantly. If there are, you gotta wait half a minute to resolve how many. So you already know wether there are geological sites or not. How many there are really isn't a factor for me in deciding wether to go there or not. I would just like the loading times reduced.
This feels like a workaround. So I guess that actually reducing those loading times isn't possible. Ah well 🤷‍♂️

Actually, I don't mind waiting, it just bothers me not knowing if it's biological or geological beforehand. Since I'm only interested in bio ones, all I need to know beforehand is if the sites will resolve a B or G (or both) types.
 
Back
Top Bottom