I see the start screen at 0% then it immediately crashes. This is the included crash report:
Assertion failed: (Index >= 0) & (Index < ArrayNum) [File:D:\Build++UE4+Release-4.12+Compile\Sync\Engine\Source\Runtime\Core\Public\Containers\Array.h] [Line: 804]
Array index out of bounds: 1 from an array of size 1
This is a standard install from the Epic Games Launcher. I added in support for Maya/Max and the debugging symbols as well as removed linux and TVOS support.
I’ve also made a post with logs, dxdiag, msinfo32 etc for my machine specs in case it helps EPIC find the cause.
Pretty serious problem if you can’t even open the editor…
I’m curious if you also have a SLI setup? I have a SLI setup, but this crash occurs even when SLI is disabled. Asking because I notice in the traceback that it’s crashing when RHI module is trying to find a supported adapter (graphics card).
I’m having the same issue here. Yesterday I had this problem and updated my graphics drivers, it worked. Today when I tryed to open ue4 4.12.4 (only the engine, no project) it crashed again, with this message:
Blockquote
Assertion failed: (Index >= 0) & (Index < ArrayNum) [File:D:\Build++UE4+Release-4.12+Compile\Sync\Engine\Source\Runtime\Core\Public\Containers\Array.h] [Line: 804]
Array index out of bounds: 1 from an array of size 1
Q1 Answer: When I run the Epic Games Launcher and select the Launch button for the unread editor as shown in the image you provided the programs starts and I see a dialog for the unreal editor and a percentage text set to 0%. This is onscreen for a split second before I get a crash report.
Q2 Answer: I cannot load the editor to even start or open a project.
Q3 Answer: I did a verify and I have the same results with no change.
Assertion failed: (Index >= 0) & (Index < ArrayNum) [File:D:\Build++UE4+Release-4.12+Compile\Sync\Engine\Source\Runtime\Core\Public\Containers\Array.h] [Line: 804]
Array index out of bounds: 1 from an array of size 1
After taking another look at the callstack I was able to find that this is a known issue (UE-17513) I have provided a link below to the original thread. Please feel free to visit the provided thread for more information and for future updates.
That’s not the same issue. I don’t have that DLL installed. That is not the same error message and just for fun I updated and installed the Displaylink Drivers as suggested and it doesn’t change anything.
Other than building it my self, I just installed it in my Windows 10 64bit PC (Different machine) using the launcher, it worked again. Are you sure you got all neccessary vc redistribute plus dxjune10?
I’ve got it working on another machine… but I don’t do my development on that computer. I’m not the only person with this identical issue… the only thing we’ve seen in common is some oculus development but I’m not running any additional software. I am tempted to reinstall but that is obviously a last resort option that I am not sure will work. I have unity 3d installed with oculus support… only other things are visual studio, adobe master collection, maya 2014 and android studio. There shouldn’t be any conflicts.
I have read somewhere in the links provided about oculus but haven’t put much attention as I am as well a new user of UE4 like the rest, good thing is, the guy said that when he disabled the oculus *something he was able to run UE4. Maybe you can try disabling Oculus.
I have this same issue, and I also like to cast my vote that I don’t think this is the same issue as the known issue UE-17513. While it looks similar, I’ve tried updating my displayport drivers per thread already, and it didn’t help.
One other clue that might help resolve this new issue is that I was able to get Oculus’ latest build of UE 4.12 to work, however EPICs builds fails. There seems to be something in their build that is working that isn’t in EPIC’s released version.
You can check my other post on this issue for more info, my dxdiag, msinfo, and crash logs.
After further investigation it appears that you were correct. This was not the same issue. There are a few different issues with this callstack. However, I was able to find that there is another issue that is known (UE-31927) that appears to suit your situation more closely. This issue in a still under investigation and has not been resolved yet. I have provided a link to the original thread below.
More information: It appears that on a PC with multiple graphics cards, where a HMD is connected to the second or subsequent graphics card(s), the editor crashes on startup at 0% due to device list not being populated correctly in FD3D11DynamicRHIModule::FindAdapter
That looks like it is completely related to my issue. I am not using dual graphics cards or displays however the error and reasoning behind it are on par with my problem. Is there any way of knowing if and when this solution will be added to the release build?
There is not a time frame in place currently for the implementation of a solution for this issue at this time. However, I will be sure to bump up the community interest on the report mention. Feel free to check the provided thread for future updates.
This looks like a likely culprit for my problem as well. Thanks!
I’m newish to Github, but I’d be happy to test it out to verify it fixes the problem on my end. What would i need to do to verify the patch is working? Just download the latest build of 4.12 from EPICs Github, and then pull in doormans pull request #2494?
Actually I see the response from ryanvanceepic on doormans pull request:
We have a similar fix for this that we’ll be releasing in 4.13.
Is there a number for ryanvanepic’s patch that I can pull in?
