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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Add comment