Getting the same. Whats going on Now? It just keeps going!
How about the fact that I have to be online in order to play offline? what kind of Mickey mouse joke is that?
2 Likes
When it’s stable and ready?
2 Likes
I promise you, you DONT want any of the recent updates yet mate. Enjoy your game whilst it still works.
1 Like
All working fine (PC, Private, modded server, EU)
Thanks for the update!
As expected, there was a little lag going in the first time after the server was restarted. I have found that exiting back to the main game menu and jumping right back in (coincidentally?) gets rid of any lag and ‘floating’ immediately.
1 Like
@Illidan @Tovan_MacKelly
We’re aware of this issue and it’s been fixed internally. We’re studying the possibility of releasing a server-side hotfix as soon as possible covering this problem.
3 Likes
PMSL - Here’s a novel idea… Lets try TESTING the patches before throwing them out ???
I swear you guys must think you’re still in Early Access !
3 Likes
With the server update that accompanies this hotfix, whitelisting seems to have stopped accepting SteamID. I can’t find any documentation on this, so with some pointers from the nice community on the Admins United: Conan Discord server, I figured out how to find the Funcom IDs now used for whitelisting (and probably a slew of other things.)
As a server owner, you can find the IDs of a player by following these steps. (This has now been edited twice. Sorry for the confusion. This is all highly strange.)
- Make sure player has tried to join your server.
- Open the relevant log.
- Search for their SteamID.
- From the join attempt line where you find the SteamID, find FLSPlayerIds_TitleID and FLSPlayerIds_MasterID and grab the strings that follow them. (That is, after the equal sign.) These are the new IDs you need to add to whitelist.txt on separate lines. (Yes, both of them. Yes, together with the SteamID.)
Some official documentation on this would be nice.
EDIT: It’s MasterID, not TitleID. My bad. This is all highly confusing.
EDIT OF EDIT: After messing around with this for hours, I have finally come to the same conclusion as BeardyTheGreek (further down.) You need all three IDs for it to work: SteamID, FLSPlayerIds_TitleID and FLSPlayerIds_MasterID, on separate lines in whitelist.txt. At least this works for me so far. I can actually get into the server again.
8 Likes
This problem is still happening. every time i try to enter the server with it running, i get the error message. So I have to close the server in order to log in and open it again.
Cool, scared the 
out of Me! LOL. Good luck on the Hot fix. We will be down until you get it up. 
Server launcher works fine and I can login my server, but I keep getting the following error in the log:
LogNet:Warning: Pong to +++.+++.+++.+++:+++++ failed
LogNet:Warning: Pong to +++.+++.+++.+++:+++++ failed
LogNet:Warning: Pong to +++.+++.+++.+++:+++++ failed
Various IP addresses and port numbers are entered in +++.
Do you know the cause?
Getting this constantly scrolling in my active server - 1 player connected.
[2020.06.29-11.35.41:324][942]LogNet:Warning: Pong to 94.211.125.108:59175 failed
[2020.06.29-11.35.41:658][952]LogNet:Warning: Pong to 109.174.112.249:38987 failed
[2020.06.29-11.35.41:811][955]LogNet:Warning: Pong to 109.174.112.249:38987 failed
[2020.06.29-11.35.41:811][955]LogNet:Warning: Pong to 109.174.112.249:38987 failed
[2020.06.29-11.35.41:812][955]LogNet:Warning: Pong to 109.174.112.249:38987 failed
[2020.06.29-11.35.41:812][955]LogNet:Warning: Pong to 109.174.112.249:38987 failed
[2020.06.29-11.35.41:888][958]LogNet:Warning: Pong to 128.78.165.143:62935 failed
[2020.06.29-11.35.42:254][969]LogNet:Warning: Pong to 83.167.122.67:55046 failed
[2020.06.29-11.35.42:376][972]LogNet:Warning: Pong to 83.167.122.67:55046 failed
[2020.06.29-11.35.42:377][972]LogNet:Warning: Pong to 83.167.122.67:55046 failed
[2020.06.29-11.35.42:377][972]LogNet:Warning: Pong to 83.167.122.67:55046 failed
[2020.06.29-11.35.42:377][972]LogNet:Warning: Pong to 83.167.122.67:55046 failed
[2020.06.29-11.35.43:799][ 13]LogNet:Warning: Pong to 71.220.31.23:63430 failed
[2020.06.29-11.35.43:921][ 15]LogNet:Warning: Pong to 86.14.63.234:63422 failed
[2020.06.29-11.35.43:996][ 18]LogNet:Warning: Pong to 71.220.31.23:63430 failed
[2020.06.29-11.35.43:996][ 18]LogNet:Warning: Pong to 71.220.31.23:63430 failed
[2020.06.29-11.35.43:997][ 18]LogNet:Warning: Pong to 71.220.31.23:63430 failed
[2020.06.29-11.35.43:997][ 18]LogNet:Warning: Pong to 71.220.31.23:63430 failed
[2020.06.29-11.35.44:455][ 31]LogNet:Warning: Pong to 85.2.90.113:52897 failed
PONG? Chinese for PING?
1 Like
But they said it was supposed to come out last week?
25MB - downloading 9999 hours, coz speed is 0, restarted steam - still 0kbps
Why?
Really?! You guys had to mess with whitelisting? No one can connect now because it doesn’t seem to be accepting SteamIDs.
Are you really gonna make server owners manually replace all the SteamIDs to whatever it is you decided to use now? Really!?
3 Likes
@Jingui while waiting … PC Hotfix (29.06.2020) - Server browser, connectivity and Friends List fixes
I’m aware of the work around but this a lot of effin work for things we never asked for! We should not have to do this at all and Funcom needs to be told.
1 Like
Yeah, I wouldn’t be so sure about that one.
1 Like