#Lack of Proper Support for IGPUs

19 messages · Page 1 of 1 (latest)

raven stream
#

Game actually runs fine 30-40 fps and was able to make it through and complete medical, but after entering research and making it about half way through the game starts crashing spitting up this error.

LowLevelFatalError [File:Unknown] [Line: 198]
Unreal Engine is exiting due to D3D device being lost. (Error: 0x887A0006 - 'HUNG')

I suspect this is also a problem with many other sections further in the game.

Many other Unreal Engine 4 games run fine on integrated graphics without crashing so it should also be the case for this game.

System Specs
i5-7300U CPU
HD Graphics 620
16GB of Ram
256GB SSD

deep ravine
#

This setup does not meet the minimum requirements

raven stream
#

As stated game actually runs fine, but then crashes because it wasn't set up with basic support to recognize devices properly.

deep ravine
#

The purpose of minimum specs is to show what is and is not supported. If you can make a mod for this, I can try to present that to staff, but this is outside of the scope of supported hardware

raven stream
#

Will search and troubleshoot, because it is happening only when in specific areas in a level.

slate geyser
#

The D3D device being lost means the graphics driver crashed or froze and was reset by Windows. Ultimately it's not likely something the developers can address, because it's specific to a problem in Intel's driver software, and even with a crash dump won't necessarily even be directly caused by something they can easily work around. If there's any newer drivers available, try updating to those. If not, maybe try workarounds like tweaking your TdrDelay higher (will only help if it's a hang and not a crash) or running it with dxvk (though their vulkan drivers are spotty as well).

deep ravine
#

if it's research, my theory would be there's a lot of light complexity that wasn't addressed in that level the way it was addressed in storage, flight deck, medical, and executive in these most recent patches.

that's just a guess at what in that level specifically might cause too much strain. there is a mod on nexus that gives access the dev cheat menu, if you want to try teleporting to other levels for testing

#

krash is much more knowledgeable about these things than i am, to be clear, so i'd assume he's correct in this

slate geyser
#

There are also generally better maintained intel igpu drivers on linux, but that's a whole different swimming pool

#

That said, if you're able to note specifically what level/area you're experiencing the crash on, it might be something a dev could look at if they know of anything that's done differently there (but it'll be impossible to verify if they don't have a device that can reproduce it)

raven stream
#

Will test all these and give results.

#

Seems to be happening around the beta quadrant.

raven stream
#

More so when looking left in the area. Here is a exact spot where it can happen, tested after multiple restarts. Also changing TdrDelay doesn't help.

raven stream
#

Also hangs when looking at central control when near the beta quadrant. After a quick run through the only areas that seem to cause the hangs are research and the 3 groves.

raven stream
#

Was able to get past the beta quad by not looking in the direction of what causes the hang, but opening the door to central command causes one also.

slate geyser
#

Keep in mind if you're adjusting the TdrDelay to give the driver more than 2 seconds to respond, the change won't be applied until after the computer restarts

raven stream
#

Still doesn't help, game simply freezes until the number of seconds has passed then shows the error after.

raven stream
#

I wonder if the issue specifically relates to virus mutants or spores? The only places where the game hangs is research and the groves.