Aller au contenu

Photo

Builder to Player out of memory error


8 réponses à ce sujet

#1
georage

georage
  • Members
  • 247 messages
I have XP and a mere 2 gb of RAM, so yes, I know I should add memory.

I plan to move to Windows 7 and get 2gb more of RAM, but, I was wondering if anyone with 4gb of useable memory is STILL getting out of memory errors when creating a builder to player export.

I am only exporting my custom areas, not core stuff, and the file is 30mb when completed, so it seems odd it runs out of memory.

The only way I can create the build is to close the toolset and reopen it, and then, without opening any areas or levels, export it.


 

#2
RanShak

RanShak
  • Members
  • 6 messages
Yes, the toolset is a Win32 app, so it can't handle a full 4 gigs of memory. There is a workaround here: http://social.biowar...1689/blog/707/. Still, you'd need a 64bit OS to benefit from it.

#3
georage

georage
  • Members
  • 247 messages
OK, but surely if a mod with 2 areas takes about 2gb of memory to export, no machine will be able to export even the smallest of modules!



Something has to change with memory management for real campaigns to be built.



Is anyone else working on a campaign module and successfully exported a reasonably-sized mod? I figure our mod will have 16 or so areas ... I better start saving up for that 16gb of RAM!




#4
AND04

AND04
  • Members
  • 154 messages

georage wrote...

OK, but surely if a mod with 2 areas takes about 2gb of memory to export, no machine will be able to export even the smallest of modules!

Something has to change with memory management for real campaigns to be built.

Is anyone else working on a campaign module and successfully exported a reasonably-sized mod? I figure our mod will have 16 or so areas ... I better start saving up for that 16gb of RAM!


hmm, i succesfully created a adzip-Module for the HD-Textures Mod (1 GB+ Filesize) as i wanted to be able to turn ehm on/off ingame and not by moving/deleting files manually - i used the workaround for the app addressing more than 2gb though - using win 7 x64 and 16GB ram atm

#5
RanShak

RanShak
  • Members
  • 6 messages
I've got 3 gigs of RAM myself and cannot open a 10 meg save file to apply my custom face morph. Toolset wants buggering 3.5 gigs just for that.

#6
georage

georage
  • Members
  • 247 messages
AND04 -- So you think the max RAM used by the toolset is 3.2 gigs (as mentioned in other threads)?



I am curious at what sort of memory usage readings you get when doing an export with 16 gigs of accessible RAM.




#7
BryanDerksen

BryanDerksen
  • BioWare Employees
  • 273 messages
The GFF editor and ERF editor are particularly inefficient in terms of memory usage, and unfortunately it looks like it'll require a rewrite to really clean them up properly.



We'd _like_ to do that, mind you. It'd be helpful for internal use as well. But it might not happen very quickly.

#8
Axe_Murderer

Axe_Murderer
  • Members
  • 279 messages
Still, even a couple/few little tweaks would help some of us alot if possible.

Modifié par Axe_Murderer, 26 novembre 2009 - 12:37 .


#9
mellic

mellic
  • Members
  • 14 messages
8Mb --> >3Gb, that's a factor of (lets see... ) about 450 or so. That's pretty bad memory complexity - what is it, like 2.8 ^ x ? Any chance we can get some kind of fix?