ED Odyssey Taupe/Gold Cobra Errors

sirpuma

sirpuma
For the past couple weeks I've been playing Odyssey heavy during exploration out in the south end of the galaxy. About 60% of the time, when I transition from ship or SRV to foot I get a Gold Cobra error. If I then try to reconnect I get Taupe Cobra error. It's incessant. If I land and walk away from my computer for a couple minutes, say to get a drink or hit the bathroom then come back and go to disembark, bam error. The only way I can get back into the game is to completely exit the game back to the launcher, then restart the game. This is extremely frustrating to say the least. Does anyone know (F-Dev?) what is going on? It would be nice to know if it's just me or my ISP connection or what.

Sir Puma
 

Attachments

  • 20220101145732_1.jpg
    20220101145732_1.jpg
    39.7 KB · Views: 169

sirpuma

sirpuma
It would have been nice to get some help with this. Odyssey is completely unplayable for me now. Every 3-5 minutes, usually when transitioning between ship/SRV/foot I get these errors and have to completely exit the game to be able to play again. I'm beginning to regret my decisions to buy and support this version.
 

STRONTIUM DOG

STRONTIUM DOG
Amazon ecs servers = :poop:
enjoy your musical chairs server type game where a group may have low server bandwidth for a while?
rather than expand with demand they seem to shrink!
try deleting your gpuworktable.xml from your projects folder just to make sure nothing nasty in the cache
but my guess is its the servers and may be little pot luck for a while as to stability
 

sirpuma

sirpuma
Factabulous said:
What did Support say when you contacted them OP?

www.pixelbandits.org

Elite Dangerous - Error codes and fixes

If you recieve an error code in Elite Dangerous, it can be tough to know what it means. Find out here with descriptions and suggested fixes
www.pixelbandits.org www.pixelbandits.org
Click to expand...
Their wiki explains the colored ship errors and basically I need to check out my router. I did recently get a new one designed for VPN so it could be a setting in there that is causing troubles with the choppy way Odyssey handles data transfers.
 

sirpuma

sirpuma
I went through the wiki steps and finally resolved to submit a ticket. Not sure where it will go. But I went though my router and there was nothing configured that could interfere. But I also didn't have the UPnP set up or port forwarding. So I went through those steps and still get the error.
 

sirpuma

sirpuma
I've had this problem for over a month and just now turned on dual IPv4/IPv6. As a test of the router I'm going to swap back to my previous one and see if I get the errors.
 

sirpuma

sirpuma
So I put in my old router and rand Odyssey flawlessly. So there's something with the new router that the game doesn't like. While IPv6 is enabled on both computer and router and I have an IPv6 address, the game itself doesn't recognize it's on. Also, with the new router UPnP is enabled, but the game doesn't see it. But the fact the game works fine (so far as I've seen) on the old router tells me I just need to work with FDev Techs to configure the new router. It has a few improved features like VPN support, so there's probably something I need to set up.
 

GroG79

G
I reads like you need to contact your ISP. The new modem is faulty or you need help setting it up correctly.

VPNs do not improve your connection btw.
 

sirpuma

sirpuma
Not running a VPN yet. The router was in it's default state, meaning no special configurations at all. I'm sure it's just something I need to configure in the router to make it work with the game. I've submitted a ticket and I'm hoping the Frontier techs can help me get it configured. I'm hoping so, anyway. Yesterday in the span of a couple hours the game crashed with a Gold Cobra connection error 7 times.
 

Caydran

Caydran
sirpuma said:
Not running a VPN yet. The router was in it's default state, meaning no special configurations at all. I'm sure it's just something I need to configure in the router to make it work with the game. I've submitted a ticket and I'm hoping the Frontier techs can help me get it configured. I'm hoping so, anyway. Yesterday in the span of a couple hours the game crashed with a Gold Cobra connection error 7 times.
Click to expand...
OP, I see the issue here.

1) You should use IPv6 on your router, but to get Elite to use it, you need to edit a file or two.
2) VPN is good, but you should try with and without it to see any difference, once you have turned on IPv6 in Elite.
3) Never, Never, Ever use UPnP. Turn it off on the router. Repeat after me, turn UPnP off....
4) You should use port forwarding and set it in your router. It should be your game machine's ip, 192.x.x.x with a port of 5100 to 5100 << (UDP/TCP, Both)

Now, to turn on IPv6 for Elite, find these files.
Odyssey "X:YourGamePath\Elite Dangerous\Products\elite-dangerous-odyssey-64\AppConfigLocal.xml"
Horizons "X:\YourGamePath\Elite Dangerous\Products\elite-dangerous-64\AppConfigLocal.xml"

In notepad, open "AppConfigLocal.xml". It should look like this:

<?xml version="1.0" encoding="UTF-8" ?>
<AppConfig>
<Network
Port="5100"
IPv6="1"
IPv4="1"
IPv6Port="0"
ReportSentLetters="1"
ReportReceivedLetters="1"
VerboseLogging="1"
UseNicGuid="{9999999999999999999999999999}" />
<Journal Address="0.0.0.0" Port="0" />
</AppConfig>

Now, change the lines in your "AppConfigLocal.xml" in YELLOW for Odyssey to match the lines above.

Don't cut and paste the above, edit your copy of the file for Odyssey.

You can edit the one for Odyssey and copy it to Horizons. Both Odyssey and Horizons will use IPv6 and the port 5100 you set up in your router for portforwarding.

EDIT: Also look at your "AppConfig.xml" file at the same paths above. Here are the correct settings for this file. It is present in both Horizons and Odyssey and can be edited in one and copied to the other.

<Network
LogToDebug="1"
Port="5100"
Upnpenabled="0"
LogFile="netLog"
MaxUpRate="750000"
DatestampLog="1"
ProtocolOffset="0"
InternalProd="false"
BytePadding="3"
Oodle="OodleDictionary4.bin"

I moved my "MaxUpRate" to 750000 for faster sends to the server. This is the speed of Elite's upload data to the Frontier Server. Works like a charm.

As a result, I don't get colored ship error codes, unless Amazon AWS is toasting things.

Hope this helps.....
 
Last edited:

sirpuma

sirpuma
Paul Eddington said:
OP, I see the issue here.

1) You should use IPv6 on your router, but to get Elite to use it, you need to edit a file or two.
2) VPN is good, but you should try with and without it to see any difference, once you have turned on IPv6 in Elite.
3) Never, Never, Ever use UPnP. Turn it off on the router. Repeat after me, turn UPnP off....
4) You should use port forwarding and set it in your router. It should be your game machine's ip, 192.x.x.x with a port of 5100 to 5100.

Now, to turn on IPv6 for Elite, find these files.
Odyssey "X:YourGamePath\Elite Dangerous\Products\elite-dangerous-odyssey-64\AppConfigLocal.xml"
Horizons "X:\YourGamePath\Elite Dangerous\Products\elite-dangerous-64\AppConfigLocal.xml"

In notepad, open "AppConfigLocal.xml". It should look like this:

<?xml version="1.0" encoding="UTF-8" ?>
<AppConfig>
<Network
Port="5100"
IPv6="1"
IPv4="1"
IPv6Port="0"
ReportSentLetters="1"
ReportReceivedLetters="1"
VerboseLogging="1"
UseNicGuid="{9999999999999999999999999999}" />
<Journal Address="0.0.0.0" Port="0" />
</AppConfig>

Now, change the lines in your "AppConfigLocal.xml" in YELLOW for Odyssey to match the lines above.

Don't cut and paste the above, edit your copy of the file for Odyssey.

You can edit the one for Odyssey and copy it to Horizons. Both Odyssey and Horizons will use IPv6 and the port 5100 you set up in your router for portforwarding.

EDIT: Also look at your "AppConfig.xml" file at the same paths above. Here are the correct settings for this file. It is present in both Horizons and Odyssey and can be edited in one and copied to the other.

<Network
LogToDebug="1"
Port="5100"
Upnpenabled="0"
LogFile="netLog"
MaxUpRate="750000"
DatestampLog="1"
ProtocolOffset="0"
InternalProd="false"
BytePadding="3"
Oodle="OodleDictionary4.bin"

I moved my "MaxUpRate" to 750000 for faster sends to the server. This is the Up/Down speed of your internet connection. Works like a charm.

As a result, I don't get colored ship error codes, unless Aazon AWS is toasting things.

Hope this helps.....
Click to expand...
Thank you for the insight. I will most definitely look at that.
 

sirpuma

sirpuma
Paul Eddington said:
OP, I see the issue here.

1) You should use IPv6 on your router, but to get Elite to use it, you need to edit a file or two.
2) VPN is good, but you should try with and without it to see any difference, once you have turned on IPv6 in Elite.
3) Never, Never, Ever use UPnP. Turn it off on the router. Repeat after me, turn UPnP off....
4) You should use port forwarding and set it in your router. It should be your game machine's ip, 192.x.x.x with a port of 5100 to 5100.

Now, to turn on IPv6 for Elite, find these files.
Odyssey "X:YourGamePath\Elite Dangerous\Products\elite-dangerous-odyssey-64\AppConfigLocal.xml"
Horizons "X:\YourGamePath\Elite Dangerous\Products\elite-dangerous-64\AppConfigLocal.xml"

In notepad, open "AppConfigLocal.xml". It should look like this:

<?xml version="1.0" encoding="UTF-8" ?>
<AppConfig>
<Network
Port="5100"
IPv6="1"
IPv4="1"
IPv6Port="0"
ReportSentLetters="1"
ReportReceivedLetters="1"
VerboseLogging="1"
UseNicGuid="{9999999999999999999999999999}" />
<Journal Address="0.0.0.0" Port="0" />
</AppConfig>

Now, change the lines in your "AppConfigLocal.xml" in YELLOW for Odyssey to match the lines above.

Don't cut and paste the above, edit your copy of the file for Odyssey.

You can edit the one for Odyssey and copy it to Horizons. Both Odyssey and Horizons will use IPv6 and the port 5100 you set up in your router for portforwarding.

EDIT: Also look at your "AppConfig.xml" file at the same paths above. Here are the correct settings for this file. It is present in both Horizons and Odyssey and can be edited in one and copied to the other.

<Network
LogToDebug="1"
Port="5100"
Upnpenabled="0"
LogFile="netLog"
MaxUpRate="750000"
DatestampLog="1"
ProtocolOffset="0"
InternalProd="false"
BytePadding="3"
Oodle="OodleDictionary4.bin"

I moved my "MaxUpRate" to 750000 for faster sends to the server. This is the Up/Down speed of your internet connection. Works like a charm.

As a result, I don't get colored ship error codes, unless Aazon AWS is toasting things.

Hope this helps.....
Click to expand...
My AppConfigLocal.XML doesn't have the UseNicGuide line.

Do you think that will cause a problem?

MaxUpRate was already 750000

Interestingly, even though I went through your setup, the game network settings still indicate IPv6 is disabled. Wonder if it matters.
 
Last edited:

Caydran

Caydran
The "UseNicGuid" should be a long number assigned to your active NIC by the game from the Windows active network. If it is not there, then Elite does not know of your NIC. I do not know how this is generated (automatically by the game) and I assume it is done by the installation, but I have never seen an AppConfigLocal.xml without one. It's definately needed, I'm starting to wonder if your installation of the game may be corrupt, with the problems you describe.

For me, my installation is somewhat complicated, as I purchased the game directly from the Frontier Store. Since this purchase also gave me a license key available from Steam for a Steam install, I let Steam install the game, and then let the Frontier installer overwrite the Steam installed path with the Frontier installation, maintaining the Steam path.

Also note, that the Frontier Store purchase was done many years ago, and the purchase and installations have changed over the years, so my installation is unique.

So, for my installation, either Frontier or Steam can update my game, but my game depends on the "Frontier Client Launcher", which I can launch without the need to launch the Steam Client first. I doubt this makes much since to you. In short, I bought Elite from Frontier and the Frontier store, which gave me a copy through Steam, but rather than play from Steam, I chose to play from Frontier, but installing it as if it were bought from Steam. The main point is to use the Frontier Launcher, not the Steam Launcher.

For me, all of this works well, network, Steam Updates and Frontier Launcher.

Depending on when and where you purchased your game may dictate how it should be installed. If it was purchased from Epic, I have no idea how folks install that. As well, many folks have Alt accounts (more than one account and install path for each) and great care must be taken to install each correctly. So, it may be worth the effort to research your game purchase, i.e. Steam, Epic, Frontier, and determine the best way to install it. Should you decide to reinstall, make sure you back-up your Journal Directory as well as your current bindings. With these safe, you can restore your history and controller settings.

In conclusion, it sounds like you may need to re-install from scratch, backing up Journals and Bindings, and then deleting all Windows paths for Eilte Horizons and Odyssey.

EDIT: In my listing of "AppConfigLocal.xml", I filled the "UseNicGuid" with 9's as this is private information, not to be broadcast to a public forum.

Hope this helps.
 
Last edited:

sirpuma

sirpuma
I understand what you're saying perfectly. I've had that multiple install source before on other games, though ED I only purchased through Steam.
 

Caydran

Caydran
sirpuma said:
My AppConfigLocal.XML doesn't have the UseNicGuide line. (Very strange. I have never seen this file without one. You need to fix this somehow, maybe a re-install?)

Do you think that will cause a problem? (Absolutely, since you are having network disconnects. Without it, Elite does not know about your NIC)

MaxUpRate was already 750000 (Mine was 250000 before I changed it. Must be default now.)

Interestingly, even though I went through your setup, the game network settings still indicate IPv6 is disabled. Wonder if it matters. (It does not matter if your game does not use IPv6. This will only allow a secondary connection to Frontier Servers. Elite will run without it, but it's nice to have if it can be made available.)
Click to expand...
 

Caydran

Caydran
My recommendation would be to find and back-up your Journal files and your current Bindings to a safe location, then delete all paths in Windows related to ED. I use "Registry First Aid" to do this, but "CCleaner" may work as well.

EDIT: Uninstall both Horizons and Odyssey in Steam and then clean up the registry with the tools listed above, before moving the Steam Client, instructions below.

If you have your Steam client installation on C: Drive, under Program Files, It would be my recommendation to move it to a secondary drive, like D:\, both to save space on C: Drive and to maintain a known install path for Steam games and Elite in particular. Steam will allow you to move the Steam Client and all the game in it to a different drive.

Moving Steam to a different drive. "D:\SteamLibrary\steamapps\common\Elite Dangerous".

It would also be nice if you have an SSD or an NvMe with a different partition for Steam, instead of Program Files, i.e. "D:\SteamLibrary"

After you have backed-up your Journals, Bindings and cleaned the system of paths, to do a fresh Steam reinstall for Horizons and Odyssey. Once complete, put back your Journals and Bindings and then look at the "AppsConfigLocal.xml" files for the correct parameters.

Hope this helps.
 
Last edited:

sirpuma

sirpuma
I have very few programs (usually only system programs) I install on C:. I maintain several physical drives for making sure I don't lose data. Haven't been able to afford SSDs yet, maybe this summer.
 
You must log in or register to reply here.
Back
Top Bottom