Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.2.0a1
Issue ID
911500
Regression
No
Remote profiling Networking should have a warning
Steps to reproduce:
1. open attached project
2. build and run
3. connect host and client together
4. use the profiler in window to connect to standalone and editor
Expected: profiler should either support remote profiling for networking or show a message that it is not supported
Actual: Network profilers are empty
*video attached. At first it is profiling standalone and no input -> profiler editor works -> profile standalone no more entries recorded
Tested on: 2017.1.0b5
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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Resolution Note:
Mass closure of UNET Bugs.
As UNet is Deprecated we are moving to low maintenance mode, where critical issues can get fixes.
Closing this bug as part of cleaning-up the Bug List.
If you feel this bug is really a road-blocker, you can reopen the bug and we will work this one.