- Newest
- Most votes
- Most comments
@REDACTEDUSER
Is it possible that you moved the location of your trees on your hard drive? To confirm, I would look at the path to the tree object. This path is located near the bottom of the parameters for the tree.
Highlighted in orange here:
REMOVEDUPLOAD
@REDACTEDUSER
Was the asset processor still running or did it finish compiling the assets when this happened? I have seen on occasion newly created assets not render in the engine when these assets have been added to a project while the editor is running. I am glad its resolved for you now!
Interestingly, when I loaded up the engine again, everything was fine, and also, when I did a direct replacement, I have just changed the path that you've shown in the image, and it seems fine. But I think there is a bug, because after replacing, if you fly close to the trees, they go invisible, but when you either close the engine, or open a level and return to the other one, they remain, no matter how close you are. So I suppose it's been solved then? But perhaps, I've just found a bug?
This post is closed: Adding new answers, comments, and votes is disabled.
Relevant content
- Accepted Answerasked 7 years ago
- Accepted Answerasked 6 years ago
- AWS OFFICIALUpdated 9 months ago
- How can I troubleshoot issues when I use the AWS Load Balancer Controller to create a load balancer?AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago