Feedback about "Open level" dialog

Hello,

I’m sure a lot of developers at Epic are already aware of the current state of the new “Open level” dialog. I’m really surprised it was pushed in the final build (4.5) since it has many and serious limitations. Such as :

  • You can’t create a new folder while being in the dialog, you have to do it via the content browser.
  • You can’t reorganize map files in this dialog, you have to do it via the content browser (live moving/duplciating a map file). This can trigger a re-save and a check of the content of the map, which is totally unwanted ! As the user I never decided that operation which can be very long depending of the map content, meaning I’m forced to wait at an unexpected moment.
  • You can rename a map by using F2 (on Windows), but you can’t by doing “right-click” to bring a menu. This is therefore an hidden feature, especially since this is the only thing that you can do in this dialog.
  • You can’t open maps that are outside of the engine/project. This is maybe a small feature, but sometimes you want to open some test map that are located outside of the project (and based on the engine content, so now real dependencies).
  • Map duplicated via the windows explorer (aka not via the Editor) display the same name in the dialog while on the disk they have different filenames. In my case I disabled the thumbnail generation because of performances issues, so I can’t guess what is inside a map. If you have many test maps, or even many backups or iterations of a same map, you can be totally lost.

There is a lot of problem with this new dialog. I hope those will be fixed soon, levels are the core of the engine.

By the way I searched a bit, but I didn’t found a way to bring back the old method. Is there a command line to use the old open level dialog (the one based on the OS of the user) ?

Bumping this. I don’t know if there was improvements planned for 4.6 however.

Hello ,

We appreciate the information provided about this issue as it helps us improve. I have made this post and the issues within aware to the developers. The JIRA report number is UE-6081. Again, we thank you for the information and will be looking into this further.

Thank you,