Project:

[Dig_Squid]

@;25928

I have created a Compute Shader and moved the simulation on to the GPU. Now I can create surfaces at 2048x2048 cells with very little performance hit. Thats about an 11x increase from the original if anyone is keeping score.

Woah, that sounds amazing! I was actually about to ask if you had thought about going down that path Do let me know if there is anything I can do to help get it into shape to review.

How are you doing collision at the moment? I would think just treating it as a thin box for collision purposes would be fine.

[Ray_Jones_312]

@;27424

** Release v0.0.3**

Link: v0.0.3

Version 0.0.3 has been released to . Moved pling calculations onto GPU and increased compute shader thread count. With tessellation and the right material setup, can now render 4096x4096 cells at realtime. Speed of all other cell counts should be increased.

Material used to blend tessellation by distance:

Credit goes to DaveTheFreak aka Scholze for the material setup. Can be found here Distance Based DX11 Tesselation - Video

Download link returns 404.

[timi707]

Absolutely great work , a great already and would really be awesome if integrated in ue4 (i think thats what is meant by pull request, im a bit of a noob when it comes to development nomenclature)

[anonymous_user_e805727e]

Does it work with 4.1.1? Because when I copied to my UE4 folder, when trying to generate visual studio project to compile the engine, I got many errors in CMD command.
Please an installtaion tutorial would be appreciated. Thanks.

[anonymous_user_e805727e]

@;38224

Hi, I have had no issues running it with 4.1.1. Are you able to post some of the error messages? Also yes I am working on a more thorough installation tutorial, I will also provide some prebuilt binaries for the more common engine versions at some point.

When I put 4.1.1 files and everything required, then I place into /Engine/Plugins/Runtime directory and I place shaders into /Engine/Shaders directory
Then I compile, I get those errors:

Erreur 3 error : Failed to produce item: C:\UnrealEngine\Engine\Plugins\Runtime\CableComponent\Binaries\Win64\UE4Editor-CableComponent.dll C:\UnrealEngine\Engine\Intermediate\ProjectFiles\ERROR UE4
Erreur 2 error LNK1120: 1 externes non rÚsolus C:\UnrealEngine\Engine\Plugins\Runtime\CableComponent\Binaries\Win64\UE4Editor-CableComponent.dll UE4
Erreur 1 error LNK2019: symbole externe non rÚsolu “private: static class UClass * __cdecl UCableComponent::GetPrivateStaticClass(wchar_t const *)” (?GetPrivateStaticClass@UCableComponent@@CAPEAVUClass@@PEB_W@Z) rÚfÚrencÚ dans la fonction "public: class UCableComponent * __cdecl FPostConstructInitializeProperties::CreateDefaultSubobject<class UCableComponent,class UCableComponent>(class UObject *,class FName,bool,bool,bool)const " (??$CreateDefaultSubobject@VUCableComponent@@V1@@FPostConstructInitializeProperties@@QEBAPEAVUCableComponent@@PEAVUObject@@VFName@@_N22@Z) C:\UnrealEngine\Engine\Intermediate\ProjectFiles\Module.CableComponent.cpp.obj UE4
Erreur 4 error MSB3073: La commande “…..\Build\BatchFiles\Build.bat UE4Editor Win64 Development” s’est arrêtée avec le code -1. C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.MakeFile.Targets 38 5 UE4

[anonymous_user_e805727e]

@;39652

Thats an with the compiling the Cable Component , not my .

but I got when compiling the source files I got from your . I will try to only copy your fluid inside /runtime and see if it works.

[anonymous_user_e805727e]

@;39694

Under the releases tab on my private fork is a zip containing only the required files for the . Get that, and place into your own project, or the plugins directory for v4.1.1 of Unreal Engine (And place the shaders into UnrealEngine/Shaders directory). My Private Fork is not up to date with the latest code (So theres a good it doesn’t even compile, and probably why you recieve those errors), I just placed the code in there as per my above comments (Not allowed to be in public repo because of shared code with Epic).

I put the plugins/runtime and then copied shader to engine/shaders. The 4.1.1 window pops up saying compiling shaders WorldGridMaterial and immediately shuts down and the engien does not start , so I copied the 4.1.1 source shader folder back, and then the engine lanched and when i enabled fluid , when restarting, I got the same message on launcher pop up window shaders WorldGridMaterial nad the engine launched and was compiling some shaders. Did I make the work correctly by only copying the in plugins/runtime and then copying back 4.1.1 shader folder thus deleting the shaders you uploaded or do I need your shadre folder that does not work?

[anonymous_user_e805727e]

@;40130

No you need my shaders for it to work as the uses them, the editor immediately shutting down during compiling shaders, sounds like an with the shaders. What are your system specs? will only work on a DX11 Windows machine (The version of OpenGL used does not support Structured Buffers), if thats what you have, can you please upload the UE4.log of an execution where you have my shaders in place (Which should be under Engine/Saved/Logs) - Which will hopefully contain the reason why it shutdown.

Lol dude, if my PC was not able to run the engine, then what am I doing here? XD: windows 7 64 bits core i7, 8 GB DDR3 and GTX 660 ! I said after I copied shaders folder from 4.1.1 source back and overwrote your shaders, I got same message and then the engine compiled shaders and started.

Anyway here is latest log after trying to run the enigne with your shaders and then crashing: http://www6.zippyshare.com/v/51494732/file.html

I hope you find a solution for that, both your plugins are marvelous, thanks

[anonymous_user_e805727e]

@;40151

The main reason I was asking for your specs was not because I believed you were running an inadequate machine, but was to ensure you didnt say Mac or Linux. Coz as I said it will only work on Windows DX11 machine. (Which your specs show should work fine)

Okay what you need to do to fix , is copy the 4.1.1 shaders in, replacing everything (Because the error your getting is in regards to the latest preview shaders, which dont work with 4.1.1). Then copy only the following shaders in (Replacing already existing ones).

• FluidSurfaceVertexFactory.usf - Main shader used for rendering
• FluidSurfaceVertexFactoryCommon.usf - Common data used by the above
• FluidSurfaceShader.usf - Compute shader for simulation
• PNTriangles.usf - I made a small modification to shader to allow the vertex factory to set the displacement before the material
• FlatTessellation.usf - Same as above

Keep everything else as 4.1.1

When you run the editor the first time, it will recompile all the shaders for the current project, is just the way the vertex factories work, I need to define some properties in the caching so that is does not always have to be cached.

Thanks.

Thank you, now it worked great. You see there are many awesome plugins available for UE4, but enabling them is a nightmùare, like Substance and coherent UI which need a new version each time a new engine update comes out and they conflict with each others. Epic should really make it easy to enable plugins or integrate the best ones in the engine by default.

BTW, I wrote fluid in search classes and I got fluid actors etc, I put one on the ground and I got grey moving ground. Please make a wiki tutorial about both your plugins and how to use them, how to get a final result with moving water surface and how to integrate a video in a screen for the other . Thanks and continue the awesome work.

[Dig_Squid]

@;41773

Agreed, I would love to see shaders become specific. So you dont have to place them into the Engine/Shaders directory.

Sorry for the troubles, but thank you for blazing a trail! I asked the rendering guys about shaders in plugins, and it is certainly something they plan to address. I’d like to keep as a , even if it does become a standard one with the engine.

[ufna]

@;44643

Sorry for the troubles, but thank you for blazing a trail! I asked the rendering guys about shaders in plugins, and it is certainly something they plan to address. I’d like to keep as a , even if it does become a standard one with the engine.

It will be really cool to have shaders as part of , instead of placing them to the Engine

(Also as to get structured buffers support on OpenGL build)

[anonymous_user_e524e3781 (anonymous_user_e524e378)]

Hiya. I follow your install instructions and everything goes into the specified locations but when I start up the project I receive error:

[Dig_Squid]

@;46396

Dynamic clamping, so if you stick the fluid surface in a river channel on a terrain, it will (using the depth buffer) clamp the vertices that are underneath the terrain.

Would it not be better to precalcuate that as part of the map build process?

[anonymous_user_e805727e]

@;47314

UPDATE: As of right now the will not compile in 4.2 preview. I am aware, I have already updated the code here locally to work. (Just need to bring PNTessellation and FlatTessellation in line with the latest release). Will most likely update sometime weekend.

Erreur 2 error : In FluidSurfaceComponent: Unknown class specifier ‘HeaderGroup’ C:\UnrealEngine\Engine\Plugins\Runtime\Source\Public\FluidSurfaceComponent.h 43 1 UE4

[anonymous_user_e805727e]

@;49719

UPDATE: Black viewport does not appear to be related to my plugins. I have tested with a clean 4.2 preview build. Built from source, didnt add my shaders, or plugins. Still black viewport. Also noticed a report on Answerhub from someone else explaining the black screen.

You mean my report? Black screen in viewport using 4.2 preview build in many samples - Feedback & Requests - Epic Developer Community Forums

Are you getting blackscreen in 4.2 preview viewport too in many examples (Elemental demo viewport is not black but when you click play everything goes black)? Please answer me if you have same thing as I did, I want to know if it is general or only related to my PC. Thanks!

[anonymous_user_e805727e]

@;50096

Oops didnt notice it was your answerhub entry. I get the blackscreen viewport in the stylized demo before play. Ill try the elemental demo tomorrow. But I also get blackscreen in static and skeletal mesh editors and blueprints. Only of v4.2 preview.

Ok thanks, The only samples that work correctly with 4.2 preview are Cavde demo and Card game which did not get updated when 4.1 was released, but still you get tremendous FPS drop in them. Epic should update the sampels and 4.2 preview build source code before releasing 4.2 which was planned to be released week.

[anonymous_user_e805727e]

Please try to integrate your plugins by default with next engine update, because they are very useful and I dont want to compile them with each update. Thanks.

[Dig_Squid]

@;50114

Please try to integrate your plugins by default with next engine update, because they are very useful and I dont want to compile them with each update. Thanks.

I would like to make a 'standard ', because it is functionality we had in previous UEs, but we need to wait for to submit it as a PR first

[Tirem]

Even logged into I can’t access the download link. >.< Is it down or am I doing something wrong?

[febreez123]

@;46461

Hiya. I follow your install instructions and everything goes into the specified locations but when I start up the project I receive error:

I am also getting the same error. I checked the directory and the binaries were not built.