I have encountered yet another compiling problem (hlcsg) Created 4 months ago2020-02-04 00:01:20 UTC by SirCobalt SirCobalt

Created 4 months ago2020-02-04 00:01:20 UTC by SirCobalt SirCobalt

Posted 4 months ago2020-02-04 00:01:20 UTC Post #343723
In all likelihood I may discover the answer to my predicament shortly after posting this thread which will inevitably be followed by me getting extremely humiliated again. But I am literally stumped right now.

For some strange reason, my hlcsg is messing up (or more likely I've messed up) and is refusing to compile my map because apparently there's a remote brush in a restricted area of my map. I have checked thoroughly and there isn't a single entity out of bounds as far as I'm concerned.

Here's what the console says:

Current hlcsg Settings
Name | Setting | Default
---------------------|-----------|-------------------------
threads [ 8 ] [ Varies ]
verbose [ off ] [ off ]
log [ on ] [ on ]
reset logfile [ on ] [ on ]
developer [ 0 ] [ 0 ]
chart [ off ] [ off ]
estimate [ off ] [ off ]
max texture memory [ 33554432 ] [ 33554432 ]
max lighting memory [ 50331648 ] [ 50331648 ]
priority [ Low ] [ Normal ]

noclip [ off ] [ off ]
null texture stripping[ on ] [ on ]
clipnode economy mode [ off ] [ off ]
clip hull type [ simple ] [ simple ]
onlyents [ off ] [ off ]
wadtextures [ on ] [ on ]
skyclip [ on ] [ on ]
hullfile [ None ] [ None ]
wad configuration file[ None ] [ None ]
wad.cfg group name [ None ] [ None ]
nullfile [ None ] [ None ]
nullify trigger [ on ] [ on ]
min surface area [ 0.000 ] [ 0.000 ]
brush union threshold [ 0.000 ] [ 0.000 ]
map scaling [ None ] [ None ]
light name optimize [ on ] [ on ]
convert game_text [ on ] [ on ]

Using mapfile wad configuration
Wadfiles not in use by the map will be excluded
Wadinclude list :
[zhlt.wad]

CreateBrush:
Error: Entity 0, Brush 34: outside world(+/-32767): (41,20,-80000)-(64,47,36)
Error: brush outside world
Description: The map has a problem which must be fixed
Howto Fix: Check the file http://www.zhlt.info/common-mapping-problems.html for a detailed explanation of this problem

Warning: Illegal Brush (edge without opposite face): Entity 0, Brush 34

Error: Entity 0, Brush 34: outside world(+/-32767): (25,4,-80036)-(80,63,72)
Error: Entity 0, Brush 34: outside world(+/-32767): (9,-12,-80032)-(96,79,68)
Error: Entity 0, Brush 34: outside world(+/-32767): (25,4,-80018)-(80,63,54)
(0.11 seconds)

----- END hlcsg -----
Having followed the link provided, unfortunately they do not provide a "detailed" explanation as much as I would prefer. I haven't a clue how to find areas of a map using coordinates, and fixing any broken brushes caused by vertex manipulation hasn't fixed the problem.

It's very awkward, but I require further assistance in my mapping endeavours and such assistance will be greatly appreciated.
Thanks in advance.
Posted 4 months ago2020-02-04 02:51:53 UTC Post #343724
It's been a while since I've dusted off my Goldsource hat, but I seem to recall HLCSG sometimes throws the "outside world" error for invalid (usually concave) solids rather than things too far off the grid. Hammer 3.x might not have this (I don't recall when it was added) but see if you can use View>Go to Brush Number to find Brush 34 and check it, or otherwise use Map>Check for Problems to see if Hammer has detected an invalid solid.
JeffMOD JeffMODCall 141.12
Posted 4 months ago2020-02-04 16:22:41 UTC Post #343725
It worked. For some reason some random brush was causing issues so I deleted it and replaced it. All is good, for now.
Posted 4 months ago2020-02-05 01:34:27 UTC Post #343726
Just an example here
Error: Entity 4, Brush 0, Side 7: has a coplanar plane at (111, 222, 333), texture AAATRIGGER
Hint: The first number is X, second is Y, and third is Z (height). If you don't know how to locate it yourself in the map, when the console points a coordinate (not the "outside world" type as shown in your log, though), you can use these coordinate numbers to create a test point-entity as the "origin" value in your .map file. Then opening your map on the editor, you search for the test entity and you'll find the place of the supposed issue.
Just letting you know. ;)
MrMystery MrMysteryBanned
You must be logged in to post a response.