MAX_MAP_MIPMAP Created 20 years ago2004-02-18 13:16:45 UTC by @LLmIxEdUp

I just bumped into this error on a compile and I have a couple of questions.

It seems I can get round this by using the "-texdata" switch on the compile command-line to bump it up to over 8192 Kb, but do I really want to do this?

Should I look at optimising the textures themselves in some way? I presume the memory used is determined by the size of the textures as well as the number. Is there anything else I should be looking for?

Is this memory allocation only relevant to the compilation process? Or does this impact the run-time?

BTW, it's a CS map - if that's relevant.

Any help much appreciated.

Check this out:
http://www.slackiller.com/tommy14/errors.htm#maxlim
Tommy is a good boy.

You can remove textures that can't be seen by painting them with the null and skip texture. Then they won't be rendered or stored, decreasing the amount of tex memory needed.

Thanks for the info. I'm compiling with a larger texdata until I can get round to 'optimizing' the textures - if it's worth it. As for NULLs - I already use them wherever possible :).

Thanks for your help