Search Issue Tracker
Won't Fix
Votes
1
Found in
2021.3.32f1
2022.3.14f1
2023.2.1f1
2023.3.0a15
6000.0.37f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
Issue ID
UUM-57048
Regression
No
Perforce serializes Prefabs with the "CLRF" line feed when pulling the project
How to reproduce:
1. Create a new project with any template
2. Change Version Control Mode to “Perforce” (Edit > Project Settings > Version Control)
3. Setup and connect to a Perforce VCS server
4. Create a new Cube GameObject (GameObject > 3D Object > Cube)
5. Save the GameObject as a Prefab
6. Check Out and Submit all the changes (Edit > Project Settings > Version Control > “Check Out”)
7. Pull the project into a different folder
8. Open the “Cube.prefab” Asset in a text editor program
9. Observe the line feed characters
Expected result: The line feed characters are in UNIX-like style - “LF”
Actual result: The line feed characters are in Windows-like style - “CLRF”
Reproduced with: 2021.3.32f1, 2022.3.14f1, 2023.2.1f1, 2023.3.0a15
Reproduced on: Windows 10 (by reporter), Windows 11
Not reproducible on: No other environment tested
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note:
We will revisit this issue in six month, and we will take it into account for the next P4 plugin iteration, potentially allowing the user to choose the line endings for their files.
Resolution Note:
We will revisit this issue in six month, and we will take it into account for the next P4 plugin iteration, potentially allowing the user to choose the line endings for their files.