Transmission not sent: I can't connect with my buddy

widdershins

W
Hey there,

My flatmate and I want to play Elite together. We're playing from the same house, same connection. We're on each others' friends lists, but we cannot contact each other in game. If we invite each other to a Wing, the invitation never comes through. If we try to send text chats to each other, we get the message: "Transmission not sent: Unable to connect to CMDR (our names here)". And if we go to the same station we're never in the same instance.

My buddy, who was playing a bit before he went away for a month (just before the powerplay update came out) says he remembers seeing lots of other CMDRs, but now can't remember seeing any in the last 3 days. Do we have connectivity / router issues? As I said, the weird thing is that when we play, the game shows that each other is playing, and is green in the friends list. But we can't interact in any way.

Does anyone have any suggestions, we're really keen to play together! Many thanks.
 

profitasse

profitasse
A fellow CMDR and I were experiencing the same problem for some time, chatting and winging up never worked (we tried it over a timespan of two weeks) - until we moved rougly 300 ly. Since then, the chat and Wing funcionality works fine for multiple and repeated sessions, so I think it's a localized problem.
Addendum: We are playing in Private Group.
For more details: https://forums.frontier.co.uk/showthread.php?t=159687
 
Last edited:

thearmysredneck

T
Same issue as you OP, except I specifically went and bought a new monitor and purchased another copy of the game so my son and I could "rule the galaxy as father and son"! Create a ticket on the support site. They will most likely ask you to mod your xml and then upload the netlogs. It was easy even for an Ole Mississippi redneck like myself. Here was the reply from the "customer support wing"

Snip..
This is something we're looking into at the moment as it appears this worked fine previous to 1.3.

I've added all the information you've provided to our internal bug reports and have marked your ticket down in my own account so I can get back to you with any updates :)

Thanks for your patience, and for getting all that info to us! It should be super useful.

Regards,
...snip

I figure the more data that can get the faster we can kick off our domination tour.
 

widdershins

W
thearmysredneck said:
Same issue as you OP, except I specifically went and bought a new monitor and purchased another copy of the game so my son and I could "rule the galaxy as father and son"! Create a ticket on the support site. They will most likely ask you to mod your xml and then upload the netlogs. It was easy even for an Ole Mississippi redneck like myself. Here was the reply from the "customer support wing"

Snip..
This is something we're looking into at the moment as it appears this worked fine previous to 1.3.

I've added all the information you've provided to our internal bug reports and have marked your ticket down in my own account so I can get back to you with any updates :)

Thanks for your patience, and for getting all that info to us! It should be super useful.

Regards,
...snip

I figure the more data that can get the faster we can kick off our domination tour.
Click to expand...

OK, thanks for the reply, I'll create a support ticket! All the best.
 

thearmysredneck

T
Also got this when I asked if it might be something on my end...

Unfortunately I think this is a bug that will mean you can't make this work on your end. Something interesting would be if you're able to swap your router for another, different router (and set it up) but that is probably out of the question.

I'll continue to update you if there's any info I receive from the developers :)
 

Skuli

S
thearmysredneck said:
Same issue as you OP, except I specifically went and bought a new monitor and purchased another copy of the game so my son and I could "rule the galaxy as father and son"! Create a ticket on the support site. They will most likely ask you to mod your xml and then upload the netlogs. It was easy even for an Ole Mississippi redneck like myself. Here was the reply from the "customer support wing"

Snip..
This is something we're looking into at the moment as it appears this worked fine previous to 1.3.

I've added all the information you've provided to our internal bug reports and have marked your ticket down in my own account so I can get back to you with any updates :)

Thanks for your patience, and for getting all that info to us! It should be super useful.

Regards,
...snip

I figure the more data that can get the faster we can kick off our domination tour.
Click to expand...

There's something about being on the same lan that keeps this from working. I've never been able to connect with my son from inside our house, but if I connect to a different network (usually my wireless hotspot) it works just fine.
 

tomalus

T
I dont understand, one day I can chat with friends in game, other day I cant, at the moment I cant... Nothing changes on my end.
 

PanPiper.

PanPiper.
Same problem with me,,

No problem with flights with other members of my clan,,just my flatmate,,on same router WiFi.
Worked before last few game updates. Last few weeks of updates can never connect in open or private, at any place in galaxy,yet we both can flight up and chat with other clan members.
Definitely a problem,,but no idea how to work around it.
Hope they can find the issue soon..
 

Dogeh

Dogeh
Add me to that list as well.
Unable to fly with my son, but was able to before. We are on the same network.
Nothing changed on our end.
 

thearmysredneck

T
Just got this today,....
Looks like we have a workaround and a potential fix coming in a future patch. Hooray!

Here's the workaround for now:

Port Forwarding:

First we need to set up port forwarding on your router. As this is a different process for every router please visit PortForward.com and search for you specific model of router. This should guide you through setting up port forwarding and then allow the game to connect to our servers.

You can select any free UDP port to use with the game. Generally we suggest port UDP/5100.

After this has been done, we need to set the port for the game in the configuration files. Open the game folder, which will be something similar: C:\Program Files (x86)\Frontier\Products\FORC-FDEV-D-1010 (the folder and name will vary depending on the version of the game you bought).

Inside the game folder, you should find the file AppConfig.xml. Right click it, select edit and then browse down until you find the network chunk, it should look like this:

Port="0"
upnpenabled="1"
LogFile="netLog"
DatestampLog="1"
ReportSentLetters="1"
ReportReceivedLetters="1"
VerboseLogging="1"

Disable UPnP by setting upnpenabled = "0", then edit the number for the port so that it matches the port you set in your router (Port="5100") and save the file, open the launcher and try to connect to the game.

Alternatively, you can replace your Appconfig.xml with the one I have attached to this ticket which contains the necessary changes.

Hopefully this gets you up and running, you'll need to do this on every PC attached to the network though (sorry) or there will be an update coming out that should fix the issue for you soon (though I don't know when that will be exactly).

Thanks for your patience while we looked into this!

Kind regards,....

Haven't tried it yet but when I get back I'll give it a shot and see what happens.
 

tomalus

T
I solved my problem by enabling UPNP on my router and enabled all traffic for elitedangerous.exe and elitedangerous32.exe in my firewall settings.
 

thearmysredneck

T
thearmysredneck said:
Just got this today,....
Looks like we have a workaround and a potential fix coming in a future patch. Hooray!

Here's the workaround for now:

Port Forwarding:

First we need to set up port forwarding on your router. As this is a different process for every router please visit PortForward.com and search for you specific model of router. This should guide you through setting up port forwarding and then allow the game to connect to our servers.

You can select any free UDP port to use with the game. Generally we suggest port UDP/5100.

After this has been done, we need to set the port for the game in the configuration files. Open the game folder, which will be something similar: C:\Program Files (x86)\Frontier\Products\FORC-FDEV-D-1010 (the folder and name will vary depending on the version of the game you bought).

Inside the game folder, you should find the file AppConfig.xml. Right click it, select edit and then browse down until you find the network chunk, it should look like this:

Port="0"
upnpenabled="1"
LogFile="netLog"
DatestampLog="1"
ReportSentLetters="1"
ReportReceivedLetters="1"
VerboseLogging="1"

Disable UPnP by setting upnpenabled = "0", then edit the number for the port so that it matches the port you set in your router (Port="5100") and save the file, open the launcher and try to connect to the game.

Alternatively, you can replace your Appconfig.xml with the one I have attached to this ticket which contains the necessary changes.

Hopefully this gets you up and running, you'll need to do this on every PC attached to the network though (sorry) or there will be an update coming out that should fix the issue for you soon (though I don't know when that will be exactly).

Thanks for your patience while we looked into this!

Kind regards,....

Haven't tried it yet but when I get back I'll give it a shot and see what happens.
Click to expand...

No joy. Still a nogo
 

thearmysredneck

T
XWaters said:
Ok - this fixed it for me and I had the EXACT same problem.

https://forums.frontier.co.uk/showthread.php?t=153735&page=4&p=2436801&viewfull=1#post2436801

*Don't forget to diisable UPnP in your router settings*! None of the above worked for me before I did that. Also worth trying the DMZ setting mentioned, but when I came to do it over I found disabling UPnP was the deciding factor.
Click to expand...

I'll give that a shot as soon as I get home. What's the dmz and how do I set it up?...oh and I used port 5100 on one machine and 5101 on the other one. I have no clue if 5101 is a port or not but...hey I tried.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom