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
- [HDRP] Decal Projector with layer mask "nothing" doesn't affect transparent objects when Decal Layers are disabled in frame settings
- "MonoBehaviour.OnApplicationQuit" is still called when quitting is canceled by “Application.wantsToQuit“ returning false
- [2D SG/VFX] Surface options are not shown in Output Inspector when 2D Sprite SG is assigned to VFX
- Collisions are incorrectly registered when setting a joint motor every frame causes
- Terrain shadows flicker while moving the Camera in the Player when Terrain contains GPU instanced materials
Resolution Note (fix version 2019.3):
2019.3.0f6
Resolution Note (fix version 2018.4):
2018.4.18f1