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
- "No HDR monitor detected." warning is shown in the Rendering Debugger even when the Editor is on HDR-enabled monitor
- Shader Graph Enum Keyword Default Value changes after reordering Entries
- Light Explorer throws “ArgumentException” error when disabling all columns from the Multi-column panel context menu
- "Freeze Camera For Culling" options are inconsistent between the Game view overlay and Rendering Debugger window
- Crash on GetOriginalSourceOrVariantRoot when creating a scene from a specific template
Add comment