Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.1.X, 2019.2.X
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2019.1.0b6
2019.1.0f2
2019.2.0a3
Issue ID
1148469
Regression
Yes
Trees are not generated from Code in the Built Game when Terrain Data is created via Code using the Constructor
How to reproduce:
1. Open the "isaac_tree_test" Scene in the attached "New Unity Project.zip" Project
2. Enter Play Mode to see the expected Behavior
3. Build and Run to see the Actual Behavior in the Standalone Build
Expected Behavior: The Trees are added and removed from the Terrain after a couple of seconds
Actual Behavior: The Trees are not generated at all
Reproducible with: 2017.4.26f1, 2018.3.14f1, 2019.1.0b6, 2019.1.0f2, 2019.2.0a3, 2019.2.0a13
Not reproducible with: 2019.1.0b5, 2019.2.0a2
-
isaac-ashdown
May 22, 2019 09:22
Apologies, I see it's marked reproducable in 2019.1.0f2. Ignore my previous comment.
-
isaac-ashdown
May 22, 2019 09:21
This is marked not reproducable in 2019.1.0b5, but the bug still occurs for me in 2019.1.3f1.
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2019.3):
fixed in 2019.3.0a5 backported to 2019.2.0b6, 2019.1.10f1