Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.6.0b1
Issue ID
861451
Regression
Yes
[Regression] Profiler is not attached to standalone build after building project with profiling in Standalone option enabled
Profiler is not attached to standalone build after building project with profiling in Standalone enabled
Steps to repro:
1. Open Unity;
2. Open attached project and 'test' scene;
3. Select File -> Build Settings;
4. Check 'Development Build' and 'Autoconnect Profiler';
5. Click Build and Run;
6. Run the compiled build;
7. Observe the Profiler window in Editor.
Actual result:
Profiler does not display any data associated with runtime build. See attached video.
Regression introduced in Unity 5.6.
Expected result:
Profiler should display runtime data when profiling in standalone is enabled in Build Settings.
Workaround is to click Profile Editor button in Profiler window one or more times.
Notes:
- Reproducible in 5.6.0b1;
- Not reproducible in 5.6.0a6, 5.6.0a5, 5.6.0a4. 5.5.0p1;
- Reproducible on Windows 10 and OSX 10.12.1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “3.3.0.37 has a regression: newly created C# files are not added in the project” text is not aligned in the Package help box
- UI Toolkit Editor Window Creator becomes deformed and stretched when the “Enter” key is pressed
- “Assertion failed on expression: 'IsFinite(distanceForSort)’” is spammed in the Console when changing Trail GameObject position to a very high number
- VFX Graph Node documentation icon is pixelated
- Cutout box is covered in a shadow when the object that houses the cutout is casting shadows
Add comment