Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
2018.3.0a2
Issue ID
1051655
Regression
No
[Improved Prefab] 2018.3: Speed trees on terrain are not rendered in prefab editor
Speed trees on terrain are not rendered in prefab editor and assertion failed error spams console
Steps to Repro:
1. Create a new or open attached project
2. Hierarchy > right click
3. 3D Object > terrain
4. drag and drop terrain in the project window to create a prefab
5. Select the prefab and click "Open Prefab" button
6. Select 'Paint Trees' tab > edit tree
7. Add a speed tree
8. Paint trees on the terrain
Actual Result:
1. Painted speed trees the in prefab editor
2. Assertion failed error spams console on painting speed trees
Expected Result:
1. Painted speed trees should be visible in prefab editor
Note:
1. If a game object is added in place of speed tree it is rendered
2. Heightmaps, textures, detail texture and meshes are getting rendered
Environment:
Windows and Mac
Occurring with:
2019.1.0a10, 2018.3.0b11, 2018.3.0a2 (e9113db2e9bf Branch: prefabs/improved)
Stack Trace:
Assertion failed on expression: 'probeSetData.identifier.IsValid()'
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
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Resolution Note (fix version 2019.1):
Speed Trees are now rendering on the terrain in prefab editor