I was doing nothing special to my map, just adding some sounds and sides work when all of a sudden my map started crashing. I looked at my map in addon and tat2.lvl was 1.09 GB! Before this happened it used to be around 95MB The world1 folder in my mod tools is only 175 MB. I have no idea how this happened, does anyone have any idea? I've tried manual cleaning many times and I even copied all my files to a new data_abc but it still was the same file size. It takes about 5 minutes to munge now and it stops at tat2.req for a long time.

Error log:

[/quote]

What are those?
Also, what was the last change you made before the problem started?

I would try "rebuilding" the map from (not-so-much-) "scratch". Basically, make a new map and start adding things from your huge map into your new map's world1 folder, munging after each small set of assets you put back in. Watch your LVLs' file sizes as you do this. When and if you notice a spike in file size, start taking out the assets that you put back in one by one, doing a manual clean of only the assets that you remove, and remunging the map after each asset you remove. Once you've narrowed it down to an asset, that must be the one that is causing the spike.

This might not work, as it could be something else, but who knows?

Cerfon Rournes wrote:

Hidden/Spoiler:

[quote="fasty"]
Message Severity: 3
C:\Battlefront2\main\Battlefront2\Source\BoundaryManager.cpp(172)
Boundary path must be convex and counter-clockwise

Message Severity: 3
C:\Battlefront2\main\Battlefront2\Source\BoundaryManager.cpp(172)
Boundary path must be convex and counter-clockwise

Message Severity: 3
C:\Battlefront2\main\Battlefront2\Source\BoundaryManager.cpp(172)
Boundary path must be convex and counter-clockwise

Message Severity: 3
C:\Battlefront2\main\RedEngineFL\Memory\RedMemory.cpp(538)
Allocating 539018536 bytes failed - no free blocks left in Heap 6 (Temp)

What are those?
Also, what was the last change you made before the problem started?[/quote]

The first three have something to do with the boundary that I moved around. I'm pretty sure they have nothing to do with this. The last one is definitely a new error that I've never seen before.
The very last thing I did was I added this line to my lua: I was working on getting a sound ingame.

Marth8880 wrote:I would try "rebuilding" the map from (not-so-much-) "scratch". Basically, make a new map and start adding things from your huge map into your new map's world1 folder, munging after each small set of assets you put back in. Watch your LVLs' file sizes as you do this. When and if you notice a spike in file size, start taking out the assets that you put back in one by one, doing a manual clean of only the assets that you remove, and remunging the map after each asset you remove. Once you've narrowed it down to an asset, that must be the one that is causing the spike.

This might not work, as it could be something else, but who knows?

That will take a very long time. I don't think it was a specific asset since everything is stock, or from Rends Sides assets. I'll slowly start working on that but I have a feeling I'll just end up remaking the whole map after a month.

The last line in your error log is basically saying that it's loaded too much custom content.

Fix that boundary. Being convex matters for linear optimization problems. It's possible (but I don't know how likely or by how much) that this could increase your file size. Use the extract tool to break apart your lvl file. That'll give you the file sizes for everything inside it. Also/Or, look in your munged folders for large files.

If you put your map under version control (SVN, Bazaar, Git, etc...), you'd be able to go back to the state it was in at any eariler time, thus undoing any mistakes. (I use Bazaar for all my projects)

That's what I should have done in the first place. I went through the munged folder and there's a file called tat2_con.lvl and its 1.02 GB. What does this mean?

fasty wrote:I went through the munged folder and there's a file called tat2_con.lvl and its 1.02 GB. What does this mean?

I don't know how it got that large, but like Zerted said, fix that boundary error.


By the way, the tat2_con.lvl is the level for the Conquest game mode. Something has gone askew and caused it to become abnormally large. I've never encountered a problem like this, so I don't know any causes.

fasty wrote:tat2_con.lvl and its 1.02 GB. What does this mean?

It means one or more of the things listed in tat2_con.lvl.req (a temp munge file or tat2_con.req if that file exists) is the source of the problem. Use the extract tool to 'look inside' tat2_con.lvl and see which section is the big one.