Beyond: Chapter 4 – Beta #4: Is Live!

Updated: 21st November 2018 @ 12.16am

At 2:05pm on the 20th November 2018 Frontier announced the details for the final part of the Beyond: Chapter 4 Beta. You can see them below or here on the official website. You can read what Frontier have said about Thargoid Conflict Zones, here. Patch notes will appear in this thread once released by Frontier. There will also be a live stream on the 22nd November at 7pm (UTC) to demonstrate the new Thargoid Conflict Zones.

“We’re pleased to announce that the next set of beta content for Beyond – Chapter Four will be Thargoid Conflict Zones and a brand-new Thargoid-attacked Megaship scenario!

“We will bring the beta servers down at 10:00 (UTC) on 21 November. Following the update, the beta server will be live at approximately 11:00 (UTC) on 21 November. There is a chance that this could run over, so we really appreciate your patience. As usual with these updates we’ll keep you as up to date as possible.

“Slightly different to previous beta additions, this Thargoid content will only be available in the Maia system during the Beyond – Chapter Four beta, though it will be available across all modes.

“Alongside this new content (below), you’ll be able to continue testing all of the previous content!

“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 – Horizons – Beta (3.3). Once that has been completed, you’ll then have access to the Beyond – Chapter Four beta. If this hasn’t appeared, please restart your launcher.

“If you’d like information as the beta progresses, you can also subscribe to our Beyond – Chapter Four Beta newsletter by clicking here.

“We can’t wait to hear what you think of the new Thargoid Conflict Zones and Megaship Scenario!”

Additionally,

“The next beta update will also include various bug fixes and improvements. We’ve made some adjustments to mining itself and all of the details will be available in the patch notes published prior to the beta update.”


 > Patch Notes


Incursion State

  • Incursion state added, along with
  • Thargoid Conflict Zone scenario (“AX Conflict Zones”)
  • Damaged megaship scenarios
  • For the Beta, the Maia system has been manually set to the incursion state, and these scenarios should appear there

Comms

  • Added a toggle to turn off the profanity filter (under the options tab in the comms panel)

Audio Options

  • Updated audio options:
  • Default/optimal volume position is now marked, allowing the player to return to default easily
  • All sliders (apart from the 3 “master” sliders (sounds, music, voice)) can be boosted as well as cut
  • Note: User volume slider positions will be reset to default on this update (this is a one time only reset)

Bug Fixes and Improvements

Anaconda

  • Fixed incorrect white lights in cockpit

Background Sim

  • Added galaxy map filter for the new ‘Civil Liberty’ state
  • Added text to indicate the happiest system in the ‘Faction Allegiance’ section in Squadrons
  • Added icons to states listed in the System Map
  • Pirate attacks and outbreaks will now occur automatically
  • Fixed Conflict Zones not always spawning in systems at War

Cobra Mk.III

  • Fixed misaligned thrusters

Codex

  • Fixed an issue where a planet that didn’t have a terraformed status set would default to being terraformable (when it shouldn’t be)
  • Fixed overlapping text in the Archive section
  • Galactic region no longer resets to your location when searching the Discoveries section
  • Added ‘Distance Traveled in an SRV’ stat
  • Narration added for “Individuals” knowledgebase articles

Comms

  • Increased the volume of the background chatter in Conflict Zones
  • Increased the chat spam limit from 3 to 5 (fixes some Voice Attack issues)
  • Fixed issue that caused chat messages not to be delivered when the recipient was on main menu

Controls

  • The binding for entering the vanity cam in ship and SRV can now be bound to the same button

COVAS

  • Increased the volume of ‘Jefferson’

Crashes/Stability

  • Fixed a crash that could occur when leaving a Resource Extraction Site
  • Fixed a crash that could occur when using the Subsurface Displacement missile
  • Fixed a crash that could occur when jumping to another system
  • Fixed crash that could occur when opening the Codex
  • Fixed that could occur when entering a Conflict Zone
  • Fixed a crash that could occur when players ship is destroyed
  • Fixed a crash that could occur when using the Pulse Wave Analyser
  • Fixed a crash that could occur when using the Prospector Limpet
  • Fixed a crash that could occur when switching ships
  • Fixed a crash that could occur when in the FSS mode
  • Fixed holo-me being incorrectly selectable from the SRV, leading to a softlock
  • Fixed a crash that could occur when switching between 3D modes
  • Fixed a crash that could occur when opening the Codex after a recent discovery
  • Fixed a crash that could occur when selling Exploration Data
  • Fixed instances of “authentication server” disconnections from mission servers

Crime & Punishment

  • Added clarification to the bounty transaction details, to explain the implications of the Kill Warrant Scanner

Decals

  • Fixed reversed decal slots on Cobra Mk.III and Imperial Cutter

Exploration

  • The Detailed Surface Scanner will now auto hide in the fire groups HUD while in normal space
  • Fixed an audio issue that could cause the scanning sound to get stuck and loop
  • Fixed an issue which meant players couldn’t buy exploration data when docked at a port
  • Stopped the ship voice line from needlessly repeating when the system has been fully scanned
  • Fixed an issue where the info panel would not update to show a planets signals while in the DSS mode
  • Fixed an issue that was preventing players from firing probes a rings around stars (the star itself can still not be probed, which is intended behaviour)
  • Bodies now appear when using the FSS mode in non-Horizon versions of the game
  • Increased the sensitivity range on the FSS movement controls
  • Added sensitivity control to the spectrum analysis bar
  • FSS mouse binding now no longer gives a ‘roll’ option
  • Scanning a nav beacon now returns full system data (ring details were missing)
  • Fixed issue that could cause ‘false’ signals to appear that couldn’t be resolved
  • The threat level of a USS is now displayed when zoomed in on it
  • The system map now indicates if the planet has been mapped or not
  • Added message when a body is passively scanned
  • Fixed an issue that was causing some bodies to appear on the system map, but were unable to be discovered using the FSS mode
  • Fixed impossible to meet efficiency targets
  • Info panel now has 2 lines to display messages on
  • Fixed some Thargoid signal sources being identified as Guardian

Federal Corvette

  • Fixed visual issues on fitted ship kit when using a paint job

Friends and Private Groups

  • Fixed a hang that could occur when browsing a very large group

General

  • Fixed issue where dropping out at ports in asteroid clusters wasn’t dropping the player near it
  • Fixed an issue that meant certain Port contacts were erroneously appearing
  • Fixed issue where Thargoid probes weren’t spawning correctly
  • Fixed issue where the left hand panel would become unresponsive when return to the players ship from an SRV
  • Fixed missing leading reticle for the Flechette launcher
  • Fixed issue that could lead to the left hand panel becoming unresponsive

Holo-me

  • Fixed some graphical issues on the avatar portrait

Lighting

  • Reduced brightness in galaxy map

Localisation

  • ‘Search’ wasn’t translated in the Friends and Private Groups menu
  • Fixed various typos
  • Fixed incorrect text on ‘Galactic Powers’ button on the home tab
  • Fixed truncated text on the ‘Galactic Powers’ button in German
  • Added translations for Detailed Surface Scanner options
  • Replaced placeholder text with actual text in Fine description

Mamba

  • Fixed thrusters not changing colour when applying engine colours
  • Fixed misaligned vanity preview cameras
  • Balance pass on boost, speed, and pitch and roll rates
  • Should now dissipate heat quicker (in line with the FDL)

Megaships

  • Fixed Z-fighting issue

Mining

  • Added information on what is inside a motherlode asteroid to the data returned by the prospector limpet
  • Added extra detail to the Subsurface Displacement Missiles outfitting description, to explain the pull and hold trigger feature
  • Fixed graphical issue after using a Displacement Missile
  • NPC ships now use their mining lasers once again
  • Fixed missing targets, UI and feedback when a multicrew member joins after a prospector limpet has been used
  • Added extra feedback icons to the areas that represent the different yield ranges when attempting to crack an asteroid apart
  • Tweaked the pulse wave analyser results to be less broad and more focused at range
  • Added new, high value materials to the motherlode asteroids (free floating materials and new surface deposits, which are found after cracking the asteroid open)
  • Increased the ammo capacity of the new mining tools
  • Stopped depleted asteroids from appearing gold when scanned with the Pulse Wave Analyser

Missions

  • Removed restriction on in space collect missions, to allow players to take them even if their ships cargo hold is below the amount needed (they will use the Cargo Depot feature)

Multicrew

  • Fixed the target panel for the gunner role
  • Fixed issue where select the view report button didn’t take players directly to the screen

Orrery

  • Fixed incorrect planetary ring orientation

Outfitting

  • Updated the refinery text to change the refernce of “Mining Laser” to “Mining Tools”

Player Journal

  • Fixed duplicate scan events
  • Fixed some wing mission cargo reported as stolen
  • FSSSignalDiscovered: add USSType info (§6.6)
  • Add new FSSAllBodiesFound event (§6.4)
  • Scan events generated automatically when entering system now logged as “ScanType”:”AutoScan” (§6.3)
  • Add new event MultiSellExplorationData (§6.10)
  • Faction info in Location/FSDJump: if it’s the player’s squadron faction, add SquadronFaction:true, and flags HappiestSystem:true or HomeSystem:true if relevant (§4.8)

Render

  • Fixed high res screen shot feature when zoomed into a body in FSS
  • Fixed some Z-fighting found at Platers’s Tyranny port
  • Fixed some flickering on glass materials in stations
  • Make the light diffusion through volumetrics similar in appearance across graphics settings.
  • Cockpit geometry occludes ship schematics now
  • Fixed some jittering in ring fog
  • Fixed for brightness of mining related volumetric effects when in shadow of planet
  • Fixed rendering of glass material behind fog in stations

Ship Name Plates

  • Text size is now affected when using leading and/or trailing spaces

Squadrons

  • Randomised the results when browsing
  • Added a new ‘Mentor’ activity tag
  • Fixed issue where players could not use the gamepad to select a member to hand over the Squadron to
  • The members list now defaults to sorting by rank (high – low)
  • Shortened the invite text to solve truncated text
  • Tags can now be edited after the Squadron has been created
  • Fixed the Squadron feed tab being incorrectly reset upon ship destruction
  • Players can now transfer ownership to players that are not currently online
  • Faction alligence page now uses current state rather than pending state
  • After a player is promoted/demoted, permissions are now granted/taken away immediately
  • Tags can now be used to filter Squadron results
  • Fixed a transaction server error when sharing a starport or settlement bookmark
  • Fixed a bug preventing some pre-registered squadrons from changing their faction affiliation
  • Fixed exploration data and CQC results not always being added to the squadron leaderboards

Stellar Forge

  • Corrected the orbit of the moon around Earth

Vanity Camera

  • Stopped the ship cockpit UI rendering through the pilots chair

VR

  • Ensured the ring scan effect (and hotspots) are correctly occluded by the planet geometry in both eyes.
  • Fixed issue that causes the camera to clip through the pilots body more than usual

 

Beyond: Chapter 4 – Beta is Live!

On the 30th October 2018 Frontier released the Beta for Chapter 4 (3.3) of Beyond. This is available to all PC owners of the game (both the base game and Horizons). You can get the full lowdown on the release here, or:

Game Director Laurence Oldham posted this message on the official forum,

Dear Commanders,

It is with a feeling of anticipation and excitement that later today we release Beyond – Chapter Four’s open PC beta, giving you the first opportunity to get your hands on with the biggest Elite Dangerous update of 2018 ahead of its official launch later this year. With that in mind, I wanted to explain how the beta process works for the newest Commanders among you and how we can work together to make this a successful beta phase for Chapter Four.

It’s been a long journey since we first announced our plans for this Chapter at Frontier Expo in October 2017 and we have been hard at work ever since, implementing many ambitious ideas and taking a deep look into aspects like Elite’s Background Simulation, Codex, and Exploration; just a few of the features you’ll be able to test during the first part of our open beta from this afternoon.

However, our journey is not yet complete.

Chapter Four will be the biggest influx of new content for Elite Dangerous in 2018 and it represents the culmination of our combined efforts during many months of development. To ensure the results will be as good as we can possibly make them, we would invite you to join us in this final opportunity to identify and fix any issues together. For us, this open beta is a vital part of the development process and our hope is that you, our dedicated community, will participate, enjoy, and let us know what you experience. Any problems you encounter during your travels, please take the time to report them to us here. Having this one central location for all Commanders to register feedback is very important as it allows us to easily collate and register comments, bugs, and suggestions. We have assigned a dedicated team to track all your reports as they come in and we are committed to improving Chapter Four based on your observations.

As we progress through the weeks, new features and new content will become available for you to try out and report on.

We are currently completing our pre-flight checks and we expect to be ready to launch shortly after 15:00 UTC. All that’s left is to say a huge thank you to everyone taking part, I really hope you enjoy it.

Laurence

The first Beta phase will feature all the features and changes seen in the first two livestreams. You can read all the details known so far about Chapter 4 here. In anticipation of this and with permission from Factabulous on the Official Forum I’ve reproduced the handy Beta FAQ.


> Beta FAQ

  • The Beta appears as a new option to start in the launcher when it is available, normal game will remain available during beta.
  • No, consoles don’t participate in the Beta. Yes other games have Beta access on consoles, ED does not.
  • To reduce the clutter in the launcher you can add the /edh option to your launcher shortcut. You are welcome.
  • No, we don’t know how large the beta is yet. CMDR Thrust from Bradford knows, but he’s too busy walking around an Atmos planet on his space legs with his NPC crew. (long standing forum joke)
  • No, you cannot take anything you find in the Beta out of the Beta
  • Your commander will be based off a copy of the live game taken during the last few weeks
  • Values in the Beta may not reflect the final game – often mission spawn rates are changed, and we can expect broker rates to change. Probably.
  • The beta may restart / become unavailable without notice. It’s a beta. Chillax.
  • No, you will not keep any unlocked tech broker recipes after the beta.
  • Anything you do in the Beta does not affect your main CMDR
  • Make sure you are running the Beta before doing destructive things. Beta often has a watermark so you can check. But double check…
  • If you are not where you want to be then FD may respond to move requests in the Beta, if you ask nicely.
  • Or you can kill your ship and respawn at the starter system if you want to get back to the bubble.
  • You can also reset your CMDR, sometimes Beta resets will set extra money/other things so you can get back to testing – check details in the beta before resetting!
  • No, you cannot take anything you find in the Beta out of the Beta
  • You need to remove the beta files after the beta, but it might be worth keeping the around until the full release as the files are allegedly used instead of downloading
  • No, you cannot take anything you find in the Beta out of the Beta
  • Report bug as beta tickets. Feel free to add your information onto existing tickets, but they are reports – not discussions.
  • Talk about the beta in the beta forums. Console users probably don’t want to hear about cool stuff they can’t access yet.
  • No point in putting in feature requests. Beta means the code is about ready to release, it will get tweaks, but not features (Many will ignore this and get irate)
  • No, you cannot take anything you find in the Beta out of the Beta.

Lavecon 2018 – Beyond: News

On Saturday the 9th June 2018 Frontier attended the annual Lavecon meet and showcased some features coming in the Beyond Quarter 4 updates, as well as some things coming in the soon to be released Quarter 2 update.

You can see the details covering a large number of additions coming to Quarter 4 by visiting the page here. Changes to Quarter 2 can be seen here.

Live stream – Discovery Scanner 1: Update

Following the live stream, Dr Ant Ross answered some questions. You can see them below, on the official forum here, or on Reddit, here.


1) Is “The Bulge” what is referred to in game as The Bubble?

The galactic bulge, or galactic core, is the blob shaped region of stars in the centre of the Milky Way. It is a separate thing from The Bubble, which is the region of human inhabited space around Sol.

2) Why did Elite Dangerous decide to use light-years and not parsecs in-game?

I don’t believe there was a specific reason why. The original Elite and its sequels also used light years for interstellar distances, and it is nice to be consistent.

3) Does the game allow for any catastrophes? Novae, rogue-planet ejection or capture, system collision?

During the generation stage, rogue-planet events and collisions are taken into account. However, these are historical and not visual effects. When you arrive in the system, you only see the results of those effects on the resulting stable system.

4) When do we get to hear about what is coming next for Stellar Forge? Like comets, flyable gas giants, etc.

Oh, yeah, that’s scheduled for MMPPPPPPH ( Ant gets dragged away by Zac ). Ahem, hm, apologies, but I can’t really talk about that at the moment.

5) Why does Elite Dangerous only use circular orbits? Are elliptical orbits too complicated?

Elite Dangerous does use elliptical orbits. The inclination, periapsis, longitude of ascending node, semi major axis and eccentricity information is all tracked.

6) There are some planets in the game that look like they would be torn apart by tidal forces. Did you say you actually simulate this? What means those close planets are actually possible?

There are some bodies which may be near the mathematical limit of that collection of matter being clumped together. However, we don’t currently have the rendering feature to display what the surfaces of those look like or how you would interact with them. In reality, you may see a distorted molten mess.

7) The in-system barycentre-orbital distribution in the game is quite vast, given the limited observed bodies (just Pluto/Charon). Is that likely true to life?

The distant orbits which are created should follow Kepler’s laws of planetary motion and classical (non-relativistic) orbital calculations. The resulting hierarchies of orbits should be feasible, but it will be very interesting to see what comes from the future of orbital mechanics analyses and exo-planet searches.

8) Is there anything orbiting within Lagrange Points at all in Elite?

There is a section of code running capture interactions in the virtual protoplanetary disk which can place bodies into the L4 and L5 Lagrange points. I believe this ends up being mostly asteroid clusters, but I have not had a look at them in a while.

9) Have you ever forgot the location of a special feature, that could be found by a player?

If I did, I have forgotten what it was. Sorry I did once make the galaxy produce Mr. Braben’s face in stars as a test for being able to inject very bright O class stars, but that was removed pre-pre-pre Alpha.

10) How close is this identifier system to any existing official naming or identifier protocols currently used by scientists? Like, could we input future data we collect in real life into Elite?

Each generated body needs a unique identifier, but also any “authored” body, say from the stellar catalogues. Authored bodies, however, have their information pre-calculated, so only do partial proc-gen at most. The system is sensitive to adding new authored bodies to the system, as it could displace the identifier of other proc-gen bodies, changing the galaxy. It is possible to make changes, but we must be careful about it.

11) Why aren’t there dark regions on the other side of the galaxy?

Do you mean lower density regions between the spiral arms? If you could please forward on an X,Y,Z sector location (as seen from the Galaxy Map grid lines) I could have a closer look and confirm. Depending on where exactly you are on that side, there are still under-dense regions, but there may also be some bleed through from the galactic bulge data placing more matter in that region that immediately appears from the image in the Galaxy Map.

12) Will Nebulas one day resemble the Hubble painted shot?

One of the common discussions on the dev floor is about the level of visual exaggeration we portray to the players. For example, most nebula images you can see are false colour ones of non-visible EM wavelengths. Do we make radiowaves visible in-game to reflect these beautiful photographs? Do we go the realistic route of showing these hydrogen clouds as greyish, slightly greenish diffuse blobs? No promises, no guarantees, nothing to announce at this time, but I am always interested in potential improvements to the rendering of stellar bodies and phenomena.

13) Does the planet surface rendering use adaptive subdivision when making the hills and craters of the planets?

Currently, the subdivisions are in smaller patches with the same amount of points in the same square arrangement. This is used, rather than non-uniform dynamic tessellation, because in our system it allows a much faster and economical generation of both render and physics meshes. We blend between detail levels of patches though, to smoothly transition from low to high vertex density.

14) Have you thought about creating permanent, full textures for popular planets that get loaded frequently?

Such large texture collections would take up a lot of graphics memory. I understand and sympathize with some of the popping that users have been experiencing, but using up that available memory would mean that other textures in the game would pop quite a bit worse.

15) How come some stars are older than the Universe in Elite Dangerous?

The oldest stars in the real Milky Way can tend towards 13,800,000,000 years. The sectors themselves have a maximum average age of 12,810,000,000 years. Unfortunately, though, there is a small, rare, bug in resolving the range of ages across a few sectors, and there have been a few cases of the stated age if a star being around 18 billion years. Yup, that’s an oopsie. Bluntly fixing this will upset some generation and alter the galaxy, so a careful approach is needed for fixing this one up. It’s my list of work to address, apologies for the delay.

16) Does ED generate hidden geometry?

The word “patch” in this answer refers to a square of terrain. For planets? The base patches on the faces of those cubes that become the planets are always there, as the data might be needed at any moment if one is traveling fast enough. The finer detailed patches are only generated when it’s reasonable for the game to expect you to need that information, depending on your altitude and speed. There might be patch information which would be beyond the horizon and so not needed for rendering in this frame. In this case, the patch is culled from the list of things to render, reducing the work on the GPU.

17) Why are there regions of stars near the core where there are defined lines of difference… i.e. one side dense star fieldother side hardly any stars at all?

A good question; I do see the reddit posts about this one fairly frequently. There are some sectors which have a large density gradient between them. One sector is over a threshold for generating stars of the size that its layer looks after. The neighboring sector may be just underneath this threshold. As this neighbor doesn’t create any systems, it donates its mass to all its child sectors and so creates many bodies. The first sector has made some heavier stars, so donates a lesser amount of leftover mass. The result is that there is an overpopulated sector and an underpopulated sector. Not all cases of this happening were smoothed out before the initial release of Elite: Dangerous, and making any alterations now would upset the proc-gen of the entire Galaxy.

We are aware of it and are still mulling over which direction to take this in.

18) Do you have anything to say on the real life discovery of Trappist-1, with it being so close to the system which the Forge created?

“Well done StellarForge!”? Also, “Well done astrophysics and astronomy researchers! You rock!”

19) I’d love to know how you integrate the catalogued star systems (stuff we see from earth)!

We created a compiler that analyzed the contents of the Hipparcos and Gleise stellar catalogs of the time and created stellar forge system entries from the details. Some entries had the full details of the star, others only the brightness, colour and direction of the star, and others somewhere in between. This compiler would take the available data and fill in the gaps using the same calculations that would be used for proc-gen systems. It would also assign BodyAddress identifiers based on the sector they would be found in. When creating a sector in StellarForge, these “authored” systems are loaded in first, their pre-compiled data taking place of generated results. The authored system also take away the mass designated to the sector, like a generated system would.

The proc-gen systems are created later with the leftover mass. The game then treats the authored and the proc-gen systems identically. As for the contents of the star systems, we have other game data resources which Mike Brookes organised which link to a system for full or partially pre-made system layouts.

20) Will we be getting those high mountains and deep ravines back at some point?

The crazy ravines and mountains (mostly on “Rocky Ice” planets) were quite striking, yes. Unfortunately, they were also causing issues in the creation and handling of the physics mesh that you would drive on (or fly into if distracted). The errors that would be encountered were severe enough to cause a crash (this was seen in public as us pre-emptively kicking you to the main menu on approach to the planet). Removing the crazy examples of ravines/ridges was necessary to:

  • allow the creation of physics patches
  • not be entirely scientifically inaccurate
  • avoid terrain which was sharp enough to look really unpleasantly jagged on VR setting.

There also used to be a few cases of a bug in the noise graph allowing the occasional mountain taller than a planet sustain, taking into account material properties and gravitation. These were just reduced to the maximally supported mountain height for the planet. We want to keep working on the planets and deliver improvements. Official people will say official things when the official time is upon us. For now, the short term work involves revisiting the planet colouration, as per the keynote from FX2017

21) How close was the old Elite 2/3 system generation compared to Stellar Forge? Are there any notable changes compared to David Braben’s original take on it or was he pretty close?

Mr. Braben worked very closely with the team to help ensure the approach was consistent but building upon his systems and that StellarForge covered any additions that were wished for at the time of Frontier and First Encounters. The maths behind the coarse level details of the models of stellar and planetary formation have not changed drastically since the 1990s, and so many calculations would be similar. What has changed is the understanding of things like how common binary pairs are and other statistical particulars.

22) Where does the initial mass component to a galactic sector come from? Real life observation, procedural generation or guess work?

Real life observations give us the approximate mass of the entire galaxy. There are various papers out there, some looking at the orbital velocities of globular clusters in the galactic halo, some trying to count types of stars in a region and extrapolate that across whole arms, some measuring the speed of stars at different orbital radii away from the core. The value we used was taken as an average from available research papers at the time. Observations of our and other spiral galaxies gives us a good idea of the distributions of that mass in 3d space.

23) How does star system naming work?

The unique identifier is transformed into a name. The sector address is encoded into a proc-gen “stellar catalog” name. The sector layer can be encoded in a single letter. Some of the numbers refer to the system within the sector at that layer.

 

Live stream – Discovery Scanner 1

As mentioned on the 3rd November, Frontier will be beginning a new series of live streams. Tonight’s stream can be seen live from 7pm and will essentially be the same talk Dr. Ant Ross gave at the Frontier Expo, but with some more in-game examples and description. You can read more about Dr Ross, here.

“Discovery Scanner is a new Elite Dangerous livestream series where we take deep dives in to the creation of some of Elite Dangerous’s most exciting features and aspects.

“For episode 1 of Discovery Scanner, we’re joined by Programmer Dr Anthony Ross, who will talk us through the creation of the Elite Dangerous galaxy – including how the stellar forge was created. Let’s go behind the scenes like never before.”

Upcoming Livestreams

During a live stream on the 2nd November 2017 Ed Lewis confirmed that at some point during the week beginning the 6th November Ant Ross will talk about the Stellar Forge and how it works. This will be similar to his talk at Frontier Expo. The following week(s) after that there will be feedback live streams with Sandro Sammarco. More details when they are known.