Search Issue Tracker
Fixed in 2018.1.X
Fixed in 2017.1.X, 2017.2.X, 2017.3.X
Votes
1
Found in
Issue ID
975920
Regression
Yes
[VCS] LightingData.asset files getting marked as text files in Perforce
Reproduction Steps:
1) Open the attached project
2) Connect the project to a Perforce server
3) Select all assets in the Project and "Version Control" -> "Mark Add"
4) In Unity choose to "Reimport All"
5) Check the P4V client, pending changelist and check the filetype of the "Assets/bob/LightingData.asset".
6) The filetype should be "binary" but it will be "text"
Reproduced with: 2017.2.0p1, 2017.2.0p4, 2018.1.0b1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
- Inconsistent hotkeys in the Terrain tool with the "Terrain Tools" installed and not installed
- "DebugAllocatorMode" option changes when changed in another Editor instance
Add comment