URC2 restores deleted empty folders

General Issues and Bug Reporting
, , ,
1

Summary

I started a new project and noticed a very annoying behavior with URC2. After deleting a folder and pushing some changes (note that deleting folders isn’t even recognized as a change), urc2 will restore the deleted empty folder

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

UI/Tools

Steps to Reproduce

  • create a folder with some asset in it
  • push the changes
  • delete the folder with the asset
  • push the changes

Expected Result

All deleted folders should remain deleted and never be automatically restored.

Observed Result

Deleted folders always reappear no matter how often one tries to delete them

Platform(s)

UEFN (v36.20)

2

+1 that does sound very annoying

3

FORT-936486 has been created and its status is ‘Unconfirmed’. This is now in a queue to be reproduced and confirmed.

4

Thanks for the report @Velocity_Zero, we are investigating this issue.

1 Like
5

Could it be linked with this somehow ?

This report i made and is a bug imo yet it says its not getting fixed ???

Just feels like something could be connected

6

Is there any resolution to this problem on the horizon? My project is plagued by old empty folders. Not only folders in the content browser, but also folders inside __ExternalActors__ and __ExternalObjects__.

7

Just wanna say im seeing this now its creating empty folders

8

+1

9

@wouter is there any news on the horizon for this particular issue? URC2 keeps re-creating old empty folders after pushing. If I do mistakes and accidentally add a temporary folder, it will be stuck permanently in my project and pollute it.

1 Like
10

@Velocity_Zero , yes this is still very much on our radar.

If you message me on Discord (epic.wobu), we can talk about a workaround solution that should be able to help you in the near term.

3 Likes
11

This issue is still happening. From my testing, it seems to be due to renaming folders to the same name, but different capitalization either from the file system or VSCode.

If you guys were able to find a workaround, please inform us.

12

+1

I also think this issue affects the speed of local content validation and session startup. When I launch a session, it freezes at around 24% for about 15 minutes. Sometimes it eventually fails with the message “failed to compute validation session.” That’s is critical issue

13

@RMCFN

I would open a separate thread for this issue. It seems unrelated to this thread.

14

up

2 Likes