i have a question about the nexus in the a6 engine. i have a computer with 2gb of ram, and a Huge level that needs about 900 of nexus. the thing is, the engine won't let me increase the nexus beyond 1024, no matter how much ram i add or virtual memory i set in windows, i get the message "Not enough memory (0MB required)". what does that mean? is the engine limited to 1024 in some way? is there any way to get past that?
thanks in advance

I have a large level with a nexus of 55.

How many entities are in your level?

So what, you're using a nexus of n.i.n.e.-h.u.n.d.r.e.d. m.e.g.s. ? O_O O_O O_O

In that case, I'm afraid, it is indeed _very_ likely for A6 not to be able to handle this. But since you usually have to push up your nexus when creating hundreds of entities in WED, why not try creating some of them at runtime via ent_create instead? Maybe this method is able to overgo the nexus limit. Just a guess, though.

I'd honestly recommend reducing your levels memory usage whereever possible. A nexus of 900 mb is almost impossible for may computers to deal with, I assume.

Joa, split your level for sub-levels, make some scripting for model/level dynamic loading. you don't need anything in level, that isn't visible by player in a moment. or you can play your game at 'matrix' like computer only

My suggestion, as an addition to Lion_Ts, is not to go over 384MB if you're targeting users with 512MB of RAM. Try to keep it at least 128MB off of the total memory, so you can play nice with the operating system like Windows XP and other programs. In other words, if you are going to target those with 256MB of RAM, go with the nexus of 128MB. Try to go as small as possible, along with your levels. Use less texture sizes as possible as you can. I hope this helps.

Though, if I may add a word or two, texture sizes usually matter more with regard to video ram instead of system ram. As most modern graphics cards have 128 MB VRAM or even more, texture sizes shouldn't be the problem here as those are normally loaded into the VRAM which is completely unaffected by the nexus to my knowledge. I may be wrong though...

When textures exceed the amount of video memory available, they are put into system RAM. When system RAM is low, it goes on the hard drive as swapfile where it becomes really slow. With the new MED, you can have the textures be linked to externally so only one instance of them is stored in video memory instead of 5 instances (duplicates) for 5 different entities using the same texture.

Splitting the level up into sublevels seem to the the best option available for you.