Crash after enabling Distance field ambient occlusion

Crash occurs after enabling Distance field ambient occlusion.
My specc:
Dell Precition Tower 7810 with a geforce 1080

I can open the scene with another PC with the same graphic card.
Any ideas where the problem lies?

Hi DanRu,

I’d like to get more information regarding your system. To do this open your command prompt and enter dxdiag

When the window appears save all information and attach the generated file in this post.

,

Hello,

for your reply. Here is the file you were asking for:
link text

Hi DanRu,

I don’t see anything wrong with your system and your drivers are up to date. I know you said you were able to enable distance fields on another machine but just to be sure I wanted to check if you are experiencing something similar to this issue.

Also, are you able to enable distance fields in a blank project on the machine that crashes? If so I may need to get a small sample project that can replicate the issue.

i cant enable distance fields on a clean project - i always get the same error message when trying to open the project. So i cant reproduce the issue you listed above.
This machine had a Quadro card before i switched to the 1080. But that shouldnt be a problem because i did a clean uninstall of the drivers and unreal too.

I did some additional research regarding your issue that lead me to this post: Increase NUM_ELEMENTS_IN_POOL Error - Platform & Builds - Epic Developer Community Forums

The error is the same as the one posted in your crash log Assertion failed: Resilt && “Increase NUM_ELEMENTS_IN_POOL”

The answer that states this: NUM_ELEMENTS_IN_POOL is 128 and set in Stats2.h. You should be able to increase it within that file. If you run into any complications by modifying this within Stats2.h, please let us know. may be something you would want to try.

P.S. The driver you are using (372.90) is close to a driver that was blacklisted by us (372.7.0). So you may also try going to a previous driver version before the blacklisted one and see if that helps.

Let me know if that helps.

in 4.12\Engine\Source\Runtime\Core\Public\Stats stats2.h i changed NUM_ELEMENTS_IN_POOL from 128 to 256 and 512 without any success.
Im new to C++ and so i just saved the header file - or do i have to do more than that?

Did you also try reverting to a previous driver version prior to 372.7.0? Just to make sure the new current driver is also problematic?

didnt try it with the 372.7.0 driver yet, but i tried it with the 368.81 which is also installed on the machine where i can open the project. Unfortnately without luck

just installed the other driver aswell - still not working

After you made the changes to stat2.h you need to compile the engine again. This will ensure that your changes are recognized.

Also, use a driver version previous to 372.7.0 that is currently labeled as incompatible and will cause the engine to crash.

Thank you for your patience. :slight_smile:

is there a tutorial on how to compile an existing engine version? Only found something where i have to download the whole engine and than build it.

Before we continue could you test to see if this error occurs with other engine versions?

We are going to test and see if we can reproduce the crash on our end with a setup that simulates yours.

Regarding making changes to the source code, you will need to build the engine from source. I would try this as a last resort since this will take some time and a little bit of research. The tutorial you want to start off with is this. A new, community-hosted Unreal Engine Wiki - Announcements - Epic Developer Community Forums

Also note that this may not address your issue. At this point my remaining option is to write a bug report addressing this issue. So that a fix can be implemented.

it occurs in 4.13 aswell for me

Hi DanRu,

I apologize for the wait. I’ve contacted other support techs to get the necessary resources to test your particular setup.

I would at least test on older versions of the engine as well to see if you can enable mesh distance fields. This well let us know if something in an engine update is causing this crash.

Hello DanRu,

I’m looking into reproducing this and have attempted with a GTX 1080 but haven’t gotten the issue to occur. If you have a moment, could you provide the dxdiag information from the other machine where this is working correctly so we can try comparing the two machines to see what may be different and causing the issue that you’re seeing?

Hello Mathew,

for taking the time trying to fix the issue.
Here is the dxdiag file from the pc where dfao works:
link text

Thank you for that information, DanRu.

From comparing the two, the main difference seems to be your connected devices. It seems that the computer that is having issues has an Oculus Rift plugged in, noted by the “Rift” entries in the Direct Input list, while the other computer does not. Could you try disconnecting this and/or connecting it to the working computer to see if having this connected is causing this crash?