We are recently experimenting with the new 4.22 engine and exporters. I’m testing both the Revit and 3ds Max exporters (using the same scene from Revit for both). We encounter an error message stating we don’t have permissions to save out content on import and also when trying to save. Ultimately the content will not save, and if we close and re-open the project these assets will be gone.
It’s happening with a variety of different assets in different scenes, and we have seen furniture like desks display this issue along with walls and other objects.
This exact same scene imported into UE4.21 will experience NO issues (even when using the 4.22 exporters for Max and Revit). Until we can resolve this our team must continue building projects in 4.21.
Hi Marie-Claude! I tried this again today after reading your post and learned 2 things:
1.) My scene contains many items with even longer names which work fine (I still wish I could rename them in Revit) so this doesn’t seem to be the issue.
2.) All of those items I posted in the screenshot above contain spaces in the filename (between Cornice and _16). I renamed these in UE4, got some errors that they still couldn’t save, removed Redirectors and then it worked.
I will have to find other scenes to test this on, but could you let me know if you think spaces are a likely issue here?
Also, is this straight import then trying to save or you are moving things around in the content browser? Not that its something you should avoid doing - simply that we need to reproduce the problem and fix it.
although in this case, the culprit was a unsupported character that quasi invisible to find. a “us” (unit separator, similar to lf or cr) character slipped in the object name from revit.
I’m working with OS X (MAC) and I’m using UE 4.25.
I have the same issue:You do not have sufficient permission to save the following content to disk
What can I do in this case? -It’s supposed this issue was resolved already in UE 4.22
For me, this was a security firewall issue. I had to manually allow Unreal Engine folders to execute, because Windows AntiVirus security measures were blocking them.