Since the last update, Autosaving will fire up URC and it would get stuck on the “updating” window for around 20 seconds to 5+ minutes (I stopped counting at 5 mins), freezing UEFN in the process. This also happens if you duplicate an asset or generally do any action that will fire up URC and it will have to update. Below I filmed a video where I caught it loading for around 12-13 seconds (didn’t start filming straight away so it was more). You can be working on Live edit, then autosave in UEFN will fire up, and editor will disconnect for 5-6 mins just to do an autosave. Meaning this is a blocker now and we cannot use URC since last update. Please test on large projects before shipping new versions of the tools, the stalling has been there almost for 6 months and made worse now.
On another occasion, while deleting a floor in live edit, Autosave fired up in UEFN and FN hard crashed (no errors, app closed), logs: 7c70fbd0-42cd-6af6-682a-9fb5bb5ba179
@Wertandrew Thank you very much for reporting this issue and spending the time to capture these videos to provide us additional context on the experience. We apologize for the additional friction it is causing, and we have a fix for this issue that will ship with the next release of UEFN.
If you are blocked in the meantime, the best mitigation to prevent the frequency of this long dialog will be to disable URC while working and re-enable when you’re ready to check-in changes or sync a new snapshot. Please know that turning on/off URC frequently comes with additional risks including the following:
Ending up in states of conflict with your collaborators since you’ll be working without a connection to the server and therefore will not receive warnings if you’re editing something someone else has checked out
Since the revision control provider is a global setting on the project, turning it off for you will set it as off for any other collaborators as well and vice-versa, which risks confusion if multiple people are changing it frequently.
Thanks again for your help, and we look forward to getting the fix in your hands soon.
Thanks for the extra clarifications, the part that turning off affects others I didn’t know. I did notice a peculiarity with that actually, which I noted in this ticket: URC checks in an actor/device even when disabled
Hey @Wertandrew just following up to let you know that earlier today we released 28.30 in which this issue should be fixed.
Since I know you were encountering some delays even before this bug, I can’t say for sure whether those will also be resolved yet (we likely have some more optimization to do there yet), but the acute problem that was causing especially long delays in 28.20 is fixed.