Major Issues with New Version of Revision Control (URC2)

General Issues and Bug Reporting
, , ,
21

Thanks everyone - these are great.
Full log files would help as well to give us the full context of what’s going on.

22

{448A145A-3290-489E-84DB-5122E683993E}
Its usage is keep going up

23

Sure, where can i find it?

24

@OMkrouger see my post above: Major Issues with New Version of Revision Control (URC2) - #15 by wouter

25

Here’s my log file

UnrealRevisionControl.log (16.4 MB)

26

UnrealEditorFortnite.log (1.3 MB)

27

This is so frustrating. When can we expect a fix?

28

any way to check in changes currently? would love to not have to upload the project to google drive every time..

29

{F6381413-122F-4C59-9D41-CDF925361CD1}
{F6381413-122F-4C59-9D41-CDF925361CD1}1131×231 38.6 KB

this is the error im getting when trying to check in

30

I think the weird snapshot number increase might be related to this (I have around 60 commits but the last commit says its snapshot number +2000). Every snapshot skips around 100/200 numbers for some reason.

31

UnrealRevisionControl.log (2.3 MB)

Failed to push revision to remote branch HEAD

32

This is actually expected @frozenarctic.

33

I am getting the same failed error message as the other people how can I fix this?

34

Hi everyone, I heard from one of the team and I’m passing along the message.

  • We’ve mitigated the core issues reported with the editor hanging/revision control operations erroring and are continuing to investigate the root causes to ensure this does not happen again
    • If you’re continuing to experience issues, please let us know, and when you do, please zip up and include your logs, which can be found at C:\Users[USER]\AppData\Local\UnrealEditorFortnite\Saved\Logs
  • We have optimizations to improve check-in and save times coming in the next release (36.20) to further mitigate some of the other issues that were reported in the forum/twitter threads.
5 Likes
35

@supreeeeemeeeee - For future reference: [FORUMS] Editing Bug Reports Causes Escalation Issues

This couldn’t be escalated by the automatic bug reporter because you changed the first post.

Thank you!

1 Like
36

Thanks @Flak. I will keep that in mind for future posts :grinning_face_with_smiling_eyes:

1 Like
37

Ahh, I see, it wasn’t posted in the bug report forum. Moving!

38

(post deleted by author)

39

(post deleted by author)

40

Revision control update is a major downgrade, push changes gets stuck on various tasks and takes much longer to get into a session which was already 35+ minutes for us.

Push verse changes is at least 10x longer due to validation. This is super painful.