[CS:GO]de_zoo

2 hours for compiles? seems high

Quote from cashed

2 hours for compiles? seems high

dust2 took me 13 hours :> (yes, decompiled, but the cp_d2 with the sdk takes ~12)

hay geniuses, wouldn't you also have to mention like what your compiling that on? a toaster for example..

Looks great squad! and I agree with fmpone that a blue ambient or spotlight would be a good idea around those fishtanks.
Also do you have an idea when the next playtest will be?

Quote from Squad

Most of it is vrad.

What does your average (full compile) map compile take?

Season takes 35 minutes on final (core i7 920)

Reducing dead space, hidden brush zones, and lightmaps will improve compile times

Wow, optimisation at it's finest!

Maybe Squad should watch THW's optimisation video ;D

Yeah i think most people don't think about optimizing the lightmaps as Cashed say.

If you have a huge 3Dskybox, don't hesitate to use a 128 or 256 lightmap because you'll not get beautiful shadows anyway.

Has anyone got any stats for how lightmaps affect compile times?

Quote from jackophant

Has anyone got any stats for how lightmaps affect compile times?

The time is proportionnal to the total number of lightmap pixels (luxels). Which is, the surface of your lightmapped surfaces divided by the lightmap size squared.

If you divide the lightmap size by 2 (16 to 8 ), it takes rougly 4 times the compile time.

In theory you should also multiply by the number of bounces, in practice the light decrease with each bounce so the factor may be more around 2/3/4.

You can also divide by the number of cores (1 core per luxel ideally).

This is a (very) rough estimation, I'm not counting the overhead, vertex lighting, bsp complexity, lightmap parametrization, textures reflectance, etc.

Needless to say I'm waiting for a GPU based implementation.

waiting for a better system in general. Having worked in multi layered data engines, recompiling a map to fix spawn points is awful.

If its just for your own internal testing purposes you can use the entity only compile.

Entity only compile takes less than a second and updates all point entities in the map. Updating/changing any brush entities or anything requiring vvis or vrad will break the compile though.

EDIT: This is after youve already done a normal compile on the map and that BSP file exists in the specified map directory youre compiling into.

EDIT EDIT: I forgot the entity only compile rules about triggers n shit but the point is if all youre doing is updating a spawn location then entity only compiles are a massive headache reducer.

i haven't tested myself but I should have. So what your saying is if I have a final compiled level and I only entity compile it updates without breaking the rad and vis?

Yup exactly.

The console will say something in red letters along the lines of "ent only compile, not final!" which is why I say its mostly for testing and time saving purposes. If you were to release a final version of the map I would make it a full regular compile.

Im not sure why this is exactly but everything should be perfect on your final compile anyways

Quote from hamilton5

hay geniuses, wouldn't you also have to mention like what your compiling that on? a toaster for example..

Given that this is a Valve game a very modern toaster is not out of question.

Map looking damn nifty (mm dat soft lighting)

Looking great! loving the detail changes

I'm up for a comp playtest if you have another one

clip it, clip it real good.