Download

NVIDIA GameWorks Integration

Do the Flex sample maps work for you? If you are having problems importing a new asset then if you can send me a DM with the source asset and some repo. steps then I can take a look.

Flow UE4 integration will be released shortly for 4.15, Waveworks should also see an update, but I don’t think you’ll see a Cataclysm UE4 update in the near term.

We don’t have a timeline for Flex diffuse particles in UE4, but I saw that someone on this forum had done an integration manually. I’ll add at task for it and see when we can get it scheduled.

Flow will indeed be updated from the Funhouse version to include self-shadowing.

@Miles.Macklin from vxgi 4.12 to current version when i want paint on a landscape in editor unreal get crash and editor closes with a fatal error.

When I start flex map example everything fine. When I add new mesh and try add flex soft asset in flex menu, it’s crash.

And screen of problem

Octopus.jpg

Oh i’ll wait for this! by the way. I downloaded your 4.15 vxgi+hairworks… branch and after i compiled it says 4.14.3.

yes, it’s not supported yet there, i haven’t made the jump to 4.15 yet, i started working on upgrading to 4.15 from this fork on my local computer, but it didnt work out. As it is, and if you check the branch historic, you’ll realised it’s merely a copy of the 4.14.3 VXGI/FLEX/… branch. I should probably delete it.

edit: i’ve just deleted it :stuck_out_tongue:

Can I use this version of UE4 on Mac?
I can’t build it with Xcode 8.1.
here is error logs:

In file included from Runtime/Engine/Public/SkeletalMeshTypes.h:16:
Runtime/Engine/Classes/Materials/MaterialInterface.h:149:19: error: ISO C++ forbids forward references to ‘enum’ types
TEnumAsByte<enum EVxgiMaterialSamplingRate> VxgiMaterialSamplingRate;

In file included from Runtime/Engine/Public/MeshBatch.h:5:
Runtime/Engine/Public/MaterialShared.h:1001:10: error: unknown type name ‘FVxgiMaterialProperties’
virtual FVxgiMaterialProperties GetVxgiMaterialProperties() const { return FVxgiMaterialProperties(); }
^
Runtime/Engine/Public/MaterialShared.h:1001:77: error: use of undeclared identifier ‘FVxgiMaterialProperties’; did you mean ‘GetVxgiMaterialProperties’?
virtual FVxgiMaterialProperties GetVxgiMaterialProperties() const { return FVxgiMaterialProperties(); }

                                                                               ^~~~~~~~~~~~~~~~~~~~~~~
                                                                               GetVxgiMaterialProperties

Runtime/Engine/Public/MaterialShared.h:1001:34: note: ‘GetVxgiMaterialProperties’ declared here
virtual FVxgiMaterialProperties GetVxgiMaterialProperties() const { return FVxgiMaterialProperties(); }
^

tell me its ok to use that branch xD

it’s like you were using the 4.14.3 branch, it’s the same ^^.

I’m porting VXGI to 4.15 at this very moment.

love you man! haha dont forget volumetric lighting!

HA! Best timing ever; I tried downloading and compiling that one last night and when I booted it up I saw it was just 4.14 and I was like, “Waaaaaait a second…”
Can’t wait for 4.15 + VXGI! It’s my dream come true. The other stuff like Flex and Hairworks are wonderful, but unnessessary; vxgi IS a requirement I have right meow, though… Also volumetric lighting, but that can wait.

PS: how have you added a signature to your posts linking to your branch? I have been digging around this site and I just can’t find that setting anywhere! It’s driving me bananas, because it’s probably insanely obvious and staring me in the face! XD

Edit: It totally was.

I’ll check this locally and update this post

edit: Ok, i can reproduce your issue here. After further look, it looks like there’s some real difference between this Flex version and the one published recently. This merged build is actually almost 1.5 month old and use a beta version of the recently released Flex.

edit-edit: i’ve now updated to most recent Flex, please re-download

I’ve just finished updating Flex to its latest update. Please re-download the build. Your issue is now fixed

Hi xenthor. from vxgi 4.12 version to 4.14 (with Nvidia branch) when i want paint a meterial on a landscape unreal get crash and editor closes with a fatal error.can you check if this problem is in your branch.if exist please resolve that bug.

Is this version of flex 1.1? And Flex contains waveworks?

Hey everyone !

Just built the VRWorks 4.14 branch today and I have to say I am quite impressed by the performance gain with Lens Matched Rendering (we observed up to half the performance gain on GPU frametime) !
That said most of our projects and blueprints have been moved to 4.15 for various reasons.

Is there any plans to branch VRWorks to UE 4.15 any soon ? Or is there a simple (ie don’t dive too much into the source code) way to merge the current 4.14 branch to 4.15 manually ?

Cheers

Can you describe your exact step by step way to reproduce this issue please?

It’s Flex 1.1 taken from the most recent update from Nvidia 8 days ago. I updated the package last night, i’ll recommend downloading it again if you download it earlier.

Does HBAO+ work with the forward renderer in UE4?

@Miles.Macklin Is there a reason why the HBAO+ branch was not updated for 2 years now? I see that HBAO+ is also part of the VXGI branch, but I dont need VXGI and I would like to keep my UE4 as close to original as possible.

Also, why is the HBAO+ still on version 2.4.0.19336705 on the VXGI branch while 3.1.0.21602716 is already available in the non-ue4 repo?