since a few days my project won’t open. Cannot explain why. The crash log mentions a few asset errors (missing textures mysteriously relocated to the original path after migrating into the project; though redirectors had always been fixed back then) all of a sudden. But they did not seem to be cause it: I fixed most of the missing assets one by one and the project will still not start.
I get the error “bad name index” like this:
[2018.06.29-10.47.15:115][ 0]LogLinker:Error: Bad name index 1632448338/139
[2018.06.29-10.47.15:115][ 0]LogLinker:Error: Bad name index 1918985543/139
[2018.06.29-10.47.15:115][ 0]LogLinker:Error: Bad name index 1869771886/139
[2018.06.29-10.47.15:115][ 0]LogLinker:Error: Bad name index 1702125901/139
[2018.06.29-10.47.15:115][ 0]LogLinker:Error: Bad name index 1129469554/139
[2018.06.29-10.47.15:115][ 0]LogLinker:Error: Bad name index 1207961/139
[2018.06.29-10.47.15:115][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.29-10.47.15:115][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.29-10.47.15:115][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.29-10.47.15:115][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.29-10.47.15:115][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.29-10.47.15:115][ 0]LogLinker:Error: Bad name index 2652103/139
[2018.06.29-10.47.15:115][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
[2018.06.29-10.47.15:115][ 0]LogSerialization:Error: Invalid boolean encountered while reading archive - stream is most likely corrupted.
What does that mean?
Weird is also the following:
[2018.06.29-10.44.35:781][ 0]LogLinker:Warning: Can’t find file ‘/Script/EnvironmentQueryEditor’
[2018.06.29-10.44.35:781][ 0]LogLinker:Warning: Can’t find file for asset ‘/Script/EnvironmentQueryEditor’ while loading E:/UE4ProjectsSamsung/MatrixProject/Content/Blueprints/AI_character/EQS/EQS_FindRangedShootLocation.uasset.
[2018.06.29-10.44.35:781][ 0]LoadErrors:Error: Error /Game/Blueprints/AI_character/EQS/EQS_FindRangedShootLocation : Can’t find file for asset. /Script/EnvironmentQueryEditor
[2018.06.29-10.44.35:781][ 0]LogLinker:Warning: Can’t find file ‘/Script/EnvironmentQueryEditor’
I wrote the AI tasks in my project a long time ago and it never complained about the missing EQS assets (which actually should be part of the editor C++ classes, how can they be missing?). Also I am pretty sure I had enabled “EQS” in the editor preferences. Either way, I cannot open my project now to check if it has been somehow disabled.
Any advice would so appreciated! Two full days of work at stake! Thanks
I made some tiny progres. I have been able to open my project by first removing the last map asset I was working on from the content folder (assuming that either the map has become corrupted or an asset that is referenced in it).
Notabaly, this does not save the project from crashing. Immediately after startup the editor starts “discovering asset data”. After a while when it gets to an asset I suppose, it crashes again. Unfortunately the log does not seem to show any consistent results that would help to pinpoint the culprit…
Also, I noticed that when I open a specific folder in which my skeletal meshes are, the editor almost immediately crashes.
I guess I will have to start deleting the assets one by one…
I have found a solution. A single asset has been corrupted, no idea why, but it was one that was placed in my scene. Here are my learnings in case anybody else stumbles upon the same problem.
Make sure you have the engine debugging symbols installed, that way you can learn a bit more about the nature of the problem when the editor crashes.
Delete your intermediary folder and see if the problem goes away (did not work for me but many people with similar problems suggested it.)
Update your project to a newer version and see if the problem goes away (did not work for me but many people with similar problems suggested it.
If that still does not help, open your project folder in explorer and start deleting your assets in a controlled fashion. So for example start by deleting half of your assets while keeping the other half and see what happens. Use the same method to narrow down to single assets. Using this method I could pinpoint the one (!) asset out of 15 000 that caused the issue.
I hope this is helpful to you!
I would like to say I am quite dissappointed about the fact that nobody every seems to respond on AnswerHub. My five questions since summer 2016 have not received a response and eventually I have returned to answer them myself. Maybe it is just me but honestly I have seen more badly formulated questions getting a response on the UE4 Answerhub. I would also think that I am an active member helping others so it kinda sucks that I never get back anything.
This specific problem of mine is I believe fundamentally related to one of my earlier (unanswered) questions about how to properly manage content in the Content Browser, how to rename or relocate stuff Robust way to manage UE4 file system - Programming & Scripting - Unreal Engine Forums . If you do that, eventually you will run into this problem even if you regularly fix redirectors. Honestly this system of redirectors is really poor in UE4 and it either should be improved or at least Epic should transparently inform people about the risks they take. I know these wise things like “decide on a naming convention and folder structure early on and stick to them” but honestly nobody who ever worked development can fulfill this to 100% and every now and then you simply have to rename an asset!
Thank you! Had the same problem for a whole day until stumbling on your solution. I think I moved a few files and one of them was the problem.
And yeah, the fact that a lot of questions (even good structured ones) goes unanswered is really disappointing.
Still, thank you for your contribution.