There's NOTHING to improve! Yet....

The fog in the daylight version is supposed to be a sandy orange color. I might change it because it sort of looks like that cheese powder crap that they put on cheetos.

As for the fences, I used the texture /tech1soc/032-15b.jpg (I think that's what it is). One weird thing I noticed with the fences is that when you look at them from far away, they display all weird and broken looking. Is that what you are talking about?
I think this might have to do with the fact that they're near the edge of the map. I initially had them right on the edge, and the above problem looked even worse (now they're one cube in from the edge). I could move them in some more, but I would have to sacrifice some playable area...

I´d try fog 1200 or something. That would remove the plain coloured appearance of the fences.

If by behaving weirdly you mean the thin grates you have in some of them, of course they start too flicker once you get such far away that they can´t be represented properly by a few pixels anymore.

And please clean up the archive. what´s with that mcosx folders and files? and package it in a way that ppl only have to extract it to the main directory and have to type /map militarybase instead of map/phoenix/militarybase... coz that´s just uncomfortable. (also asking people to clean up your mess).

The fog appears in front of the solid fence, but not in front of the sky, making the fence appear orange. Is that what your problem was? I'm reluctant to reduce the fog because I want people to see it. Besides, it has no effect on the playability of the map. But I suppose I'll try to compromise somehow...

By the fences behaving weirdly, I mean this:
http://www.geocities.com/crash3519/screenshot_41854.bmp

"what´s with that mcosx folders and files?"

Well, I am a Mac user, but I don't see how you could have possibly figured that out just by looking at the files...
Ok, I'll clean things up... but man, you PC users are laaazy; we Mac users actually have to place the files in /packages manually, spending a whole thirty seconds doing it, too.
And if you can't be bothered to type long map names, CrazyTB wrote this excellent script:
http://www.quadropolis.us/node/85?PHPSESSID=9c250890eee97de7b47b4b8a675d5e0a

\,,/

The package should be simple, you should add a new folder only if you're adding models, textures, skyboxes, etc, and map files should go into Base folder. This isn't for lazyness it's for order. Also new users of the game could not get how to play them.

About the map, I really liked it. The terrain is nicely done, and those fences are really neat.

But obviously isn't perfect, so here's what I didn't like. Beyond the fences lies nothingness, this is such a common error, try adding some dunes and background, make it nice to view and not ending in skybox.
The rusty trim texture gets a little too repetitive, I think that if you find yourself a neat wall texture the map would look a lot better.
You could add some detail to the exterior architecture of the buildings.

Nice work!

Thanks, this is exactly the kind of feedback I'm looking for.

Adding background terrain would require a /mapenlarge, but the problem is that the two sides where I actually want to add terrain would still be on the edge so I would have to move everything.
Is there an easy way to move entities with the architecture? If not, well, I'll do it, but I won't enjoy it...

"The rusty trim texture gets a little too repetitive"

For the fences, or for the buildings? Or for something else entirely?

And I was just kidding about the laziness comment... heh... Ok maybe I wasn't. But I agree with keeping it organised; I just thought it would make more sense if everything was in one folder. But if everyone else is doing it the way you're saying, I guess I'm going to have to change.

Again, thanks, and be sure to check back soon.

\,,/

Doesn´t have to do with being a mac or pc user.
Sauerbraten offers a clear directory structure, that one should be using.

Means download,extract to main folder, start sauer, type /map whatever
and play. Not having to do it diffrently for all maps, remembering any subfolders while typing the map name etc.. I usually take a look in the zip, and when I see "packages" I know I can just extract. Most maps I don´t find to have this directory structure, I mostly don´t bother with.

That screenshot looks like 16bit depth buffering to me. Try to use the 24bit depth buffering of your gfx card and that should go away.

Textures:

"the current one is too striped-looking"

Totally agree. I already changed the buildings' exteriors to the solid rusty green metal texture with the rivets appearing only at corners, doorways, etc.... You'll see what I mean. As for the ceilings, I don't like them either. Any suggestions for what texture I should use instead?

"try to avoid abrubtly changing textures along a flat surface"

Um... where did you find this to be a problem, exactly?

Map size:

Way ahead of you. I already did a "/mapenlarge" and added large plateaus all around as background terrain. This solved the problem I had (a few posts back) and should also hopefully solve the problem that I believe makkE was having.

Fences:

I actually originally had the entire fence with the thin vertical bars. But... I changed it because I have a slow box and all that detail was soaking up a lot of memory. I think I can compromise, though...

Stay tuned for version 1.1

\,,/

"where did you find this to be a problem, exactly?"

This will be easier to show than to describe. I took the liberty of altering one of the corridors just to give you an example of what I was talking about. You can check out the altered map, along with some before and after screenshots here.