Rad issues? Created 15 years ago2009-02-24 02:02:46 UTC by Fonzie Fonzie

Created 15 years ago2009-02-24 02:02:46 UTC by Fonzie Fonzie

Posted 15 years ago2009-02-24 02:02:46 UTC Post #263186
First I would like to state that I have been compiling out of hammer and not zoners tools.
My issue is im seeing a rediculous % of lightdata when I compile and I am wondering what is causing the lightdata to increase so drastically every time I create a new room.

vis.exe v1.3 (Dec 30 1998)
-- vis --
2 thread(s)
346 portalleafs
980 numportals
BasePortalVis: 0...1...2...3...4...5...6...7...8...9... (0)
LeafThread: 0...1...2...3...4...5...6...7...8...9... (2)
average leafs visible: 58
visdatasize:6571 compressed from 15224
3.0 seconds elapsed

qrad.exe v 1.5 (Apr 6 2000)
--- Radiosity --
2 threads
[Reading texlights from 'C:\PROGRA~1\VALVEH~1\tools\lights.rad']
[1 texlights parsed from 'C:\PROGRA~1\VALVEH~1\tools\lights.rad']

3765 faces
532318 square feet [76653792.00 square inches]
34602 patches after subdivision
13 direct lights
BuildFacelights: 0...1...2...3...4...5...6...7...8...9... (3)
visibility matrix: 71.4 megs
BuildVisLeafs: 0...1...2...3...4...5...6...7...8...9... (55)
MakeScales: 0...1...2...3...4...5...6...7...8...9... (46)
transfer lists: 204.5 megs
SwapTransfersTask: 0...1...2...3...4...5...6...7...8...9... (10)
GatherLight: 0...1...2...3...4...5...6...7...8...9... (0)
Bounce #1 added RGB(112202, 112202, 56321)
FinalLightFace: 0...1...2...3...4...5...6...7...8...9... (4)

Object names Objects/Maxobjs Memory / Maxmem Fullness
---------- ------------- ------------- ------
models 102/400 6528/25600 (25.5%)
planes 4072/32767 81440/655340 (12.4%)
vertexes 4789/65535 57468/786420 ( 7.3%)
nodes 1367/32767 32808/786408 ( 4.2%)
texinfos 339/8192 13560/327680 ( 4.1%)
faces 3765/65535 75300/1310700 ( 5.7%)
clipnodes 3765/32767 30120/262136 (11.5%)
leaves 992/8192 27776/229376 (12.1%)
marksurfaces 4196/65535 8392/131070 ( 6.4%)
surfedges 16881/512000 67524/2048000 ( 3.3%)
edges 8462/256000 33848/1024000 ( 3.3%)
texdata [variable] 3788/2097152 ( 0.2%)
lightdata [variable] 1325562/2097152 (63.2%)
visdata [variable] 6571/2097152 ( 0.3%)
entdata [variable] 22326/131072 (17.0%)

Total BSP file data space used: 1793011 bytes

118 seconds elapsed

What is causing this to happen & what will the reprocussions be if nothing is done about it?

TY for your time&Help

-Fonzie
Posted 15 years ago2009-02-24 06:26:52 UTC Post #263188
get Zoner's. It is idiotic to use the old qtools... The Hammer download should have them removed/replaced with the latest ZHLT imo... seriously.

ZHLT 3.4 FINAL (32-bit)
ZHLT 3.4 FINAL (64-bit)
Captain Terror Captain Terrorwhen a man loves a woman
Posted 15 years ago2009-02-24 06:31:02 UTC Post #263189
Yeah, I'd definitely recommend you switch to ZHLT...

That aside, though, it does seem to be an awful lot of lightdata for a 2 minute RAD compile. Either your rooms are really large, or you have a leak (you DID compile with CSG/BSP before VIS and RAD?) or you have a few switchable lights. (Offhand I believe a switchable light effectively doubles the lightdata for the illuminated area, since it has to generate both on and off lighting.) Or, uh, all three...
Posted 15 years ago2009-02-24 06:56:47 UTC Post #263191
Well the map in question is a conc map for TFC so yes some of the rooms are very large. I know its not a leak issue since there is no fullbright nor does the compile log have the leak leak leak error. I did compile csg/bsp before vis and rad aswell. No switchable lights. I just set up zhlt and am currently compiling the map for the first time over it. So far it seems alot smoother however I cannot find the lightdata being used on the compile log for zhlt : /
You must be logged in to post a response.