I am having problems relating to E1005. And I do not believe it to be due to a damaged file, and am wondering what limits there are for memory? I plan to convert to .dds, but in the meantime would like to have the largest levels run smooth in uncompressed formats.


At the time of error, which occurs upon loading a level - My nexus is showing around 350MB, with the system memory around 900MB. But this doesn't seem to add up, as the entity memory consumed is showing 214MB and Bmaps, 61MB, everything else is near 0, and it says I still have over 700MB available. My virtual memory is set over 4GB and the nexus is set at 200MB.

If E1005 appears after the engine loads the damaged file, then this cannot be the problem, because everything loads fine if I stay under a limit. The only time this happens is when my nexus is approaching near 400MB, and my sys_memory is showing over 900MB. If I load the same levels with a few less models, to keep it under the limit, then it works fine. I can get all my reasources to load fine if I stay under a limit. I've also run into a E2000 saying I ran out of D3D memory from time to time, although only when it shows the nexus close to 400MB and I escape the E1005.

Does the nexus amount to the MB on my 3dcard? And what uses ram and virtual memory? Am I going over my computers limit? My computer has 4GB of ram, a 512MB card, and 4GB virtual memory. The manual seems a little fuzzy on this, and I need to plan accordingly to develop a solid product.

If it's not a damaged file, E1005 means that you're going over your computer limits. The nexus setting is for speeding up the level loading only. When 350 MB nexus is consumed, you should also set up the nexus to 350 MB.

sys_memory indicates the amount of virtual memory consumed by your game. Textures, entities and levels all consume virtual memory. When they are active, i.e. visible or accessed by script, they also consume physical memory.

The memory of your PC is running out when either virtual or physical memory is completely consumed and can not be allocated anymore. If you see E1005, your PC is in an unstable state because no memory is left. E1005 is often followed by a PC crash because some other program, or DirectX itself crashes when it gets no memory.

If your PC is equipped with 2 GB physical memory, you have maybe less than 800 MB left for your game. When all your 900 MB game content consumes physical memory at the same time and can't be swapped to hard disk, you'll get E1005.

Conclusion: Your game probably consumes too much memory for a normal PC today. Try reducing texture and entity sizes. Use DDS. The F11 panel should tell you what the main memory consumption is caused from.

Thanks for the quick response JCL. This makes sense, and I had a feeling I was pushing the limits due to lightmap model duplicates, although I have a few more questions.

Why doesn't the memory consumed by entities, sounds, bmaps, ect. in the statics panel add up to what it is showing for the nexus and sys_memory variables? When added up it is less than half of the sys_memory.

Why does it show over 700MB of memory as still being available in the stats panel when the error occurs?

Is there a statistic showing the amount of physical memory(RAM) the game is using, if not, could there be one?

What is the graphics card memory(512MB) used for?

The texture memory indicated in the F11 panel is video memory. That's on your 3D card and is totally unrelated to the virtual and physical memory of your PC. DirectX uses memory management, so there is also virtual and physical video memory. Yes, I know that's confusing...