strange map error -1 reply

Please wait...

DuketheLuke

You are reading this.

50 XP

15th February 2009

0 Uploads

309 Posts

0 Threads

#1 11 years ago

I've been mapping a little on one of my maps, but I got this error once, I forgot what it said, something about bad textures, or strange brushes, but I ignored it, so I continued mapping, the next time I opened the map, everything was deleted, I'm like 'WTF' so, I look at the console, and it says this:

34127:89: parse error at '-1.#IND': expected '#number' brush 3006: parse error entity 0: parse error

any help pl0x?




Guest

I didn't make it!

0 XP

 
#2 11 years ago

Was it something along the lines of "degenerate planes"? If so you need to immediately delete the brushes causing the error. In my experience trying to save a map which is experiencing this error can lead to far greater problems.




lassev

Degenerate scripter

50 XP

21st June 2004

0 Uploads

847 Posts

0 Threads

#3 11 years ago

Sounds like the map lost its worldspawn definition. If you feel adventurous, you could open the map in a text editor and check the very beginning looks like this:

// entity 0 { "classname" "worldspawn" // brush 0 Any worldspawn attributes would be listed below the classname (or around it). If these lines aren't there, Radiant can't likely open the map properly. You could fix them by hand. Alternatively you could open your autosave.map (or .bak) or mapname.bak backups, which ever is most up to date.