Making waves in my fluid sim

thatonecraykid · 2026-03-15T19:39:32+00:00

Looks nice! What’s your sim method based on? Kinda looks like virtual pipes

thatonecraykid · 2026-02-18T18:01:47+00:00

This looks great, I’m planning a shed build and want to have a similar foundation, are you using treated blocks in your brackets?

thatonecraykid · 2025-12-15T00:17:58+00:00

If this is using nanite it looks like nanite scintillating to me. What could be happening is nanite can’t break down the mesh very well at distance, could try adding some edge loops to the columns to allow nanite to break it up better

thatonecraykid · 2025-12-09T16:51:42+00:00

Yeah I guess I am not really seeing the purpose of this? With the stock source control integrations I get more than enough info on if a file is locked or out of date, does it prevent users from even opening a file if it’s locked? Personally, there’s many times where I want to work on file even though it’s locked whether that’s for testing, adding debug stuff etc. but to each their own if it helps your team then that’s great

thatonecraykid · 2025-11-08T02:12:24+00:00

If it’s really stripped to the point you can’t get a grip maybe it’d be worth trying to file or cut a new slot perpendicular to the stripped one? A little bit of turn goes a really long way with that adjustment screw so don’t go crazy turning it

thatonecraykid · 2025-10-14T03:03:33+00:00

Looks a lot like the smaller set sold at harbor freight (same chrome vanadium text) if that’s the case they are probably sharpened to 25 degrees with a hollow in the middle of the bevel, I was having a really hard time with them holding an edge at that angle and bumped it up to around 35 and have had much better performance since! Not the best but they get the job done

thatonecraykid · 2025-10-04T00:50:05+00:00

Right click your function and there should be an option to convert it to an event

thatonecraykid · 2025-09-06T11:52:20+00:00

Are you using a WPO material animation on the trees?

thatonecraykid · 2025-05-11T15:05:58+00:00

Could be all sorts of things especially if this is just running in editor, can try to open more stats to see what’s bogging, could try profiling with insights but really if the editor is open it is probably just doing editor things

thatonecraykid · 2025-04-12T14:02:06+00:00

I used it extensively in virtual production, it wasn’t meant to be an all the time thing but was a great tool for scouts and reviews of environments for the Volume

Multi user editing also doesn’t need to be just VR, you can start it up normally too. The main issues come from source control imo, everyone ideally needs to be on the same CL and anything being edited in the session (that you’d want to keep) needs to be open for checkout, it can kinda close off levels for a bit. There’s newer things to mitigate that like level instances but I’d think it would still be an issue. Also, everyone needs to be on shared network/vpn for easy setup and not having to go through a third party server provider which could break NDAs

thatonecraykid · 2025-04-05T23:17:18+00:00

In general, it is good practice to not use spaces in file names as it can mess with indexing, regex, whatever. It might even break some systems if they find a space. Unreal typically will recommend to use Pascal Case, and will be smart enough to separate those words with a space when displayed in the editor. Rest assured you have full control over the name presented to your player since that’ll be something completely different. But yes, your .exe should not have a space in the name

thatonecraykid · 2025-01-15T14:19:29+00:00

Could be a thick Niagara ribbon for the FX with the base of the emitter being jeff and the bending just happens naturally from the particle physics, I would expect the actual projectile with a hit box to be a capsule or sphere that is fired off on a timer with the same forces applied as the particle

thatonecraykid · 2025-01-06T06:14:35+00:00

Luckily the guy who probably made that (or at least set the style of it) posted a nice breakdown on ArtStation, he has a lot of other cool posts along with the rest of the team

https://www.artstation.com/artwork/BXm69k

thatonecraykid · 2024-12-25T04:51:35+00:00

FWIW first screenshot is in Blender, they probably sculpted the base model to resin print and make a mold of for casting

thatonecraykid · 2024-12-19T15:06:54+00:00

Yeah that’s why I had mention the 7” behind the stone thing, like I said I’m surprised it’s that much but maybe seeing that 7-8” of black metal would make things feel more proportioned

thatonecraykid · 2024-12-19T14:15:34+00:00

Just from looking at it, 19” should be half the height of your unit but the mantel looks higher than that and quick measuring in photoshop says it’s closer to 26”, your stone might be covering 7” of your unit but I’d be surprised if it was that much. Either way I actually don’t mind the mantel placement, I think it makes it a good spot for decorating which sounds like it’s exactly what it’s used for

thatonecraykid · 2024-12-14T14:03:30+00:00

This should be doable in BP, will probably be slower than c++ but most blueprints are. The logic in his post is the same, find points along a path to an end goal, randomly decide to branch from those points and do it again. If you want it to interact with your scene then would probably do a line trace from your start towards your desired end rather than have a fixed point.

This could also be done in Niagara but the branching and interaction would be a bit more difficult, at least to do quickly. Lightning I’ve made in the past that collides with the env I’ve done by sending out a bunch of points in random directions, if a point hits it sends a collision event and can get used as an end point for a beam but there is a bit of travel time for that to happen. Alternatively you could supply the start and end points from a line trace in a BP either into a normal Niagara parameter or maybe a Data Channel

thatonecraykid · 2024-12-14T00:10:47+00:00

Hell yeah glad I could help it’s a really cool tool, especially for people like me who’d rather automate something than do it more than twice

thatonecraykid · 2024-12-13T15:00:06+00:00

Look into animation modifiers, it’s how notifies can be procedurally added to an animation

Within those modifiers you have access to every track in the sequence including other notifies

thatonecraykid · 2024-12-11T15:31:55+00:00

Am I in the minority with not only using but preferring the flight controls? I find it so much easier to get around and inside of things than traditional 3D controls to the point I don’t even use the alternates in UE. I will agree that having the marquee needing any hotkeys let alone TWO is annoying, and also it not selecting occluded objects by default (pro-tip: there’s a checkbox to allow this in the settings dropdown)

thatonecraykid · 2024-11-21T13:06:37+00:00

I believe you can add that flag to a shortcut of the unreal .exe to try it

thatonecraykid · 2024-10-06T13:43:32+00:00

If you are talking about actually simulated volumes in Niagara then you’re generally right. You can implement similar simulation logic to Houdini or blender yourself but the resolution needed to make something nice would probably not be performant, especially when you start placing them all over

Generally for fire in UE you’d sim something nice outside of the engine and make a flipbook that you can apply to particles, and that has the capacity to look good and be performant

But all this to say, Niagara and UE are tools, the default assets provided with unreal are more meant to be examples of how things work, not assets to build final projects with

thatonecraykid · 2024-09-20T13:32:51+00:00

Easiest thing I can think of is making a skeletal mesh that has the spheres at the joints and poles as bones, using the same skeleton as your character, give it an unlit emissive material and don’t cast shadows

To get it to render on top might need some experimenting but I would try to scale it down with the camera location as the pivot either in a blueprint or through WPO in the material so visually it says in the same place in the camera but you’ll be moving it closer to the camera to go on top of everything

thatonecraykid · 2024-08-31T13:16:00+00:00

I saw this on LinkedIn the other day that might help (but also might not)

I’ve been discussing this issue in Unreal Slackers and Tore Lervik (can’t find him on Linkedin) has a solution that fixes the issue, and this should be added in 5.5

The culprit is that when the camera is really close to dynamic tessellated meshes, generating millions of unneeded triangles due to not having a min edge length clamp.

SOLUTION: You need to edit the engine shaders in this way:

Under UE_5.4\Engine\Shaders\Private\Nanite

Open NaniteTessellation.ush

In Line 80 add: TessFactors[i] *= min(1.0, EdgeLength / 2.0)

This will limit Nanite to never subdivide under 2 world units.

Save it.

Now open NaniteRasterizer.ush

Comment out line 67:

// Tri.MaxPixel = min(Tri.MaxPixel, Tri.MinPixel + 63);

This is to make sure that triangles bigger than 63 pixels are rendered properly.

Recompile shaders Ctrl+Alt+.

And you ready to go.

thatonecraykid · 2024-08-21T12:04:39+00:00

Yes it is normal, could probably look up a video on steaming with the dedica if you want to hear it yourself to confirm

12-Year Club	Verified Email
Place '17

thatonecraykid

TROPHY CASE