EVERYTHINGS GONE!!!

I just fixed a few problems with my Classic map, when I got in compiling order, I compiled it, and got quite a surprise.

All of my entities FORGOT THEIR PROPERTIES!!!! Models weren't apearing, doors wont open, light enviornments don't face the right direction, everything has defaulted...

So, I now say, WTF HAPPENED?!?!?!?

The damage has already been done to my map, so I'm edit edit NOT edit edit looking for a solution to fix it. But can anyone tell me WHAT was the cause of this?! rant

Only thing I can think of was that I loaded up ubb3r sUpp3r Us3L3ss point file, while looking for a leak.

Thats the only abitrary thing I've done to my map. :sad: D: :sad: D:

Don't you have any older versions of the map?

No. :sad:

Well consider this a lesson learned. I doubt there's any way to get the
entity values back. Did you try both the .map and .rmf? I have 50
versions of the map I'm working on. :smile:

I don't have an rmf either :sad:

sounds like you possibly compiled using the wrong fgd?

you know that hammer makes backups of the .map and .rmf everytime you compile, and names them as .max and .rmx, don't you?

Holy crap, thats news to me! How the hell did that piece of info slip by me?! Not that I've ever had a need for them...but its the sorta thing you'd assume you'd know of.

I never knew that either, but at least Reno didn't know so I don't feel that stupid. :biggrin:

sounds like you possibly compiled using the wrong fgd?

you know that hammer makes backups of the .map and .rmf everytime you compile, and names them as .max and .rmx, don't you?

Holy damn! That's news to me!

Even if I got a backup file, it would still have the same problem. I looked in the map file and check some entities, and all the properties were defaulted. And since you have to save every time you compile, then the max file would have the same problem :\

did u even look at the max file?

Yep - it's no different :P

if you have an previously compiled bsp that is ok, you could decompile it and rip all the ents out together, and paste them back into hammer.

2 words.....back up.

Condense, economise! One work 'backup'.

I remember once when I went to go open up one of my rmf files in Hammer, the whole map was gone. Unfortunatly I could do nothing about it. You can see how I wouldn't consider losing my entity properties that bad.

Did you 'remove unused entity keyvalues' or something? I can't see this sort of thing happening unless you mess around with the FGDs and check for errors, fixing that problem.

fishy said:
sounds like you possibly compiled using the wrong fgd?

you know that hammer makes backups of the .map and .rmf everytime you compile, and names them as .max and .rmx, don't you?

Me chimes in with my own ignorance

Good god man! I wish I had known that a long time ago!

Leperous said:
Did you 'remove unused entity keyvalues' or something? I can't see this sort of thing happening unless you mess around with the FGDs and check for errors, fixing that problem.

Actually, yes. A little while before I compiled, I did a quick check for errores, and practically every entity had an "unused key values" error

That's different. That just means you've ticked a flag or entered a value in an entity where it doesn't apply. Fixing a problem like that should not delete their other values.

did you upgrade your valve hammer editor? I know there were issues happening when people updated the hammer, older version rmf's got corrupted and crap.

Ferret said:
did you upgrade your valve hammer editor? I know there were issues happening when people updated the hammer, older version rmf's got corrupted and crap.

Heh. I really don't upgrade my version of WC (I'm still saying WC :smile: ) It took me like.... a year or so before I went from 2.1 to 3.3. So 3.3 is where I'll stay until I need to upgrade :\

Didn't you feel foolish after waiting so long and depriving yourself of v3's useful additions? Doesn't it seem silly that you could be making the same mistake again?

ReNo said:
Didn't you feel foolish after waiting so long and depriving yourself of v3's useful additions? Doesn't it seem silly that you could be making the same mistake again?

What are you saying?

That VHE 3.5 beta is better in some way O_o

I don't have much intention on downloading another WC/VHE unless they put in something like, real time lighting :razz:

They aren't exactly huge downloads, and 3.5 does add a few nice features such as model previews, pointfile display in the 3D window, and user selectable background colour for the 3D view.

http://collective.valve-erc.com/index.php?go=hammer_beta

i've not had to load a map to find a leak since i started using 3.5. every one was found, in the editor, at a fraction of the time that it would have taken if i hadn't upgraded.

and i cant even guess at how much time the model preview has saved me.

didn't know about the background colour though.

Come to think of it, you are even missing out on 3.4's improvements G.Ball! Sure most of them are reasonably small, but timed depth selection in the 3D view is very handy.

Fishy, having a crazy bright background colour such as pink makes finding leaks quite a bit easier too, its far more obvious to spot than the default black.

I appreciate the suggestion, but I'm fine with 3.3 :smile:

I don't get it, its not a big download, and it adds useful features - there is no reason NOT to get it!

ReNo said:
Come to think of it, you are even missing out on 3.4's improvements G.Ball! Sure most of them are reasonably small, but timed depth selection in the 3D view is very handy.

Fishy, having a crazy bright background colour such as pink makes finding leaks quite a bit easier too, its far more obvious to spot than the default black.

Haha, mine is pink. :smile:

If you're stubborn enough to not want to download 3.4 even why would I trust that you'd do anything to fix your map problems Ball?

Whats this pink background I hear about?

Gorbachev said:

ReNo said:
Come to think of it, you are even missing out on 3.4's improvements G.Ball! Sure most of them are reasonably small, but timed depth selection in the 3D view is very handy.

Fishy, having a crazy bright background colour such as pink makes finding leaks quite a bit easier too, its far more obvious to spot than the default black.

Haha, mine is pink. :smile:

If you're stubborn enough to not want to download 3.4 even why would I trust that you'd do anything to fix your map problems Ball?

I do fix my map problems.

I'm pretty careful with my mapping, so I usually don't run into real big humongus errors. Worst problems I have are generally problems that are "unforseen"... like having cordon bounds delete your map... hoo ha. :heee:

$loth said:
Whats this pink background I hear about?

What more information can you possibly need to know? You can change the background colour of the 3D view, which has been mentioned multiple times already.

ReNo said:

$loth said:
Whats this pink background I hear about?

What more information can you possibly need to know? You can change the background colour of the 3D view, which has been mentioned multiple times already.

:rolleyes: oops I should read more carefully.

by the way, i still take my clothes down to the river and bash them off of big rocks. none of them new fangled washing machine gadgets for me.

:rolleyes:

Maybe it's a little late, but there's something like GetDataBack to recover old files, you know ?

G.Ballblue said:

Gorbachev said:

ReNo said:
Come to think of it, you are even missing out on 3.4's improvements G.Ball! Sure most of them are reasonably small, but timed depth selection in the 3D view is very handy.

Fishy, having a crazy bright background colour such as pink makes finding leaks quite a bit easier too, its far more obvious to spot than the default black.

Haha, mine is pink. :smile:

If you're stubborn enough to not want to download 3.4 even why would I trust that you'd do anything to fix your map problems Ball?

I do fix my map problems.

I'm pretty careful with my mapping, so I usually don't run into real big humongus errors. Worst problems I have are generally problems that are "unforseen"... like having cordon bounds delete your map... hoo ha. :heee:

You don't seem to realize what I'm saying though. It's not a question of mapping practices but using newer tools that were updated for reasons. The maps are far less prone to glitches in the 3.4 version and while 3.5 is a beta I've had 30+ maps run through it with no issue. It's the same deal with still using the old Quake tools...sure they run, but there are Zoner's and then Merl's and even Cagey's for certain bits...they are made for the game in its current form. There is now a different version of the game, and to use old toolsets and expect them to be fine is just...odd. By getting the latest of the fully tested Hammer and Compile tools you will be eliminating issues that may be unforseen to you but have been experienced by many others and were fixed. So you cannot complain that the error has happened because of your own fault of not getting a newer version that works just fine. It's like blaming Windows for getting Blaster when you had the update available for over a year and just didn't feel like getting the update. Sure it's unforseen to you, but there are updates for reasons.

While maybe this won't fix this particular issue, it's something to think about...

DO NOT USE THE .MAP FORMAT AHHHHHH

(if thats what you were using that is)

The only thing I've used the .map format is to recover cripple maps of others by using QuArK to open it, save, then open it in Hammer and then save to .rmf.

I think G has something to hide... why else would you not DL the new hammers?