20 Mb .ass tool limit, and potential fix.

**[EJ] Bean** · November 8th, 2007 06:24 PM

I've been working on a map the past few weeks, encountering different problems. It has been a learning experience. Anyway, in case this has not been said before:

I encountered an error when compiling my map -- tool said that my .ass file had exceeded the 20 megabyte limit. To fix the problem, I compared and contrasted different versions of the map to find the source of the problem. It turned out it was an object I made that wasn't even linked to the frame. I then found that by deleting every single object not linked to the frame, my map's .ass size went from 23 megabytes to 13 megabytes. I had always thought these non-linked objects were ignored, but i guess not. Hope this helps people who've had the same problem.

**Ki11a_FTW** · November 8th, 2007 09:40 PM

wow, i thought the other objecs werent involved with the file at all

**[EJ] Bean** · November 8th, 2007 09:53 PM

My theory is that all the geometry is included in the .ass and tool ignores it it, but if if it's too big for tool to use, it can't ignore it in the first place.

**Zeph** · November 9th, 2007 10:10 AM

Console developing at its finest. Possibly Live forcing you to play by their rules as well?

**[EJ] Bean** · November 9th, 2007 03:14 PM

What do you mean?

**johnnyblaz20** · November 9th, 2007 03:50 PM

I wonder if you uncheck the "export hidden geometery" when exporting the .ass file if it would still show up.. Probably would but I thought it would have been ignored also. Oh well, thanks.