visdatasize higher in 2.3.36

(pazur) #1

i have a _blocksize of 768… therefore my visdatasize is quite high. slowly im reaching the limit. i know that more detail should lower the visdatasize but i went already trough my map and “cleaned” up unnecessary structure.

now this:
2.3.32 visdatasize:1659848
2.3.36 visdatasize:1768120
(vis -fast)

i would like to use the latest q3map2 but i cant when i reach vis limit with 2.3.36 and get MAX_VISIBILITY_EXCEEDED :eek: i had this error already with 2.3.32 but reducing skybox size did it for the moment. plz clarify about this higer visdatasize

(r3tina) #2

Maybe I’m being a bit blunt, but a VIS data size of > 1,5 MB is a bit much, no matter what map. Are you sure you can’t make more brushes detail? Have you used the caulk hull method? (building a simple caulk hull around your rooms, thus greatly reducing VIS size)

(pazur) #3

caulk hull is a good idea for some parts of the map :slight_smile: but i will only use this method when i have no more choice reducing vis data… another trick would be to removing(or making detail) structural caulk that “seals” some hudge fog brushes in my map(its kind of hellfog where the player falls in)… then i probably get a waring during compile but it will still work

(Old_Fellow) #4

Why don’t you increase _blocksize to decrease your vis data size?

(pazur) #5

because i have fogclip(foghull) with _farplanedist 2560. 768 results in the best r_speed

(ydnar) #6

Q3Map2 supports _blocksize in vector form:

“_blocksize” “1024 1024 768”

Will split on 1024 units in XY, and 768 units in Z. They can be seperately controlled to suit the map.

y

(pazur) #7

ahh right… i had this already: blocksize 768 768 2048. i will optimize my map a bit more(with all the methods mentioned). i think i will stay under the limit also with higher visdata of 2.3.36. thx for the help guys