Elite Dangerous | Trailblazers Update 2 - Wednesday March 19

Greetings Commanders,

We will be releasing a new update for Elite Dangerous on Wednesday March 19.

Release Schedule (All times in UTC)
  • 9AM - Servers offline for maintenance
  • 11AM - Servers back
Please be aware these are estimated times and are subject to change.

Update Notes

Features of Note/Journal Additions
  • A temporary system has been introduced relating to "System Claim Unsuccessful" errors - after one such unsuccessful claim, the system will be marked as invalid and no further claim attempts will be permitted.
    • This is a known issue which is caused by the game being unable to locate a suitable position for the initial starport, which can occur for many different reasons. Repeated claim attempts by any player on an affected system will never result in success.
    • As these positional issues are resolved, affected systems will be removed from the invalid list and will once again be claimable.
The following Journal entires are now actually logged:
  • The powerplay data in the event "Location" and "FSDJump" supplied regards of if the players is pledged to a power or not.
  • "PowerplayCollect"
  • "PowerplayDeliver"
  • "PowerplayMerits"
  • "PowerplayRank"
  • "CarrierLocation"
  • Added a new status flag for the npc crew to indicate if they're active or not.
  • Added a new status flag SupercruiseOvercharge for overcharge status.
  • Added a new status flag SupercruiseAssist for whether assist is active.
  • Ensured that the lightsOn status flag is active when the flashlight is active.
Community Goal
  • The new megaships from the recent Community Goal will be deployed with the update

Bug Fixes:
  • Fixed a crash when switching views in the System Map
  • Fixed an instance of a mission interaction crash
  • Fixed instances of crashes when scanning a megaship or installation
Server side improvements:
  • Renaming of facilities should be now be consistently permitted for the system architect
  • Planetary ports can now be renamed by the system architect
  • Inactive system colonisation ships will now be marked as they jump back to the registration origin system
  • Star system information will now be updated correctly when completing facilities with differing game language settings
  • Improved stability of game client during system colonisation ship jumps
  • Significantly improved capacity for server-client information transfer relating to player colonised systems
    • This is intended to prevent any further instances of temporarily deactivating the colonisation contact. The team will continue to monitor the situation closely as humanity expands.
If you encounter any further issues please be sure to report them on our Issue Tracker.
Paul_Crowther
I'm a bit uncomfortable bringing this up, but could you advocate for the idea that tritium should be automatically taken from the Fleet Carrier's cargo hold without the need for an intermediary like the Type-9? 🫣
 
Paul_Crowther
I'm a bit uncomfortable bringing this up, but could you advocate for the idea that tritium should be automatically taken from the Fleet Carrier's cargo hold without the need for an intermediary like the Type-9? 🫣

Or that a future update can allow folks to buy a FC module that auto replenishes from the cargo hold. Call it an Advanced Refuelling Service if you will, and it replaces the standard refuel option and takes the same space but has a slightly higher weekly upkeep. That way folks who need the function can have it, and the folks who want a bare bones carrier don't have to pay for the extra.
 
Greetings Commanders,

We will be releasing a new update for Elite Dangerous on Wednesday March 19.

Release Schedule (All times in UTC)
  • 9AM - Servers offline for maintenance
  • 11AM - Servers back
Please be aware these are estimated times and are subject to change.

Update Notes

Features of Note/Journal Additions
  • A temporary system has been introduced relating to "System Claim Unsuccessful" errors - after one such unsuccessful claim, the system will be marked as invalid and no further claim attempts will be permitted.
    • This is a known issue which is caused by the game being unable to locate a suitable position for the initial starport, which can occur for many different reasons. Repeated claim attempts by any player on an affected system will never result in success.
    • As these positional issues are resolved, affected systems will be removed from the invalid list and will once again be claimable.
The following Journal entires are now actually logged:
  • The powerplay data in the event "Location" and "FSDJump" supplied regards of if the players is pledged to a power or not.
  • "PowerplayCollect"
  • "PowerplayDeliver"
  • "PowerplayMerits"
  • "PowerplayRank"
  • "CarrierLocation"
  • Added a new status flag for the npc crew to indicate if they're active or not.
  • Added a new status flag SupercruiseOvercharge for overcharge status.
  • Added a new status flag SupercruiseAssist for whether assist is active.
  • Ensured that the lightsOn status flag is active when the flashlight is active.
Community Goal
  • The new megaships from the recent Community Goal will be deployed with the update

Bug Fixes:
  • Fixed a crash when switching views in the System Map
  • Fixed an instance of a mission interaction crash
  • Fixed instances of crashes when scanning a megaship or installation
Server side improvements:
  • Renaming of facilities should be now be consistently permitted for the system architect
  • Planetary ports can now be renamed by the system architect
  • Inactive system colonisation ships will now be marked as they jump back to the registration origin system
  • Star system information will now be updated correctly when completing facilities with differing game language settings
  • Improved stability of game client during system colonisation ship jumps
  • Significantly improved capacity for server-client information transfer relating to player colonised systems
    • This is intended to prevent any further instances of temporarily deactivating the colonisation contact. The team will continue to monitor the situation closely as humanity expands.
If you encounter any further issues please be sure to report them on our Issue Tracker.
Can you confirm please if the Journal Manual is being updated to V38 with specifics of the journal changes.
 
Greetings Commanders,

We will be releasing a new update for Elite Dangerous on Wednesday March 19.

Release Schedule (All times in UTC)
  • 9AM - Servers offline for maintenance
  • 11AM - Servers back
Please be aware these are estimated times and are subject to change.

Update Notes

Features of Note/Journal Additions
  • A temporary system has been introduced relating to "System Claim Unsuccessful" errors - after one such unsuccessful claim, the system will be marked as invalid and no further claim attempts will be permitted.
    • This is a known issue which is caused by the game being unable to locate a suitable position for the initial starport, which can occur for many different reasons. Repeated claim attempts by any player on an affected system will never result in success.
    • As these positional issues are resolved, affected systems will be removed from the invalid list and will once again be claimable.
The following Journal entires are now actually logged:
  • The powerplay data in the event "Location" and "FSDJump" supplied regards of if the players is pledged to a power or not.
  • "PowerplayCollect"
  • "PowerplayDeliver"
  • "PowerplayMerits"
  • "PowerplayRank"
  • "CarrierLocation"
  • Added a new status flag for the npc crew to indicate if they're active or not.
  • Added a new status flag SupercruiseOvercharge for overcharge status.
  • Added a new status flag SupercruiseAssist for whether assist is active.
  • Ensured that the lightsOn status flag is active when the flashlight is active.
Community Goal
  • The new megaships from the recent Community Goal will be deployed with the update

Bug Fixes:
  • Fixed a crash when switching views in the System Map
  • Fixed an instance of a mission interaction crash
  • Fixed instances of crashes when scanning a megaship or installation
Server side improvements:
  • Renaming of facilities should be now be consistently permitted for the system architect
  • Planetary ports can now be renamed by the system architect
  • Inactive system colonisation ships will now be marked as they jump back to the registration origin system
  • Star system information will now be updated correctly when completing facilities with differing game language settings
  • Improved stability of game client during system colonisation ship jumps
  • Significantly improved capacity for server-client information transfer relating to player colonised systems
    • This is intended to prevent any further instances of temporarily deactivating the colonisation contact. The team will continue to monitor the situation closely as humanity expands.
If you encounter any further issues please be sure to report them on our Issue Tracker.
We need the demolish facility button, and boosted insulating membrane production. Please.
 
doing a dance while there is a maintenance
zuraraBYE.gif
 
Nice to see that things get fixed! Good work!

Personal wishlist:

1. Bug Fix: Placement of construction sites near the sun places somewhere else in the system
2. "Undo Construction" button
3. "Cancel Colonization" button to stop colonization of new system.
 
Back
Top Bottom