Unity Issue Tracker - Terrain data becomes corrupted after pulling from git remote

Won't Fix

Won't Fix in 2023.3.X

Votes

1

Found in

2019.4.37f1

2020.3.31f1

2021.2.17f1

2021.3.3f1

2022.1.0b13

2022.2.0a8

2022.2.0a17

2022.3.0f1

2023.1.0a1

2023.2.0a1

2023.3.0a3

Issue ID

UUM-3890

Regression

No

Terrain data becomes corrupted after pulling from git remote

Terrain

-

Jun 07, 2022

How to reproduce:
1. Clone the repository (linked in the edit below)
2. Switch to the terrain-origin branch and create a new testing branch based on it
3. Open the Editor
4. In the SampleScene select the Terrain GameObject in the Hierarchy
5. Check if the "Perlin Heightmap" bool is enabled in the Inspector window under the Simple Height Map Updater Script
6. Enter Play mode and observe that Terrain's heightmap is successfully updated
7. Exit the Play mode, save the changes, and close the Editor
8. Commit and push the changes into the testing branch
9. Switch to terrain-origin and then back to the testing branch to pull the Terrain data from the remote
10. Open the Editor and observe the Terrain data object in the Project window

Expected results: After pulling from the remote terrain data remains the same as before switching branches
Actual results: After terrain data is pulled from the origin it becomes broken in the Editor. Uknown errors are also thrown in the Console

Reproducible with: 2019.4.37f1, 2020.3.31f1, 2021.2.17f1, 2022.1.0b13, 2022.2.0a8

Notes:
1. Perling noise-based heightmap is generated using Mathf.PerlinNoise() method
2. The issue occurs with random heightmaps as well, but it occurs less frequently
3. The issue did not occur when generating heightmap using a couple predetermined values. For instance alternating rows of 0 and 1

Resolution Note:

Thank you for bringing this issue to our attention. Unfortunately, after careful consideration, we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues.
We acknowledge that the current Terrain system has a number of limitations, so we are currently investing in a large amount of discovery work to determine exactly what is needed most and how we can bring it to you at the quality level you have come to expect and address the most pervasive pain points in the most effective and efficient manner. However, we know each case is different, so please do continue to log any issues you find, and provide general feedback on our roadmap page to help us prioritize.
Forum to discuss feature requests: https://forum.unity.com/threads/world-building-public-roadmap-and-feature-requests.1437163/
Roadmap: https://unity.com/roadmap/unity-platform/3d-world-building
Resolution Note (2023.3.X):

Thank you for bringing this issue to our attention. Unfortunately, after careful consideration, we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues.
We acknowledge that the current Terrain system has a number of limitations, so we are currently investing in a large amount of discovery work to determine exactly what is needed most and how we can bring it to you at the quality level you have come to expect and address the most pervasive pain points in the most effective and efficient manner. However, we know each case is different, so please do continue to log any issues you find, and provide general feedback on our roadmap page to help us prioritize.
Forum to discuss feature requests: https://forum.unity.com/threads/world-building-public-roadmap-and-feature-requests.1437163/
Roadmap: https://unity.com/roadmap/unity-platform/3d-world-building

Log in to vote on this issue

Search Issue Tracker

1