Couple questions about world wrapping, streaming distance and some other things.

So far I was putting my world together with the World Browser using tiles in a layer with a certain draw distance.

First I would like to know would the best way would be to make a wrapping world. Basically be able to walk in one direction and end back up where I started. The world will be big enough so you cant see to the same place again. I would also like this to work over multiplayer. I also thought that UWorld:SetNewWorldOrigin was implemented and called when entering a new map tile, but that doesn’t seem to be the case? My pawn’s coords are still increasing/decreasing when walking over to new tiles.

Then I would also like to know how to change the tile stream distance during runtime with C++ so I can change it together with the view distance.

Also, any suggestions how big in m/km a tile should be and how far the max view distance should be? And to have a more detailed terrain would it be ok to use a terrain scale of 50 instead of 100 or would the performance hit be to great?

Thanks for any help and suggestions.

Also have a question on answerhub if anyone would rather reply there: Any theories on how to make a wrapping world? Also, how to change stream distance over C++? And could use suggestions on what world tile size max view distance and terrain scale to use. - UE4 AnswerHub

I’ve been researching this issue myself instead of working this morning. This is all I have gleaned, I could be wrong though so take it with a grain of salt. Single player is in better shape than multi, but see this link for a discussion of Unreal tech for a server side solution to larger worlds. Basically it’s going to take some work on your end. Also here.

TLDR; A) World Browser at this point won’t let you do a world that wraps back around it seems. B) Changing streaming distance at runtime would be cool, hopefully they’ll expose it as they develop the world browser C) size and scale will be a function of performance, and really, for most computers, having 8k of heighmap being displayed at once (no matter how you stretch/scale it) is quite a lot of data. I’m in the process of running some tests, but I’m starting off with terrain scale 100 and a max view distance for of about 12 kilometers. I’m hoping that beyond that a little horizon fog, proper terrain occlusion, and some luck will keep me from seeing the edge of the earth.

One thing, though this depends on your needs: terrains really don’t need to be that high-res, with a normal map baked from a high poly version of your terrain over the whole terrain tile and some other shader tricks (global color map with AO Cavity and Edge maps along with a tiling noise normal) you can really get some good looking stuff. I’ve actually ran into the opposite problem when using world machine, too high resolution and the terrain becomes unplayable because of all the erosion channels and funky stuff going on. More often than not I find myself smoothing the terrain down in world machine after baking the high resolution terrain for maps so that it’s not a PITA to traverse. Most terrains are actually pretty smooth in part so you don’t get stuck, and you don’t need a lot of resolution for that. Consider using static meshes in the places you need that little bit of extra detail (sharp cliffs/etc).

and vote for the large world coordinate system on the roadmap.

Just my .50