Unable to rename any content OSX Sierra 10.12.6

Development Programming & Scripting
1

When adding any new content to the project. The rename function does not work in any of the various ways:

  1. Right clicking the folder or content, and selecting “rename”

  2. Highlighting the folder or content, and pressing F2

  3. Double clicking the folder or content name in the sources panel

To reproduce the bug, create a new blank project in Unreal Engine 4.18, using OSX Sierra version 10.12.6. In the sources panel, right click and create a new folder. try any of the methods listed above to rename the folder. The name of the folder will flash white as if it will allow the rename function to work, but will just return back to it’s normal state. The same repro can be done for any new content, such as materials or animations.

2

Hi BlackMagic89,

I tried to reproduce this in 4.18 on a MacBook Pro (10.12.6) and a Mac Pro (10.13.1), and on both machines I was able to rename assets and folders using all three of the methods that you mentioned. Are you using the binary version of the Engine installed through the Launcher, or did you build the Engine from source code?

3

Hi ,

I am using the version installed through the Launcher. I previously was working in 4.17.2 and had the same issue occur. I updated to 4.18, before reporting the bug, to see if that would resolve the issue. The update did not fix the issue. 4.17.2 was also installed using the Launcher.

4

I tried again with brand new test projects using the binary Engine installed through the Launcher, and was still able to rename assets and folders. Would it be possible to get a video of what you are doing so I can make sure I am duplicating your process exactly?

5

Here is a link to the video that I made to show the bug. I am using starter content in my project, but I made a brand new blank project in the video to show that it happens there also.

https://drive.google.com/open?id=1gvUO3h-YJFajoM7RQ4NUw6ysCXU0nWM7

6

Hi BlackMagic89,

Sorry for taking so long to get back to you on this. I tried again to reproduce this in 4.18.3, but was unable to do so. Unfortunately all of our Macs have been upgraded to MacOS 10.13, so it is possible that is preventing me from reproducing the issue. Do you continue to see this occur in newer Engine versions, or on MacOS 10.13?

7

Hi ,

I did forget to update this thread. I actually have not seen this issue since upgrading to MacOS 10.13. I also have not seen the issue in UE 4.19 or 4.20. It seems to have resolved itself. Thank you for the help.