Proper Map making guide

[AP_Studios]

@Tymax;687163

I am rather surprised to experience a lack of documentation/guides on how to properly create a map for ARK.
Nobody (also not in all the outdated video “tutorials”) ever gets into that topic, besides the self-explanatory stuff.

I’ve picked together what i can from Twitch streaming sessions and would like to point some things out before i continue to walk in the dark. This might also comes in handy for other people, who want to get into map creation for ARK and wonder about these basic things.

I’ve basically created a test map with the size of the island (1x google search for the sizes). After fiddling arround with the landscape materials, I found out that there is a package for materials which includes all of such, which are used in the island, the center and scorched earth. In case you are new, here you go -> Universal Landscape Material - ARK Modding Wiki

After setting up everything, I’ve cooked & exported the map (local, no upload). I then copy the modfiles, load them in ARK and get started on my map - but the performance is terrible.
This is an example what I meant - you basically need to create multiple landscapes and add them kinda together - that doesnt get mentioned anywhere.
And meanwhile i really wonder, is that the correct way? You create a bunch of levels with each a landscape inside and then fiddle them together to make it look like its one landscape? Or am i missing something bigger in this whole spaghetti workflow?

This question directly allows for a subquestion - while loading other maps one can observe that they are split into x_far and x_near. If i had a guess, x_near simply adds smaller meshes, rocks, grass and maybe some non-culling clutter - am I right about that or is there an even bigger scheme?

Here is the thing …
Ark uses level streaming, but, on a very very simple level. Yes they use “chunks” like level streaming, but, all levels are always loaded. They do not cull out. Your performance issue is possibly something other then the landscape itself (depending on the map res, 1k, 2k, 4k, 8k)
Ark uses 4.5.1 with some 4.7 features
Ark uses some really out of date assets
Ark uses some REALLY bad blueprint code, like, really bad
Ark uses little to no optimization in any area of the code/blueprinting
Ark uses 0 documentation (for its modders) and most, if not all, data is so far out of date its nearly worthless

^ we can argue that the functionality and issues are due to being so far out of date, and, using an edited version (to work for them) of the 4.5.1 source for UE4, the world will never know. Point is, you are doomed from day 1.

The foliage scheme > you are correct. Nothing more then a culling reason. Its setup wrong, for proper foliage culling, but, F it … its their design
I made a map, using the proper culling and design schemes and i was able to extend to replication bounds (1.2 mil x -1.2 mil X Y) and you would have never known things were culled out at any time. The trees just use LOD and stay in place (to cover that all the other foliage is missing). Its just a performance trick is all. Hide what users cant see from a distance to help unload and save on memory.

Making 100 maps and adding them, or, 1 map and using it, makes no real difference. I say this while biting my tongue due to its situational. I wouldnt ever load a 4k map in Ark, thats just asking for pain. 1k sure, anything less, might get a bit ugly on the eyes. Welcome to making maps - you think its bad in the first day, just give it time, it will get much worse. lol.