so i have a bug with adding in a static mesh to foilage. it keeps crashing. i am using 4.4.2 right now.
this is the crash report:
!Id:e8c94e45003bd68395eddc67222ee3f0
Unknown exception - code 00000001 (first/second chance not available)
Assertion failed: (Index >= 0) & (Index < ArrayNum) [File:D:\BuildFarm\buildmachine_++depot+UE4-Releases+4.4\Engine\Source\Runtime\Core\Public\Containers\Array.h] [Line: 536]
Array index out of bounds: 0 from an array of size
I am more than happy to help, though I will need a bit more information. Does this happen in a blank project with no additional content? Can you post your crash logs here so we can have a look? Additionally, what kind of static mesh and material are you using? If you have anything attempting to produce material wind effects in foliage, this is a known issue that is currently being assessed by development staff. Thank you!
So i tested some various meshes and i found out that the mesh is bugged. i made costum grass in speedtree from a tutorial but when i export en import it into unreal its bugged it doesnt show annything its a black box and when i try to open in it crashes.(link the crash report down below). but i tried foilage with standard tree from speedtree and it works it doesnt crash at all. so its an export/import issue with that file.
the scene has the standard assets. its just a random scene so i can test various materials and scripts.
Crash report(when dragging the static mesh into foilage spot)
!Id:e8c94e45003bd68395eddc67222ee3f0
Unknown exception - code 00000001 (first/second chance not available)
Assertion failed: (Index >= 0) & (Index < ArrayNum) [File:D:\BuildFarm\buildmachine_++depot+UE4-Releases+4.4\Engine\Source\Runtime\Core\Public\Containers\Array.h] [Line: 536]
Array index out of bounds: 0 from an array of size
The problem does seem mesh specific. When we looked at it, the foliage mesh has a material but has no polygons or vertices. This is what is causing the crash. Try using a different static mesh and see if it produces the same error.
We have not heard from you in quite some time. I am marking this as answered for tracking purposes. If you are still experiencing this crash, please comment with the requested information.