Search Issue Tracker
Fixed in 2021.3.46f1
Fixed in 2021.3.X, 2022.3.X, 6000.0.X, 6000.0.25f1, 6000.1.0a1
Votes
0
Found in
2021.3.42f1
2022.3.42f1
6000.0.15f1
Issue ID
UUM-77908
Regression
No
UnityYAMLMerge cannot open files when using long file paths on Windows
How to reproduce:
1. Make sure long file paths are enabled
2. Extract SceneFile.zip file to a directory structure that exceeds the default Windows character limit
3. Run UnityYAMLMerge with "[PathToEditor]\Editor\Data\Tools\UnityYAMLMerge.exe" merge [PathTo]SceneFile.unity [PathTo]SceneFile.unity [PathTo]SceneFile.unity
Expected result: No errors are thrown
Actual result: “Can not open file “ error is thrown
Reproducible with: 2021.3.42f1, 2022.3.42f1, 6000.0.15f1
Reproducible on: Windows 10
Not reproducible on: No other enviroment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Play Mode framerate drops significantly when moving the mouse cursor with high polling rate
- Create workspace does not update the Unity Version Control and Branch Explorer windows leading to multiple clicks on “Create workspace” which throws an “already exists” error when Creating a workspace with the Branch Explorer window open
- Default and Result encoding properties have blank dropdowns by default when opening the Unity Version Control Settings
- Crash on "StoredGraphicsBuffer::GetGfxBufferID" when activating VFX via extention of Activation Track in Timeline window
- [Linux] Stack trace file path and line number information is missing when IL2CPP Stacktrace Information is set to "Method Name, File Name, and Line Number"
Add comment