NVIDIA GameWorks Integration

[Netrve]

@;348308

VXGI does not. It just uses the same D3D11 device that’s used for main rendering. We considered running some or all of VXGI workload on a separate GPU, but there would be too much traffic between GPUs and too many synchronizations to make such separation practical.

Would that change with the next generation of GPUs? I’m thinking about GPUs which will support NVLink, would that be beneficial in case or is separation impractical because of other reasons?

[anonymous_user_7c71c8ec]

@;348331

Would that change with the next generation of GPUs? I’m thinking about GPUs which will support NVLink, would that be beneficial in case or is separation impractical because of other reasons?

Not sure. Maybe.

Currently there are two multi-GPU scenarios in which VXGI can benefit:

1. AFR SLI, where for example GPU 1 renders odd frames and GPU 2 renders even frames. In case, both GPUs perform voxelization on every frame and have copies of all data, and nothing is copied between GPUs. mode is supported by the library (although we rarely test it).

2. VR SLI, where each GPU renders a view for one eye. Both GPUs would perform voxelization and shadow map rendering, but G-buffer rendering, shading and cone tracing would be separated. mode has not been implemented yet.

[anonymous_user_d4447896]

Is 4.8_NVIDIA_Techs the latest branch from to use if you want all techs so far ? Also is it UE4.8 or UE4.8.3 ? I have loaded in a 4.8.3 project I made with world comp and landscapes and all my landscape materials are showing as the world grid material. I can’t seem to change them or paint on them either.

Edit. Ok sorry, landscape work ok now.

[Nudlegaru]

@;348336

Not sure. Maybe.

Currently there are two multi-GPU scenarios in which VXGI can benefit:

1. AFR SLI, where for example GPU 1 renders odd frames and GPU 2 renders even frames. In case, both GPUs perform voxelization on every frame and have copies of all data, and nothing is copied between GPUs. mode is supported by the library (although we rarely test it).

2. VR SLI, where each GPU renders a view for one eye. Both GPUs would perform voxelization and shadow map rendering, but G-buffer rendering, shading and cone tracing would be separated. mode has not been implemented yet.

I thought that will bring back SFR which will be betetr for multiple GPU and will reduce the lag.

[anonymous_user_0cce59911 (anonymous_user_0cce5991)]

Could you please help me solve hairworks plugin for maya 2015 problem? I keep getting an export error “The 20 out of 56 fur stands share mesh verices with other lines. They will not be exported!” I use latest version of hairworks plugin. Reinstall the plugin, snap CV to growth mesh vertex 1 by 1, doesn’t works. The funny thing is… it works like charm until yesterday and now it doesn’t even work with simple sphere.
Sorry to post on thread, but the nvidia devtalk forum doesn’t have living human anymore.

is link to scene file

[anonymous_user_7c71c8ec]

@;348552

I thought that will bring back SFR which will be betetr for multiple GPU and will reduce the lag.

I haven’t looked into it yet, but my guess is that for VXGI, SFR SLI will be very similar to VR SLI: both GPUs voxelize all geometry, and only screen-space workload is separated.

By the way, in the recent versions in vxgi-dev branch, you can see the time it takes the GPU to process world-space and screen-space VXGI workloads if you type “stat unit”. The FPS counter is not to be trusted though, because enabling stat unit adds a CPU-GPU sync and reduces the FPS in that branch.

[Gandosh]

@Musetatron;348826

Could you please help me solve hairworks plugin for maya 2015 problem? I keep getting an export error “The 20 out of 56 fur stands share mesh verices with other lines. They will not be exported!” I use latest version of hairworks plugin. Reinstall the plugin, snap CV to growth mesh vertex 1 by 1, doesn’t works. The funny thing is… it works like charm until yesterday and now it doesn’t even work with simple sphere.
Sorry to post on thread, but the nvidia devtalk forum doesn’t have living human anymore.

is link to scene file

Try using less curves.

[anonymous_user_78daa01b]

@;335303

Hi guys,

So I was hoping to use the new 4.8-dev branch. Compiled, all went well. Hbao works, which is the only I need, really. But unfortunately, I’ve got the same flickering using Deferred Decals as with 's merged 4.8 branch. only happens in 4.8 branches, 4.7 had no issues. 's a video to demonstrate what happens (switching Early Z-pass is what’s causing , shutting it off disables decals altogether )

[video]https://youtu.be/JWq-EbM0uPI[/video]

There is something fishy with deferred decals even in the official release, but there I was able to fix it (following the same procedure is a “no go”).

So anyone has seen before? Any idea how to fix ?

Thanks in advance for any help!

Sorry to bump , guys. But maybe it just got buried under other posts. Still wondering if anyone knows what’s going one ? It kinda stops me from using 4.8 and HBAO And I am guessing there’s a good will persist in the upcoming 4.9.

[Mike.Skolones]

@;346834

Any news on faceworks?

You won’t see a FaceWorks integration anytime soon. Sorry about that, but we have decided not to pursue the integration at time.

[Mike.Skolones]

@Aabel;346353

Density for Hairworks seems to be broken.

The density attribute works fine in Hairworks viewer. I think a few other attributes aren’t working as well, I will double check later weekend when I get some more time.

I’m bringing to the attention of others on the HairWorks team. I don’t know what could cause the problem you describe, or whether it is a problem at all, or some miscommunication about how to tune the settings. Which UE4 branch are you using? THe official HairWorks branch, or the branch?

[anonymous_user_7c71c8ec]

@;349172

Sorry to bump , guys. But maybe it just got buried under other posts. Still wondering if anyone knows what’s going one ? It kinda stops me from using 4.8 and HBAO And I am guessing there’s a good will persist in the upcoming 4.9.

I just found out what causes the flickering… it was a bug in our VXGI temporal reprojection integration, which switched the Z buffers at the wrong time. Fixed internally.

You can work around by setting r.VXGI.TemporalReprojectionEnable = 0.

[anonymous_user_26f8a6cf]

@.;349224

I’m bringing to the attention of others on the HairWorks team. I don’t know what could cause the problem you describe, or whether it is a problem at all, or some miscommunication about how to tune the settings. Which UE4 branch are you using? THe official HairWorks branch, or the branch?

I am using Galaxymans branch. I am assuming that the attributes are supposed to work in UE4 the way they work in HairWorks viewer. In Hairworks viewer the texture acts as a multiplier to the density attribute, in UE4 the scalar attribute does nothing, the texture works, but is not a multiplier, but a direct input, which means a density of 1.

It would also be fantastic if Nvidia could provide plugins for Houdini. It’s a much more cost effective solution for creating guide hairs than Maya + shave. For independent artists anyway.

[anonymous_user_78daa01b]

@;349227

I just found out what causes the flickering… it was a bug in our VXGI temporal reprojection integration, which switched the Z buffers at the wrong time. Fixed internally.

You can work around by setting r.VXGI.TemporalReprojectionEnable = 0.

Dude, you rock! That was the.

To anyone else who runs into problem - use the cvar that has provided, and set Early Z-pass to Opaque and masked meshes (Decide automatically disables Dbuffer Decals for some reason).

Thanks again!

[Xu_Nie]

@Aabel;346353

Density for Hairworks seems to be broken.

The density attribute works fine in Hairworks viewer. I think a few other attributes aren’t working as well, I will double check later weekend when I get some more time.

It should be due to LOD. Turn off Detail LOD and try again.

[anonymous_user_0cce59911 (anonymous_user_0cce5991)]

@;349073

Try using less curves.

Thanks, I have tried deleting curve and It works when there is only 5 curve remained but I still confuse what cause problem because it meets the req. “one vert per curve” in the doc. Another strange is that some model will works smoothly if I import .Obj from other app but the model i made in maya often fail to export hairworks correctly.

[anonymous_user_26f8a6cf]

@Xu Nie;349512

It should be due to LOD. Turn off Detail LOD and try again.

was the! thank you.

[Netrve]

Hey guys,
I wanted to know if anyone else using 's branch ran into following (and might have a fix for it):
It looks like GPU particle systems are broken. CPU particle work fine, but GPU particles just stay stationary in a sphere. Everything looks fine within the particle editor preview, but as soon as I place the system within a level it breaks. The particles ignore all modules and flicker as well. If needed I can provide screenshots later on.
The particle systems work fine on “vanilla” UE4 builds. Does anybody have a clue?

Greetings,

[Chesire]

@;350058

Hey guys,
It looks like GPU particle systems are broken.
The particle systems work fine on “vanilla” UE4 builds.

Vanilla builds work fine indeed but GPU particles have been broken on VXGI builds ever since the initial version.
I’m very much interested in a fix for (that won’t include ‘please lower your graphics settings to mobile’ :D).

[Jakeypoos]

I’m a bit confused,is the title of video wrong.

or is face works integrated with UE4.

's a video from 2013

[Netrve]

@;350140

Vanilla builds work fine indeed but GPU particles have been broken on VXGI builds ever since the initial version.
I’m very much interested in a fix for (that won’t include ‘please lower your graphics settings to mobile’ :D).

Huh, I never noticed that and I’m using VXGI since the beginning as well…but thanks for the information!
Maybe because I haven’t been creating/using gpu particle system within my project which uses GameWorks or I just forgot it.

I’m surprised that hasn’t been fixed already, GPU particles are quite important. Did they mention why hasn’t been fixed?