itsRabies

An hour of development in UEFN is actually 2-3 hours of actual time (not counting afk or using other apps while waiting). Here is what takes away from it (with a beast PC and 1Gbps connection): - Renaming a file in content browser (3-8ish secs) - Moving a file in content browser (same) - Deleting a file in content browser (same) - Opening live edit (1-6 mins) - Crashes (??? mins) - Starting the project (3-10mins) - Any edit that desyncs live edit, like landscape editing, scene graph and verse editables change (1-6 mins) - Closing unnecessary popup windows that constantly spam the editor (2-3 secs) - Placing a blueprint or FortPlaysetItemDefinition in viewport (0.3-0.5 secs per case) - Migrating content UEFN to UEFN (6-20 mins) - Checking memory (7 mins) - Moving player to test area, or camera to player (5 secs) - Fixing UEFN grids after restart (4 secs) - Falling and flying back up because player jump didnt trigger in edit mode (4 secs/case) - Closing extra asset windows in UEFN (1-2 secs/window) - Reopening texture data dropdown on architecture (2 secs/case added since a few updates back - roughly 40-60 occurrences per working session) 1) Most of what is listed above should not take more than 1 second, to match other editors, and we are in the minutes in some 2) In a usual "1-hour" session, there are around 2k-3k edits for level design, so multiply bullet 9 (0.4 x 2500 = 1000 secs taken away just waiting on things to spawn on viewport alone) I would love to sit down with Epic and create an initiative to speed up the editor. I sent messages about that multiple times before, and every time I was told those fixes are "low priority" So don't talk to me about time, because really its your weakness as an editor; it's in fact, the slowest editor I've used in my career, by a long shot. If you want to fix it, my DMs are open