...
Tip | ||
---|---|---|
| ||
The two most common causes for issues on Xbox are below. It's good to make sure these are resolved early.
|
Xbox Troubleshooting
Info |
---|
If an issue outside our control such as NAT type that can't be corrected or AUS/NZ clients, have the client submit a support ticket to FDev explaining the situation. They will generally fuel the client if we're unsuccessful due to problems that we can't resolve |
Friend Request Notification Not Received | |||
---|---|---|---|
Step | Possible Causes | What to Confirm | Possible Solution |
1 | Known Xbox Issue of notifications not appearing | Client has sent friend request | Rat needs to manually add client (i.e. reverse FR) |
2 | Client and rat have not sent each other friend requests | Confirm that client and Rat have each sent friend requests and the Rat has the client as a Favorite | Client changes friendship status of the Rat to “Favorite” |
3 | Xbox Live Server Issues | Xbox Live services are operational http://support.xbox.com/xbox-live-status | Reschedule rescue until Xbox Live services are fully functional |
...
Rat and/or Client Name Not Showing on Comms Panel | |||
---|---|---|---|
Step | Possible Causes | What to Confirm | Possible Solution |
1 | Client and rat have not sent each other friend requests | Confirm that client and Rat have each sent friend requests and the Rat has the client as a Favorite | Client changes friendship status of the Rat to “Favorite” |
2 | Online Safety and Privacy settings prevent multiplayer gaming | Account Settings > Online Safety and Privacy Settings are Set to Adult Default | Client changes Online Safety and Privacy Setting to Adult Default. Client can change the settings back after the rescue if they're concerned about security/privacy. It's critical that this is set correctly, even just "hiding friends" is known to cause issues with the comms panel. A full reboot of the Xbox may be required for the change to be reflected (including pulling the power cord from the Xbox) |
NAT Type | Network Settings > Network, NAT Type is Open | Client and/or rats with moderate/strict NAT Type hard reboot their Xbox including pulling the cord for 10 seconds | |
Client and/or rats reconfigure their router for port forwarding or place the Xbox in the DMZ http://forums.xbox.com/xbox_support/networking-hardware/default.aspx | |||
Confirm that no other Xbox’s are connected to the Network and reboot the Client or Rat’s Xbox | |||
If NAT type can't be corrected, have the client submit a support ticket to FDev explaining the situation. They will generaly generally fuel the client if we're unsuccessful due to problems outside our control. | |||
Geographic | Geographic location of client and rat(s) are compatible (i.e. US/US, EU/US) | Reschedule the drill and attempt with different rats from the same region | |
3 | Miscellaneous | In game text comms work | Rat invites client to wing (i.e. reverse wing) |
Rat jumps to another system or drop to normal space and back to supercruise | |||
Have the client SC Hop and attempt to wing from local. If that doesn’t work have the Rat follow the client and drop manually on their low wake |
Wing Invites are Immediately Cancelled | |||
---|---|---|---|
Step | Possible Causes | What to Confirm | Possible Solution |
1 | Online Safety and Privacy settings prevent multiplayer gaming | Account Settings > Online Safety and Privacy Settings are Set to Adult Default | Client changes Online Safety and Privacy Setting to Adult Default. Client can change the settings back after the rescue if they're concerned about security/privacy. It's critical that this is set correctly, even just "hiding friends" is known to cause issues with the comms panel. A full reboot of the Xbox may be required for the change to be reflected (including pulling the power cord from the Xbox) |
NAT Type | Network Settings > Network, NAT Type is Open | Client and/or rats with moderate/strict NAT Type hard reboot their Xbox including pulling the cord for 10 seconds | |
Client and/or rats reconfigure their router for port forwarding or place the Xbox in the DMZ https://support.xbox.com/en-US/xbox-one/networking/nat-error-solution | |||
If NAT type can't be corrected, have the client submit a support ticket to FDev explaining the situation. They will generaly generally fuel the client if we're unsuccessful due to problems outside our control. | |||
Geographic | Geographic location of client and rat(s) are compatible (i.e. US/US, EU/US) | Reschedule the drill and attempt with different rats from the same region | |
2 | Miscellaneous | Chain wing client and rat using another rat or friend of the client | |
Attempt to wing with client from Local contacts in supercruise | |||
3 | Unknkown Bug | Unknown at this time |
Rat Can’t Instance with Client | |||
---|---|---|---|
Step | Possible Causes | What to Confirm | Possible Solution |
1 | General Instancing | n/a | Follow standard instancing SOP: SC Hop, Manual, wingless, Voice Comms, Assign Additional Rats as appropriate |
2
| Online Safety and Privacy settings prevent multiplayer gaming | Account Settings > Online Safety and Privacy Settings are Set to Adult Default | Have client change their Online Safety and Privacy Settings to “Adult Default” and hard reset their Xbox |
NAT Type | Network Settings > Network, NAT Type is Open | Client and/or rats with moderate/strict NAT Type hard reboot their Xbox including pulling the cord for 10 seconds | |
Client and/or rats reconfigure their router for port forwarding or place the Xbox in the DMZ http://forums.xbox.com/xbox_support/networking-hardware/default.aspx | |||
Confirm that no other Xbox’s are connected to the Network and reboot the Client or Rat’s Xbox | |||
If NAT type can't be corrected, have the client submit a support ticket to FDev explaining the situation. They will generaly generally fuel the client if we're unsuccessful due to problems outside our control. | |||
3 | Geographic | Geographic location of client and rat(s) are compatible (i.e. US/US, EU/US) | Reschedule the drill and attempt with different rats from the same region |
If the client is AUS/NZ or we're otherwise unable to instance with them, have the client submit a support ticket to FDev stating that they contacted us and we were unable to instance. In the past FDev support have refueled the client when we were unable to |
...