Unity Issue Tracker - Upgrader-created terrain layers should use a short hash instead of the collection of numbers (to be more file-system safe)

Fixed in 2019.2.X

Votes

Found in

Issue ID

Regression

Upgrader-created terrain layers should use a short hash instead of the collection of numbers (to be more file-system safe)

-

Oct 09, 2018

Steps to reproduce:
1. Open terr-before-2019-1.zip and unzip it
2. In Project window go to Assets\_TerrainAutoUpgrade

Reproducable with: 2018.3.0a1, 2018.2.0b9, 2019.1.0a4

Expected results: No strange files are created
Actual results: Files with long names containing mainly numbers are created in one of the folders

Note: There were terrain changes in 2018.3

Resolution Note (fix version 2019.2):

The files represent the painted terrain materials; previously they were stored internally in the Terrain, but to enable cross-tile painting we broke them out into their own files. For versioning old versions of the Terrain it copies the data out to new files, and has to make up some name for them. It also does this in a way that it can easily figure out if other tiles have the same data painted in them - hence the weird names. Feel free to rename those files and/or move them.

If there is an issue with the names it picks, let us know with some suggestions for a better naming scheme.

tinyzoo

Oct 06, 2020 17:17

I am using 2018.4.23 LTS and would really prefer not to upgrade to 2019 because of the networking components that have been stripped out. But I'm getting some massive filenames in this folder. Here is an example:
_TerrainAutoUpgrade/layer_MudRockyAlbedoSpecularMudRockyNormals(5.000,5.000)(0.000,0.000)(0.000,0.000,0.000),0.000,0.000.terrainlayer.meta

This is causing some very serious issues for my project. Is there a fix for this for 2018 LTS projects? Or is the only recourse to upgrade to 2019?
tinyzoo

Oct 06, 2020 17:05

I am using 2018.4.23 LTS version. I am starting to have some SEVERE issues due to these insanely long file names. I am trying not to upgrade my project at this point because I don't want to break things that I finally got working. Is there any fix for this problem for the 2018 LTS versions? Or is the only fix to upgrade to 2019?