Thanks for the review, Rabe. The caps was worth a try, it's just getting a little irritating after a while.
I did some minor cosmetic changes:
1)Removed all Trak5 textures but Panel2a & the textures inside the TC-3's (the planes)
2)Changed the textures on the TC-3s _{(the planes)} from the Trak5 to a darker version of mm-metalbase2 with trak5 tile3_n because I want it to look armour-plated
3)The trak5 pipes were replaced with different coloured mm-metalbase2 textures
4)Removed all the X's from the barriers, as they took up too much WTR
5)Added subtle differences in the flat floors to break up the monotony a little bit
6)Moved the sunlight & yawed cloudbox

If you could please explain the clipping and texture flaws a little more I'll gladly change them.

До свидания и Спасибо
-P

So what's defined as "futuristic textures"? Trak5, Lunaran, Phillipk sets?
Suggestions on how to make the spammed textures effective/what to change them to would be helpful.
I changed the lighting to a whiter colour.
До свидания и Спасибо
-P

Is not very easy to teach how to not make spammed textures in a comment, texturing is not easy, its like "just dont do spam it"
if you got a wall dont fill it with just one texture, first you have to add shapes or add at least 2 textures to the wall, also, for the floor you used in one part boxes textures, instead of that, use concrete, wich doesnt need volume to looks good.
Now about the lights i prefer any other colour than whitem white is boring and make the map looks unfinished, the yellow is fine, but preferably more soft.

Good examples about textures: Tempest, alloy, hashi, nucleus, turbine, ot.

Okay, I added a bunch of pipes, ducts, and textures to the walls, roofs, & changed the box floor texture. Step in the right direction or no?
До свидания и Спасибо
-P

The texturing is still a terrible mess. If you arent that experienced with texturing yet, you should use only one or mix a maximum of two texture packs. If you decide to use two texture packs, make sure that both either have or dont have normal/height/spec maps and also have similar shadersettings (which you can adjust of course). Unless your goal is a lot of contrast (like a dirty outside world and a clean underground laboratory environment) you should also choose packs that have similar "dirtiness", like for example tech1soc and egyptsoc on metl3 which almost blend into each other.
You just randomly mixed like a dozen completely different texture packs, sometimes even on one wall directly beside each other, what created very unrealistic contrasts. An example are the perfectly clen trak5 textures directly beside extremly dirty rorschach textures, where there is no reason for one one to be clean and the other one to be dirty. Another bad example are the lunaran textures, which have heavy normal and parallax mapping, directly beside tecsoc textures, which dont have either of those layers, what makes the surface look unrealistic and the texture flat and boring. Aside from your choice of texture the placement isnt good at all either. In many places on your map the textures dont fit on the geometry. When greating the geometry you have to have your textures in mind and make sure you have a fitting texture for every surface, what means that it isnt cut off at a palce where it shouldnt be.
I noticed the same mistakes on most of your other maps, so I would highly recommend you start with not using more than one or two texture packs per map and generally spend more time on getting things actually fit and look good and not just getting them done.

This may sound a little bit harsh, but had to be said. I wish you good luck with your map and look forward to seeing some improvements :)

probably have a bumpmap or parlexmap shader set when only using a diffused texture:

setshader bumpspecwold //i dont remember if this is a real shader or not
texture 0 mytexture.jpg
texture 0 mytexture2.jpg
texture z mytexture2_b.jpg
texture s mytexture2_s.jpg

mytexture.jpg will show an error because it is expecting a spec (s) and normal (b) map but only receiving a diffused. This makes your texture look very odd, instead try.

setshader stdworld
texture 0 mytexture.jpg
setshader bumpspecwold
texture 0 mytexture2.jpg
texture z mytexture2_b.jpg
texture s mytexture2_s.jpg

remember to set your shader every time you switch texture types. This problem can sometime happen between documents as well:
//mymap.cfg
texturereset
texture 0 sky.jpg
texture 0 mytexture.jpg
texture 0 another.jpg

texture 0 simplediffuedetex.jpg //this one may error

most packages files do not reset the shader to stdworld at the end of the document, this may cause anything below an exec to error, so make sure you either dont define textures after exec or set the shader before defining the texture:

//mymap.cfg
texturereset

setshader stdworld
texture 0 simplediffuedtex.jpg

I would rather not look at the examples Chasester's stated as they even crash your Sauerbraten...

I've once made a file which you could always use as a reference of the shader-settings within Cube Engine 2 (Sauerbraten and Red Eclipse, I guess).
It contains a cfg-file with all those settings and some respective information about it.
Texture Prefabrication

I've also made a Map Prefabrication once, but I've never actually finished it (well, the lighting-command part and so on. However, the texturing part should be finished).
Map Prefabrication

P.S.
I've got to warn with the Map Prefab, it used to be on an SVN version and rendered on OpenGL only (as that was default back then). However it shouldn't matter the shader-settings (except those custom shaders but they aren't in default Sauerbraten anyway).