Update 18.01

Paul_Crowther

Senior Community Manager
Frontier
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.
 
Maybe, at some time, by any occasion, we could get them (and maybe other decals?) in black, like the ship name and ID?

OjjFvHbK_o.png
 
Last edited:
I entered the game shortly after I posted that. Everything running smotthly for me. Even the loading of the title screen happened surprisingly quick.

Looks like the hamsters had finished their lunch break and had a coffee.
YMMV I guess. Still sits at a black screen for three minutes for me and now also getting CTDs.
 
I'm not sure if the recent release did that... but looks like 3a pre-engineered FSD (from the old CG) is no longer applicable to the experimental effect implementation... but I strongly remember it was and I have other sizes with experimental applied.

should I report a bug? or that is a known one?
 
Looks like titans are still bugging out with all vents blue and no pineapple. Can just sit there and listen to the audible cues the titan makes when preparing to open and then opening the vents and the vents just remain blue and un-targetable. Over and over.
 
Looks like titans are still bugging out with all vents blue and no pineapple. Can just sit there and listen to the audible cues the titan makes when preparing to open and then opening the vents and the vents just remain blue and un-targetable. Over and over.
 
Are we allowed to question if the Titan’s anti-Guardian field still remaining active but then oddly stopping once you get closer to the Titan is intentional?

(And that the ‘Thargoid Titan’ state still remains active anyway, plus hyper/interdictions. I’m not sure the fleet has really abandoned the system yet …)
 
I don’t know if anyone else has this problem, but I’ve had this problem for over a year now!!
this is on all ships!!
1) this bug affects only the lightest colors, such as white or chrome
2) the ship must not be lit by a star
 

Attachments

  • Cobra mk3.jpg
    Cobra mk3.jpg
    238.3 KB · Views: 146
  • Imperial cutter.jpg
    Imperial cutter.jpg
    177.3 KB · Views: 147
Last edited:
This is where a public test environment that always has verbose logging enabled might be helpful.
 
I don’t know if anyone else has this problem, but I’ve had this problem for over a year now!!
this is on all ships!!
But your screenshots don’t explain the problem. That ships have the vehicle hangar model visible when they don’t have one equipped?
 
Hey guys, it looks like the update is not working. Titan is bugged even more than before I tired playing today, and almost all the instances were getting bugged before I could finish my ammo.
 
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.

Issue Tracker https://issues.frontierstore.net/issue-detail/63585
 
Back
Top Bottom