Search Issue Tracker
Fixed in 5.3.6
Votes
1
Found in
5.3.4p2
Issue ID
788517
Regression
No
UnityYAMLMerge crashes when given specific scenes to merge
Reproduction steps(Repro gif in the edit):
1) Download and extract users submitted scenes.
2) Import folder with scenes to Unity version of your choice Editor/Data/Tools (for simplicity sake).
3) Shift right click and hit "Open command window here".
4) Copy, paste and run this command:
"UnityYAMLMerge.exe" merge -p "UnityYAMLMergeFail\Base.unity" "UnityYAMLMergeFail\Source.unity" "UnityYAMLMergeFail\Target.unity" "UnityYAMLMergeFail\UnityYAMLMergeFail\Result.unity"
Reproduced with: 5.1.4f1, 5.2.4f1, 5.3.4p2, 5.4.0b13
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment