Page History

...

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="1"
       LogFile="netLog"
       DatestampLog="1"
       ReportSentLetters="1"
       ReportReceivedLetters="1"
       VerboseLogging="1">
 </Network>

This is the configuration you should normally use when testing IPR. Do not set up static port forwarding on your router unless you MUST, as the normal config is what FDev presently want to test.

If you need to use port forwarding to set up a working connection:

<Network
       Port="5100"
       upnpenabled="0"

...

       LogFile="netLog"

...

       RouterPort="5100"
       DatestampLog="1"

...

       ReportSentLetters="1"

...

...

ReportReceivedLetters="1"

...

...

VerboseLogging="1">

...

 </Network>

Then, consult your router's manual on how to set up a port forward to your computer. You want to forward UDP traffic on port 5100 to the computer which runs Elite: Dangerous. Alternatively, you may place your computer in the router's DMZ, although this is considered less secure than forwarding just the port itself. 

Please note that whenever you update your client, you must make this change to AppConfig.xml again, as the update process overwrites the file.

...

• 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)

You will also need to attach your NetLog file for the relevant time period. The Netlog files are stored in the Products\Elite-Dangerous-64\Logs directory on Windows and in the Elite Dangerous/Logs directory on macOS, and are split into parts while your client is running. It is therefore important that you locate the correct file to submit. It should be:

...

• 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 collect the client's netlog?

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

...