Aardvark is really rather unoptimized (extremely poor usage of func_details)

[ddm999]

Aardvark has some really horrific usage of func_details, which leads to extremely long compile times (probably more than 10x longer than it should take) and inflates the file size (fully optimized, it should be more than 6Mb smaller than it is now - 31Mb to less than 25Mb).
(No offence intended towards who made the map, just to clarify.)

This makes modifying the actual map file for things that should be quick fixes actually take a vast amount of time due to compile time (essentially requiring that you leave it running overnight), and also means anyone slightly changing the maps for use on their server will probably think Hammer's just crashed when compiling given how long it takes.

In fact, some of the stuff that is func_detailed is actually making the performance WORSE by creating even more visleaves.
This image is taken with func_detail hidden:

These small latches generate 2 extra visleaves each for absolutely no reason.

But then the cylindrical columns that should be func_details and the curved walls are not.
This leads to the visleaf count being at least 10x as many as should be needed.

Unfortunately, the issue is so large and across the entire map that it may be quicker to instead rebuild the entire thing based on the old map but using a box room structure.

I'll see what I can do, but it may take a long time.
( Luckily it's half term next week for me, so I'll have time to waste. 👍 )