...
| Table of Contents | ||
|---|---|---|
|
| Info | |||
|---|---|---|---|
| |||
Significant network changes have been implemented in E:D 2.2.03/1.7.03. This should help improve instancing. Now that this is deployed to live, we need further data on any instancing problems, so they can hunt down any other bugs that are still lurking. Please ensure your client is set up for IPR reporting, and report ALL instancing problems. |
| Info | ||
|---|---|---|
| ||
FDev have opened up for XBox IPR reports, and will be looking into server-side logs for reported instancing problems. Please see below for information on what you need to report when instancing fails on XBoxFDev has implemented a method to provide more verbose logs directly to their systems in the Beta now going live. Rats with Beta access, if you could head on to the beta and do some running around, and try some rescue scenarios, that would be great. Any time you fail to instance with another rat or 'client', hit Ctrl-L to generate a logfile on FDev's servers. Also, please report it on the IPR Jira, but you do not need to include netlogs. Please mark it as a Beta case in the summary and attach the beta label. Note that the Ctrl-L logging function has a one hour cooldown between uses. There is a battery of tests here you can run in beta with fellow rats. |
Preparing your Elite: Dangerous client for IPR
...
The section you are looking to replace is the Networking section. Replace it with the following:
<Network
upnpenabled="01"
LogFile="netLog"
DatestampLog="1"
ReportSentLetters="1"
ReportReceivedLetters="1"
VerboseLogging="1">
</Network>
...
Provide too much information rather than too little, but try to keep to relevant information to the instancing problem, not to the rescue itself.
Xbox IPR reporting
FDev have opened for XBox instance problem reporting, and will be checking server side logs for when we run into problems there. There are a few important points to remember when it comes to XB reporting.
- You will not have a NetLog to submit, as XBox does not produce these. Ignore the request to upload them.
- Please include your NAT type in the report
You must be ready to provide the following information:
- Your CMDR name
- The client's CMDR name
- The system the rescue happened in
- The approximate time the instancing failed in GMT/UTC (The in-game clock is UTC, you may use that as reference)
- Did you see the wing beacon only when you dropped to normal space?
- Were you able to send and receive text comms with the client?
- Did the wing iconography show the client as destroyed even if they weren't?
- Did supercruise hop or a restart alleviate the problem?
- Were you altogether unsuccessful with instancing with the client?
- Did you have instancing problems with any of the other rats?
- Did you see the client or other rats in Supercruise?
- Did you have a successful party chat with the client/other rats?
Ensure that you set the Platform correctly to Xbox.
Create an Instancing Problem Report
...