I added the open world demo collection to one of my projects (I guess its called KiteDemo) and I am now trying to remove it.
I’ve been sitting here for about 10 minutes now with my CPU usage at 100% and windows’ resource monitor is reporting that the engine is not responding. I do not have the demo map open, nor anything referencing the assets, in fact I never placed any. I probably opened up the demo map once and that was it. I realize the pack is about 6.7 gigabytes but in today’s day and age I’m wondering if the time I’m sitting here is really justifiable? Looking at the resource monitor you can see that there are 4 shader compilers working… for what? Things should be deleting, not compiling.
On a side note, I also noticed quite a few times when I delete or relocate a folder of assets within UE, the original folder will remain and contain references. But it clogs up my hierarchy. I had deleted them in windows explorer and re-added all my materials to my objects after they had all gone missing according to the engine
To add to this bug, when I relocate a folder within UE, it empties the contents of each folder to the new location, however the references to each object that was moved seem to remain in their original locations while being invisible to the engine, but visible to windows explorer. I have to delete these items in windows explorer after moving/relocating/deleting objects.
Is this only occurring with the Open World assets? The reason I ask is because those assets are extremely large and can definitely increase CPU usage when they are being deleted.
Are you attempting to delete the folder from windows explorer or from the editor itself?
If you’re not experiencing the issue while attempting to delete other assets, this leads me to believe that it is related to the fact that the open world demo assets are immensely heavy on performance. Something I’d recommend when deleting large files like that is to try to delete them from windows explorer instead of in the editor, and ensure that the editor is closed at the time. I haven’t been able to reproduce the issue with any large folders that I have on my end, but if you are able to do so with normal assets from starter content or something along those lines please feel free to post a comment to reopen the thread.
In the meantime, I don’t believe that this is an engine bug, as it is expected that working with these assets will use a large amount of memory due to the quality of the assets themselves.
Also, as for any other issues you are experiencing relating to folders in UE4, please create separate posts for each so that we can investigate each issue separately if you believe that they are bugs.
Let me know if you have any further comments or questions related to this issue.
