Update 18.01

"WarDoggo, post: 10328222, member: 231634"

Any word on if this patch will also fix the bug not allowing CMDRs to apply an Experimental Effect to the 5A Pre-Engineered FSD?

This update fixes the issues listed in the notes. We do continue to investigate other reported issues, but this update resolves those specifically mentioned.

There will be a small update, around the 250MB mark.

"Factabulous, post: 10328237, member: 72134"

250M - HUGE decal (y)

Actually we've just added in my latest mix tape. It's six hours of incoherent screaming. I expect it to do well in the charts.

Greetings Commanders, We will be releasing Update 18.01 on Thursday 7th March to resolve some issues during the usual Thursday maintenance. Downtime is expected to be approximately 3 hours. Release Schedule:

• 5AM UTC - In game broadcasts begin
• 7AM UTC - Downtime commences
• 10AM UTC - Update 18.01 releases and servers back online

Update Notes

• A fix for Titan vents becoming stuck and the core not being exposed. A nice amount of WD40 can solve many issues.
• A fix to stop Titan cores becoming exposed multiple times when vents are blocked. The cores will now be a little more reserved.
• Fixed instances of incorrectly triggering Titan behaviour post destruction. They won't show off quite as much when they are supposed to be having a bad time.

Keep an eye on this thread and our social channels for updates!

"texasp8, post: 10328218, member: 101746"

Thursday 7th Paul. I blame the Thargoids.

"HEBELEHUBELE, post: 10328790, member: 299417"

The bugs on Titan still persist, vents and core are stuck

Would you be able to enable netlogs and report the issue on the Issue Tracker? In order to tell Elite Dangerous to create a Netlog file you will need to perform the following steps: If you are currently playing the game please select Save and Exit to exit to the main menu. This will allow you to access the Network section of the Options menu.

• Open the Network options menu.
• Set the option labelled Logging to On.
• Save and exit to desktop

Please access your AppConfig.xml which be found in the projects folder where you installed the game and open this in Notepad. You'll see a block near the bottom named "Network". Please insert the following lines somewhere in that block - ReportSentLetters="1" ReportReceivedLetters="1" VerboseLogging="1" Any new network logs produced will now include more detail, which will help us with our investigation. Please attempt to recreate this issue in-game and then attach the corresponding network log so we can check it out. AppConfig file location (default): C:\Users\username\AppData\Local\Frontier_Developments\Products\elite-dangerous-odyssey-64 Netlogs location (default): C:\Users\username\AppData\Local\Frontier_Developments\Products\elite-dangerous-odyssey-64\Logs Once you have encountered this issue and have sent us the logs in your report, feel free to remove the line of code from the AppConfig file.

"Kzak, post: 10328670, member: 56644"

The Leigong titan is down to 10 controlled systems now.

Servers are coming back online now and the Update is available. Please allow a little time for servers to coax some of the hamsters back into action before you panic they aren't back up.

Missions should be working correctly now. If you are still having issues after restarting can you share in here.

Can you check that you have 'Shader Preparation on Startup' in your 'options->Display' set to 'on'.