Warning CreateExport: Failed to load Outer for resource ... for many blueprints
we just run into a problem of one of my team mates machine. On that machine we get the warning "Warning CreateExport: Failed to load Outer for resource ..." a lot (<800) in many blueprints. And after that the editor is crashing most times. I copied his project folder over to my machine and there is everything running fine. We reinstalled the launcher and unreal as well as completely deleted and force synced the whole project from P4. But nothing is helping. On all other team machines in our team the project is running fine.
After deleting and resynching the whole project I get once the error: "Failed to import 'C:/Program Files (x86)/Epic Games/4.12/FeaturePacks/StarterContent.upack'. Failed to create asset '/Game/StarterContent'" But unreal is installed with starter content.
One artist is completely blocked atm. please help.
asked Aug 02 '16 at 03:05 PM in Using UE4
You can try the following (make a backup of your project folder before or have it in source control). This helped me with UE 4.19.2:
answered Oct 09 '18 at 04:21 PM
SO i just ran into this problem in the past week or so, we are using git hub and doing all of our source control through it. We are also using git LFS. I played around with a couple of different things to get past this error, including the help ideas suggested above. I can't give a concrete step by step solution to the problem. But I can give the things i did to ultimately get past this problem.
At this point i repulled my repo, and things started to work.
I believe that this essentially purges all the references within your git delta history (i could be wrong if anyone can correct). SO THE WARNING HERE is if you don't want to lose all of those references within your git history don't do this. This effects the references in all of the repo's branches.
The rabbit hole I went down to solve this problem: https://community.gamedev.tv/t/project-still-broken-since-refactor/59468 https://help.github.com/articles/removing-files-from-git-large-file-storage/
I'm having the same issue, for me the problem was that the level I was loading had previously contained a blueprint that no longer existed.
answered Dec 12 '18 at 12:39 AM
Follow this question
Once you sign in you will be able to subscribe for any updates here