Hello everyone,
When using the foliage tool I can no longer check/uncheck the box in the foliage library thumbnail. Nor can place any instance or paint any instance on the scene.
I can effectively not use the tool. Any answers to this issue? I’m running a project in 5.5.4.
Thank you for your time and help.
Hey there @espylicious! Welcome to the community! Is the foliage library fully visible in the foliage window? Is it all foliage in the foliage library or can newly created foliage work correctly? Does this occur only for that project or all projects for your current installation?
Hello @SupportiveEntity ,
Thank you for the response.
The foliage library is not fully visible. I tried deleting what was in there and then re-dragging content into it and then i would get the “error/warning” that it was already saved?
It’s only this project where its not working. with a new project under this same installation, the foliage tool works as intended.
Edit: I had the same foliage in another level under this same project. I deleted the levels I wasn’t using under this same project…is that the problem? Any fix to this or am I SOL?
It’s possible there’s some asset data that was corrupted somehow like this thread where the user’s workaround was deleting the foliage assets entirely and rebuilding them once the UI was functional (though they were outright crashing).
I deleted the foliage assets in the content folder. Added a new asset via bridge, when I dragged a single asset from that new folder, it would automatically add the entire foliage folder yet the tool is still inoperable and I’m not seeing the check box or save icon on the foliage library thumbnail.
Is there a way to transfer my scene (as i have it blocked out) into a new level in a new project?
Sounds like the foliage tool itself is entirely broken for this project, so let’s try and get rid of all temporary data as a last ditch.
First, back your project up entirely somewhere safe, then delete these three folders:
Then run the project, it will regenerate the necessary files. Does change anything?
If not, yes we can migrate the maps themselves with the migration feature:
Just don’t try to migrate to different engine versions.
Deleting those three files and running the project again fixed the tool.
If it happens again or persists I will migrate to a new project, but for now it has restored the tool.
Thank you so much for your time and help!
Fantastic! Generally you can delete these folders whenever you come across an Unreal Engine module failing or acting oddly, however you’ll notice that it also removes your autosaves, last error logs, backups, and you have to fully rebuild shaders every time.
