I thought this was interesting. Could it be the problem I have seen in a lot of custom maps?
Check your init.con - make sure it does not have this line:
textureManager.alternativePath Texture
I believe this will cause the game to load the BFV texture directory twice, causing BFV to use excessive ammounts of memory.
Note:
textureManager.alternativePath Texture/mud
and
textureManager.alternativePath Texture/dust
should be ok - just not 'texture' by itself..
Check your init.con - make sure it does not have this line:
textureManager.alternativePath Texture
I believe this will cause the game to load the BFV texture directory twice, causing BFV to use excessive ammounts of memory.
Note:
textureManager.alternativePath Texture/mud
and
textureManager.alternativePath Texture/dust
should be ok - just not 'texture' by itself..