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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment