Відео

I'll say this. Datalayers still have some issues. One of them is this Async issue. I haven't found a way to properly Async load layers without just being very careful of assets within the layer. The reason I use a combination of world partition and layers is to offer a degree of control to individual rooms if necessary. If world partition is off the table then there are other ways to handle this though. Either a Tighter control of what assets are within a space, which would mean more layers. Or actors within layers that handle loading some of the other layers, or actors. I'll give an example. You have a Layer with a single (Or multiple) actors inside it. within that actor is a begin play or other event command using either delays or a timeline potentially that starts a controlled loading process of other layers or creation of additional actors when it starts ticking. Basically making the initial load cheap and spreading the cost over a period of time like Async would do. This is not really ideal but until epic offers a better solution this is a work around that can be used. It's not the worst work around but its not the best either and larger games may have trouble using this in a general setting due to complexity.

@@UnrealFundamentals Thank you! Thats pretty helpful! Hopefully in 5.5 they fix this.

If you are using world partition and datalayers it could be streaming them out based off the partition distance. First thing I would check is if you have them set to world partition streaming or not. Or if you accidentally added them to multiple layers. If you regularly copy or duplicate actors it adds them to the same datalayer as the original actor but can also add them to whatever datalayer you're currently working in which can be confusing if you don't catch it.

@MrElgate yeah. AI gets complicated but you can check for tags using the blackboard keys and the custom BP Decorators. It's been a while since I've done it but it's definitely possible.

well world partition can be very helpful but it's also kind of non-descript. A good example is a building with lots of hallways or connected walls with a bunch of tightly packed static meshes. these can be a huge burden on performance in a small space and relying on world partition can load in a bunch of stuff you don't need which will use ram and GPU performance while it culls the objects you can't even see. it really is something that needs to be decided on a per instance basis though. world partition can be customized to an extent but it has its limits which is why datalayers exist. In fact I primarily use datalayers over world partition since it gives you really good control over what is and isn't loaded in.

@Shexuja This is true. I handle data layers in a similar manner. world partition has a lot of advantages, especially in open world designs but in more linear or closed off areas, I think datalayers are far more performant. really though using them together is the Ideal where world partition can handle larger structures or things that are generally more visible while datalayers handle the objects or more hidden areas where you may only see them briefly under certain circumstances.

@@georgesoros7849 Thank you for that. I appreciate the comment.

@Cazaq yeah. I specified 5.3 cause I didn't want people to try this on other versions and expect it to work. A lot of things will probably change about all this. The way epic handles datalayers is new in general for them so hard to say where it'll all end up.

Oh...it works on server only, so there is no way to use it in multiplayer

Glad I could help!

There is actually a solution to this. its not very complicated but its easy to miss. give me little bit and I'll make a video for it specifically. I'm sure a few other people will be looking for this same thing.

ua-cam.com/video/7Hp4-gJ0SAQ/v-deo.html Here is the link to video.

Glad you liked it. I ramble a bit. I try to be Succinct but I want people to understand the system itself and not just copy it directly since that's usually more helpful in the long term.

Yeah a lot of stuff changes between versions and ue5 as a whole is changing regularly. I've been trying to title my videos so they mention the version number specifically so as they change things it hopefully wont conflict or confuse people. But yeah 5.4 is pretty crazy. I typically don't mess with versions until they fully release in case epic changes some stuff from the preview to full release, which does happen sometimes.

once 5.4 fully releases I may have to go back through and do a more in depth video on that as well.

@@UnrealFundamentals ​ @UnrealFundamentals Yeah, it's like they heard us. Last night in our country, the official version of UE5.4 was released. I'm also researching about world partition because I've always wanted to understand it and create a huge world, combined with UE's Mass AI system. Looking forward to your new video, blogger.“

I would agree with this to an extent. I think it depends on how you use the data layers though. if you use it like how I do in this example then having HLOD on smaller objects would most likely increase memory usage and impact performance. if you focus on using just HLOD and world partition and ignore the Data layers then I think this could work as well but using all 3 for distance based visuals would probably be overkill and end up negatively affecting your project. as a side note to this. if you focus on HLOD and world partition and use data layers to just change the environment in drastic ways, like if you want the same landscape but maybe a town or something gets bigger over time then I think this is still a viable way to use all 3. that depends heavily on the type of game you're making though.

Thank you for that. You're my first comment on any video. if you have any requests let me know. I have some ideas but when you can talk about anything sometimes coming up with a single topic can be a bit challenging.