Spring - User contributions [en]

Tutorial:CreateMaps(Fnordia et al)

2005-10-13T07:36:50Z

60.234.132.130: /* Preparing your map */

'''Original by aGorm, with help from LathanStanley'''



==The Idea==
First of all you need an idea. There is no point (OK, there is some point for test purposes) in making a map just like another one that already exists. You need to think of certain things before you make your map.
# Is this map idea different, not just a copy of someone else's?
# Does my map idea give each player a fair share of the cover and high ground?
# Is my map idea possible to make?
# Is it possible with the amount of time I'm willing to spend?

If you answered yes to the above, then you are 25% of the way towards making your map!

You should probably doodle it on a piece of paper to act as a guide later.

==The Tools==
With your idea hopefully sketched out, it's time to get the tools to make the map! (You can skip this if you already have them.)

For all your map compiling needs you should first download the [http://fileuniverse.com/?p=showitem&ID=1234 newest MapConv program].

You will also need some image editing software. Favorites are Photoshop, the [http://www.gimp.org/ GIMP], And Paintshop Pro.
The GIMP, however, is the only one that's free!
(I'm going to have to assume you know how to use the program you choose. If you can't there are loads of tutorials on the net.)

You may also want to check out [http://www.planetside.co.uk/terragen/ Terragen] for generating terrain. But as you have to pay to render anything of a good size, I won't mention it other than here. Another tool for generating terrain is the freeware tool [http://www.delphigl.de/projects/terrtexgen/eng_index.html TerrTexGen]. "It generates a terraintexture on the base of a grayscale heightmap und uses five surfacetextures that are distributed over the heightmap."

==Preparing your map==
This is the fun part! And also, often, the longest part.

For a map you will need several different things:
# a texture map
# a height map
# a metal map

And several optional things for added functionality:
# a tile map

They all have certain needs! Read this bit carfully!

===Texture Map===
All maps are based on a texture image. This image's width and height must be an exact multiple of 1024 pixels. So, for instance, you can have a "4096 by 8192" image, but not a "4096 by 4608" image, as 4608 does not divide by 1024. It, like all three maps, must be saved as a 24 bit BMP.

It may look like whatever you want! Find a texture (preferably, one that you can tile seamlessly) and fill your texture map with it. You could, for instance, fill the whole image with a sand texture. This would make your whole world look like sand. You could then decide to add a few patches of grass to it by finding a suitable grass texture and adding it on in patches. So you'd have a map that was mostly sand with a few patches of green.

===Height Map===
Next is the height map. This must be exactly one eighth (1/8) of the size of the texture map '''+ 1 pixel!''' For instance, if the dimensions of your texture map are "4096 by 8192", divide 4096 and 8192 each by 8 and add one to the result of each. The result for this example would be "513 by 1025". The height map is a black and white BMP. Only use black and white, no colour! (well its better to work it as a greyscale image, and when saving to process, convert to rgb and save as bmp, that way you get a 24 bit bmp)

White areas are the tops of mountains; black areas are the sea floor or the bottom of valleys. The shades of grey between are the different heights between! When you draw your heightmap, make sure the white blends into the black with greys. I suggest you use the blur tool. If you have a white splodge in a patch of black you will have a very tall pillar that won't look natural at all!

===Metal Map===
Finally, you need a metal map. This is the same size as the height map, one eighth (1/8) of the size of the texture map '''+ 1 pixel.''' On this one you paint down red (in verying degrees) to represent metal. So a red spot that is RGB(50,0,0) will provide about a 5th of the metal patch of red RGB(255,0,0) will give.

On this map you can also place green pixels. Each green pixel will create 1 geothermal vent. If you put down a green splodge you will get a cluster of geo vents! Only place 1 pixel.

Ensure you have all three saved as 24 bit BMPs and you're ready to convert it all to a map!

===Tile Map===
iles are basically repeating images. They are exactly the same. The map compiler, by comparing peices to the texture to each other, sees which little square tiles in your texture are exactly alike. If they are the same, instead of wasting precious harddrive and bandwidth space, the compiler sets a reference from on tile to the next. If your map is made out of only one small tile, repeating for the whole texture, the map will compress extreemly well. Down to only a few kilobytes. But this would look very boring. So most map makers use a variety of tiles to make their map more interesting. A good map maker will find a balance between looks and size.

To make a tile:
Open up your image editing program.
Create a new image.
As the Spring engine uses a 32 pixel tile engine, you have to set your image size to 32 pixels, or a multiple of 32 pixels. Therefore, tile sizes should be one of the following:
32x32 pixels,
64x64 pixels,
96x96 pixels,
128x128 pixels
etc.
Tiles also do not have to be square, it is perfectly possible to make rectangular tiles. Tiles should also be seamless, so that when repeated do not seem to have an obvious edge.

Once you have created your tile, do a Fill operation with a texture. The texture of course is our tile that we have made in the previous step. If you do not know how to do this, ask around. Make sure to state which image editing software you use, so we can help you easier.

Now, once you have your basic tile down, add in different features on your map, such as mountains, rivers, seas, deserts, grasslands, or whatever your map has. Remeber, for smaler file sizes make these different features out of tiles as well. If you do all of this properly, you can get your file size down very small, and this will keep everyone happy.

==MapConv.exe==

Instuctions pulled from [http://fileuniverse.com/?p=showitem&ID=1234 the newest MapConv program]. If all goes well, the MapConv.exe should create four new files: mini.bmp, mini.dds, yourmapname.smf, and yourmapname.smt.

<code>USAGE:

mapconv [-l] [-i] [-c <compression>] -x <max height> -n <min height> [-o
<Output file>] [-e <tile file>] [-y <Typemap file>] -m <Metalmap file> -a
<Heightmap file> -t <Texture file> [--] [-v] [-h]

Where:

-l, --lowpass
Lowpass filters the heightmap

-i, --invert
Inverts the height map vertically (not the height values but the height map
(uhm someone rewrite this))

-c <compression>, --compress <compression>
(value required) How much we should try to compress the texture file.
Default value 0.8 . (lower=higher quality, larger file)

-x <max height>, --maxheight <max height>
(required) (value required) What altitude in spring the max(0xffff) level
of the height map should represent

-n <min height>, --minheight <min height>
(required) (value required) What altitude in spring the min(0) level of
the height map should represent

-o <Output file>, --outfile <Output file>
(value required) The name of the created map

-e <tile file>, --externaltilefile <tile file>
(value required) External tile file that will be used for finding tiles,
tiles not found in this will be added in a new tile file

-y <Typemap file>, --typemap <Typemap file>
(value required) Type map to use, uses the red channel to decide type,
types are defined in the .smd, if this argument is skipped the map will be
all type 0

-m <Metalmap file>, --metalmap <Metalmap file>
(required) (value required) Metal map to use, red channel is amount of
metal, green=255 is where to place geos (one pixel=one geo). Is resized to
fit the mapsize

-a <Heightmap file>, --heightmap <Heightmap file>
(required) (value required) Input heightmap to use for the map, this
should be in 16 bit raw format (.raw extension) or an image file. Must be
xsize*128+1 x ysize*128+1 in size.

-t <Texture file>, --intex <Texture file>
(required) (value required) Input bitmap to use for the map. Must be
xsize*1024 x ysize*1024 in size. (xsize,ysize integers determined from this
file)

--, --ignore_rest
Ignores the rest of the labeled arguments following this flag.

-v, --version
Displays version information and exits.

-h, --help
Displays usage information and exits.

Convers a series of bmp/raw files to a spring map. This just creates the .smf
file, you will also have to create a .smd file using a text editor
</code>
==Mothers MapConv==
The usage is the same as above, with the following exceptions:
All features (including GeoVent/Tree/Grass) are now on their own FeatureMap. This is a 24bit bmp specified with the -f <featuremapname.bmp> flag.
''It should be 1/8th the resolution of your map.'' (i.e. 1 pixel smaller in each direction then your heightmap)

Tree's and GeoVents are placed on the green layer.
*255 Places a GeoVent
*200-215 Places tree types 1-16

MapConv will try to place these features in the exact spot you place them, it will then go into crackhead mode if it cannot.

Grass is the blue layer. The blue value maps to a 'pseudo-density' of the grass. The 'grass' map in the engine is very very low resolution, so be aware that you will not get nice linear results. 255=full grass, 0=no grass.

The red layer places 'Arbitrary Features,' aka wreckages. One pixel of red equals one feature. Red '1' gives you a feature of the first arbitrary type, 2 the second, 3 the third, and so on.

===But what are these 'Arbitrary Features,' Im so confused!===
They are 'features' found in the /features/All Worlds or /features/corpses filesystems. Which feature is 'type 1' is defined on a map-by-map basis via a new file called 'fs.txt'. This file should contain <cr> delimited feature names. The first line is the feature placed when a red=1 dot is found, etc.

===Ok, Now what do I do?===
If you are using any custom features, and/or you want to mod-proof your map, you should include them in the sd7 that you package the map in. The tree structure should look something like:

<code>
<mapname.sd7>
-maps/
-mapname.smf
-mapname.smt
-mapname.smd
-Objects3d/
-<featurename[s]>.3do(specified in the tdf)
-features/
-All Worlds/
(and/or)
-Corpses/
-<featurename[s]>.tdf
-textures/
-tatex/
-<texname[s]>00.bmp or .tga
</code>
Without getting into modding/unit making I will say that the .tdf tells you the name of the .3do ("Object="), and the name of the 'feature' is in the top brackets. The .3do specifies the texture names. The engine looks for those texture names + 00 in either bmp or tga format in tatex.

Examples of a built-in XTA wreckage name would be <code>armckfus_dead</code> which would be looking for a tdf (likely armckfus_dead.tdf) that has a [armckfus_dead] section which then specified something like <code>Object=armckfus_dead</code>.

armckfus_dead.3do Would then specify some texture like <code>wreck01b</code> which would go looking for either a wreck01b00.bmp or wreck01b00.tga file.

[http://fileuniverse.com/?p=showitem&ID=1421 Start with this version of MapConv]
or
[http://www.fileuniverse.com/?p=showitem&ID=1507 This one]
[I will clean this up and add more later --Mother]

==Making your map work==
This is the final push. Once Sharp map has finshed it will spit out a .sm2 file. This needs to be copyed to the MAPS folder in Spring. But you still need one more thing: an .smd file. Basically, this file tells the game things like the maximum metal, the light colours, the clouds, etc. (All the bits you were thinking that you hadn't done yet!)

I would suggest you copy the .smd of another map and fiddle with the settings until you get what you want. smd's can be opened in notepade or similar. Look at all the .smd's so you can get a jist of what each option does. Make sure both the .sm2 and .smd have the same file name then start up Spring (not the client!) in [http://taspring.clan-sy.com/wiki/FAQ#People_talk_about_.27Single_Player.27._How_do_I_start_a_single_player_game.3F single-player mode] and run the commanders script. Choose your map and away you go!

==SMD Rundown==
What follows is all that we (aGorm and LathanStanley) have figured out in the SMD's. Its by no means the be all and end all, but it's the next best thing.

* Goto [[Maps:SMD]] for a more detailed listing

===General Map Information===
* Description is just a short description of your map. Keep it simple.
* TidalStrength determines how much energy tidal generators will produce. A normal figure is around 20.
* Gravity, as you would expect, affects ballisitcs and how far units fly after an explosion.
* MaxMetal is the maximum amount of metal you will gain from one game square in 1 second from an area of metal that had a red value of 255 in your metal map. If making an old style metal deposit map, then this will be quite high: maybe 2 or 3. If you are making a new style metal-all-over-the-place-map, then it will be low: perhaps 0.2. Also for old style maps, you'll have to fiddle with the...
* ExtractorRadius, which is the area that is harvested by 1 metal extractor. For old style maps make this very small, so as they only take from one deposit.

===Atmosphere, Water Colours===
Each value (it would appear this bit is by no means gospel) is a representation of the RGB values for that parameter. It would appear to be relative, i.e. you can put in what ever numbers you like and the game will work out what you want. The best way to go about it is to look at it as percentages.
The numbers 1, 0.5, 0.2 refer to 100% red, 50% green and 20% blue. But 2, 1, 0.4, will get the same result. Using numbers below one for all the numbers will result in the colour being less bright.

This is all a bit confusing so an example will be given:

SkyColor=0.2 0.1 0.5;

In this example the sky is coloured with 20% red, 10% green, and 50% blue, approximatly RGB(51,25,127), resulting in a very deep night-time blue. Other colours are added to the initial sky colour. If you set your sun as being a pale yellow and it came out rather green, this is why.

One helpful tip is ''negative'' colour. That's right: you can type in a negative number for a colour and it will remove it from the base sky colour. Just be careful not to go below the original values or you may get a surprise.

===The Sun System/Shadow System===
The Sun System/Shadow System is quite a useful tool as well in making your maps look ''well done''.
Within the .smd file there is a line:

"SunDir=-1 1 -.5; //direction of sun" (The part of the "//" is a comment.)

The numbers "-1", "1", ".5" determine the angle and elevation of the sunlight system.

The first number is the X angle (East/West) (from -1 to 1) where any negative number means the sun is on the West (and therefore shadows will be cast east), and any positive number means the sun is on the East (and therefore shadows will be cast west), and if the number is 0 there are no east or west shadows, the sun is directly above you.

The second is its elevation, (0 to 1), this number is how far from the horizion the sun is, ignoring it's angle. Thus, 1 puts the sun directly overhead (while still casting angular shadows) and 0 putting it directly on the horizion.

The final number is the Z angle (North/South). (I know, I know, they wrote the engine with Y as elevation and Z as vertical. Don't blame me.) It is just like the East West positioning, where negative numbers put them on the North, and positive numbers put them on the South.

'''Example Usage:''' If you want the shadows ''in'' one of the boxes (your shadow casting surface is in the middle), use the numbers provided, or start from them and tweak the angle and sun height as seen fit.

N
----------------------------------------------
| ( 1 .5 -1) | ( 0 .5 -1) | (-1 .5 -1) |
----------------------------------------------
W | ( 1 .5 0) | ( 0 1 0) | (-1 .5 0) | E
----------------------------------------------
| ( 1 .5 1) | ( 0 .5 1) | (-1 .5 1) |
----------------------------------------------
S

'''Note:''' on the current build, it ''will'' cast the shadows in the proper direction, etc. Negative direction numbers tend to make some maps unstable and cause crashes. The best solution would be to rotate or flip your map to where the shadows point up or right (North or West). I do believe these bugs are being worked on and will be fixed soon.

We can only hope this has been helpful! Any questions, or things you think we have missed, please ask us in the maps section.

[[Category:Maps]]
[[Category:Development]]

Tutorial:CreateMaps(Fnordia et al)

2005-09-28T05:33:23Z

60.234.132.130:

'''Original by aGorm, with help from LathanStanley'''



==The Idea==
First of all you need an idea. There is no point (OK, there is some point for test purposes) in making a map just like another one that already exists. You need to think of certain things before you make your map.
# Is this map idea different, not just a copy of someone else's?
# Does my map idea give each player a fair share of the cover and high ground?
# Is my map idea possible to make?
# Is it possible with the amount of time I'm willing to spend?

If you answered yes to the above, then you are 25% of the way towards making your map!

You should probably doodle it on a piece of paper to act as a guide later.

==The Tools==
With your idea hopefully sketched out, it's time to get the tools to make the map! (You can skip this if you already have them.)

For all your map compiling needs you should first download the [http://fileuniverse.com/?p=showitem&ID=1234 newest MapConv program].

You will also need some image editing software. Favorites are Photoshop, the [http://www.gimp.org/ GIMP], And Paintshop Pro.
The GIMP, however, is the only one that's free!
(I'm going to have to assume you know how to use the program you choose. If you can't there are loads of tutorials on the net.)

You may also want to check out [http://www.planetside.co.uk/terragen/ Terragen] for generating terrain. But as you have to pay to render anything of a good size, I won't mention it other than here. Another tool for generating terrain is the freeware tool [http://www.delphigl.de/projects/terrtexgen/eng_index.html TerrTexGen]. "It generates a terraintexture on the base of a grayscale heightmap und uses five surfacetextures that are distributed over the heightmap."

==Preparing your map==
This is the fun part! And also, often, the longest part.

For a map you will need several different things:
# a texture map
# a height map
# a metal map

They all have certain needs! Read this bit carfully!

===Texture Map===
All maps are based on a texture image. This image's width and height must be an exact multiple of 1024 pixels. So, for instance, you can have a "4096 by 8192" image, but not a "4096 by 4608" image, as 4608 does not divide by 1024. It, like all three maps, must be saved as a 24 bit BMP.

It may look like whatever you want! Find a texture (preferably, one that you can tile seamlessly) and fill your texture map with it. You could, for instance, fill the whole image with a sand texture. This would make your whole world look like sand. You could then decide to add a few patches of grass to it by finding a suitable grass texture and adding it on in patches. So you'd have a map that was mostly sand with a few patches of green.

===Height Map===
Next is the height map. This must be exactly one eighth (1/8) of the size of the texture map '''+ 1 pixel!''' For instance, if the dimensions of your texture map are "4096 by 8192", divide 4096 and 8192 each by 8 and add one to the result of each. The result for this example would be "513 by 1025". The height map is a black and white BMP. Only use black and white, no colour! (well its better to work it as a greyscale image, and when saving to process, convert to rgb and save as bmp, that way you get a 24 bit bmp)

White areas are the tops of mountains; black areas are the sea floor or the bottom of valleys. The shades of grey between are the different heights between! When you draw your heightmap, make sure the white blends into the black with greys. I suggest you use the blur tool. If you have a white splodge in a patch of black you will have a very tall pillar that won't look natural at all!

===Metal Map===
Finally, you need a metal map. This is the same size as the height map, one eighth (1/8) of the size of the texture map '''+ 1 pixel.''' On this one you paint down red (in verying degrees) to represent metal. So a red spot that is RGB(50,0,0) will provide about a 5th of the metal patch of red RGB(255,0,0) will give.

On this map you can also place green pixels. Each green pixel will create 1 geothermal vent. If you put down a green splodge you will get a cluster of geo vents! Only place 1 pixel.

Ensure you have all three saved as 24 bit BMPs and you're ready to convert it all to a map!

==MapConv.exe==

Instuctions pulled from [http://fileuniverse.com/?p=showitem&ID=1234 the newest MapConv program]. If all goes well, the MapConv.exe should create four new files: mini.bmp, mini.dds, yourmapname.smf, and yourmapname.smt.

<code>USAGE:

mapconv [-l] [-i] [-c <compression>] -x <max height> -n <min height> [-o
<Output file>] [-e <tile file>] [-y <Typemap file>] -m <Metalmap file> -a
<Heightmap file> -t <Texture file> [--] [-v] [-h]

Where:

-l, --lowpass
Lowpass filters the heightmap

-i, --invert
Inverts the height map vertically (not the height values but the height map
(uhm someone rewrite this))

-c <compression>, --compress <compression>
(value required) How much we should try to compress the texture file.
Default value 0.8 . (lower=higher quality, larger file)

-x <max height>, --maxheight <max height>
(required) (value required) What altitude in spring the max(0xffff) level
of the height map should represent

-n <min height>, --minheight <min height>
(required) (value required) What altitude in spring the min(0) level of
the height map should represent

-o <Output file>, --outfile <Output file>
(value required) The name of the created map

-e <tile file>, --externaltilefile <tile file>
(value required) External tile file that will be used for finding tiles,
tiles not found in this will be added in a new tile file

-y <Typemap file>, --typemap <Typemap file>
(value required) Type map to use, uses the red channel to decide type,
types are defined in the .smd, if this argument is skipped the map will be
all type 0

-m <Metalmap file>, --metalmap <Metalmap file>
(required) (value required) Metal map to use, red channel is amount of
metal, green=255 is where to place geos (one pixel=one geo). Is resized to
fit the mapsize

-a <Heightmap file>, --heightmap <Heightmap file>
(required) (value required) Input heightmap to use for the map, this
should be in 16 bit raw format (.raw extension) or an image file. Must be
xsize*128+1 x ysize*128+1 in size.

-t <Texture file>, --intex <Texture file>
(required) (value required) Input bitmap to use for the map. Must be
xsize*1024 x ysize*1024 in size. (xsize,ysize integers determined from this
file)

--, --ignore_rest
Ignores the rest of the labeled arguments following this flag.

-v, --version
Displays version information and exits.

-h, --help
Displays usage information and exits.

Convers a series of bmp/raw files to a spring map. This just creates the .smf
file, you will also have to create a .smd file using a text editor
</code>
==Mothers MapConv==
The usage is the same as above, with the following exceptions:
All features (including GeoVent/Tree/Grass) are now on their own FeatureMap. This is a 24bit bmp specified with the -f <featuremapname.bmp> flag.
''It should be 1/8th the resolution of your map.'' (i.e. 1 pixel smaller in each direction then your heightmap)

Tree's and GeoVents are placed on the green layer.
*255 Places a GeoVent
*200-215 Places tree types 1-16

MapConv will try to place these features in the exact spot you place them, it will then go into crackhead mode if it cannot.

Grass is the blue layer. The blue value maps to a 'pseudo-density' of the grass. The 'grass' map in the engine is very very low resolution, so be aware that you will not get nice linear results. 255=full grass, 0=no grass.

The red layer places 'Arbitrary Features,' aka wreckages. One pixel of red equals one feature. Red '1' gives you a feature of the first arbitrary type, 2 the second, 3 the third, and so on.

===But what are these 'Arbitrary Features,' Im so confused!===
They are 'features' found in the /features/All Worlds or /features/corpses filesystems. Which feature is 'type 1' is defined on a map-by-map basis via a new file called 'fs.txt'. This file should contain <cr> delimited feature names. The first line is the feature placed when a red=1 dot is found, etc.

===Ok, Now what do I do?===
If you are using any custom features, and/or you want to mod-proof your map, you should include them in the sd7 that you package the map in. The tree structure should look something like:

<code>
<mapname.sd7>
-maps/
-mapname.smf
-mapname.smt
-mapname.smd
-Objects3d/
-<featurename[s]>.3do(specified in the tdf)
-features/
-All Worlds/
(and/or)
-Corpses/
-<featurename[s]>.tdf
-textures/
-tatex/
-<texname[s]>00.bmp or .tga
</code>
Without getting into modding/unit making I will say that the .tdf tells you the name of the .3do ("Object="), and the name of the 'feature' is in the top brackets. The .3do specifies the texture names. The engine looks for those texture names + 00 in either bmp or tga format in tatex.

Examples of a built-in XTA wreckage name would be <code>armckfus_dead</code> which would be looking for a tdf (likely armckfus_dead.tdf) that has a [armckfus_dead] section which then specified something like <code>Object=armckfus_dead</code>.

armckfus_dead.3do Would then specify some texture like <code>wreck01b</code> which would go looking for either a wreck01b00.bmp or wreck01b00.tga file.

[http://fileuniverse.com/?p=showitem&ID=1421 Start with this version of MapConv]
or
[http://www.fileuniverse.com/?p=showitem&ID=1507 This one]
[I will clean this up and add more later --Mother]

==Making your map work==
This is the final push. Once Sharp map has finshed it will spit out a .sm2 file. This needs to be copyed to the MAPS folder in Spring. But you still need one more thing: an .smd file. Basically, this file tells the game things like the maximum metal, the light colours, the clouds, etc. (All the bits you were thinking that you hadn't done yet!)

I would suggest you copy the .smd of another map and fiddle with the settings until you get what you want. smd's can be opened in notepade or similar. Look at all the .smd's so you can get a jist of what each option does. Make sure both the .sm2 and .smd have the same file name then start up Spring (not the client!) in [http://taspring.clan-sy.com/wiki/FAQ#People_talk_about_.27Single_Player.27._How_do_I_start_a_single_player_game.3F single-player mode] and run the commanders script. Choose your map and away you go!

==SMD Rundown==
What follows is all that we (aGorm and LathanStanley) have figured out in the SMD's. Its by no means the be all and end all, but it's the next best thing.

* Goto [[Maps:SMD]] for a more detailed listing

===General Map Information===
* Description is just a short description of your map. Keep it simple.
* TidalStrength determines how much energy tidal generators will produce. A normal figure is around 20.
* Gravity, as you would expect, affects ballisitcs and how far units fly after an explosion.
* MaxMetal is the maximum amount of metal you will gain from one game square in 1 second from an area of metal that had a red value of 255 in your metal map. If making an old style metal deposit map, then this will be quite high: maybe 2 or 3. If you are making a new style metal-all-over-the-place-map, then it will be low: perhaps 0.2. Also for old style maps, you'll have to fiddle with the...
* ExtractorRadius, which is the area that is harvested by 1 metal extractor. For old style maps make this very small, so as they only take from one deposit.

===Atmosphere, Water Colours===
Each value (it would appear this bit is by no means gospel) is a representation of the RGB values for that parameter. It would appear to be relative, i.e. you can put in what ever numbers you like and the game will work out what you want. The best way to go about it is to look at it as percentages.
The numbers 1, 0.5, 0.2 refer to 100% red, 50% green and 20% blue. But 2, 1, 0.4, will get the same result. Using numbers below one for all the numbers will result in the colour being less bright.

This is all a bit confusing so an example will be given:

SkyColor=0.2 0.1 0.5;

In this example the sky is coloured with 20% red, 10% green, and 50% blue, approximatly RGB(51,25,127), resulting in a very deep night-time blue. Other colours are added to the initial sky colour. If you set your sun as being a pale yellow and it came out rather green, this is why.

One helpful tip is ''negative'' colour. That's right: you can type in a negative number for a colour and it will remove it from the base sky colour. Just be careful not to go below the original values or you may get a surprise.

===The Sun System/Shadow System===
The Sun System/Shadow System is quite a useful tool as well in making your maps look ''well done''.
Within the .smd file there is a line:

"SunDir=-1 1 -.5; //direction of sun" (The part of the "//" is a comment.)

The numbers "-1", "1", ".5" determine the angle and elevation of the sunlight system.

The first number is the X angle (East/West) (from -1 to 1) where any negative number means the sun is on the West (and therefore shadows will be cast east), and any positive number means the sun is on the East (and therefore shadows will be cast west), and if the number is 0 there are no east or west shadows, the sun is directly above you.

The second is its elevation, (0 to 1), this number is how far from the horizion the sun is, ignoring it's angle. Thus, 1 puts the sun directly overhead (while still casting angular shadows) and 0 putting it directly on the horizion.

The final number is the Z angle (North/South). (I know, I know, they wrote the engine with Y as elevation and Z as vertical. Don't blame me.) It is just like the East West positioning, where negative numbers put them on the North, and positive numbers put them on the South.

'''Example Usage:''' If you want the shadows ''in'' one of the boxes (your shadow casting surface is in the middle), use the numbers provided, or start from them and tweak the angle and sun height as seen fit.

N
----------------------------------------------
| ( 1 .5 -1) | ( 0 .5 -1) | (-1 .5 -1) |
----------------------------------------------
W | ( 1 .5 0) | ( 0 1 0) | (-1 .5 0) | E
----------------------------------------------
| ( 1 .5 1) | ( 0 .5 1) | (-1 .5 1) |
----------------------------------------------
S

'''Note:''' on the current build, it ''will'' cast the shadows in the proper direction, etc. Negative direction numbers tend to make some maps unstable and cause crashes. The best solution would be to rotate or flip your map to where the shadows point up or right (North or West). I do believe these bugs are being worked on and will be fixed soon.

We can only hope this has been helpful! Any questions, or things you think we have missed, please ask us in the maps section.

[[Category:Maps]]
[[Category:Development]]

Community news

2005-07-06T05:55:43Z

60.234.132.130: /* 2005-07-05 - Map Editing Guide Updated */

On this page, you can post news items that will be seen in the top right section of the frontpage. You can use this to post if you have created or found something of interest to the Spring community, such as a new map, a useful tool or perhaps a new useful page in the wiki. Details on how to update this page can be found [[Community_news_editing | here]].

----

===2005-07-05 - Map Editing Guide Updated===
You know you wanted to make that map? Well now you can! Check it out in the Wiki, or click on the link.
[[Create_maps]]

===2005-07-03 - New strategy guide===
A new strategy guide to help out new players has been added to the wiki.
Here's the link: [[Spring guide!]]

===2005-07-03 - Community news section===
A new site feature has been added, that allows users to contribute news that will be seen in this section.

This might be useful to expose new maps for example to those that don't visit the map forum regularly.. We'll see how it turns out.

FAQ

2005-06-10T07:13:14Z

60.234.132.130: /* Will TA Spring support campaigns? */

==General information==

===What is TA Spring?===
TA Spring is a project to create the best RTS ever (no joke). There are three principle goals which we hope to achieve.

. . . . . .A) Reach a stage where TA Spring can flawlessly execute most of Total Annihilation's original gameplay, with its original units in their original format.

. . . . . .B) Add new features as we see fit, fix bugs, and release new versions when we feel it is appropriate to do so.

. . . . . .C) Support the mod community as we see fit.

===When will TA Spring be ready?===
Now! You can get the latest beta from the download page.

===Will TA Spring be free?===
That's the current plan.

===I want to help, what can I do?===
Until we have finished our own map and unit formats, we are not looking for anything in particular.

===I want to donate.===
People have made clear their desire to donate to the project, and so far, we have been fairly reluctant about accepting donations. Our main concern? While we certainly hope to have something playable released in the near future, there is no guarantee that it will ever happen. Unforseen events arise, and it would be most unfortunate if everyone who donated felt swindled because the project did not turn out as they had hoped, or was not released at all.

We do not plan to be more or less productive solely based upon the quantity and frequency of donations received. The TA Spring project is here only because we view this as an enjoyable hobby.

===I read all that and I still want to donate.===
Very well then! You can find the required details [http://taspring.clan-sy.com/donate.php here]. It will be much appreciated. :)

==Technical==

===What APIs does TA Spring use?===
OpenGL for rendering.
DirectSound for sound.
Winsock for networking.

===What language is TA Spring written in?===
C and C++.

===Is TA Spring open source?===
Yes, it is. Go to the downloads section of the site to download the source code.

==Requirements==

===What platforms will TA Spring run on?===
At the moment, it only runs on Windows. If someone wants to port it to another platform, please contact us once we have an initial release ready. We will not, however, port it ourselves at any time (in the forseeable future). There is simply no compelling reason for us to do so. Additionally, we would like to focus on getting it working well on just one platform.

===What sort of a system will I need to run TA Spring?===
You will most certainly need a 3D graphics card to run TA Spring, which will probably require at least a GeForce3 (note that a GeForce4 MX is not better than a GeForce3). Minimum CPU requirements are a little more complex. A more powerful CPU will have the capability to support larger maps and a greater maximum unit limit. A 1ghz CPU should be able to support an estimated 500 units. The needed memory will also vary with unit count and mapsize, but 512mb should be enough.

==Content==

===Do TA Spring maps need a "ground"?===
TA Spring maps do require a ground. We have had many requests to have space maps, however, a "true" (ala Homeworld) space setting is not likely. It would have to wait until a much later stage. This does not mean that TA's style of "space" maps won't be possible, (see the Final Frontier TC for examples of this).

===You stated that TA Spring uses the TA unit format.===
TA Spring does use the Total Annihilation unit format. However, we do plan to make TA Spring compatible with a custom unit format of our own design.

===How powerful will TA Spring's custom format be?===
Total Annihilation's unit format was extremely limited. Most of these limitations will either be expanded or non-existent in TA Spring's custom unit format. One of the most exciting improvements is the introduction of an entirely new method of scripting, with nearly complete control over every aspect of a unit's actions and behaviors.

===Does TA Spring have a limited number of weapons?===
No. Unlike Total Annihilation, TA Spring's weapon IDs will be unlimited.

===Does TA Spring have a limited number of unique units?===
No. Unit IDs, like weapon IDs, will be unlimited.

===Will units have a maximum of 3 unique weapons?===
Total Annihilation had a limitation that permitted a maximum of 3 unique weapons per unit. This limit will exist in TA Spring only if a unit is made in the original Total Annihilation format. To bypass this limit, a unit would have to be created entirely within the limits of our own format.

===I'm curious as to the per-unit polygon limit.===
The engine itself does not have a polygon count limit. The limit is that of the processing power of today's computers. Since TA Spring requires a 3D card, the maximum polygon count per unit will be several times higher than Total Annihilation's. No real numbers yet though. We're gonna leave it up to the mod community to figure that one out.

===Will units be able to perform basic terraforming?===
Total Annihilation units probably won't have any terrain editable functionality. Feature units may be endowed with such functionality, but it's more of a gameplay issue and has not been decided upon yet.

===Will tunnel building be possible?===
Subterranean areas of any sort will be impossible.

===Will the ground's water retention be editable?===
No. Water will always collect when a piece of land has a height below sea level.

===Does TA Spring have a limit on the number of races?===
TA Spring has no limit on the total number of sides/races.

===What are the sizes of the biggest and smallest units?===
Static units (buildings, defenses, etc.) have no size limitations in the engine. Technically, neither do mobile units, but units with a footprint larger than 4x4 "squares" (an arbitrary size standard created by Cavedog) might have problems pathfinding.

===What is going to be the maximum possible sea depth?===
For all practical purposes, it will be unlimited. The depth values are stored as "float variables", so it is doubtful that maps would ever be made which even come close to approaching the limit.

===Will TA Spring support campaigns?===
No such support is planned at the moment but if someone wants to program it, go ahead.

===How big will the TA Spring files be?===
TA Spring will be as big as however much content is included with it. The "essential" files (engine files mostly) will only be several megabytes large. Content (such as maps and units) will add considerable size to the TA Spring download. However, it is not known at this point just how much "content" will be included with the first release.

===How will TA Spring render sound effects?===
Sound is rendered 3D, meaning that the volume and direction (assuming a multi-speaker setup) vary with the location of the camera from the sound "emitter". What this translates into gameplay terms means that the closer you are to a unit making a sound or motion, the louder the sound will be. Additionally, the sound will be heard differently depending on which way the camera is facing relative to units making sound.

===Will TA Spring have ambient sound?===
There is no ambient sound, and we haven't planned on adding it so far.

===Will there be an AI or a "skirmish" mode?===
We will create an interface that people can use to create there own skirmish AIs later.

===Will a "possess" or a FPS option be present?===
Yes, it is possible to fully control a unit from the first person view. It is more of a gimmick, but it still allows for a nice diversion once in a while.

==Playing==

===People talk about 'Single Player'. How do I start a single player game?===
You will have to go into your TA Spring folder and find the 'Spring.exe' file. Double click on it and say 'yes' to host.

===When I try to make a single player game, it gives me an error.===
Your graphics card probably can't support Spring. If you read the requirements it did say GeForce 3 or better. Go to the settings file in your TA Spring directory and lower some of the options. Sometimes that works.

===Does TA Spring support AI Players?===
Not yet. Fortunately for you they are currently working on it, :)

===When I try to connect to the lobby it gives me an error.===
There could be 2 problems. Either you don't have an account, or the server is down. If you don't have an account, make one. If the server is down, you'll just have to wait.

===Sometimes when I try to join games it gives me an error.===
The host is behind a firewall.

===When I make games nobody joins.===
You are probably behind a firewall

===When a multiplayer game starts I never make it past the loading screen.===
This indicates a problem with your video card. Once again the best way to deal with this situation is to make sure your video card has the latest updates and that all Spring video features are on the lowest settings.

===When a multiplayer game starts, I make it past the loading screen, but when I get into the game it says, "Waiting for Host", and does a 10 second countdown. It always reaches zero and boots me out, what gives?===
This is a firewall issue. There are three things you can do to fix this. First, make sure your windows firewall is either off, or is not blocking the TA: Spring application. Secondly, if you are behind a router, you can forward the ports that the host is using (especially if you are the host), and it usually fixes the problem. To do this you must go to your router configuration page. You can see what port 'you' are using (as the host), by hosting a multiplayer game in the Spring Lobby. You must make this your trigger port, and make sure that it is open for both TCP and UDP. Thirdly, if none of the aforementioned worked. The best thing to do (assuming you are behind a router) is to set the DMZ (Demilitarized Zone). All you have to do is find the personal IP if the computer you are using and add it to your router's DMZ list.
Good Luck

===Sometimes when I chat in the 'game lobby', people can't hear me.===
I would recommend closing and restarting the whole Spring application after each successful game. Weird things tend too happen. (By successful I mean all the players loaded and the game started.)

===I got into the game, but some people didn't.===
Then they probably are having firewall or video card difficulty. That is not your fault. Please ask them too leave if they are still there when you get into the 'game lobby'.

===What is with this weird right-click mode? I'm bout to break my keyboard.===
Sorry, you'll just have to get used to it. As of now it can't be changed.

===Why is somebody else also controlling my units?===
In the 'game lobby' there are two sets of teams. There are the 'Teams' and the 'Ally Teams'. If you are on the same 'Team', then you both get the same commander, and can control the same units. If you are on 'Ally Teams', then you both get different commanders and can't control each others units.

===Then why would I want to be on the same 'Team' as somebody?===
Because it's fun to just drive around units and not have to worry about commanding. (Assuming that one of the people on the team is commanding.)

===How do I talk to my allies only?===
You must type 'a:' before you speak. Here's an example: a: Now I am talking to my allies only.

===Help! After I'm finished driving a unit, the camera is all insane! This is nuts! How do I fix it?===
Whoa now. Calm down. Just press ctrl + mouse button 3 to change camera modes.

===After I'm finished driving a unit, where what used too be my mouse pointer is now a crosshair. Why?===
-This is a special 'view mode' that allows you to move around the screen much faster. It's good for viewing the battle or getting screenshots. Simply press on your third mouse button too revert back to your mouse pointer.

===But I don't have a third mouse button!===
The key 'J' works in the same way as the 'middle mouse button' does. So where you would use ctrl + middle mouse button to change camera modes, ctrl + j does the same thing. Pressing J once will also switch you from 'crosshair mode' to 'pointer mode' and vice versa.

===Sometimes my units just get deleted. Why?===
For some reason units get deleted when they go into the wrong places. Where are the wrong places? Nobody really knows. Just hope for the best.

===People are cheating! How do I stop it?!===
Well currently, you can't. The best thing to do is just not play with the cheaters anymore.

===Well how do you cheat?===
Well first you have to do three successful backflips while chanting I love my mommy. Then you lick your computer screen and say, "Please oh please give me lots of metal and energy."...

===How do I ally or unally in game?===
I'm pretty sure you can't. Yet.

===How do I give somebody units or metal or energy?===
Press 'H'.

===How do I continually give somebody metal and/or energy after a certain point (i.e. Original TA commands +setshare..., +shareall)?===
You'll notice that on your metal and energy bars (top of screen), there are two red bars. You have to put them wherever you want your metal and energy too be shared after.

===Man I am soooo sick of XTA. How do I play AA or OTA instead?===
Well. Somebody has made a patch to turn TA Spring into OTA. An AA patch has been released, and can be downloaded from fileuniverse. It will be out soon. But really, why would you want to go back to OTA?

===Why am I destroyed so easily by long range assaults?===
This is a realistic feature of TA Spring. Units will automatically attack 'radar blips' (units that they can not actually see, but that are indicated on radar). However, the accuracy is very bad while shooting at radar blips until 1)Your unit kills a lot of units and gets experience, or 2)You get a targetting facility.

===Can I kick people from my 'game lobby' or my game?===
First of all, you have to be the host to kick. In theory, you would right click on someone's name in the 'game lobby' and that would give you the option to kick them. This feature is not currently supported, however, but it will be fixed soon.

===When I'm 'driving' my commander, I can't use my laser?===
The TA: Spring team will most likely add a way for you to use your commander's laser soon.

===I hate driving around with the 'arrow keys'. Is there any way I can use the 'W-A-S-D' controls(the controls most First Person Shooters use anymore)?===
Go into your Spring directory and edit the uikeys file. Keep in mind that 'S' is originally a 'hot-key' that will stop your units and that 'D' is a 'hot-key' for your commander's D-Gun. You might want to change those too.

===I turned the shadows feature on; I still don't see shadows. What gives?===
Your graphics card canÃ‚Â´t handle shadows, so Spring automatically turns them off.

===I can't go backwards when I am 'driving' a unit. Why not?===
Because TA units where never intended to go backwards. Sorry.

===I'm in the Unreal Tournament 2004 kind of mood. How do I strafe?===
You can only strafe in 'brawler type' ships(The brawler, rapier, and light gunships.)

===Sometimes when I play with certain people I get HUGE sync errors that continue throughout the game.===
It's because they have a differen't mod installed than you. If, for example, you have not installed a mod, and somebody is in the game with you that has the OTA mod installed, it will cause the 'sync' error.

===How can I record and watch demos/replays ?===
The game is always recorded to test.sdf which is overwritten by each new game. Change the name if you want to save it. To view a demo start spring.exe as non server and enter the full demo name (coolgame.sdf for example) as server address. You must change the name to something else than test.sdf to view a demo.

FAQ

2005-06-10T06:50:55Z

60.234.132.130: /* When will TA Spring be ready? */

==General information==

===What is TA Spring?===
TA Spring is a project to create the best RTS ever (no joke). There are three principle goals which we hope to achieve.

. . . . . .A) Reach a stage where TA Spring can flawlessly execute most of Total Annihilation's original gameplay, with its original units in their original format.

. . . . . .B) Add new features as we see fit, fix bugs, and release new versions when we feel it is appropriate to do so.

. . . . . .C) Support the mod community as we see fit.

===When will TA Spring be ready?===
Now! You can get the latest beta from the download page.

===Will TA Spring be free?===
That's the current plan.

===I want to help, what can I do?===
Until we have finished our own map and unit formats, we are not looking for anything in particular.

===I want to donate.===
People have made clear their desire to donate to the project, and so far, we have been fairly reluctant about accepting donations. Our main concern? While we certainly hope to have something playable released in the near future, there is no guarantee that it will ever happen. Unforseen events arise, and it would be most unfortunate if everyone who donated felt swindled because the project did not turn out as they had hoped, or was not released at all.

We do not plan to be more or less productive solely based upon the quantity and frequency of donations received. The TA Spring project is here only because we view this as an enjoyable hobby.

===I read all that and I still want to donate.===
Very well then! You can find the required details [http://taspring.clan-sy.com/donate.php here]. It will be much appreciated. :)

==Technical==

===What APIs does TA Spring use?===
OpenGL for rendering.
DirectSound for sound.
Winsock for networking.

===What language is TA Spring written in?===
C and C++.

===Is TA Spring open source?===
Yes, it is. Go to the downloads section of the site to download the source code.

==Requirements==

===What platforms will TA Spring run on?===
At the moment, it only runs on Windows. If someone wants to port it to another platform, please contact us once we have an initial release ready. We will not, however, port it ourselves at any time (in the forseeable future). There is simply no compelling reason for us to do so. Additionally, we would like to focus on getting it working well on just one platform.

===What sort of a system will I need to run TA Spring?===
You will most certainly need a 3D graphics card to run TA Spring, which will probably require at least a GeForce3 (note that a GeForce4 MX is not better than a GeForce3). Minimum CPU requirements are a little more complex. A more powerful CPU will have the capability to support larger maps and a greater maximum unit limit. A 1ghz CPU should be able to support an estimated 500 units. The needed memory will also vary with unit count and mapsize, but 512mb should be enough.

==Content==

===Do TA Spring maps need a "ground"?===
TA Spring maps do require a ground. We have had many requests to have space maps, however, a "true" (ala Homeworld) space setting is not likely. It would have to wait until a much later stage. This does not mean that TA's style of "space" maps won't be possible, (see the Final Frontier TC for examples of this).

===You stated that TA Spring uses the TA unit format.===
TA Spring does use the Total Annihilation unit format. However, we do plan to make TA Spring compatible with a custom unit format of our own design.

===How powerful will TA Spring's custom format be?===
Total Annihilation's unit format was extremely limited. Most of these limitations will either be expanded or non-existent in TA Spring's custom unit format. One of the most exciting improvements is the introduction of an entirely new method of scripting, with nearly complete control over every aspect of a unit's actions and behaviors.

===Does TA Spring have a limited number of weapons?===
No. Unlike Total Annihilation, TA Spring's weapon IDs will be unlimited.

===Does TA Spring have a limited number of unique units?===
No. Unit IDs, like weapon IDs, will be unlimited.

===Will units have a maximum of 3 unique weapons?===
Total Annihilation had a limitation that permitted a maximum of 3 unique weapons per unit. This limit will exist in TA Spring only if a unit is made in the original Total Annihilation format. To bypass this limit, a unit would have to be created entirely within the limits of our own format.

===I'm curious as to the per-unit polygon limit.===
The engine itself does not have a polygon count limit. The limit is that of the processing power of today's computers. Since TA Spring requires a 3D card, the maximum polygon count per unit will be several times higher than Total Annihilation's. No real numbers yet though. We're gonna leave it up to the mod community to figure that one out.

===Will units be able to perform basic terraforming?===
Total Annihilation units probably won't have any terrain editable functionality. Feature units may be endowed with such functionality, but it's more of a gameplay issue and has not been decided upon yet.

===Will tunnel building be possible?===
Subterranean areas of any sort will be impossible.

===Will the ground's water retention be editable?===
No. Water will always collect when a piece of land has a height below sea level.

===Does TA Spring have a limit on the number of races?===
TA Spring has no limit on the total number of sides/races.

===What are the sizes of the biggest and smallest units?===
Static units (buildings, defenses, etc.) have no size limitations in the engine. Technically, neither do mobile units, but units with a footprint larger than 4x4 "squares" (an arbitrary size standard created by Cavedog) might have problems pathfinding.

===What is going to be the maximum possible sea depth?===
For all practical purposes, it will be unlimited. The depth values are stored as "float variables", so it is doubtful that maps would ever be made which even come close to approaching the limit.

===Will TA Spring support campaigns?===
No such support is planned at the moment but if someone want to program it, go ahead.

===How big will the TA Spring files be?===
TA Spring will be as big as however much content is included with it. The "essential" files (engine files mostly) will only be several megabytes large. Content (such as maps and units) will add considerable size to the TA Spring download. However, it is not known at this point just how much "content" will be included with the first release.

===How will TA Spring render sound effects?===
Sound is rendered 3D, meaning that the volume and direction (assuming a multi-speaker setup) vary with the location of the camera from the sound "emitter". What this translates into gameplay terms means that the closer you are to a unit making a sound or motion, the louder the sound will be. Additionally, the sound will be heard differently depending on which way the camera is facing relative to units making sound.

===Will TA Spring have ambient sound?===
There is no ambient sound, and we haven't planned on adding it so far.

===Will there be an AI or a "skirmish" mode?===
We will create an interface that people can use to create there own skirmish AIs later.

===Will a "possess" or a FPS option be present?===
Yes, it is possible to fully control a unit from the first person view. It is more of a gimmick, but it still allows for a nice diversion once in a while.

==Playing==

===People talk about 'Single Player'. How do I start a single player game?===
You will have to go into your TA Spring folder and find the 'Spring.exe' file. Double click on it and say 'yes' to host.

===When I try to make a single player game, it gives me an error.===
Your graphics card probably can't support Spring. If you read the requirements it did say GeForce 3 or better. Go to the settings file in your TA Spring directory and lower some of the options. Sometimes that works.

===Does TA Spring support AI Players?===
Not yet. Fortunately for you they are currently working on it, :)

===When I try to connect to the lobby it gives me an error.===
There could be 2 problems. Either you don't have an account, or the server is down. If you don't have an account, make one. If the server is down, you'll just have to wait.

===Sometimes when I try to join games it gives me an error.===
The host is behind a firewall.

===When I make games nobody joins.===
You are probably behind a firewall

===When a multiplayer game starts I never make it past the loading screen.===
This indicates a problem with your video card. Once again the best way to deal with this situation is to make sure your video card has the latest updates and that all Spring video features are on the lowest settings.

===When a multiplayer game starts, I make it past the loading screen, but when I get into the game it says, "Waiting for Host", and does a 10 second countdown. It always reaches zero and boots me out, what gives?===
This is a firewall issue. There are three things you can do to fix this. First, make sure your windows firewall is either off, or is not blocking the TA: Spring application. Secondly, if you are behind a router, you can forward the ports that the host is using (especially if you are the host), and it usually fixes the problem. To do this you must go to your router configuration page. You can see what port 'you' are using (as the host), by hosting a multiplayer game in the Spring Lobby. You must make this your trigger port, and make sure that it is open for both TCP and UDP. Thirdly, if none of the aforementioned worked. The best thing to do (assuming you are behind a router) is to set the DMZ (Demilitarized Zone). All you have to do is find the personal IP if the computer you are using and add it to your router's DMZ list.
Good Luck

===Sometimes when I chat in the 'game lobby', people can't hear me.===
I would recommend closing and restarting the whole Spring application after each successful game. Weird things tend too happen. (By successful I mean all the players loaded and the game started.)

===I got into the game, but some people didn't.===
Then they probably are having firewall or video card difficulty. That is not your fault. Please ask them too leave if they are still there when you get into the 'game lobby'.

===What is with this weird right-click mode? I'm bout to break my keyboard.===
Sorry, you'll just have to get used to it. As of now it can't be changed.

===Why is somebody else also controlling my units?===
In the 'game lobby' there are two sets of teams. There are the 'Teams' and the 'Ally Teams'. If you are on the same 'Team', then you both get the same commander, and can control the same units. If you are on 'Ally Teams', then you both get different commanders and can't control each others units.

===Then why would I want to be on the same 'Team' as somebody?===
Because it's fun to just drive around units and not have to worry about commanding. (Assuming that one of the people on the team is commanding.)

===How do I talk to my allies only?===
You must type 'a:' before you speak. Here's an example: a: Now I am talking to my allies only.

===Help! After I'm finished driving a unit, the camera is all insane! This is nuts! How do I fix it?===
Whoa now. Calm down. Just press ctrl + mouse button 3 to change camera modes.

===After I'm finished driving a unit, where what used too be my mouse pointer is now a crosshair. Why?===
-This is a special 'view mode' that allows you to move around the screen much faster. It's good for viewing the battle or getting screenshots. Simply press on your third mouse button too revert back to your mouse pointer.

===But I don't have a third mouse button!===
The key 'J' works in the same way as the 'middle mouse button' does. So where you would use ctrl + middle mouse button to change camera modes, ctrl + j does the same thing. Pressing J once will also switch you from 'crosshair mode' to 'pointer mode' and vice versa.

===Sometimes my units just get deleted. Why?===
For some reason units get deleted when they go into the wrong places. Where are the wrong places? Nobody really knows. Just hope for the best.

===People are cheating! How do I stop it?!===
Well currently, you can't. The best thing to do is just not play with the cheaters anymore.

===Well how do you cheat?===
Well first you have to do three successful backflips while chanting I love my mommy. Then you lick your computer screen and say, "Please oh please give me lots of metal and energy."...

===How do I ally or unally in game?===
I'm pretty sure you can't. Yet.

===How do I give somebody units or metal or energy?===
Press 'H'.

===How do I continually give somebody metal and/or energy after a certain point (i.e. Original TA commands +setshare..., +shareall)?===
You'll notice that on your metal and energy bars (top of screen), there are two red bars. You have to put them wherever you want your metal and energy too be shared after.

===Man I am soooo sick of XTA. How do I play AA or OTA instead?===
Well. Somebody has made a patch to turn TA Spring into OTA. An AA patch has been released, and can be downloaded from fileuniverse. It will be out soon. But really, why would you want to go back to OTA?

===Why am I destroyed so easily by long range assaults?===
This is a realistic feature of TA Spring. Units will automatically attack 'radar blips' (units that they can not actually see, but that are indicated on radar). However, the accuracy is very bad while shooting at radar blips until 1)Your unit kills a lot of units and gets experience, or 2)You get a targetting facility.

===Can I kick people from my 'game lobby' or my game?===
First of all, you have to be the host to kick. In theory, you would right click on someone's name in the 'game lobby' and that would give you the option to kick them. This feature is not currently supported, however, but it will be fixed soon.

===When I'm 'driving' my commander, I can't use my laser?===
The TA: Spring team will most likely add a way for you to use your commander's laser soon.

===I hate driving around with the 'arrow keys'. Is there any way I can use the 'W-A-S-D' controls(the controls most First Person Shooters use anymore)?===
Go into your Spring directory and edit the uikeys file. Keep in mind that 'S' is originally a 'hot-key' that will stop your units and that 'D' is a 'hot-key' for your commander's D-Gun. You might want to change those too.

===I turned the shadows feature on; I still don't see shadows. What gives?===
Your graphics card canÃ‚Â´t handle shadows, so Spring automatically turns them off.

===I can't go backwards when I am 'driving' a unit. Why not?===
Because TA units where never intended to go backwards. Sorry.

===I'm in the Unreal Tournament 2004 kind of mood. How do I strafe?===
You can only strafe in 'brawler type' ships(The brawler, rapier, and light gunships.)

===Sometimes when I play with certain people I get HUGE sync errors that continue throughout the game.===
It's because they have a differen't mod installed than you. If, for example, you have not installed a mod, and somebody is in the game with you that has the OTA mod installed, it will cause the 'sync' error.

===How can I record and watch demos/replays ?===
The game is always recorded to test.sdf which is overwritten by each new game. Change the name if you want to save it. To view a demo start spring.exe as non server and enter the full demo name (coolgame.sdf for example) as server address. You must change the name to something else than test.sdf to view a demo.

Spring:Community portal

2005-06-09T20:24:39Z

60.234.132.130:

Welcome.