It seems since the recent update, some static meshes that were placed on the map with foliage paint, aren’t showing in a launched session or private upload? Why is this?
@LosesoIcanwin Thank you for your report! We would like to look into this further, would you be able to submit a bug report using the form available here? Fortnite Creative
For more information, such as how to get the reference ID, please check out the article here: https://create.fortnite.com/news/using-the-creative-and-uefn-bug-reporting-form
This is also happening in my project where specific foliage is not showing up in my game, but it is visible in the engine.
Still an issue for us… we think its a spatially loaded issue, but foliage instances don’t allow you to turn that setting off so I dont know what to do
Have you found a solution for this by any chance?
I am also having this problem. it happens on a specific Landscape Streaming Proxy.
same issue
I think its because we (even me untill now) was duplicating separate foliage actors with ALT+DRAG method of duplicating props around the map, which is incorrect way of using the Foliage Tool! Just learned this!! My solution is go around the map, see where the foliage si missing, remove it and reapply via correct way : Single Instance placing or Paint mode in Foliage Tool!
Anyone found out yet why this is happening?
(post deleted by author)
(post deleted by author)
We found out It’s because of fortnite props, building pieces, devices etc. Fortnite assets like that seem to have something built in that removes foliage around it. Even without placed foliage meshes, with their default grass, the grass will be hidden around the area where the fortnite asset is. Our theory is that this has smt to do with the foliage issue, and thats why any foliage near a fortnite asset doesn’t show. So yeah try to avoid using fortnite devices, build pieces, and props near your foliage if possible. Def recommend using custom imported stuff for environments if you can
@Flak ?
If this thread doesn’t help, please start a new thread with your latest information. This one is too old for bug tracking. Thank you!