Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.2.X, 2017.3.X, 2018.1.X
Votes
0
Found in
2017.3.0f3
Issue ID
990979
Regression
No
UDPClient does mot receive UDP messages in Editor/Build
Steps to reproduce:
1. Open the attached project
2. Open the Main.unity scene
3. Generate UDP messages on the local network using port 11000
4. Play the scene
5. Observe, the console window is empty
Actual results: Console window is empty
Expected results: Console should either spit out the UDP message as a string or an error message
Reproduced with: 5.6.5p1, 2017.1.3p1, 2017.2.1p3, 2017.3.1p1, 2018.1.0b6, 2018.2.0a1
Fixed in: 2018.2.0a5
Backported to: 2017.2.2p2, 2017.4.1f1, 2018.1.0b12
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
Add comment