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
- "SupportsRandomWriteOnRenderTextureFormat()" shows "False" when executed on 2023.2 and 6000.0 streams
- Size of ShadowCaster2D with Casting Source set to a Collider increases when RigidBody2D is attached to the GameObject
- GameObjects with a material derived from a Custom Lighting Surface Shader are displayed as skewed on quads when the Camera's Width and Height properties of the Viewport Rect are lower than 1
- Warning 'Unable to find player assmebly' is thrown when building some Project Templates
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
Add comment