NVIDIA GameWorks Integration

[anonymous_user_b1c15813]

@;225883

Crashes after build every time:

MachineId:
UserName:

Unknown exception - code 00000001 (first/second  not available)

Fatal error: [File:C:\Users\\Documents\UnrealEngineSource\UnrealEngine\Engine\Source\Runtime\Core\Private\GenericPlatform\GenericPlatformMemory.cpp] [Line: 54] 
Ran out of memory allocating 58731628704 bytes with alignment 0

KERNELBASE + 37901 bytes
UE4Editor_Core!FOutputDeviceWindowsError::Serialize() + 285 bytes [c:\users\\documents\unrealenginesource\unrealengine\engine\source\runtime\core\private\windows\windowsplatformoutputdevices.cpp:95]
UE4Editor_Core!FMsg::Logf__VA() + 463 bytes [c:\users\\documents\unrealenginesource\unrealengine\engine\source\runtime\core\private\misc\outputdevice.cpp:526]
UE4Editor_Core!FMallocTBB::OutOfMemory() + 93 bytes [c:\users\\documents\unrealenginesource\unrealengine\engine\source\runtime\core\public\hal\malloctbb.h:46]
UE4Editor_Core!FMallocTBB::Realloc() + 191 bytes [c:\users\\documents\unrealenginesource\unrealengine\engine\source\runtime\core\private\hal\malloctbb.cpp:99]
UE4Editor_Core!FHeapAllocator::ForAnyElementType::ResizeAllocation() + 37 bytes [c:\users\\documents\unrealenginesource\unrealengine\engine\source\runtime\core\public\containers\containerallocationpolicies.h:348]
UE4Editor_Engine!TSparseArray<TSetElement<TPair<FString,FShaderParameterMap::FParameterAllocation> >,TSparseArrayAllocator<FDefaultAllocator,FDefaultBitArrayAllocator> >::Empty() + 134 bytes [c:\users\\documents\unrealenginesource\unrealengine\engine\source\runtime\core\public\containers\sparsearray.h:224]
UE4Editor_Engine!operator<<() + 179 bytes [c:\users\\documents\unrealenginesource\unrealengine\engine\source\runtime\core\public\containers\sparsearray.h:400]
UE4Editor_Engine!operator<<() + 21 bytes [c:\users\\documents\unrealenginesource\unrealengine\engine\source\runtime\core\public\containers\set.h:624]
UE4Editor_Engine!operator<<() + 181 bytes [c:\users\\documents\unrealenginesource\unrealengine\engine\source\runtime\core\public\containers\array.h:1165]
UE4Editor_Engine!operator<<() + 108 bytes [c:\users\\documents\unrealenginesource\unrealengine\engine\source\runtime\shadercore\public\shadercore.h:544]
UE4Editor_Engine!DoReadTaskResults() + 747 bytes [c:\users\\documents\unrealenginesource\unrealengine\engine\source\runtime\engine\private\shadercompiler\shadercompiler.cpp:124]
UE4Editor_Engine!FShaderCompileThreadRunnable::ReadAvailableResults() + 562 bytes [c:\users\\documents\unrealenginesource\unrealengine\engine\source\runtime\engine\private\shadercompiler\shadercompiler.cpp:893]
UE4Editor_Engine!FShaderCompileThreadRunnable::CompilingLoop() + 369 bytes [c:\users\\documents\unrealenginesource\unrealengine\engine\source\runtime\engine\private\shadercompiler\shadercompiler.cpp:1019]
UE4Editor_Engine!FShaderCompileThreadRunnable::Run() + 112 bytes [c:\users\\documents\unrealenginesource\unrealengine\engine\source\runtime\engine\private\shadercompiler\shadercompiler.cpp:504]
UE4Editor_Core!FRunnableThreadWin::Run() + 86 bytes [c:\users\\documents\unrealenginesource\unrealengine\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:73]
UE4Editor_Core!FRunnableThreadWin::GuardedRun() + 93 bytes [c:\users\\documents\unrealenginesource\unrealengine\engine\source\runtime\core\private\windows\windowsrunnablethread.cpp:26]
 + 88557 bytes
ntdll + 181569 bytes

's what I did, cloned Release, then checkout VXGI
Then run the Setup batch, it asks if I want to replace the couple Nvidia files, I hit No
After that, I run the build project files
Start up the project in Visual Studio
I set it to Development_Editor x64
Build UE4
but it doesn’t work when I try to run the editor
It works without VXGI checked out though.

Try step before running the editor “In solution explorer, under Programs, find ShaderCompilerWorker > Right click > Build.”

Thanks,

[Mike.Skolones]

@;225884

Try step before running the editor “In solution explorer, under Programs, find ShaderCompilerWorker > Right click > Build.”

Thanks,

That should do it. I did check in Win64 shadercompilercommon.dll, not yet sure if that would fix it, but rebuilding the ShaderCompileWorker should do it. is not a bug specific to VXGI, it’s a general UE4 problem due to missing dependencies in the solution.

–

[Mikand79]

@Shuckster96;225411

I seem to be getting specific error; I do not know the root cause of scenario. I built the VXGI branch successfully but Windows 8.1 complains of a missing entry point in a .dll file. Is there an easy fix for ?

@;225516

Happens the same to me. I just gave up on it; too much other things to do anyway…

If Im not mistaken error comes from the dbghelp.dll that ships with the github dependencies of the Engine, it has a different version than what Visual Studio or the Debug Tools installs. It gets loaded and called when the Engine dies and tries to collect the call stack and stuff for submission to Epic, so its not directly related to the NVidia stuff.

[Mikand79]

If you happen to have to build the engine more often, instead of using Visual Studio which by itself uses a lot processor time and memory with UE open you can make yourself a suitable command line environment.

I use a command prompt with the compiler, all needed tools and git in path, and a build script for the engine. Used it without issues on the NV branches too:

@echo off

call Engine\Build\BatchFiles\Build.bat ShaderCompileWorker Win64 Development
call Engine\Build\BatchFiles\Build.bat UnrealLightmass Win64 Development
call Engine\Build\BatchFiles\Build.bat UnrealPak  Win64 Development
call Engine\Build\BatchFiles\Build.bat UE4Editor Win64 Development

…must be started from the root of the engine directory that you want to build.

You can change it to build any part in any configuration you see fit. ‘Build.bat UE4Game HTML5 Shipping’ would build the client files for blueprint games used to package for HTML in shipping configuration in the editor f.e.

So building from git hub sources actually is easy

[Nudlegaru]

@;225724

Tilde key only works if viewport is in focus. ie: If you clicked anywhere else (eg: Content Browser, Details panel etc) then it wont work.

I was sure I tried when viewport is highlighted and I tried that again, the problem is tilde key in an AZERTY keyboard location is not ~ but ², ~to get ~ you need to press Alt Gr + 2, but even that doesn’t work, even turning the keyboard to english by clicking shift + Alt doesn’t help that. UE4 needs to support AZERTY keyboards, because even by keybindings some movements’ controls for the viewport, you can’t do the same for when you click play and you have to click shift+alt again. I couldn’t find where to rebind console key in the options.

@;225724

Are you sure you dont have Used with Vxgi Voxelization option in your material?

I checked again for the materials in the Cornell Box sample and all materials have that option enabled by default.

@;225724

That’s because none of your materials are being used with VXGI.

The option was enabled by default, I even now enabled all other options for VXGI for the materials, but typing r.VXGIDebugMode 2 or r.VXGIDebugMode 3 or r.VXGIDebugMode 0 in the outpot log doesn’t still let visualize respectively neither the voxelized opacities nor the emittance colors nor the Diffuse result. Please someone help me to visualize them.

@;225724

Pardon me but which Cone Tracing parameter?

one:

@;225774

You can find cone tracing parameters in the “Post Process Volume” put in the scene.

Thanks,

Thanks but I typed PostProcessVolume_VXGI in the search tab but I could find the VXGI diffuse and VXGI specualr you showed. Waht should I add to the scene to find them? Thanks

[Nudlegaru]

@.;225891

That should do it. I did check in Win64 shadercompilercommon.dll, not yet sure if that would fix it, but rebuilding the ShaderCompileWorker should do it. is not a bug specific to VXGI, it’s a general UE4 problem due to missing dependencies in the solution.

–

I noticed you updated the engine 13 hours ago : /NvPhysX/UnrealEngine/commit/8216f6550eb6caf00444f8fdf36d5cedd2038e9d

but as the commentator on that page said, the code may be overwritten, I also suspect the zip file got updated too, so I won’t recompile the engine again, I think building ShaderCompilerWorker is enough right?

[Nudlegaru]

I hope your next demo will be demo: the one shown at 0:12 and 3:34: watch?v=_E1oVl2d01Q

[darthviper107]

@.;225891

That should do it. I did check in Win64 shadercompilercommon.dll, not yet sure if that would fix it, but rebuilding the ShaderCompileWorker should do it. is not a bug specific to VXGI, it’s a general UE4 problem due to missing dependencies in the solution.

–

Ah, thanks, that got it working.

It’s actually running pretty well on my work computer, GTX 660

[anonymous_user_b1c15813]

@;225941

I was sure I tried when viewport is highlighted and I tried that again, the problem is tilde key in an AZERTY keyboard location is not ~ but ², ~to get ~ you need to press Alt Gr + 2, but even that doesn’t work, even turning the keyboard to english by clicking shift + Alt doesn’t help that. UE4 needs to support AZERTY keyboards, because even by keybindings some movements’ controls for the viewport, you can’t do the same for when you click play and you have to click shift+alt again. I couldn’t find where to rebind console key in the options.

I checked again for the materials in the Cornell Box sample and all materials have that option enabled by default.

The option was enabled by default, I even now enabled all other options for VXGI for the materials, but typing r.VXGIDebugMode 2 or r.VXGIDebugMode 3 or r.VXGIDebugMode 0 in the outpot log doesn’t still let visualize respectively neither the voxelized opacities nor the emittance colors nor the Diffuse result. Please someone help me to visualize them.

one:

Thanks but I typed PostProcessVolume_VXGI in the search tab but I could find the VXGI diffuse and VXGI specualr you showed. Waht should I add to the scene to find them? Thanks

Do you have any “PostProcessVolume” in your scene, if not then add it to your scene and you can find it in the details panel of that PostProcess volume.

Thanks,

[anonymous_user_0df12f74]

@;225941

I was sure I tried when viewport is highlighted and I tried that again, the problem is tilde key in an AZERTY keyboard location is not ~ but ², ~to get ~ you need to press Alt Gr + 2, but even that doesn’t work, even turning the keyboard to english by clicking shift + Alt doesn’t help that. UE4 needs to support AZERTY keyboards, because even by keybindings some movements’ controls for the viewport, you can’t do the same for when you click play and you have to click shift+alt again. I couldn’t find where to rebind console key in the options.

Go to Edit -> Project Settings and select the Input tab on the left. At the bottom of the page on the right you will see “Console Keys”, with you can choose any key you want to toggle the console.

[Nudlegaru]

@;225958

Do you have any “PostProcessVolume” in your scene, if not then add it to your scene and you can find it in the details panel of that PostProcess volume.

Thanks,

I added a PostProcessVolume and found the options. Thanks, one problem solved. Now I need to visualize voxelized opacities, he emittance colors and Diffuse result using r.VXGIDebugMode 2 or r.VXGIDebugMode 3 or r.VXGIDebugMode 0 just like in the video : watch?v=_E1oVl2d01Q

and :

&d=1424291403

Anyone succeeded in visualizing them?

[anonymous_user_b1c15813]

@;225973

I added a PostProcessVolume and found the options. Thanks, one problem solved. Now I need to visualize voxelized opacities, he emittance colors and Diffuse result using r.VXGIDebugMode 2 or r.VXGIDebugMode 3 or r.VXGIDebugMode 0 just like in the video : watch?v=_E1oVl2d01Q

and :

&d=1424291403

Anyone succeeded in visualizing them?

It should be working. I am able to visualize it. Use command “r.VXGI.DebugMode 2” instead of “r.VXGIDebugMode 2”, there is a missing between vxgi and debugmode.

I am testing it in the “CornellBox” project provided. I haven’t tried it with any other project yet.

Thanks,

[Nudlegaru]

@;225990

It should be working. I am able to visualize it.

I am testing it in the “CornellBox” project provided. I haven’t tried it with any other project yet.

Thanks,

What did you do to visualize it? First I started output log for the Cornell Box sample , then I entered r.VXGI.DiffuseTracingEnable 1

Then I checked that all materials have the option used with VXGI enabled, I even checked all options for VXGI in materials parameters.

Then I eneterd r.VXGIDebugMode 2 in the output log, nothing happened. Same with 3 and 0 values

[anonymous_user_b1c15813]

@;226004

What did you do to visualize it? First I started output log for the Cornell Box sample , then I entered r.VXGI.DiffuseTracingEnable 1

Then I checked that all materials have the option used with VXGI enabled, I even checked all options for VXGI in materials parameters.

Then I eneterd r.VXGIDebugMode 2 in the output log, nothing happened. Same with 3 and 0 values

Use command “r.VXGI.DebugMode 2” instead of “r.VXGIDebugMode 2”, there is a missing between vxgi and debugmode.

Thanks,

[WinterLanternPro]

Is there a way to increase the distance at which the VXGI ends? I’m having issues with the Realistic Rendering sample lighting when you back far enough way from the window.

[darthviper107]

How do we control the VXGI distance? Right now it only renders about a distance of 1000cm

[Nudlegaru]

@;226005

Use command “r.VXGI.DebugMode 2” instead of “r.VXGIDebugMode 2”, there is a missing between vxgi and debugmode.

Thanks,

Thank you very much, it worked. I knew sth was missing/wrong.

BTW, how do you check « Used With VXGI » (or any other option) on all surface materials at the same time or do you have to do it material by material individually?

[anonymous_user_b1c15813]

@;226014

Thank you very much, it worked. I knew sth was missing/wrong.

BTW, how do you check « Used With VXGI » (or any other option) on all surface materials at the same time or do you have to do it material by material individually?

I think you have to go through each material and check it.

Thanks,

[rubenst]

@;226008

How do we control the VXGI distance? Right now it only renders about a distance of 1000cm

Console command: r.VXGI.Range NUMBER

replace “NUMBER” with something that suits your needs, but as always be aware of entering ridiculous amounts there

[Nudlegaru]

@;225095

are some test I did with Realistic Rendering Demo

https://www.dropbox/s/vxnedzmrmgui84v/RoomNight.png?dl=0

https://www.dropbox/s/6yjxdguhom9mig3/RoomNight2.png?dl=0

https://www.dropbox/s/x2gkhnh1eewm1v5/RoomNight3.png?dl=0

https://www.dropbox/s/g0dlhmu7de786eg/RoomNightNoLight1.bmp?dl=0

https://www.dropbox/s/4etakrk4kpqec53/RoomNightNoLights2.bmp?dl=0

https://www.dropbox/s/hxylll5ofqyc0jw/RoomNightNoLigts.bmp?dl=0

Thanks,

Great job you did !

Can you please tell me how did you enable VXGI for flashlight you hold in NightRoomNoLights ? Bceause it is compound light with blueprint.

Also how did you set up all the surface materials to be able to get VXGI on them? For example, when I click the couch, then on element 0 in the materails, it opens MI_Couch_NOSSS_Mat_Ins which doesn’t have VXGI options, when I scroll down, in general tab, I click on MI_Couch_NOSSS_Mat inside it and it opens a tab where I can modify the VXGI options and enable it (Used with VXGI). Is that right?

Well, even doing so doesn’t get me colour bleeding like in your pics and r.VXGI.DebugMode 2 doesn’t get me the same results as yours :

&d=1424464446 as if VXGI is not correctly enabled in the scene.

I hope you can tell me the steps that made you reach such results.

Thank you very much !