I can't activate the tracker, I've already tried to re-install, Offline mode, etc etc etc. Help
Printable View
I can't activate the tracker, I've already tried to re-install, Offline mode, etc etc etc. Help
Ive heard from others and I too am having the same issue, ERROR: SOCKET_TIMEOUT
I'm also having this problem, started a couple of days ago, running the current (2/16/2021) version of Recursion and Windows, it was working fine one night, then the next day i started getting this error and haven't been able to fix it, Offline mode doesn't work, running the program in admin mode didn't work either, tried reinstalling, also didn't work. I'm not sure of what else to do to try and remedy the issue, any help would be appreciated.
The stat tracker uses the Planetside 2 Census API servers for its sessions. It's literally how it correctly tracks the various kills you make.
But those API servers are managed by DBG, not Recursion.
And the API servers are currently having some problems, so we're stuck waiting on DBG to fix it. Not much we can do till then.
Thanks for the explanation!
Is this not what offline mode is for though? I thought that would work if the servers were, you know, offline.
If I recall correctly, 'offline mode' just means not needing to use the Recursion login servers for your stat tracker sessions (which severely reduces how many features you're able to have in a stat tracker session, compared to online mode); the PS2 Census API servers themselves would still need to be up and running.Quote:
Originally Posted by astag
Planetside 2 is currently under maintenance though (started at 4:30 AM Pacific Standard Time, estimated duration of 6 hours). Hopefully, the API will be fixed once DBG brings the game servers back online.
The other stat sites that I know of (Fisu, Voidwell, etc.) are working fine now, post-maintenance (they were having issues before). It's just Recursion that is still having issues, as such I have a feeling that it won't get fixed until DBG is told specifically where the problem lies. Is there any way a Recursion coder could tell DBG just which process is broken/needs to be restarted?
Just tossing out ideas here. I miss the Recursion in-game stats window!
I enabled the debug log, here's what startup looks like:
Code:17-Feb-2021 3:42:20 PM Loading Cookies...
17-Feb-2021 3:42:20 PM ...Cookies Loaded
17-Feb-2021 3:42:21 PM Saving Cookies...
17-Feb-2021 3:42:21 PM ...Cookies Saved
17-Feb-2021 3:42:21 PM Microsoft Windows NT 6.3.9600.0 x64
17-Feb-2021 3:42:21 PM Running application...
17-Feb-2021 3:42:21 PM Loading component: C:\Program Files (x86)\Recursion\RecursionTracker\Settings\ComponentSettings.xml
17-Feb-2021 3:42:21 PM Component loaded
17-Feb-2021 3:42:21 PM Loaded components.
17-Feb-2021 3:42:23 PM Start loading all items cache
17-Feb-2021 3:42:23 PM Finished loading all items cache
17-Feb-2021 3:42:24 PM An error has occurred:
An error has occurred: A call to SSPI failed, see inner exception.
at System.Net.Security.SslState.InternalEndProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.Security.SslState.EndProcessAuthentication(IAsyncResult result)
at System.Net.Security.SslStream.EndAuthenticateAsClient(IAsyncResult asyncResult)
at SuperSocket.ClientEngine.SslStreamTcpSession.OnAuthenticated(IAsyncResult result)
for me too it's always inactivable recursion don't want to connect anymore it's boring its removing all the charm of PS2 !!!:emot-f5:
I'm no longer getting Socket_Timeout, now i'm getting Player_Missing
Tested again today. Still can't start a session, but the error message is different now.
"ERROR: PLAYER_MISSING"
As of 2/19/21, I still get ERROR: SOCKET_TIMEOUT
Same here; it went back to the first error.Quote:
Originally Posted by Test1fy
Possibly obvious question here, but do we know if anyone has submitted a bug report or something to DBG about this? I.E., does DBG even know that something is wrong on their end? I'd submit something, but I have no clue how to describe what's wrong.
DBG are the equivalent of a chicken with its head cut off. The majority of the IP (intellectual property) has pretty much left the studio. Typically, when a software company publish an API, they provide some kind of SDK (software development kit) or integration standards that help developers actually leverage the API.
The documentation that I'm aware of is incredibly dated. I think what we're seeing here is updates are being made to the game with very little understanding of the impacts to the API (IP walking out the door). Considering 3rd party products that depend on that API are tertiary at best from a priority standpoint, I don't see this getting fixed any time soon.
Once DBG either resolve the mismatch they've introduced in the API or provide updated documentation for folks like Recursion to modify their code or config, this is going to persist.
I would recommend everyone just open a ticket in the DBG support portal and complain about it. The more squeaky the wheel, the quicker it'll get oiled :).
Okay, I've been in touch with one of the stat tracker devs. No ETA on a possible fix, but they're looking into it.
Some of the stat tracker libraries are quite old, and might actually be part of the problem here.
Well... That was quick... Recursion is now working for me!!! Yay!
Yup. Fix is now live. For anyone else reading here: Use the update feature on the client.Quote:
Originally Posted by squirt
Full credit goes to "lllSilencerlll", the main developer for the Recursion stat tracker client.