Sorry, this is my first time packaging a game on UE4, or any game at all for that matter. I somewhat learned how to cook and package, thank you UE4 and Hour Of Code, and Jonas Molgaard on Youtube (UE4 - Some Packaging tips and tricks - YouTube)
Though, I have 860 map warnings and HAD 28 errors / critical errors on my current four (4) map files.
Currently I am able to play through my game from Title screen to level one, to level one score page, to load level 2, with zero blueprint errors at all, and no errors are exposed during the cooking or packaging.
I successfully build each map and edit to produce zero errors / critical errors… then duplicate the entire base folder to make a new one and delete folders Binaries, Build, and Intermediate, then I open the project from the folder there. I am successfully able to cook, and package my project with zero errors / critical errors. (I still have a bunch of warnings like 540+ or something I’ve been working on them, I don’t know if it is mandatory, the yellow text)
Upon launching the .exe inside the newly created WindowsNoEditor folder, and after I load the very first level after my title screen, I get this error. I have no idea what I should do or where to go from here.
Assertion failed: !bCurrentRequiresAdjacencyInformation || (bCurrentRequiresAdjacencyInformation && SharedBuffers->AdjacencyIndexBuffers) [File:D:/Build/++UE4/Sync/Engine/Source/Runtime/Landscape/Private/LandscapeRender.cpp] [Line: 2159]
0x00007ff8e763d759 KERNELBASE.dll!UnknownFunction []
0x00007ff7860cef46 MyFirstFPS.exe!UnknownFunction []
0x00007ff7860d2708 MyFirstFPS.exe!UnknownFunction []
0x00007ff785e17acd MyFirstFPS.exe!UnknownFunction []
0x00007ff785db8b6b MyFirstFPS.exe!UnknownFunction []
0x00007ff785dbaae0 MyFirstFPS.exe!UnknownFunction []
0x00007ff7886727e6 MyFirstFPS.exe!UnknownFunction []
0x00007ff78868b872 MyFirstFPS.exe!UnknownFunction []
0x00007ff78747c006 MyFirstFPS.exe!UnknownFunction []
0x00007ff7874a51ed MyFirstFPS.exe!UnknownFunction []
0x00007ff7874988a1 MyFirstFPS.exe!UnknownFunction []
0x00007ff785c07bbb MyFirstFPS.exe!UnknownFunction []
0x00007ff785c08d00 MyFirstFPS.exe!UnknownFunction []
0x00007ff785c0e735 MyFirstFPS.exe!UnknownFunction []
0x00007ff7860eb9ff MyFirstFPS.exe!UnknownFunction []
0x00007ff7860e3cc0 MyFirstFPS.exe!UnknownFunction []
0x00007ff8e8c57034 KERNEL32.DLL!UnknownFunction []
0x00007ff8e9e1d0d1 ntdll.dll!UnknownFunction []
Crash in runnable thread TaskGraphThreadHP 14
I figured out the problem on my project to make it package correctly with this error. Thankfully, there were no more errors, and both levels, all four maps, proceeded to load correctly.
What I had to do, since I deciphered the error message down word for word and read it was having an issue with some sort of “Landscape” somewhere “File:D:/Build/++UE4/Sync/Engine/Source/Runtime/Landscape/”. It must have been in something he imported or tinkered with? I did not look at his blueprints so I cannot say specifically or exactly what was causing this error. I simply deleted the three basic ones he had imported so we could start anew, since we are early on in the project. (he added stuff such as a Landscape Sludge/Slime pool, with a Landscape Pool, and two Landscape Floors) In the main editor window, I clicked on “Modes, then Landscape” and was able to easily find and edit/delete the files in the “World Outliner”.
Since my water and floor for the pools worked, I’ll have to show my friend how I do it. 
After packaging, everything checks out! Success! I hope this helps someone out there with a similar issue.
Now I understand it is important to check the cook and build Output Log errors often and package after to see if you have a serious error (I will begin this as standard practice every time I finish new code, function, landscape, or mesh) so then you know if you use it in the future it will not cause a serious issue and have to address past errors and inputs, so then the progression becomes real, or Unreal perhaps lol
I also ran into this same error when trying to package one of my projects. Since the error was happening due to a landscape object in a level downloaded from the marketplace, I didn’t have access to the original author of the level, and I didn’t want to spend the time recreating the landscape. So as a workaround, I exported the offending landscape and re-imported it using the technique described here. This effectively makes the landscape into a static mesh, which bypasses the landscape rendering that has the assert in it. This isn’t a perfect technique, as I lost some foliage info in the process, but for my purposes, it worked well enough.
I encountered the same issue, but I resolved it in a manner that was both brutal and precise. Initially, I deleted half of the content in the scene. If the error persisted, I removed the other half, continuing this process until I confirmed that the terrain was causing the crash (it might be the terrain in your scene as well). Then, I removed the material of the terrain and found that the crash disappeared, leading me to conclude the issue was with the material. Upon opening the material, I disconnected half of the material node links, but the error persisted. Even after disconnecting all the links, the error remained. I began to inspect the default settings of the material and eventually, under Tessellation, I found an option named “D3D11TessellationMode.” Changing it from “PNTriangles” to “No Tessellation” resolved the issue. If this helps you, please consider logging in and giving me a thumbs up for all my effort!
1 Like
This my friend! This is the error that I also gst on the second map load! UE4.26