not sure how to work the hlods

Summary

trying to do hlods but I’m unsure what’s stopping it apart from these errors that I do not understand maybe somthing to do with my files?

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

World Building

Platform(s)

pc

Island Code

not yet

Upload an image




Screenshot 2025-01-25 014752.png

Wow, I haven’t seen that type before.

World Partition errors
Localization errors… I did see some posts about that

I can’t open the bottom image

Can you post your World Settings again ?

1 Like

Screenshot 2025-01-25 014752
last picture doesnt let you on it??


Screenshot 2025-01-26 003509
world settings

Have you used Build World Partition Editor Minimap and Build Autolocalization on this project ?

Maybe thats what the errors are referring to, if you’ve made any map changes since doing it ???

No never used it before
This is a different map from than the other map you might remember that I needed help on

Yes, I remember

I see your using the regular World Partition on this one. Lucky, probably would have wasted even more time playing with the new ones settings.

The HLOD name is funny… not for you though…
So you replaced the HLOD layer a few times ?
and does Build Landscape give any red errors ?

Must be something map side props or other stuff
what non prop stuff have you got going on ?
did you modify any HLOD settings for anything non-prop ?

1 Like

Building landscape does give a red error but it doesn’t fail last time I did it I saw that there was only a issue with a prop manipulation volume but when I click to go to the prop it does nothing (on message log).
I have only turned off HLODS for inside buildings like walls and floors and other buildings things.
I have enabled HLODS for props that I’ve resized?

Red Build Landscape errors will fail HLOD.

So the prop manipulator doesn’t actually exist ?
or does it.

see if you can find a name for it thats a .uasset file
type it into the Outliner and see if it comes up, if it doesn’t maybe it will give a path so you can delete it with windows

if it doesn’t then something may be referencing it even though its gone, check anything it might have been tied to.

1 Like

Am gonna try do your suggestion today after the Fortnite update but I have a question about the data layers because am I supposed to have 7 on one map?

Are you using data layers on this map ?

I have no personal experience with data layers.
I would assume you could use as many data layers as memory permits,

Do devices always need to be loaded, so they should not be in a data layer?

Does having props in unloaded data layers cause issues if they’re included in the HLOD, can’t be calculated because they’re not loaded or something of that nature ?

Is this where the new World Partition settings would be used ? A different HLOD layer for each different set of data layers ???

I of course have no answer to any of your questions unfortunately but this question was for the map that kept crashing whenever you load it up in launch session I was thinking could that be reason for it as no other project I have has that many.

I found the prop manipulator and got rid of it thats no longer a issue but this might be where all the issue is:




this island was duplicated project named “outbreak” and it was put on “bigreload” which I deleted the level for

Ignore those load errors, they’re normal for all at the moment.

OK that sounds like a reason for it not finding the path.

Maybe double click on your GameFeatureData in the Content Browser and check the default map.
Maybe theres other places to look that hold the default level info or something ???
Researching what is affected by duplicating projects and changing map levels might be the go.

1 Like



its the right one
there’s millions of errors about thing in the content browser saying that the system can’t find the file specified
not sure if output logs transfer same messages form project to project but I have all those red errors on a different project

The localization thing is an issue…

If you auto localized on the old level or the project with the level you switched, that could explain these errors and the localization needs updating or replacing.

I also read the autolocalization can affect textures with words on them or some internal naming that needs it.

Maybe a Build Localization could help…

I’ve also been considering the snapshot situation, if not all files are accounted for or even mild HD corruption, moving the entire project folder elsewhere before syncing to a previous snapshot, would give a totally fresh folder just in case something has been left over.
I wonder if making a snapshot, moving project files then downloading the snapshot would clear anything ?

1 Like

Sorry I never got back to you I gave up.
But your help was very appreciated and I am on the right track so far🫡

This topic was automatically closed after 180 days. New replies are no longer allowed.