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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment