Jump to content

Sekra

Member
  • Content Count

    10
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Sekra

  • Rank
    Newbie
  1. Sekra

    Critical error loading profile?

    As of around 11:30 today my issues with this have been resolved.. EDIT: Just to clarify, thats 11:30 Helsinki timezone
  2. Sekra

    Critical error loading profile?

    Yeah, you can also find the same errors in the logfiles in the EFT folder. As suggested that using a VPN solves the issue I installed a free (but slow) VPN service and lo and behold not a single error was received in the menus but everything worked slowly so I didnt try to play a match. So this is definitely something that DNA is doing (AGAIN I might add, this is not the first time they've done poo like this and always they deny that anything is wrong on their end) either knowingly or unknowingly. Only thing we can do is call their customer support and complain that whatever they are doing is corrupting the data transfer. Someone needs to remind DNA that this is not Trumplandia and net neutrality has never been on the table in our country. I also made a support request for Tarkov support and they replied that since there is no problem connecting via VPN it's definitely something on our ISP end. EDIT: Also one noteworthy thing that I noticed from the logs is that the game version data verification and login details are transferred via https instead of just http and they seem to work at least for me fast and reliably meaning whatever is corrupting the data cannot interfere with the https transfer which I believe is a testament that it works as intended at least on this case.
  3. Sekra

    Critical error loading profile?

    Well.. I finally actually managed to connect to a match and play, funny part was that I could shoot, walk around, kill, unlock and open doors, get shot and loot bodies completely normally.. but I could not loot a single container in the game.. When I opened a container simply nothing happened. I tried a couple of cases, a safe, a tool case and a medic bag and nothing. And I don't mean the containers were empty, the inventory of the container simply did not open at all.
  4. Sekra

    Critical error loading profile?

    Okay, I just turned off "Web shield" on my Avast Antivirus, and I can now log back in the game at least.
  5. Sekra

    Critical error loading profile?

    Yeah thats a horseshit default answer, nothing to do with the game. And since theres 10+ people here all using DNA complaining the same issue, its obviously between DNA and Tarkov servers. I just ran a tracert to the servers the game is trying to connect to and it seemed to have routing issues connecting to the other server, although eventually it did find a route. First one is fine, as described earlier: Tracing route to 85.195.73.70 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms LEDE.lan [192.168.1.1] 2 12 ms 10 ms 10 ms <removing for my own privacy>.dnainternet.fi [xxx.xxx.xxx.xxx] 3 7 ms 9 ms 7 ms kuo2-sr2.dnaip.fi [62.78.106.170] 4 10 ms 8 ms 12 ms kuo2-tr2.dnaip.fi [62.78.108.70] 5 23 ms 23 ms 21 ms rma1-tr2.dnaip.fi [62.78.107.34] 6 25 ms 21 ms 21 ms tuk2-sr1.dnaip.fi [62.78.104.85] 7 23 ms 22 ms 22 ms s-b5-link.telia.net [80.239.194.178] 8 26 ms 23 ms 22 ms s-bb4-link.telia.net [62.115.119.110] 9 41 ms 49 ms 43 ms ffm-bb3-link.telia.net [80.91.246.212] 10 42 ms 43 ms 43 ms ffm-b7-link.telia.net [80.91.251.54] 11 51 ms 49 ms 49 ms gw-telia.meitner.router.frankfurt.de.velia.net [213.248.79.30] 12 44 ms 45 ms 44 ms 85.195.73.70 Trace complete. The second tracert however, some issues: Tracing route to ns3017017.ip-151-80-109.eu [151.80.109.170] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms LEDE.lan [192.168.1.1] 2 13 ms 11 ms 9 ms <removing for my own privacy>.dnainternet.fi [xxx.xxx.xxx.xxx] 3 11 ms 11 ms 7 ms kuo1-sr1.dnaip.fi [62.78.106.86] 4 8 ms 7 ms 7 ms kuo1-tr1.dnaip.fi [62.78.117.242] 5 21 ms 21 ms 22 ms kuo2-tr2.dnaip.fi [62.78.107.167] 6 23 ms 22 ms 21 ms rma1-tr2.dnaip.fi [62.78.107.34] 7 32 ms 21 ms 22 ms tuk2-sr1.dnaip.fi [62.78.104.85] 8 24 ms 26 ms 24 ms 149.11.164.1 9 24 ms 27 ms 22 ms be3377.ccr22.sto03.atlas.cogentco.com [154.54.36.89] 10 40 ms 37 ms 37 ms be2282.ccr42.ham01.atlas.cogentco.com [154.54.72.105] 11 51 ms 51 ms 49 ms be2816.ccr42.ams03.atlas.cogentco.com [154.54.38.209] 12 59 ms 58 ms 65 ms be12488.ccr42.lon13.atlas.cogentco.com [130.117.51.41] 13 53 ms 61 ms 53 ms be2871.ccr21.lon01.atlas.cogentco.com [154.54.58.186] 14 60 ms 59 ms 64 ms be100-154.ldn-5-a9.uk.eu [94.23.122.201] 15 * * * Request timed out. 16 69 ms 67 ms 68 ms be100-1047.fra-5-a9.de.eu [94.23.122.241] 17 65 ms 90 ms 66 ms be101.sbg-g2-nc5.fr.eu [91.121.215.196] 18 * * * Request timed out. 19 78 ms 70 ms 71 ms be50-7.sbg-4a-a9.fr.eu [188.165.9.72] 20 69 ms 69 ms 69 ms ns3017017.ip-151-80-109.eu [151.80.109.170] Trace complete. Somewhere along this way there are some issues, it takes a while for it to time out the timed out ones too.
  6. Sekra

    Critical error loading profile?

    Same issue, DNA in Finland too..
×
b38e7c858218a416ef714554dce933a2