If “Project Settings” > Engine > Rendering > Texture Streaming is True, when I start the game (Launch on Windows or command line), the scene is rendered, however, at the beginning, landscape height is not accurate, after a while, the height is correct.
If Texture Streaming is False, I experience longer loading time before the scene starts to be rendered, but I don’t see the height inaccuracy once the scene is presented.
Thoughts?
Thanks!
============================
It could also be that the geometry LOD is not at 0 at the beginning, but how can I eliminate the problem?
Could be:
-
If using OpenLevel() and Texture Streaming is True, the landscape LOD mesh is not fully generated when the level is fully loaded into memory and starts to be rendered.
-
If Texture Streaming is False, the loading time is long enough so that the LOD mesh is fully generated when the level is shown.
The landscape heightmap textures should stream in almost instantly. How long does it take for you?
The height inaccuracy time is several seconds.
Is this with cooked content or just launching with -game?
How large is your landscape?
The texture streamer is supposed to prioritize streaming of landscape textures over everything else, so I’m surprised it’s taking long at all. This was a change for 4.10 I believe. Texture streaming is optimized for cooked content, however.
I somewhat failed to cook, so it’s -game. Landscape size is the same as LandscapeMountains demo.
Hi, I appended to the quesiotn: “It could also be that the geometry LOD is not at 0 at the beginning”, thanks!
Looks like the engine does not prioritize streaming in mipmap 0 of HeightmapTexture or not prioritize the nearest component’s mesh to be generated first.
“r.TextureStreaming 0” results in similar effect.
I can use the Move Level tool to move the “component on which player is spawned” to another level (Loading.umap, which is small and loaded very fast), and Load the other landscape components as a Streaming Level.
Maybe should utilize World Composition.