I'm not sure if people ran into this issue, but I have tracked quite a lot of memory usage down to overly sized worlds (not so much the objects in it).

I have created a world with 1200+ area's, and painted them with textures (some are overlayed of course for additional effects), and my memory usage goes to 91% of my available juice :(

My specs:
Intel Core i7-4960X 3.6 GHz
Asus 2011 Rampage IV Extreme
Crucial Ballistix Tactical 24GB DDR3-1600
Nvidia GTX 780 TI 3GB
EE 2.0 64-bit editor

I have duplicated my project without the large world, and do not have this issue. I also tried and decrease the viewport-size, as well as turn all the graphic-settings as low as possible, though without much luck...

Anyone else with an insanely large world not streaming correctly??

Additional information:

- Max viewable area size = 4
- Tested on 2 different units, same issue

It appears so that the editor loads every heightmap[area] in the entire world, and then starts streaming; is there something wrong with the unloading of heightmaps not in the active range?

Hi, I've just tested this on ERPG2 world, and don't have any issue.
I've set view area radius to 1, then to max, then to 1, and memory usage was normal.

Perhaps your world is being processed in the background thread.

You can verify this by doing "build/export/project data"
-here if it waits for world data then it means it's still being processed

I started the "build/export/project data" about 2 hours ago, and it finished 200 world areas of 1790 total areas.

So once this is through, EE won't take 22.898.435 kB of memory during the normal process?

It shouldn't. EE unloads from memory areas that are out of range.

Well, to get back to this, I found out the following:

I let the engine build the areas (all 1790 of them) and the world now loads faster.. However... Each time I am in the world, or I add some objects to specific areas, the world freezes for about 10 seconds, and my RAM goes up to 14gb. This happens roughly in an interval of 20 seconds of no lag, 10 seconds of lag, repeat. Of course, after checking this, I closed down the world and let it build again, seeing that 96 area's need to finish building in the background...

Thus, my question: why is this background thread soooooo slow, and how can I improve on this?

EDIT: Building 96 world areas takes about 15-17 minutes in the background
EDIT2 : I added 3 objects, 5 world areas need to finish building, and using 20gb of memory.

Can you please attach some screens of your world? (different angles and zoom)
I'm curious if it's any special.

Can you let me know the world settings:
-size of a single area (in meters)
-heightmap resolution that you've selected
-please attach the screen of World Path Settings (the Tab on the top)

Do you have any complex meshes in the world? (hi poly count)

World Settings:
- Size of Single Area : 64 (default)
- Heightmap Resolution : 64 (default)
- Path settings as image attached

World Screenshots:
-- Link Removed; issue solved --

Password of the file is in your private messages [sorry guys, I don't like showing unfinished work]

Additional Information:
- When I let the world active in the viewport, it finishes to build areas faster than if it's not active [Took roughly 20 minutes, instead of 2 hours]
- I get max FPS count with a view range of 20 after areas have finished building
- No high-poly models are in place [all models are split accordingly from within 3DS Max, edited the pivot, and imported in the engine]
- All assets in the world have physical bodies [Trees do not have physical bodies on their leaves of course]
- Leaves are rendered as grass [not all, only those on the ground or of small tree's where the environment allows it]

You've set Path Cell Size to 1 Centimeter, which is overkill.
This is the cause of your high memory usage.

(04-20-2014 10:17 PM)Esenthel Wrote:  You've set Path Cell Size to 1 Centimeter, which is overkill.
This is the cause of your high memory usage.

And you are right! I created a new world and compared the Path settings, oh my. I could have edited those in the beginning when the world was still small with the illusion that it would affect how I would place objects on a grid...

I guess even the strongest of computers cannot handle that kind of stress!

I now set it back to standard; what would your suggestion be for a naval-based game filled with islands ?

set as high value as possible