Too many lights?

[Dystopia]

I tried adding lights to my map via glowing textures, but it takes like 30 mins to compile 4 jumps. I don't think im leaking anything and im not enclosing my entire map in a skybox either. The only suspicious line I can find in the compile log is "too many lights 8193/8192".

Spoiler (click to show/hide)

Compile log if it helps

Valve Software - vbsp.exe (Nov 10 2016)
4 threads
materialPath: C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\tf\materials
Loading C:\Users\Dys\Documents\jump_viceisbad.vmf
ConVarRef mat_reduceparticles doesn't point to an existing ConVar
fixing up env_cubemap materials on brush sides...
ProcessBlock_Thread: 0...1...2...3...4...5...6...7...8...9...10 (0)
ProcessBlock_Thread: 0...1...2...3...4...5...6...7...8...9...10 (0)
Processing areas...done (0)
Building Faces...done (0)
Chop Details...done (0)
Find Visible Detail Sides...done (0)
Merging details...done (0)
FixTjuncs...
PruneNodes...
WriteBSP...
done (0)
writing C:\Users\Dys\Documents\jump_viceisbad.prt...Building visibility clusters...
done (0)
Creating default LDR cubemaps for env_cubemap using skybox materials:
   skybox/sky_day01_01*.vmt
 ! Run buildcubemaps in the engine to get the correct cube maps.
Creating default HDR cubemaps for env_cubemap using skybox materials:
   skybox/sky_day01_01*.vmt
 ! Run buildcubemaps in the engine to get the correct cube maps.
Finding displacement neighbors...
Finding lightmap sample positions...
Displacement Alpha : 0...1...2...3...4...5...6...7...8...9...10
Building Physics collision data...
done (1) (92856 bytes)
Placing detail props : 0...1...2...3...4...5...6...7...8...9...10
Water found with no water_lod_control entity, creating a default one.
Compacting texture/material tables...
Reduced 124 texinfos to 98
Reduced 20 texdatas to 15 (556 bytes to 344)
Writing C:\Users\Dys\Documents\jump_viceisbad.bsp
Wrote ZIP buffer, estimated size 213607, actual size 212589
1 second elapsed

** Executing...
** Command: "C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\bin\vvis.exe"
** Parameters: -game "C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\tf" "C:\Users\Dys\Documents\jump_viceisbad"

Valve Software - vvis.exe (Nov  2 2016)
4 threads
reading c:\users\dys\documents\jump_viceisbad.bsp
reading c:\users\dys\documents\jump_viceisbad.prt
 333 portalclusters
 697 numportals
BasePortalVis:       0...1...2...3...4...5...6...7...8...9...10 (0)
PortalFlow:          0...1...2...3...4...5...6...7...8...9...10 (0)
Optimized: 75 visible clusters (0.24%)
Total clusters visible: 31822
Average clusters visible: 95
Building PAS...
Average clusters audible: 189
visdatasize:19986  compressed from 31968
writing c:\users\dys\documents\jump_viceisbad.bsp
0 seconds elapsed

** Executing...
** Command: "C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\bin\vrad.exe"
** Parameters: -both -game "C:\Program Files (x86)\Steam\steamapps\common\Team Fortress 2\tf" "C:\Users\Dys\Documents\jump_viceisbad"

Valve Software - vrad.exe SSE (Nov  2 2016)

      Valve Radiosity Simulator     
4 threads
[Reading texlights from 'lights.rad']
unknown light specifier type - lights

[56 texlights parsed from 'lights.rad']

Loading c:\users\dys\documents\jump_viceisbad.bsp
Setting up ray-trace acceleration structure... Done (0.07 seconds)
5019 faces
5850424 square feet [842461056.00 square inches]
0 Displacements
0 Square Feet [0.00 Square Inches]
5019 patches before subdivision
405601 patches after subdivision
12335 direct lights
BuildFacelights:     0...1...2...3...4...5...6...7...8...9...10 (1065)
too many lights 8193 / 8192

I tried googling but the only post about this involves actual light entities which I don't have. Anybody knows whats going in?

[?oss]

considering its vrad's thing u could try to increase lightmaps scale on the whole map

[plep]

considering its vrad's thing u could try to increase lightmaps scale on the whole map

^

This is the MOST COMMON light issue you'll encounter.

Having a lightmap scale of 64 by default (32 if the map isn't too big) is decent enough for me. You can always make this number lower on specific faces to have smoother light.

[Dystopia]

Changing lightmap scale fixed it for me though I could've sworn I tried changing it before... Weird though cuz my map is currently still really really small...

[plep]

Changing lightmap scale fixed it for me though I could've sworn I tried changing it before... Weird though cuz my map is currently still really really small...

I could take a look in your vmf if you want

[879m]

Maps have a maximum amount of lighting information they can store. Your map was juuuust over this. The lightmap scale on the glowing textures or the entire map must have been really low to go over the light limit in 4 jumps.

[John]

glowing textures are known to be really expensive so if you can avoid using them i'd suggest you do. if not then definitely increase the lightmap scale to like 64 or 128.

[Dystopia]

Thanks guys, for now since its fine I won't change anything yet. If I get more problems in future I'll either raise the lightmap scale again or change to other types of lighting

[pants]

You can also just change the lightmap scale of JUST the texturelights, keep in mind with a low scale a small strip of texture can be dozens of light sources. You can see this by changing your 3D view to the 3D lightmap grid, where basically every square here represents a light. Which is why getting a uniform glow strip effect can be quite costly compared to a few light entities just illuminating the area.

A smart way to adjust them easily is to assign them all to a custom visgroup, rather than fumbling around the map to change them manually.

I guess another broad tip is that you can have different lightmap scales depending on how far away/how detailed you need something. So a distant textlight could have a higher scale compared to something that will be level with a players sight.