Hi,
Since API was updated after 2.17 version the server connection is taking way too long to establish connection.
In 2.17 PhotonNetwork.ConnectUsingSettings(); Takes around 1-2 seconds to connect. Any version after 2.17 taking around 15 seconds.
Using PUN2 free v2.41 . (Same happens in 2.4)
Could you please make any clearness on this, is it something related to free version on recent updates?
I don’t know why this pops up after the update but I guess this is related to figuring out the best region to connect to. All regions gets pinged 5 times and if there are a lot, this adds up.
Which platform do you build for and on which Editor version and platform do you get these results?
Make sure the “Best Region Summary” is being saved and used in subsequent starts of the app. If you maybe clean all Player Prefs, this would be gone. If it’s present, in best case you only ping one region (to confirm it’s still fast)…
Hi Tobias,
Refreshing the player prefs and making new best region summary doesn’t make any changes. Editor version is 2020.3… (subversion was changed several times, the problem is present on any engine version).
Platform is Windows build Il2CPP.
With or without photon Server Settings has fixed region set to “ru” (for some reason it’s a best one), it’s anyway connecting quite long time. If I replace 2.41 folder with Photon 2.17 the problem is gone, it’s connecting to server in a click with or without fixed region.
Can you try with a new blank project the photon demo scene ?
I use the version v2.40 (22. November 2021) in two of my games with Unity 2019.4.0f1 and i do not have this issue. (i use fixed region).
Hi,
I have tried 2.41 with a fresh project and there is no problems with connection, at least demos are working fine.
What could be the problem then? Cache?
Alright, looks like I was able to isolate this issue.
After replacing my old PhotonServerSettings.asset with the one from a fresh project it works fine now.
There is only one difference I’ve noticed. The port is now 0, (which is correct according to tooltip) In previous settings port was 5050, as I was testing onpremise server.
Looks like 2.17 didn’t react on specified port like it does newer versions.
The problem is now solved, thank you for the help!
Oh, this was with a local server? And you had a port set? Sorry you ran into that.
Yes, a while ago, we applied to port value properly, no matter if you use a Name Server or not (you should always use one, even for self hosted Photon Server v5).
Glad you could solve this.