Development:System Backgrounds - Revision history

Tbeholder at 13:58, 22 February 2014

2014-02-22T13:58:20Z

Nikai: sp, update

2010-07-11T08:27:54Z

sp, update

pyramid: /* Space Backgrounds */

2008-06-12T07:30:35Z

‎Space Backgrounds

pyramid: /* Development Needs and Tasks */

2008-04-12T22:49:21Z

‎Development Needs and Tasks

pyramid: /* Texture Requirements */

2008-04-09T09:02:22Z

‎Texture Requirements

pyramid: /* See Also */

2008-03-13T13:16:30Z

‎See Also

pyramid: /* Software, Tools, Tutorials */

2008-03-13T13:03:24Z

‎Software, Tools, Tutorials

pyramid: /* Texture Requirements */

2008-02-21T11:26:15Z

‎Texture Requirements

pyramid: /* The Process */

2008-02-06T14:39:41Z

‎The Process

pyramid: /* References */

2008-02-02T00:41:17Z

‎References

← Older revision		Revision as of 13:58, 22 February 2014
Line 232:		Line 232:
	==See Also==		==See Also==
	*[http://www.debevec.org/HDRShop/tutorial/tutorial4.html Panoramic Image Conversion with HDR Shop]		*[http://www.debevec.org/HDRShop/tutorial/tutorial4.html Panoramic Image Conversion with HDR Shop]
		+	*[http://gallery.artofgregmartin.com/tuts_arts/making_a_star_field.html "Make a Realistic Star Field" tutorial by Greg Martin]

@@ Line 65: / Line 65: @@
 ===Data Compression Requirements===
-Space backgrounds are non-transparent, hence DXT1 compression will suffice. Assuming a very large distance to viewer the compressed textures do not require mipmaps. This can be achieved with nVidia texture tools unsing the command:
+Space backgrounds are non-transparent, hence DXT1 compression will suffice. Assuming a very large distance to viewer the compressed textures do not require mipmaps. This can be achieved with nVidia texture tools using the command:
 * <code> ''nvcompress -bc1 -nomips background_original.png background_data.bmp'' </code>
@@ Line 84: / Line 84: @@
 ==Including and Testing==
-First of all, copy your six texture files to the <code>data4.x/textures/backgrounds</code> directory.
+First of all, copy your six texture files to the <code>data/textures/backgrounds</code> directory.
 The easiest way to test your new background is by trying it out in the test system.
@@ Line 95: / Line 95: @@
 <code>''./vegastrike test/planets.mission''</code>
-Once you are happy with your texture, choose a system that you want to put it in. To generally (for all systems that are using it) replace e.g. the old "blue2" background you can search in data4.x directory using the command
+Once you are happy with your texture, choose a system that you want to put it in. To generally (for all systems that are using it) replace e.g. the old "blue2" background you can search in <code>data</code> directory using the command
 <code>''grep -R "blue2.png" sectors/*''</code>
@@ Line 165: / Line 165: @@
 As of September 2007, svn has two directories for texture data:
 * \masters\textures that holds the original textures and also source files that were used to create the textures (if you are willing to share them so that larger resolutions may be produced in the future if required)
-* \data4.x\textures that holds the textures used in game.
+* \data\textures that holds the textures used in game.
 =Tutorials=

← Older revision		Revision as of 07:30, 12 June 2008
Line 25:		Line 25:

	Creating space background from original images (e.g. Hubble) is not recommended. What you usually would do in such a case, is to map an original image (if you choose use real universe imaginary, though I would recommend to make sure that the original image is not copyrighted) to the inner side of a sphere and then rotate a 90º angle camera four times around one axis (faces 1-4) plus another two times (faces 5-6). This means that at current minimum resolution of 1024x1024, in order to get the same quality without enabling texture interpolation, you would require an original image with at least 4096 pixels (1024 x 4 (one-axis rotations) and truly ridiculous 32768px for 8192px faces. Here we have two good reasons not to use original images as the basis for our space background (copyright and high original resolution). It is rather essential to create your individual space background to use in Vega Strike. Resolution should be no issue with any 3d rendering programs.		Creating space background from original images (e.g. Hubble) is not recommended. What you usually would do in such a case, is to map an original image (if you choose use real universe imaginary, though I would recommend to make sure that the original image is not copyrighted) to the inner side of a sphere and then rotate a 90º angle camera four times around one axis (faces 1-4) plus another two times (faces 5-6). This means that at current minimum resolution of 1024x1024, in order to get the same quality without enabling texture interpolation, you would require an original image with at least 4096 pixels (1024 x 4 (one-axis rotations) and truly ridiculous 32768px for 8192px faces. Here we have two good reasons not to use original images as the basis for our space background (copyright and high original resolution). It is rather essential to create your individual space background to use in Vega Strike. Resolution should be no issue with any 3d rendering programs.
		+
		+	Each system uses 6 cube faces each with maximum 1024x1024 resolution. You can go up to whatever your card memory will take, I guess maybe around 8192x8192 if there are not too many ship types in the system with a 256MB VRAM card. However high resolutions might utilize the VRAM too much in the presence of many different textures in the same system (ship types, planets, rings, suns, stations) so we have opted for maximum resolution of 1024x1024 for now.
		+
		+	With a 1024x1024 textures and a standard FOV of 37.5 degrees we are viewing about 427 pixels on the screen ( = 4102437.5/360). With a monitor resolution of 1280 this corresponds to one background pixel being stretched to 3 screen pixels ( ~1280/427 ). To get a clean image we would need at least a background face resolution of 3*1024x = 3072x, which not being POT would make it 4096x (2^12) and end up in 64MB VRAM usage per system background (shock!) while the 1024x1024 resolution makes it only 4MB.
		+
		+	We are currently encoding backgrounds with DXT1 which has a very high compression ratio (8:1 without alpha channel) and the banding is more prominent. It is a known behavior with smooth hue gradients and DDS compression.

	==Texture Requirements==		==Texture Requirements==

@@ Line 16: / Line 16: @@
 Proposed development roadmap:
-*Phase 1 [50%]: Replace existing textures with at least 1024x1024 textures (release quality)
+*Phase 1 [58%]: Replace existing textures with at least 1024x1024 textures (release quality)
 *Phase 2 [ 0%]: Expand the set of textures to include more variety per system
 *Phase 3 [ 0%]: Develop cinematographic quality backgrounds

@@ Line 56: / Line 56: @@
 * RQ - Release Quality: textures with horizontal resolution of 1024 or above and medium degree of artistic quality
 * CQ - Cinematographic Quality: textures with horizontal resolution of 2048 or above and high degree of artistic quality
 ==Creating and Naming==

← Older revision		Revision as of 13:16, 13 March 2008
Line 223:		Line 223:


−	~~=====~~Author: [[User:pyramid\|pyramid]]~~=====~~	+	'''Author: [[User:pyramid\|pyramid]]'''

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

@@ Line 214: / Line 214: @@
 =References=
-==Software, Tools, Tutorials==
+==Software, Tools==
 *[http://www.debevec.org/HDRShop/tutorial/tutorial4.html Panoramic Image Conversion with HDR Shop]

← Older revision		Revision as of 11:26, 21 February 2008
Line 28:		Line 28:
	==Texture Requirements==		==Texture Requirements==

		+	===Generic Image Requirements===
		+
		+	Please read this [[Development:Graphics_Requirements]] page before continuing to the specific requirements.
		+
		+	===Specific Image Requirements===
	We require six images that make the six sides of the imaginary box: back, front, right, left, top, and bottom.		We require six images that make the six sides of the imaginary box: back, front, right, left, top, and bottom.

@@ Line 121: / Line 121: @@
 ** which texture(s) you'd like to replace
 ** display your candidates
-** briefly describe briefly the method of creation and tools used
+** briefly describe the method of creation and tools used
 ** If you'd like to replace more than one texture, describe how you would assign the favorites of the poll to the individual textures

← Older revision		Revision as of 00:41, 2 February 2008
Line 215:		Line 215:

	=====Author: [[User:pyramid\|pyramid]]=====		=====Author: [[User:pyramid\|pyramid]]=====
		+
		+	[[Category:Development]]