Re: ***Error*** parsing brush
Posted by Orpheus on
Fri Feb 13th 2004 at 12:56am
Posted
2004-02-13 12:56am
Orpheus
member
13860 posts
2024 snarkmarks
Registered:
Aug 26th 2001
Occupation: Long Haul Trucking
Location: Long Oklahoma - USA
i had an error like this once, it reported a solid having an error, i deleted it, and i'll be damned if it didn't move..
finally i do not know what solve dit but i did do this all..
1) export to map.. close hammer, reload hammer, reload map.. sometimes the offending solid is removed.
2) delete the whole offending object the solid is connected to.. in wildcards map, he had some rockwork doing this, i had to delete whole rocks to solve it. in the end it seemed like hammer could only report the error once, and come to find out, his map had 5 or 10 errors.. thats why IMO it seemed to move.
3) turn the solid to a func_wall.. this may help.
4) reboot your pc.
hope this helps.
Re: ***Error*** parsing brush
Posted by Gollum on
Fri Feb 13th 2004 at 3:26am
Gollum
member
1268 posts
525 snarkmarks
Registered:
Oct 26th 2001
Occupation: Student
Location: Oxford, England
You should mark Orpheus' answer correct, since it did actually solve the problem you posted. In my (considerable) experience it is not possible to introduce new problems by fixing a compile error, no matter how much this may sometimes seem the case. It is likely that these "new" problems were already there.
I'm afraid I can't think of an obvious answer to your new problem :sad: I assume HL loads normally without your map? Maybe you could check your custom resources are in the right places.
Another unlikely possibility is that you've done an -onlyents compile that got broken.
Re: ***Error*** parsing brush
Posted by Xylo the Cheese on
Fri Feb 13th 2004 at 4:28am
13 posts
1 snarkmarks
Registered:
Feb 12th 2004
Occupation: Student
Location: CO, USA
Thanks for the tips, but nothing goes. I've tried a killbox tester map with my custom texture, and it runs fine.
I've also tried removing the custom texture from my map, even taking the wad out of wc and reloading. the only wad left in is halflife.wad. Still didn't go.
I loaded c2a5 fine.
I dunno wtf i did to this map, but thanks for all the help all the same! i'll still look for the HL console log...
(PS yes i'm sorry for marking Orpheus' answer wrong, i was really at ends deciding which way to go. if i could, i would take it back to suggested instead of right/wrong)
Re: ***Error*** parsing brush
Posted by Edge Damodred on
Fri Feb 13th 2004 at 10:17am
Posted
2004-02-13 10:17am
237 posts
54 snarkmarks
Registered:
Apr 24th 2002
Occupation: student
Location: I don't even know anymore
Or you could write your own compiler and have it correct errors when .map format is incorrectly exported :biggrin: ...which was my research project for Console until I decided I didn't want to write the code for radiosity or calculating visibility portals and constructing a whole BSP tree. So I decided just to parse a Q3 map and learn how to use each of its components to get the geometry onto the screen and running at an acceptable rate...
Re: ***Error*** parsing brush
Posted by Leperous on
Fri Feb 13th 2004 at 6:16pm
Leperous
Creator of SnarkPit!
member
3382 posts
1635 snarkmarks
Registered:
Aug 21st 2001
Occupation: Lazy student
Location: UK
There's something dodgy going on in the .MAP, and it's quite easy to recreate the error :smile: Basically open your .MAP into a text editor, and go down to the first lump of bracketed lines and look at the 2nd line inside:
{
( -224 -480 160 ) ( -224 -96 160 ) ( 160 -96 160 ) TEST [ 1 0 0 -5.3333 ] [ 0 -1 0 48 ] 0 1.2 1.2
[color=red]( -224 -96 128 ) ( -224 -96 160 ) ( -224 -480 160 ) TEST [ 0 -1 0 48 ] [ 0 0 -1 64 ] 0 1.2 1.25
[/color]( 160 -480 128 ) ( 160 -480 160 ) ( 160 -96 160 ) TEST [ 0 1 0 -48 ] [ 0 0 -1 64 ] 0 1.2 1.25
( 160 -96 128 ) ( 160 -96 160 ) ( -224 -96 160 ) TEST [ -1 0 0 5.3333 ] [ 0 0 -1 64 ] 0 1.2 1.25
( -224 -480 128 ) ( -224 -480 160 ) ( 160 -480 160 ) TEST [ 1 0 0 -5.3333 ] [ 0 0 -1 64 ] 0 1.2 1.25
( -224 -96 128 ) ( -224 -480 128 ) ( 160 -480 128 ) TEST [ 1 0 0 0 ] [ 0 -1 0 0 ] 0 1 1
}
Somewhere on that second line, there will be a square bracket [ instead of one of the red parentheses ( surrounding a set of co-ordinates- simply change it and you'll be ok again :smile:
Re: ***Error*** parsing brush
Posted by Leperous on
Sat Feb 14th 2004 at 12:18am
Posted
2004-02-14 12:18am
Leperous
Creator of SnarkPit!
member
3382 posts
1635 snarkmarks
Registered:
Aug 21st 2001
Occupation: Lazy student
Location: UK
Compiles fine for me, with Zoner's tools v2.5.3 (yes they're old!)
Re: ***Error*** parsing brush
Posted by Xylo the Cheese on
Sat Feb 14th 2004 at 12:32am
Posted
2004-02-14 12:32am
13 posts
1 snarkmarks
Registered:
Feb 12th 2004
Occupation: Student
Location: CO, USA
This sounds like something i should look into, does anyone know where i can find 2.5.3 unmodified? i can't find it on google... :rolleyes:
Re: ***Error*** parsing brush
Posted by Xylo the Cheese on
Sat Feb 14th 2004 at 2:02am
13 posts
1 snarkmarks
Registered:
Feb 12th 2004
Occupation: Student
Location: CO, USA
Well, after failing to find out where the console log is, i decided to copy each wing of the school into a new map and save it. guess what, it works now. who knows what the f**k happened, but it seems to work now.
thanks for all the help, sorry for wasting your time. i'll assume that orph's first tip would've solved the problem for anyone else...
from now on, you are officially allowed to refer to me as "f**king n00b"
Re: ***Error*** parsing brush
Posted by Dr Brasso on
Sat Feb 14th 2004 at 4:09am
1878 posts
198 snarkmarks
Registered:
Aug 30th 2003
Occupation: cad drafter
Location: Omaha,NE
ROFLMAO!!!! i like this kid.....hes dedicated, and hes humble.....good man... :wink:
Doc B... :dodgy:
Re: ***Error*** parsing brush
Posted by Orpheus on
Thu Feb 19th 2004 at 11:39am
Posted
2004-02-19 11:39am
Orpheus
member
13860 posts
2024 snarkmarks
Registered:
Aug 26th 2001
Occupation: Long Haul Trucking
Location: Long Oklahoma - USA
even in my five years, i have had maps compile fine, but fail to load, (pitcrew map) .. i always managed to fix them eventually, but the point is, this issue will never stop, till you quit mapping.. get used to it :/