Search Issue Tracker
Fixed
Fixed in 2022.3.70f1, 6000.0.63f1, 6000.2.14f1, 6000.3.0f1, 6000.4.X, 6000.4.0a6, 6000.5.0a2
Votes
0
Found in
6000.0.61f1
6000.2.11f1
6000.3.0b9
6000.4.0a4
Issue ID
UUM-126068
Regression
Yes
UnityYAMLMerge fails to merge on some computers when some specific files are used
How to reproduce:
1. Extract the attached “LaptopPC.zip“
2. Run the Command Prompt as administrator
3. In the Command Prompt, navigate to the folder where “LaptopPC.zip“ was extracted
4. In the Command Prompt, enter DoEverything.bat and execute it
5. Follow the instructions in the Command prompt
Expected result: After “replay_merge.bat” is run, the MergeTool window appears
Actual result: After “replay_merge.bat” is run, the MergeTool window does not appear, and the result_replay.asset is empty
Reproducible with: 6000.0.61f1, 6000.1.0a1, 6000.2.11f1, 6000.3.0b9, 6000.4.0a4
Not reproducible on: 2023.1.0a1, 6000.0.23f1 (1c4764c07fb4)
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Notes:
- Make sure Perforce is installed
- The issue reproduces only on some computers, even with the same Perforce version
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Add comment