First I'd like to wish every1 a late merry Christmas

Trying to load a .map gives this error- its crazy

http://i22.photobucket.com/albums/b329/paulb39/radianterror.jpg

That error is not not good. Search for 'assertion failure' you will find post after post about this error.

Rasta writes...

any way to fix it?

The easiest way is to have a working backup of your map and start over from there.

If you don't have one, remove the things you've added since the last time your map worked.

Or do a forum search as Rasta suggested. There are many things which can cause this and equally many solutions.

The_Caretaker writes...

unfortunately- its another mappers .map file- i was gonna make everything caulk- then wen cod4 radiant comes out make it for that, and give him all credit ( I got his permission)

and that was the only version he had- I did the thing in tut section
the reg file and bat file- but it didint work

offer him a case of beer before he kills you.......

Extreme solution:

Open the .map file in notepad or (shudder) wordpad, and delete the last few brushes, save as a new .map filename, and open the new one in radiant. See if it works. YMMV.

So what causes this error?
He found 3 .maps so far- all give the same error- in both my and his radiant

I tried deleting the last brushes- didn't work

how would that of worked anyway?

.map files sometimes get corrupted by Radiant as they are constructed (the program is a bit buggy IMHO). Sometimes the only affected elements are the last few brushes or other object you added to the map, and removing them will sometimes restore the map to a syntax that does not crash radiant.

Buggy behavior included extra vetices in a brush, duplicate verts with bad coordinates, or other badly constructed or formed map elements with characteristics that radiant cannot deal with. That's why deleting the offending elements will sometimes make the map "readable" to Radiant's data parser. This buggy behavior is another good reason to save frequently, and back up your .map files as you go so that you can always revert to a working file if your updated one "goes bad".