compile error

small_sumo · Post by **small_sumo** » Mon May 26, 2003 2:28 pm

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

Post by **jv_map** » Mon May 26, 2003 2:48 pm

First remove all custom pk3s. If it doesn't help, probably your .map file is corrupt

(check .bak file).

small_sumo · Post by **small_sumo** » Mon May 26, 2003 3:18 pm

Hmmmmm dunno much about .bak file. But this line is repeated about a million times.

936.000000 ( ) ( )

in the .bak file

Post by **jv_map** » Mon May 26, 2003 3:32 pm

Argh uh oh

Can you load any of the files in Radiant?

small_sumo · Post by **small_sumo** » Tue May 27, 2003 2:18 am

Any? Well the map file loads fine.

Me thinks sumo will put this one in the toilet and start again.

tltrude · Post by **tltrude** » Tue May 27, 2003 6:01 am

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).

small_sumo · Post by **small_sumo** » Thu May 29, 2003 8:22 am

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.

FUBAR515034 · Post by **FUBAR515034** » Tue Jun 24, 2003 8:08 am

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

small_sumo · Post by **small_sumo** » Tue Jun 24, 2003 9:37 am

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.

m0g · Post by **m0g** » Tue Jun 24, 2003 10:02 am

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

tltrude · Post by **tltrude** » Tue Jun 24, 2003 10:51 am

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.

mohaa_rox · Post by **mohaa_rox** » Tue Jun 24, 2003 1:02 pm

renaming the .bak works? i thought only snapshots.