http://www.geocities.com/bg_mapper/de_lomamk.zip
(Just to make it easier)
Even if he's "Anonymous" and "Unknown"?LOL! Sr. Accountless, what a laugh! Nice one Alex!
You can hardly talk Sr. Accountless!
Some advice:I wrote that for Joe_Cool. I'm not critiscing you, just giving some friendly advice. I'll check your map when I get home.
*Have a plan
*Do a rough sketch on grid paper
*Split the map up into 'parts'. This way you can compile small areas. This makes it easier to target errors and will prevent you from going insane when you compile a massive map thats has leaks and errors all over it.
*Carve is a no-no most of the time. Use Vertex Manipulation, you will love it!
*Be realistic. Half-Life is over 5 years old, so don't try to make a 'super duper, ultra fantastic, mega gigantic death map' because there's no chance that it will work. Work to Half-Life's limits.
*Having said that, theres a lot of things you can do in Half- Life. Be creative. No one wants to see a grey box with a gun and a few million enemies
*Have fun!
That means you have too many entities visible/see-able at that time. There are two likely causes for this:Run VIS and then see.
Your not running VIS, or your map has huge ammounts of entities visible at a time.
Solution: run VIS -full, block line-of-sight (aka. vis blocking), combine like entitys in the same room - but only in the same room.
This can refer to several different errors:As for the Half-Life title you have to replace it with an mpeg file and only when you are doing a mod. Any video editing program with titles can do this. Check the tutorial on this site about making mods for some more information.
1. The "too many wads" as mentioned above. 8 wads in WC/Hammer is a good limit, more may cause this error among others. If you are using more than 8 wads you can use Wally to combine the extra wads into one custom wad.
2. Too long a path/name for the map or compiling tools. Only a limited amount of memory is set aside for the path/names. Solution is to move the compiling tools or map into a shallow folder.
3. Having a space in a path/name. Examples: frequently Program Files is part of the path name. Compiling tools do not like the space between "program" and "files". Solutions are to either use the MSDOS pathname, or to move the offending files from under the spaced folder, or put quotes " " around the whole path name in WC/Hammer so that windows uses it right. If your map has the space in its name (eg. Bob map), remove the space and change it to (Bobmap).