Search Issue Tracker
Active
Under Consideration for 6000.5.X
Votes
0
Found in
6000.0.65f1
6000.3.3f1
6000.4.0b3
6000.5.0a4
Issue ID
UUM-131076
Regression
No
"vector<bool> too long" error is thrown when using UnityYAMLMerge
Reproduction steps:
1. Open Command Prompt
2. Use “cd“ to navigate to the “ReproProj“
3. Run command: "<EDITOR LOCATION>\Data\Tools\UnityYAMLMerge.exe" merge RampVr_01-04_Crew_Stairs.ancestor.unity RampVr_01-04_Crew_Stairs.source.unity RampVr_01-04_Crew_Stairs.destination.unity
Expected result: YAML Merge resolves conflicts
Actual result: Prompt with text “vector<bool> too long“ is present
Reproducible with: 6000.0.65f1, 6000.3.3f1, 6000.4.0b3, 6000.5.0a4
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
- Text Script Importer Reference button links to a Missing Page when clicking the Reference Button in the Inspector
Add comment