I should be so pissed!

(MadJack) #1

Oh yeah, so pissed!

But I’m not. I just had the possibly most sanity damagable thing happen. I was nicely working on map, filling some ent key/values then I saved…

BAM! Radiant closes… Alright, no biggie, let’s retart it and go on from there. Woulnd’t be the first time right? Start that damn thing…

2D/3D area is empty… hmmm… File->Recent->Ebe.map Stays Empty… :???:

Switch back to ultraedit. I get a message telling me the source of ebe.map has changed. Do you want to keep your actual copy or reload the new content. Unfortunately I reload with new content. Empty file.

Panic sets in.

I know I cleaned up THE WHOLE place of .bak files yesterday night! I’m NOT supposed to have one. Since I save quite often I don’t think there’s an autosave.map. It rarely has time to autosave. I have to check… I can’t think about having lost everything. The last backup I have dates from April 10th. I’ve been working LOTS of hours for the last 3 months!!!

Joy. There is actually an autosave.map and an ebe.bak. ebe.bak is more recent. The good part is that since yesterday I mostly worked on getting the command map’s notifications of objectives to work correctly so since that’s in the script file I barely have any changes to make to bring it back the way it was.

As usual, the moral of the story is to keep RECENT backups…

Had I not found a backup, I was seeing myself getting my right arm in TTimo’s throat, pass his stomac, grab his intestines, pull it all out, make a big knot and shove them back in by the hole down below.

Sorry if some think posting that kind of things is irrelevant/stupid/etc but I had to vent.

(CrazedFan) #2

With every compile I save a new backup. map_1a, map1b, map1c…

Live and learn.

(Oh yeah, bummer man.)

(MadJack) #3

The worst is I usually keep a recent backup when cleaning old files but I failed to put one aside yesterday.

I think that’s a bit overkill the way you do it CrazedFan. At 14 MB a pop for each file, wouldn’t be long I’d break the 1 CD size.

I think that from now on I’ll keep a nightly backup. The last save, that’s if it doesn’t crash, will go into the backup dir…

(Java.Lang) #4

I save mine by date. Every stable compile I do (at least one a day) I save that .map file by project_date. Works for me.

(=DaRk=CrAzY-NuTTeR) #5

thats a bummber, but this can releive stress

Place both hands around the monitor stand and pull like you would throttle your subling for spilling gravy down your cloths

start whacking your computer

you live and learn, turning autosave off nomatter much you save is a bad thing

have you lost all your map completely?

(Ragnar_40k) #6

Like Al Lowe said: “Save early, save often” (afaik I remember that was an advice in “The Official Book of Leisure Suit Larry”).
I learned this the hard way too. Now I make backups to different HDs or to CDs regulary.
And when you make things for the 2nd time you can make them usually faster ;-).

(Mr_Tickles) #7

I really thought you meant drunk :slight_smile:

Yeah, after I read this thread, I went and did a load of 3-point clipping, can get quite fun when you get into it. Anyway, I was just about to do some vertex moving to finish off some fiddly bits, I grabbed hold of one of the green dots, and Radiant promptly crashed. I’m glad I started to enjoy the clipping :). And tis true, it is much faster the second time around.

Just had a brainwave, don’t know if it could be implemented into radiant though. A much easier way of 3-point clipping would be to simply set a user defined number of points (minimum 4, otherwise radiant could default back to to 3-point clipping). These points would be placed on each of the vertexes of the shape you wanted, and then radiant could fill the resulting block in when you press enter, it would be so much easier to design odd shapes. It really would.