Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.3.X
Votes
0
Found in
2018.4.0f1
2018.4.2f1
2019.2.0a1
2019.3.0a1
2020.1.0a1
Issue ID
1182142
Regression
No
Unable to control to which PC the Player connects when using 'Autoconnect Profiler'
Steps to reproduce:
1. Create a new project
2. Build a Standalone player with 'Autoconnect Profiler' enabled
3. Open Profiles on two different PC/Mac connect on the same network
4. Launch Player. Notice that it connects to two different Editors. (it might take ~5 sec)
If the issue isn't reproducible
5. Manually connect to the player on the second PC
6. Close Player
7. Open Player
Expected results: Player connect to one Editor
Actual results: Player connect to several different Editors
Reproduced with: 2020.1.0a4, 2019.3.0b3, 2019.2.4f1, 2018.4.9f1
Note:
- In 2017.4 other PC/Mac can not find the player.
- The issue is reproducible if two PC/Mac are connected to the same WiFi network.
- The issue is not reproducible if one PC/Mac is connected to LAN and other to WiFi
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
- [RenderingDebugger][InputSystemPackage] Ctrl+Backspace shortcut doesn't work to open the Rendering Debugger when New Input System is in use
- No option to skip video transcoding when launching a Project
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
- Symbolic links disappear when a .xcframework file is added through the Unity Editor
- Errors regarding importing occur upon opening a project when the "Library" folder is deleted
Resolution Note (fix version 2019.3):
2019.3.0f6
Resolution Note (fix version 2018.4):
2018.4.18f1