Page 1 of 1
compile error
Posted: Mon May 26, 2003 2:28 pm
by small_sumo
26470 files in pk3 files
************ ERROR ************
ParseEpar: token too long
then a bit further down......
************ ERROR ************
LoadPortals: couldn't read C:\MOHAA\main\maps\abtf_bots.prt
Posted: Mon May 26, 2003 2:48 pm
by jv_map
First remove all custom pk3s. If it doesn't help, probably your .map file is corrupt
(check .bak file).
Posted: Mon May 26, 2003 3:18 pm
by small_sumo
Hmmmmm dunno much about .bak file. But this line is repeated about a million times.
936.000000 ( ) ( )
in the .bak file
Posted: Mon May 26, 2003 3:32 pm
by jv_map
Argh uh oh
Can you load any of the files in Radiant?
Posted: Tue May 27, 2003 2:18 am
by small_sumo
Any? Well the map file loads fine.
Me thinks sumo will put this one in the toilet and start again.
bak
Posted: Tue May 27, 2003 6:01 am
by tltrude
The .bak file is a back up file for your map. You just have to change the extention name to .map to use it. I may still have a copy of your map if you want me to look (as it was then).
Posted: Thu May 29, 2003 8:22 am
by small_sumo
Yeah Tom if its ok with you mail me what you have. I looked at redoing the map and realise how much work is in it
.
Its definately corrupted, it wont make a bsp.
..
Posted: Tue Jun 24, 2003 8:08 am
by FUBAR515034
Never saw a reply in this one. Would help if you guys posted your findings here. So we could get help. I have the same prob
Posted: Tue Jun 24, 2003 9:37 am
by small_sumo
No solution found I think. I survived because Tom send me an older copy of my map file. Al I can sugest to to make prefabs from your broken map and try to build a new one a piece at a time making sure you dont add the gremlin. These days I save extra copies of my map file as they seam to get delicate in the later stages.
Posted: Tue Jun 24, 2003 10:02 am
by m0g
Im not sure if this will help, but i found the error somewhere else... for a different game though. Probably means the same...
************ ERROR ************
ParseEpar: token too long
"Error: ParsePar: token too long"
While it usually indicates you have a string that's too long in an entity, it can also indicate a much more widespread file corruption.
?Go to the entity report screen, and search for entities containing values with ? in it (see image). Edit the entity, press the 'SmartEdit' button and delete any properties that look like gibberish (contain ?). Recompile.
Page is
here
.map
Posted: Tue Jun 24, 2003 10:51 am
by tltrude
Hmmm... That sound like a problem I had once. My .map file crashed and burned. It turned out to be quotation marks I had put in a message trigger value. Appearently the editor puts in the quotes, so when I put them in, the line had double quotes and made everything go kaboom. I found it by opening a copy of the .map file with Wordpad and deleting sections until I narrowed it down to the bad line.
Posted: Tue Jun 24, 2003 1:02 pm
by mohaa_rox
renaming the .bak works? i thought only snapshots.