[Community Project] WIP Weather & Water Shader

[anonymous_user_0df12f74]

@Dijon;251584

First of all, I would like to thank those who have contributed so freely of their time to bring community project to life. Something that I noticed in 's tutorial video, he used temporary sphere components to create a visual representation for each of the values in the TestPoints array and I thought, “****, that’s clever!” (Kind of wish I had thought of it though). At the end of the tutorial, however, he deletes the spheres and I was thinking that it might be useful to keep them to facilitate tweaking or further upgrades. I also wanted a way to automate the visualization process so that the buoyancy spheres that appear onscreen are the same size specified in the Buoyancy Movement Component. I have an implementation that contains both C++ code, and a blueprint macro, to do and want to share it in case anyone else can make use of it. The problem is, I don’t know how I should do . I had trouble with Project v1.0 so I downloaded the Demo that provided a link for. Therefore, I am not working from the plugin project as I don’t know how to integrate new code into a plugin (not a problem with the 4.7 Project that I am using).

So, with the disclaimers out of the way, here’s what I did. Hopefully the pictures are clear enough to read (and follow). In short, I created a C++ class that is derived from USphereComponent, so it is essentially the same as what used, except that I change certain parameters from their defaults so that the end-user doesn’t have to change the values in every buoyancy sphere. The values set are:

• Visible in Editor
• Hidden in Game (can be changed in the BP macro to change all buoyancy spheres at once)
• No Physics, No Collision, No Mass so that the buoyancy spheres do not physically change the model.

The user can use Add Component to create these buoyancy spheres as components in his/her blueprint. The code for these buoyancy spheres is as follows:

.h file

.cpp file

The blueprint macro:

The end-user Construction Script:

If anyone finds useful, you’re welcome to it.

Hey Dijon,

Thank you very much for looking into ! I created a basic setup that drew a DebugSphere using the radius and location, but it is rather glitchy since a DebugSphere from blueprint requires a Duration. From a construction script a duration is problematic, set it to a few seconds and move the sphere’s location causes a thick line of spheres to be drawn in that direction, or if you set it really low it disappears too quickly. To turn them on/off I just created a simple boolean for Debug mode, and also added in a Struct to the plugin to represent a testpoint (Location, Radius, and Buoyancy Multiplier) to make it a bit more standardized. Both of these recent additions will be ideal for integrating your solution above.

is extremely helpful as I had been planning on recreating the spheres in code (due to the issues noted above), so you couldn’t have posted at a better time! I will integrate it into the project asap, it looks like a great solution to the problem. Thank you very much for putting together, I will add you to the contributors list as well.

Right now we are adding in new additions to the branch on , the 1.0 branch has already fallen behind. So if you want to test out the latest features (I will add your code in today) you can Download as Zip or fork the repo from here:

Thanks again for sharing !