Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
5.4.1f1
Issue ID
851278
Regression
No
[VCS] Asset which has binary TerrainData as sub-asset shows up as text in p4v
Steps to reproduce:
1. Setup perforce server and workspace
2. Move attached TerrainTest project to workspace and open it using editor
3. Enable VCS in project and verify that Asset Serialization is forced to text
4. In top menu, click "Test/Add". This will create new Test.asset file and move New Terrain asset as a sub-asset of created object
5. Open p4v and notice that Test.asset is marked as <Text>
Doesn't happen with default terrain data file - only reproducible when it's moved to be a sub-asset.
Reproduced with: 5.4.1f1, 2017.3.1p3, 2018.1.0b9, 2018.2.0a2
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