Hi.

Is there a way to have more than 500mb for a WMB ?
Iam pretty stuck right now cause of that nexus - thing...i dont see a full working map with this limit.

When using -nx command above 500 i get "Out of memory" on game start. Is it because my video card is 512mb ? Or has this nothing todo with the nexus value?
Memory usage is around 700mb btw, says the debug panel.

edit: I already reduced size of nearly all textures to max of 1024x1024 (DDS only). Using ent_animatefrom etc. I could save a lot of memory (around 80+-) for the 4096x4096 terrain texture (using cause ShadeC terrain shader is not finished). I know acknex is old and i already design/building less than expected in my mind, but still i feel 500mb is not enough. Guess with around 600 i would be happy. My "problem" is that nearly all npc's, guns and assets are on screen (one map), maybe thats why i want to consume more than 500mb nexus...

Any tips ? Is there something that consumes a lot of nexus i should take care of ?

I have found this in the documentation:

-nx number

Size of the nexus in megabytes. The nexus is a contiguous virtual memory area that the engine allocates at startup for caching entity files and level textures and geometry. It speeds up level loading and prevents that the game suddenly aborts at runtime when memory is running low. The nexus size depends on the size of the biggest level of the game. The bigger the nexus, the bigger levels can be rendered - but the more virtual memory is allocated at startup .

When you set the nexus in Map Properties, WED uses the -nx command line option to transfer the nexus size to the engine. The default value for the nexus is 40 megabytes. The maximum value is limited by the Virtual Memory Setting of the Windows OS, minus around 500...1000 MB that should remain free for the operating system. The current nexus requirement is indicated in the statistics panel and can be read from the nexus variable. The recommended maximum nexus value for commercial games is 200. When setting higher values, you should be aware that several Windows subsystems - including DirectX - tend to crash without error message when the virtual memory is running low.

If the nexus size is exceeded, the engine will allocate additional memory from the PC's virtual memory pool. If the virtual memory is also used up, the application will issue an error message and terminate. The level_mark and level_free functions only work when the nexus is not exceeded. In engines older than A7, exceeding the nexus size will produce a "Nexus too small" error message. The engine must then be restarted with a nexus size higher than that you've used before (e.g. -nx 80 for 80 MB nexus size).


So, maybe you can adjust somehow your system settings to achieve a bigger usage. Or not.

I know the text thanks. Anyway iam confused.

If u enter more than 500 in wed it will jump back to 500.
If i use -nx above 500 engine crash at start. I dont see why only acknex tells me iam out of memory.

I dont want possible gamers to configure windows for game start. Today 500mb is really not that much.

Guess i have to load areas like postal2. Reduced what i could to stay below 480 but still map feels "empty"...

Have you tried to increase the virtual memory size in your OS?
Here is little help how to do that: How to set virtual memory size in windows
Anyway what is your setting now?

Its Windows 10 64b (std settings) and set to 4,8gb.

Taskmanager says my acknex.exe takes 1.4gb. As i said before this cant be the solution and i dont see a reason for this.
In the debug panel it says mem 770 btw (fre 3700).

Maybe iam wrong, but it seams 500mb is a map limit, no matter of virtual memory ? Why is WED limiting the input to 500 if not ?
I already read from other users that theres some limitation, like above 1.5gb it runs out of memory. But i dont know if this is true or not.

If really 500 is a limit...well its pretty funny then
edit: For now i found a way to replace the mem-eating terrain tex, i am down to 400 and it even looks a lot better than before and runs a lot faster. Nice. Now my content fits in and i can go on building my map.
But still my question about that limit exists.

I think WED has indeed a 500 MB limit, probably motivated by the thought that no sane game developer would ever come close. That was back in 2001. But you can override that limit, you need not set the nexus in WED.

Still, when your game uses more total memory than Windows can provide per process, the first thing to crash is DirectX. That happens right at start when the nexus is too big.

Well then iam not sane indeed. 500mb seams not that much for me, but maybe its because iam thinking with 2021 standards who knows.
If i would be sane, i had left 3dgs like all the other users did. Lucky my motivation isnt making money with games...and still loving acknex

Iam now down to 350. I did not plan to make a new dying light, but i reached the 500mb really quick.
I removed two mem-eating things, i knew from beginning they were not good, now with 350 iam pretty sure thats more than enough for my planed stuff.

I dont wanted to bash the engine btw...Anyway, 500 is a limit, iam not sane, my content fits in, nexus is 350 yet (enough for my stuff)...the rest i dont care right now.

edit: ent_purge does not free nexus memory (what makes sense somehow) if iam right. So you always have to provide n-amount of mem for all weapons etc.
Iam glad i have now enough "air to breath" with the nexus usage.


Thanks.

Wish i had seen this before...
https://ntcore.com/?page_id=371

Found this patch in the "Hecknex world" thread, that allows x86 apps to use the 4gb provided by os. If 2gb is my limit, not 4gb then i know why i was confused.
https://opserver.de/ubb7/ubbthreads.php?ubb=showgallery&Number=484548#Post484548

I just patched WED, acknex and MED. All programs now seams to work nice. And besides, now i can use -nx 900 before a error appears. Not that i ever need this much, but its nice to have

Also MED can now handle some files he could not before. I was able to create them with med, but if i wanted to open again, med was "out of memory". All those problems (at least it looks like it for the first test, will see at we...finally with enough time to invest) are gone now.
edit2: Dont patch WED. Opening map compiler will crash the app.

edit:
For me its still one of the greatest software ever made...since a3