Shit is not hard, it's easy to get 75-80% there, which for most cases is good enough. the last 10-15% is the tough work of fine-tuning it and experimenting to be perfect for your application. Game companies can afford to do that because each extra percent nets them more time they can keep a player addicted to their game.

Could we use load instead of sample? Its faster and we dont get into interpolation problem.

THATS WHY HES THE GOAT! THE GOAT!!!

This might be a silly question, but why is there a memory concern with the flipbook? Isn't it a single 4096x4096 texture that is sampled multiple times? Is that not particularly small in the grand scheme of things, in the case of a game that would utilize 2 or 2k textures for most assets?

Amazing I was thinking about something like this for vr games where I don’t want to stress the gpu with distance field collisions. For the last problem you could just parent the particle system to the mesh and have the calculations in local space until it drops?

Awesome! Looking forward to part 2!

Other solution less complex.. im my case use in videogames when my lead don't want use fake particles with stripe billboards is: one emisor for impacting traced particles with the ceil surface where I use o the position of the hit and killed position generated death, 2nd emissor for spawned owned particles emisor taking position with a event handler, finish this one again with other emisor for create the droplets when hit the other emisor on the floor surface using a similar method that in the last situation. In all this process Iam not using CUSTOM nodal scripting. I apologize you because not speak english nice. I prepare this fx in less 10 minutes with a nice enhancement. I wish to know the advantges your complex and interesting propousal. Nice day guy.

Help~ I can't find "Add Particle" from NeighborGrid3D, I'm using UE5.1

when is the grass model tutorial, its awesome

Quick question, I'm currently using latest version of unreal engine and I'm contemplating whether to use lod or nanite grasses for my game, which one is better for the current state of ue? Performance wise, thanks!

Why your wind texture uv can scroll by it texture node self without any time node? 16:01

I would love to see you implement this with the actor pooling you've mentioned. I might give it a shot aswell if I have the time. This could be like an automatic solution for limiting the amount of skeletal meshes you want to simulate at once, if there are multiple pawns interacting with foliage, since the system is dependant on the amount of pooled actors you have spawned in the beginning. We may need to implement prioritization around the player, since this is the area we want to see the effect all the time. And what about using two LODs of the skm, one with more bones and one super simplified with for example only the root bone, that is only used if another pawn in medium distance is interacting with the foliage? I have no idea if that would even be worth it regarding the extra work and the visual effect tho.

I'm familiar a bit with c++ myself already (created a few not very complex game features), but I would still be looking forward to see your approach.

omg your videos is unpredictable fr fr

How's performance? It's for big projects?

Awesome tutorial. How would this be applied to physical boids like other AI enemies, not Niagara particles

Really amazing, is there any possible to make the tutorial for waves and foam for sailing boat, thanks in advance 🐱

1:14 where is this plugin located at?

Hi, does checking off "World Position Offset Writes Velocity" setting on the InstancedStaticMesh component help with that velocity glitch? Didn't have opportunity to check it myself yet.

Amazing tutorial. Would you consider doing a tutorial for making an interactive snow material / system? I tried making one using parallax occlusion mapping and render targets but never got it fully working.

Is there a way to implement this into my arch viz project?

Yesssssss

A couple of things from all the feedback I gathered: 1 - Static instances could be simply scaled to (0,0,0) for the skeletal swap, instead of removing/adding instances! You'd then need to store that index in the skeletal blueprint so you can revert that instance's scale back to its initial (x,y,z) scale to swap back with the static instance. 2 - Static instances could be configured to have a simple spherical collision and overlap events could be triggered on your character to get instances you'd be overlapping with. The 'OtherComp' hit component could be cast to an FoliageInstancedStaticMeshComponent and the 'OtherBodyIndex' would thus point to the instance's index, to trigger the skeletal swap. That would allow you get rid of the 'get instances overlapping sphere' method and solve the spatial query problem by letting Chaos handle that optimization on its own. 3 - The dual character capsule setup is unecessary. You can call 'IgnoreActorWhenMoving' function on the character's main capsule and provide the spawned skeletal actor to prevent the two-way interaction! Thanks to all of you for your very valuable feedbacks!

Au lieu de supprimer une instance et l'ajouter de nouveau plus tard, il est possible de passer une transform avec un scale de zéro ( via la fonction UpdateInstanceTransform ) C'est une technique utilisé communement

Does this grass properly move when a player character walks through it? I apologize, but I watched the video and I still am not clear if it's physicalized in this manner.

Hum, et si on utilise le lightweight instance, qui permet de changer automatiquement un ISM en actor correspondant, ce serais pas plus pratique ?

Is this gonna run on mobile? And how "cheap" is it actually (like would you do this for actualy games)? I really like this idea tbh

What I don't understand is EPIC has a HEAP of different more efficient data structures available in C++ they could expose to BP to help people out instead of everyone doing AllActorsOfClass / Sphere Overlap on their Character etc that everyone currently does... THierarchicalHashGrid2D (MASS and SmartObjects use), THierarchicalSpatialHash, TSpatialHashGridPoints, TPointHashGrid2, TPointHashGrid3, FSparseDynamicOctree3, TOctree, TOctree2, FSparseDynamicPointOctree3

Est-ce qu'il ne serait pas simplement possible de faire un capsule trace sur le tick ou sur un timer et de simplément convertir les objets qui sont dans le hit?

Merci pour le bon contenu !

I made similar thing about month ago and had most of the same problems and found few things. You don't need to replace skeletal meshes with static meshes, there is render static bool on skeletal mesh component, that renders it without bones and you can change it in runtime. I placed them in level as bp with sk components and tried to turn off tick on bp, but through insights I found that skeletal meshes are still ticking separetly, so you have to turn them off too, that was quiet heavy on CPU. There is also only tick pose when rendered option on sk component and you can also turn off simulate physics, when you are far from it. Disabling skin cache for sk asset can get you some performance, because you don't need it when its interactive.

I had the same experience with lightweight instances! What a pain. But in theory they can do things which are very hard to do by yourself. If I remember correctly they will do some conversion under the hood if you trace against them they will get converted as soon as you acess the underlying actor. So the pointer will point to an actor which doesn't exist yet. Or was it on trace hit? No idea. And no idea if it actually works. But sounds pretty cool especially if you don't have to replace line trace code and such.

could apply this to fluid flux?

Hi! May I know how to slow down the scan outline effect and also how to make the blue color transparent (from the video 11:08)? Because I set my range to a very big number, the effect happen too fast, causing not gradually smooth transition. The blue color also covered up my entire sky and it doesn't look good. Thanks in advance! Fyi, the MF_ScanEffect_GetGridWorldPosition function can be fixed from (BPAC_Scan Component), I think it is from the [event begin play > set scalar parameter value > grid cell size default value], set the value other then 0, should be working properly

Couple feedbacks as I finish this tutorial episode. Thank you so much for the free content. This is absolute gem. Everything is high quality, artistically and technically. With everything plainly shown. 14:16 - I love that you explain everything in depth, even though in the final product you don't really use the implementation. It really helps us understand what we are doing, instead of blindly following the tutorial. (TBH, I don't understand half the things about the Technical Art side, but it's nice to see what affects whatXD) About optimization - I was beyond surprised that the frame time was so low. I implemented mine in C++ (which is why it's been taking me longer than it should). Got the frame count to be around 0.03ms... I'm going to have to test it out in VR (maybe it'll be around 0.2 - 0.3ms?), which means if I'm going to use Forward Rendering, I will disable some more features, which might possibly decrease it even more (around the 0.2ms mark). Excited to go to the next episode.

Cool video! Great chennel! Subscribed.

Nothing makes sense. If you want to teach something, explain it step by step from the beginning to the end in a single video. Even if you made a blade of grass in Blender, explain how you did it. This way, nothing makes sense. You would only satisfy yourself.

Is there any way to implement the outline effect with Forward Rendering, or is it only for Deferred Rendering? The World Normal node seems to be only supported by Deferred Rendering

1:50 :D

Hi I am a beginner UE5 developer. Is there a reason why you spawn the postprocess actor instead of just making it a component of the Player Controller? Also, what are the instances we have to set the post process priority to a high number? What could be some specific circumstances where overlapping volumes cause a problem? As always, thanks for the video:)

Great tutorial! Although I'm way out of my depth, I maintained enough neural buoyancy to get it all working up to 18:00 in UE 5.4.1. And now for the waves. And my question: would this work with Niagara Wave Pool system? Or even Houdini wave/particle sim brought into UE with the HoudiniNiagara plugin? TY again for the tut, I'll see if I can recreate that super simple water Material shader next.

Approximately after 30:00 my brain started to explode :)

Really cool stuff, Ive been working on a foliage generator in engine using geometry script and my own implementation of the LSystem branching algorithm.. with some tweaking it could output that point data no problem along with a generated mesh.

blueprint struct 😱😱

This is fantastic.

It's more expensive to make vegetation interaction based on bones, so it's not as good as shader.

Nice work.happy to see you progress :)

I still don't understand how you created a random color for all the grass

WOw!

This just makes me smile. I joined your Patreon to support your work. Thanks for the amazing breakdown!