I get this odd compile error every time i compile. the error is different every time, even though between compiles the only thing i have changed is a texture here and there.

(rad part of compile)

Win32 Specific Data:
physics [variable] 2000816/4194304 (47.7%)
==== Total Win32 BSP file data space used: 3300764 bytes ====

Linux Specific Data:
physicssurface [variable] 6545771/6291456 (104.0%) VERY FULL!
==== Total Linux BSP file data space used: 7845719 bytes ====

Win32 Specific Data:
physics [variable] 4219938/4194304 (100.6%) VERY FULL!
==== Total Win32 BSP file data space used: 8347819 bytes ====

Linux Specific Data:
physicssurface [variable] 13424188/6291456 (213.4%) VERY FULL!
==== Total Linux BSP file data space used: 17552069 bytes ====


Win32 Specific Data:
physics [variable] 2648677/4194304 (63.1%)
==== Total Win32 BSP file data space used: 4791024 bytes ====

Linux Specific Data:
physicssurface [variable] 8594483/6291456 (136.6%) VERY FULL!
==== Total Linux BSP file data space used: 10736830 bytes ====


As you can see the percentages are very different for each compile, even though hardly anything has been altered in the map. Any ideas what could be causing this?

thanks

This usually means that you badly used displacements, such as excessively using Power of 4 displacements or applying high power displacements to all the faces of a polygon.

Try reducing the power of some displacements, delete non-visible displacements... It's a matter of optimization. Also, "Very Full" still appears when you reach 80% or more, but then it doesn't matter. Anything under 100% is fine, but you have 136%

Originally posted by Dash
This usually means that you badly used displacements, such as excessively using Power of 4 displacements or applying high power displacements to all the faces of a polygon.

Try reducing the power of some displacements, delete non-visible displacements... It's a matter of optimization. Also, "Very Full" still appears when you reach 80% or more, but then it doesn't matter. Anything under 100% is fine, but you have 136%

Should this be below 100% for both windows and linux? (I presume this is related to what type of server is running the map)

Short answer: Yes. It's a bad idea to overflow the stocking capabilities of your map.