Search Issue Tracker
By Design
By Design in 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
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
- Motion vectors are displayed when Phong Tessellation is used on the material and Skinned Motion Vectors are enabled on the GameObject's Skinned Mesh Renderer component
- Shader Graph Enum Keywords always select last element in Entries when Stages is set to Fragment and Recursive Rendering is enabled in the Scene
- [Mac] Glitchy visual artifacts appear when moving around a scene with Sphere Handles
- Crash on memcpy_repmovs when selecting NavMesh Agent objects while in Play Mode in a specific scene
- Console shows Exception: {"error":"not found","detail":["not found"]} after opening Build History window
Resolution Note:
Checking the provided scene files, we detected a corruption in the content of the ancestor scene, where the prefab instance pointing to "8883655615442723683" has a duplicate property "m_AnchoredPosition.x".
File: RampVr_01-04_Crew_Stairs.ancestor.unity
Lines: 9560-9569
For this reason, even though the source and destination scenes have solid information, the merging calculation against the ancestor scene fails.
Removing the duplicate property from the ancestor scene makes the merge operation run properly.
Resolution Note (6000.5.X):
Checking the provided scene files, we detected a corruption in the content of the ancestor scene, where the prefab instance pointing to "8883655615442723683" has a duplicate property "m_AnchoredPosition.x".
File: RampVr_01-04_Crew_Stairs.ancestor.unity
Lines: 9560-9569
For this reason, even though the source and destination scenes have solid information, the merging calculation against the ancestor scene fails.
Removing the duplicate property from the ancestor scene makes the merge operation run properly.