Uasset files will not load

Development Asset Creation
, ,
1

Hi there,

I’ve researched this up and down and can not get these files to load into my project. I have tried dragging them into the content folder. I have copied them into the content directory. I have moved them around in the content directory. No matter what I do these uasset files will not load.

The uasset files come from a download in this thread:

these are the files I used:

I’m running the latest 4.11 version.

I would really love to use these files if someone could help me it would be greatly appreciated.

Thanks,

Arthur

2

I never got one of the assets to work. I could load them into a 4.10 project but not a 4.11 project. I gave up on one of them.

3

I just tried to put them in the windows content folder, editor opened, and the editor saw them without any problem … and I have the 4.11.2 …

4

im tring to migrate .uasset textures as shown in the official documentation - Landscape quickstart tutorial (landscape quickstart > 3. Painting), for some reason engine does not see those texture files, that are copied to my project from ContentExamples. It does not even save my newly created folders, that i created from content browser… 4.11.2

update: Actually creating a new folder from inside content browser - displays a newly created folder in the content browser (as expected), but in windows explorer those folders do not exist

5

4.11.2 trying to follow the tutorial:
https://docs.unrealengine.com/latest/INT/Engine/Landscape/QuickStart/4/index.html (Landscape Quickstart page 4)

  1. migrated .uasset files can not be seen by the content browser.

  2. creating new folders from content browser does shows newly created folders inside the content browser, but in windows explorer (so those actually were not created)

also i noticed, that content browser supports importing a lot of different filetypes of any kind, but not the .uassets, so i can not follow the Quickstart tutorial properly (in this case can not at all)

Update:
migrating files entirely through Content browser (without manual folder management through windows explorer) does help here

a second potential workaround is to “export” those assets (they are extracted away from .uassets in this case)