Summary
Branching & Revision Control Feedback
Branching and Revision Control are amazing concepts, and the practical use of them on paper is really good. However, after using them for a while, we’ve found that the actual execution has been much worse than expected.
The biggest issues we’ve experienced are loading times, quality of life, and, most importantly, overall stability.
Whenever we merge branches, it can take significantly longer than expected and often leads to unexpected errors or issues that are difficult to understand. We’ve encountered multiple situations where something should have worked after merging, but didn’t.
For example, I changed a variable in a UMG. A teammate then synced and merged the branch, so the variable should have been available in their project. However, it wasn’t, which caused an error. We eventually had to resolve it by committing the change out and then compiling before everything started working correctly.
These kinds of issues happen randomly and make the workflow much more error-prone. Combined with the long loading times and the amount of troubleshooting required after merges, it negatively impacts the overall developer experience.
Developer Experience Feedback
My main suggestion for improving the overall experience would be to add notifications when someone checks in or commits changes to a branch.
Currently, there’s no clear notification when someone makes changes to another branch, which makes it difficult to know when new changes are available and when you should sync or merge.
Overall, Branching and Revision Control are great ideas, but the current implementation needs significant improvements in stability, performance, error handling, and communication between team members.
Please select what you are reporting on:
Creative
What Type of Bug are you experiencing?
Lore
Steps to Reproduce
Merge
Expected Result
Good loading times, with everything compiling in the correct order: assets first, then Verse.
Observed Result
One issue we’ve noticed is that Verse sometimes doesn’t detect newly changed assets correctly when working with Branching and Revision Control.
For example, we’ve had situations with UMG where a variable was changed, but after the other person synced and merged the branch, the change simply wasn’t there. This can lead to random errors that are difficult to understand or reproduce.
We’ve also had issues where changes either don’t sync properly or don’t appear at all, and sometimes the only way to fix them is to delete the .lore file and re-sync/compile everything.
On top of that, the loading times when syncing or merging branches are extremely long. These delays and issues generally don’t happen when everyone is working on the same branch.
Overall, the concept is great, but the combination of Verse not detecting new asset changes, UMG changes not syncing correctly, random errors, needing to delete .lore files, and very long load times makes the workflow much less reliable than simply working on the same branch.
Platform(s)
PC
Island Code
5791-2777-2631
Upload an image
Additional Notes
Loading speed was better in the previous version.