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
- AI Assistant upgrade banner's `Open package Manager` link doesn't work
- Sub-asset UI does not refresh when undoing Renderer Feature add or remove actions in a URP Renderer asset
- Scene flickers with a green tint when using Screen Space Ambient Occlusion and Contact Shadows with raytracing
- Scripts with null Components on GameObjects are not removed when calling GameObjectUtility.RemoveMonoBehavioursWithMissingScript
- Color Curve Key values remain visible after changing Curve type
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.