Will this problem be fixed? It only happens when running the engine through SED/WED and not the published version. The reason I need it fixed is that I have some levels that won't even load up once because the engine consumes so much memory(1.7GB+). This means I have to cut back on texture resolution and art assets that could otherwise be much much better.

Thanks.

I thought pegamode already found the problem?

In my case I only get the error if I run my project in debug mode (I don't know why debug mode consumes about 1GB more memory, but I think there will be a simple reason).

William seems to get the same error although he is not running his project in debug mode, but by just starting it from SED / WED.

There are two reasons for that. First, when the engine is started in debug mode, it allocates more memory for code and variables. When you have a huge script and use large arrays, this can use a lot of memory, up to 100 MB or more.

The second reason is that the engine runs as a SED process in debug mode, meaning that you have to terminate SED after a debug session. Otherwise the memory is not freed and accumulates with every debug run. Of course this does not happen when you only start your project, without debugging.

When you start it from WED with the map open at the same time, you need at least twice the memory. Once for the engine and once for the map in WED. For fixing this, just don't have several programs consuming huge memory amounts running at the same time. Better start the engine with SED, or even better, start it directly with a shortcut or from a command line.

I'm just clicking the black run button in SED to play. I don't ever use the debug mode or anything, and just tried WED for testing. From what I gather, the black arrow button should not be causing this?

Correct. The black run button just starts the engine with the name of your script and the command line options you've set up.

When your game consumes a different amount of memory dependent on in which folder you start it, the first thing I'd do is comparing the files in the publish and development folders.

Do you mean my work folder? Should I take out anything not related to the game? Does it read subfolders as well?

As far as I've understood you, your problem was that when you start your game from the work folder, it consumes more memory than when you start it from the CD folder? So check any file differences in the work folder and path, compared to the CD folder. I mean files with the same name, but different content or different size.

Yeah, I found some image files and deleted them. The memory is still huge but at least I can run and test now. I am running the game from the work folder for testing only.

Well this problem reared it's ugly head again... after switching to windows 7 32 bit I cannot get the game to even run through "test mode" in SED. It just loads the game up and takes about 1.6GB in the memory counter of the taskbar. It then crashes instantly with directx errors. Windows 7 uses more memory natively than XP did.

So... I tried re-installing A8 with the latest edition, created an empty work folder, and the copied and pasted the files from my demo folder. In total the whole Gstudio folder is 900 MB.

But that did not matter, the problem is still there! It consumes 1.6GB for a 900MB folder.

The problem does not appear if I publish the game. The game in the published folder uses the exact same resources I put in the work folder and only takes 400MB to load up.

Any ideas on this problem? It looks like it's gotta be an engine issue only relating to the non-published engine.