UUM-126068
Fixed in 6000.2.14f1Mentioned in 32 Unity 6 release notes.
First fixed in 6000.2.14f1 (Nov 26, 2025); relisted in 31 later releases.
| Version | Section | Risk | Impact | Note |
|---|---|---|---|---|
| 6000.5.0b8 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.5.0b7 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.5.0b6 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.5.0b5 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.5.0b4 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.5.0b3 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.5.0b2 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.5.0b1 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.5.0a9 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.4.0f1 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.5.0a8 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.4.0b11 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.4.0b10 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.4.0b8 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.4.0b9 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.5.0a7 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.5.0a6 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.4.0b7 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.4.0b6 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.4.0b5 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.5.0a5 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.4.0b4 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.5.0a4 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.4.0b3 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.4.0b2 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.5.0a3 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.4.0b1 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.4.0b1 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.3.0f1 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.3.0f1 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.0.63f1 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. | |
| 6000.2.14f1 | Fixes Version Control | Fix | UnityYAMLMerge tool was adding long path specifiers to the file paths passed to the fallback merge tools, causing p4Merge to fail. |