Also the file location D:\build++UE5.… is not a valid folder unless UE5 does something wierd internally!
Im not calling any arrays anywhere this is a fresh problem that started when I added in a navmeshboundsvolume.
I noticed all of a sudden the recastnavmesh object dissapeared. so i restarted the editor.
Now i dont have a project at all (luckily this was a test project little work in it, as the same happened on my previous work)
Im beginning to think there is an issue with the navmesh possibly, but if i delete the external actors folder the project loads. Apart from an empty map.
Any ideas? 2 projects now this has happened. Unreal 5.1.1
The array indices seem consistent across projects, which makes me believe there is actors missing form the list in the map, as im using the 3rd person template as a testing level.
This happens on a basic project too just a floor and skydome/lights etc. But always after the navmesh is added
This stuff is definitely a bug-type situation, probably related to the third-person template needing a small fix after an update or a download corruption. If you could go ahead and turn this into a bug report, that would probably be the best course of action.
Not sure whether to report a bug just yet. After further playing around based on your thoughts something corrupted. I went to the Epic Launcher and did a verify. Shortly after starting it went to installing.
Now this didnt fix my issue. But it made me think there was some sort of corruption going on somewhere. So i removed all copies and version of unreal AND the epic launcher.
I then did a total reinstall of everything and it seems to be up and running again.
Just incase also before i did this i upgraded my boot SSD m.2 drive. Initially it was 250GB which was fine as i install everything to a secondary SSD anyway. But space was a little low, maybe the page files were getting short on space, i dont know. Maybe irrelevant but its now cloned to a new 1tb nvme drive.
So all this and i have a working editor again and no corruption.
The new SSD drive may have been irrelevant but just incase i thought id mention it as it was a step i took, and may or may not have been a factor!
Any re-occurances i have will surely make it to a bug report im guessing. but so far so good!
Thanks again!
PS i marked your post as solution as indeed it all points to corruption.
