Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.7.0
Issue ID
NCCBUG-223
Regression
No
Client connects in version .21 and will not connect in .22
1. What happened
I upgraded my working project from .21 to .22 and the client will no longer connect.
I have been working with NoelStephens on this issue and he requested I submit the issue as a bug.
Please contact NoelStephens in regards to :
https://forum.unity.com/conversations/netcode-nt-tick-duplicate-server-already-sent-an-update-on-tick-0-and-is-attempting-to-send-agai.627754/#message-1299190
2. How can we reproduce it using the example you attached
Run Host on LAN
Attempt to connect client via IP
Failed connection no error messages otherwise
associated.
Note: No CQA testing was carried out.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
This was a user support issue that was resolved by modifying their startup code for the host to include the ServerListenAddress:
==================================
if (!bConnected)
{
GameObject.FindAnyObjectByType<vfMPConnecting>().MakeVisible(true);
UnityTransport ut = NetworkManager.Singleton.GetComponent<UnityTransport>();
ut.ConnectionData.Address = sIp;
// Add this to your script
ut.ConnectionData.ServerListenAddress = sIp;
ut.ConnectionData.Port = iPort;
==================================