Radiant crashing on loading my map (corrupt .MAP)

(G0-Gerbil) #1

Yup, latest version of helmsdeep won’t load now since I started messing with ye multi stage constructibles.
Neither 1.4.0 or 1.3.12 load it with the same errors.
It appears to lock up when loading (textures load first), then if I pull up the task manager, I get this alert:

'(process:208): Gtk-CRITICAL (recursed) **: file gtktextbuffer.c: line 543 (gtk_text_buffer_emit_insert): assertion ‘g_utf8_validate (text, len, NULL)’ failed
aborting…

Clicking on aceptar (spanish OS \o/) gives me:

'(process:208): Gtk-CRITICAL (recursed) **: file gtktextbuffer.c: line 543 (gtk_text_buffer_emit_insert): assertion ‘g_utf8_validate (text, len, NULL)’ failed
aborting…

(process:208): gdkGLExt-WARNING (recursed) **: wglMakeCurrent() failed
aborting…

I assume the second window is actually not a real problem in itself, merely a side-effect of the initial error.

The .MAP file is about 10megs, but goldrush is 12megs so I don’t think it’s a buffer overflow or anything.

Any clues before I start wading through the .MAP file by hand to see if somehow there’s a missing " from a corrupt file write or something? :slight_smile:

(G0-Gerbil) #2

Ho hum, opening the file makes it clear enough the problem - the file has become massively corrupted :confused:
Time to try to bsp->map and see what I can salvage :frowning:
Naturally it happens the one day I haven’t made a backup…

(StormShadow) #3

Did you try autosave? Or your most recent .bak file?

Hopefully you wont lose too much :frowning:

(G0-Gerbil) #4

Autosave has never worked for me, producing empty files :confused:
Well, lost a morning’s work - annoying because it was all the objectives and it would have been virtually ready for alpha then!

(MadMaximus) #5

oh man that is tough =/ do you only work off one copy of the map? ive gotten into the habbit of ctrl-s or even changing the map name version to a new number as in test1, test2, even sometimes after changing one texture… i must have 90 map files of the same map in my editing et folder, different series also… the rumba1 to rumba32 series, movingon1 to movingon12 series and so on…

and your right about that autosave… i mean, it does work… but i turned it off for other reasons… like when i was testing a map and all of a sudden my fps dropped 20 frames and the game got sluggish… til i realized that it was radiant autosaving while i was playing.

hope you can get your work back… be a shame to lose it all, or have to rebuild it, good luck man.

(G0-Gerbil) #6

well, I think I grabbed most of the entities converting bsp to map, now I need to merge them with the previous saved version.
Yeah I change the number (am up to v57 myself), but this time I forgot, which figures.
Why the autosave doesn’t work I’ll never know, it’s pissed me off but nothing has fixed it, so not a lot I can do really.

(G0-Gerbil) #7

It’s only gone and bloody well happened again :confused:
Not lost quite as much this time but I think I’ll give it a rest for today before I blow a blood vessel.

Any ideas?

According to radiant the map has 715 entities and 13788 brushes - what limit am I hitting that’s causing radiant to screw up??? :frowning:

(Ifurita) #8

I time and date stamp the file name of every Save As, typically once per day, more if I’m doing a lot of new things to the map. When I’m ready to compile, I strip off the time and date stamps, so that I only have one .bsp file, /lightmaps folder, .script, etc

(G0-Gerbil) #9

I’ve got fine backup procedures (apart from when I ignore them ;)) - but I want to know why radiant is wiping over half of the current file when you save :confused:

(Chruker) #10

You might want to check your harddrive for errors (bad sectors and such).

I’ve had maps up to 32000 brushes witch had no problems loading at all.

I don’t know what radiants limits are in regards to brushes and entities, but its higher than q3map2.

From the source code I have for q3map I can see that there is a limit of 32768 brushes and 1024 entities. I’ve personally reached the same limit with 32768, so I guess thats also the limits in q3map2.

Anyhoo, I would definately check my harddrive if I was you. Did your OS crash after you had saved the map last time?

I don’t like the autosave function because I usually can’t remember where I got to exactly.

(G0-Gerbil) #11

I’ll sort my hard drive out tonight. Got to be worth a try.
As for autosave, I’d use it if it worked for me :confused:

(=DaRk=CrAzY-NuTTeR) #12

hmmmm, tuffy

well if it keeps happening when u decompile

and if radiant wont autosave

then ur pretty much fucked,

might be something wrong with ur comp, i think u should send the .map file to a freind and see if thay can open it, if so u have a big problem, if not u lost a mornings worth of work :frowning: life aint perfect

(G0-Gerbil) #13

Naah once a map file is fooked it’s obvious what the proiblem is (opening in notepad/wordpad/word shows second half of file is pure garbage).
So no recovery possible, just got to try to prevent it happening again, and preferably get bloody autosave working.
Time to download ET again (oh the pain on a 10k a second line :/), uninstall it, and radiant, and start them over from scratch :frowning:

Not got a means to reinstall OS (new computer came with a hard-drive burnt image of XP - want a legit copy of ANYTHING in Colombia? You can forget it :/), so that’ll have to wait for now…