NVIDIA GameWorks Integration

[Mike.Skolones]

@dvd.kh;259872

the point light is not enough good for soft shadows & VXGI lighting … Why?

Do you have a screenshot showing the problem?

Edit: just saw the screenshots on the previous forum page. Which features of that screenshot are the problem, specifically?

[anonymous_user_bcf66e2c]

@.;259871

Something sounds wrong there. Are you running the latest driver? By ‘sample scene’, do you mean the Cornell Box? It sounds like you are seeing anomalous behavior, I don’t know why that would happen. Could you capture a movie with stats visible? Did you say you are running the version from 's repo? Have you also tried the 4.6 version from the NvPhysX repo? I’m wondering if something is amiss with the 4.7.3 changes. We should have a fresh update from the VXGI team later week, I know they had some concerns about the changes they had seen in 4.7.3.

Thanks,

I also have some concerns about the changes made for 4.7.3 in my build, I will take another look at it in my build while I wait to see what the VXGI team do. Although as I stated above, I get more FPS from the same scene as with a lesser graphics card.

[Mike.Skolones]

@;259413

1)Just a wild guess but it doesn’t look like works particularly well with animated light sources and/or geometry right?
I’m trying to render a scene with some Speedtrees flickerfree but failing miserably

2)Also spotting quite a lot of little corners and tight-fit geometry where there’s flickering when doing an animation (only camera moves).
I’ve tried various approaches but once a piece of geometry flickers, I find the only solution to get rid of it is to move the geometry slightly further apart.
No whilst testing but for production I reckon it’s a huge no. Any pointers as to what to do and what to avoid?

The SciFi Hallway had animated lights, it worked fine. I’ll ask the VXGI guys for an explanation of flicker and how to avoid it. Hopefully some of the improvements in the upcoming version will reduce artifacts like that.

[Chesire]

@.;259884

I’ll ask the VXGI guys for an explanation of flicker and how to avoid it. Hopefully some of the improvements in the upcoming version will reduce artifacts like that.

Thanks and please do. You could also check the free sample package available from Speedtree and see if you guys manage to render out a short clip with animated foliage where shadows/ao produce desirable and don’t bombard your scene with small jitters, blinks and blobs. (foliage mats flagged for VXGI). I failed but I’m gladly told that’s due to an error on my end.

[anonymous_user_52a14607]

@dvd.kh;259872

the point light is not enough good for soft shadows & VXGI lighting … Why?

I’ve already posted as an ages ago. The current version of VXGI has not implemented voxelization for distance field soft shadows - they are currently working on that.

[Chesire]

@dvd.kh;260031

Are you kidding? I tested speed tree & interior scene & others … everything is fine. you have to tweak the VXGI params … Read the VXGI documentation that’s available in VXGI branch. You have to spend time for getting good results … nothing else …

Because it works for you doesn’t necessarily mean it works for everyone else. You get that right? I am not getting stable results on animated Speedtrees. Obviously these produce moving shadows and when you have -example- a tree with a bush underneath it, with the bush hugging a wall, I can clearly see the AO and Colorbleed jumping allover the place. I’ve tested my *** off so please instead of telling me to tweak settings which is about as broad a comment as you can give, lets just assume for a moment that indeed I have read the documentation, know -to a certain extend- what I’m doing- and just see an I can’t get rid of no matter how I try. I’ll keep at for sure but please show just a tad more respect to someone trying to achieve workable results as much as you are yourself.

[Gandosh]

@dvd.kh can you please resize your picture? its getting hard to see other posts. Same images same size is pretty confusing.

[Mike.Skolones]

@DrifterGames;259093

Thanks for all the great work. I’m really looking forward to turf , a quick question: How practical is turf for large (really expansive) outdoor scenes? Normal grass planes are awful performance-wise, wondering how turf fares…

From what I’ve been told, TurfEffects does a much better job in performing transitions between LODs and you can have really smooth fade-outs which are barely noticeable. We still expect to have reasonably-sized coverage for the grass as the library currently does not have any build-in fallbacks which could scale well beyond ~500 meters (roughly when a single grass blade becomes comparable to a single pixel on a screen)

[anonymous_user_52a14607]

@;260072

Because it works for you doesn’t necessarily mean it works for everyone else. You get that right? I am not getting stable results on animated Speedtrees. Obviously these produce moving shadows and when you have -example- a tree with a bush underneath it, with the bush hugging a wall, I can clearly see the AO and Colorbleed jumping allover the place. I’ve tested my *** off so please instead of telling me to tweak settings which is about as broad a comment as you can give, lets just assume for a moment that indeed I have read the documentation, know -to a certain extend- what I’m doing- and just see an I can’t get rid of no matter how I try. I’ll keep at for sure but please show just a tad more respect to someone trying to achieve workable results as much as you are yourself.

Yes, does indeed sound like a classic voxel cone tracing. Because the color info in higher mip-maps voxels are propagated from the lower mip-maps voxels, any movement of a lit surface will have an impact on these higher mip-map voxels which cover a larger volume. is most noticeable when moving an emissive object around - you will see stuttering and flickering, which is caused by a lack of smooth transition between the object moving from one higher mip-map voxel to another. You can probably call some sort of temporal voxel aliasing, which is very difficult to address.

A possible solution suggested in the GameDev forums was to perform some sort of voxel anti-aliasing, where the transparency of a voxel is dependent on the amount it is filled by the object. I have never been able to get to work properly in my Opengl voxel cone tracing programming.

A solution that I have got to work to address was to increase the detail of the mip-map filtering. i.e. at the moment, I believe that the color values are averaged over 2x2x2 voxels. Increasing filtering to 3x3x3 voxels will make a noticeable improvement to the flickering/stuttering caused by dynamic objects.

[WWWWWWWWWWWWWWWWWWWW]

Can I use the NVIDIA HairWorks in Mobile and Tablet?

[Mike.Skolones]

@Aabs Inc.;260338

Can I use the NVIDIA HairWorks in Mobile and Tablet?

At point HairWorks will require support.

[WWWWWWWWWWWWWWWWWWWW]

Can I use the NVIDIA HairWorks in PS4, Xbox One and Mac?
Windows Only?

[Mike.Skolones]

@Aabs Inc.;260351

Can I use the NVIDIA HairWorks in PS4, Xbox One and Mac?

As I said above, HairWorks is right now, and it will remain that way for some time. Mac will require a GL port; we may have XB1 and PS4 ports in progress already, I will check.

[Gandosh]

Hi . any news from faceworks?

[WWWWWWWWWWWWWWWWWWWW]

Do Will also corresponds to the Mobile & Tablet in the future?
Required Geometry Shader(Android Extension Pack, etc…)?

[darthviper107]

@;259413

1)Just a wild guess but it doesn’t look like works particularly well with animated light sources and/or geometry right?
I’m trying to render a scene with some Speedtrees flickerfree but failing miserably

2)Also spotting quite a lot of little corners and tight-fit geometry where there’s flickering when doing an animation (only camera moves).
I’ve tried various approaches but once a piece of geometry flickers, I find the only solution to get rid of it is to move the geometry slightly further apart.
No whilst testing but for production I reckon it’s a huge no. Any pointers as to what to do and what to avoid?

It should work fine with dynamic lights and meshes, it’s fully dynamic

[Mike.Skolones]

@Aabs Inc.;260362

Do Will also corresponds to the Mobile & Tablet in the future?
Required Geometry Shader(Android Extension Pack, etc…)?

It really depends on the capabilities of the device. These features are appropriate primarily for a higher-end PC at point; soon we may see mobile devices with sufficient capabilities, but your typical mobile device performs like an older mid-range PC at best.

[Mike.Skolones]

@;260358

Hi . any news from faceworks?

Not yet, sorry, the Faceworks team has been working on other projects recently.

[Mike.Skolones]

@dvd.kh;260551

Hello … Howto solve the point light soft shadow problem? What happened?

Have you tried with both the 4.7 () and 4.6 ( NvPhysX) branches? The VXGI team is looking into it, and believes is a bug in the UE4 integration, not in VXGI library itself, because the VXGI library shouldn’t affect the shadows that way. Hopefully we’ll have a new build up later week, with that artifact resolved.

[Netrve]

@.;260468

It really depends on the capabilities of the device. These features are appropriate primarily for a higher-end PC at point; soon we may see mobile devices with sufficient capabilities, but your typical mobile device performs like an older mid-range PC at best.

As far as I know the Shield devices have the strongest GPU at point (even with support) and the X1 is going to come out, but then again I only saw its use in a stationary console so far. I doubt that we will see hardware powerful enough anytime soon, manufacturers are not really considering mobile games when creating their devices, except for Nvidia, so most of the times more power is only used to outrun the competition, even if that leads to stupid decisions in so many cases.

I’m happy that we are finally advancing in graphical fidelity after so much time, so please don’t ruin by targeting mobile too

Anyways, I’m really looking forward to see more GameWorks coming out, a lot of the stuff looks so interesting. ^^

Greetings,