Editor 4.4.2 Crashes on Start With LightPropagationVolumes enabled

Development Programming & Scripting
1

As per topic. If I put r.LightPropagationVolume=1 in ConsoleVariables.ini I get a crash on Editor startup.

I know that LPVs are experimental works in progress, but I was hoping to see how they worked with a couple of small scenes I want to set up.

I had same crash behaviour with 4.4.1.

Is this a known issue with this version of editor or am I doing something wrong?

Thanks!

2

Hey excelynx,

Thank you for your report. We have assigned this issue to a member of our support staff, and they will begin investigation as soon as possible. If we are unable to reproduce issue, or we need additional information, our staff member will comment here with additional questions. Otherwise, we will post an ‘Answer’ once we have logged issue in our bug database or we have a solution for it.

In meantime, please be sure to review our suggestions for how to report a bug, and feel free to edit your post if you have additional information to provide:

Please and attach crash logs and dump files from your project directly after a crash, as well as your system information.

Thanks!

3

Hi,

There is a known issue with LPV and translucent materials that will instantly crash editor. We have recently escalated this issue to see if we can at least get a fix in to stop crash from happening.

To clarify, when LPV is on and if you are starting up editor with basic level with two chairs statue with glass and that table. If you click on glass translucent material it will crash editor.

If you’re getting different results, please list your steps to clearly reproduce error and I will test it out to make sure it’s not same issue.

Thank you!

Tim

4

Hi Tim!

This is actually just a straight-up crash when loading editor before editor is even responsive.

All I’m getting in callstack is:

!Id:b8ce49c7ec19650c77c0aca78b33f708

From logs:

[2014.09.16-00.03.51:086][ 0]LogRenderer:Warning: Reallocating scene render targets to support 32x32.
[2014.09.16-00.03.51:123][ 0]LogRenderer:Warning: Reallocating scene render targets to support 1144x896.
[2014.09.16-00.03.51:225][ 0]LogCrashTracker:

[2014.09.16-00.03.54:692][ 0]LogWindows:Error: appError called: Rendering thread exception:
Fatal error!

Address = 0xf17f75c6 (filename not found) [in C:\Windows\system32\nvwgf2umx.dll]

and

Unhandled Exception: EXCEPTION_INT_DIVIDE_BY_ZERO

[2014.09.16-00.03.54:841][ 0]LogWindows: Rendering thread exception:
Fatal error!

Address = 0xf17f75c6 (filename not found) [in C:\Windows\system32\nvwgf2umx.dll]

This is version 4.4.2 - 2289767 binary.

I’m running a GTX 780 with 340.52 drivers.

If you need any other information from me, please feel free to let me know!

Thanks for your time and help!

Simon

5

Can you post Crash Logs and Dmp from your project here in a file. ([your project ] / Saved / Logs /)

Also, are you using any other changes to your consolevariables.ini file or are you just using one variable listed above?

Is this happening with all projects or a specific one?

If it’s happening with a specific one, can you tell me which template/project to use to test on my end?

Thank you!

Tim

6

Sure, Tim!

only change to ConsoleVariables.ini is aforementioned “r.LightPropagationVolume=1”

This is happening with all projects.

Doing some Googling for nvwgf2umx.dll only brings up an issue with another DX11 game.

It’s kind of a strange issue in that it only happens with that variable enabled and is completely fine otherwise.

Let me know if you need anything else from me.

Thanks!

Simon

Logs

7

So I did a little more digging and found cause on my end:

If I end OVRService_x64.exe, everything starts up and works fine, including LPVs.

I initially tried removing nvwgf2umx.dll, which then led to a crash in OVRDisplay64.dll. Then I figured it might have something to do with OVRService_x64.exe, killed that and lo and behold editor with LPVs enabled works just fine.

Obviously having editor crash if I have OVRService_x64 running isn’t ideal, and to my knowledge LPVs were recently fixed (4.3 or so) to work in VR/stereo mode - so I’m not sure what root cause is.

Hopefully that information helps!

EDIT: fix may actually be result of using power button to turn Rift off, rather than ending OVRService_x64.exe. Rift is currently set to Direct Mode. It definitely has something to do with Rift being either on or enabled.

8

Thanks for updating. I’ve gone ahead and marked this as answer in event that it helps someone else with a similar issue.

Thanks again!

Tim