Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0b2
Issue ID
905325
Regression
Yes
[Regression][FrameDebugger] SpeedTree preview is pink and corrupted in Frame Debugger
Steps to repro:
1. Open attached project and 't1' scene;
2. Open Frame Debugger (Window -> Frame Debugger);
3. Expand any event that renderers SpeedTree mesh (e.g. DepthPass.Job);
5. Select any draw call under this event (e.g. Draw Mesh Conifer_Desktop_LOD0);
6. Open Preview tab of Frame Debugger window;
7. Observe tree rendering.
Expected result:
SpeedTree mesh renders in white color and is consistent with mesh preview (see attached expected.png screenshot).
Actual result:
SpeedTree mesh is pink and corrupted (see attached actual.png screenshot).
Regression introduced in Unity 2017.1.0b2.
Notes:
- Reproducible in 2017.1.0b2;
- Not reproducible in 2017.1.0b1, 5.6.0p3, 5.6.0f3, 5.5.2p1;
- Reproducible on Windows 10 and OSX 10.12.3;
- Reproducible in both Editor and Standalone build;
- Reproducible only for SpeedTree models, not reproducible for simple primitive meshes.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment