UFO:AI - Recent changes [en]

Artwork

H-hour — Wed, 08 Sep 2010 08:26:26 GMT

← Older revision		Revision as of 08:26, 8 September 2010
Line 174:		Line 174:
	* [http://lounge.ego-farms.com/ Tutorials for digital content creators]		* [http://lounge.ego-farms.com/ Tutorials for digital content creators]
	* [http://opengameart.org Open Game Art]		* [http://opengameart.org Open Game Art]
		+	* [http://www.burningwell.org/gallery2/v/textures/ BurningWell] - Public domain images for textures

	[[Category:Contribute]]		[[Category:Contribute]]
	[[Category:Artwork]]		[[Category:Artwork]]

UFO-Scripts/seq *.ufo

Bayo — Tue, 07 Sep 2010 20:02:38 GMT

Example: +tool

← Older revision		Revision as of 20:02, 7 September 2010
(One intermediate revision not shown)
Line 1:		Line 1:
-	~~==General==~~	+	A sequence is a cinematic using the game engine to render 3D models, image, text, sounds, and music. It can be displayed in fullscreen, or as a part or the GUI.
-	~~The [[tutorials]] shown in~~ the main [[UFO-Scripts/ui/*.~~ufo\|UI]] are sequences. See [[TODO]]~~.	+

-	~~==Sequences==~~	+	With this type of UFO-script we can make your own sequences. Have a look at the '''base/ufos/seq_*.ufo''' for more examples.
-	With this type of UFO-script ~~you~~ can make your own sequences. Have a look at the '''base/ufos/seq_*.ufo''' for more examples.	+

-	==precache [~~models~~\|pics]==	+	==<code>precache [model\|pics]</code>==
	* .. for <code>models</code> as parameter: pathnames relative from {{path\|base}}-folder		* .. for <code>models</code> as parameter: pathnames relative from {{path\|base}}-folder
	* .. for <code>pics</code> as parameter: pathnames relative from {{path\|base/pics}}-folder		* .. for <code>pics</code> as parameter: pathnames relative from {{path\|base/pics}}-folder
Line 22:		Line 20:
	</pre>		</pre>

-	==camera NAME==	+	==<code>camera NAME</code>==
	* '''omega''': [[V_VECTOR]]		* '''omega''': [[V_VECTOR]]
	: moving		: moving
Line 44:		Line 42:
	</pre>		</pre>

-	==2dobj NAME==	+	==<code>2dobj NAME</code>==
	* '''text''': [[V_TRANSLATION_MANUAL_STRING]]		* '''text''': [[V_TRANSLATION_MANUAL_STRING]]
	: the translateable text		: the translateable text
Line 82:		Line 80:
	</pre>		</pre>

-	==model NAME==	+	==<code>model NAME</code>==
	* '''tag''': [[V_STRING]]		* '''tag''': [[V_STRING]]
	:		:
Line 118:		Line 116:
	</pre>		</pre>

-	~~==sound NAME==~~	+	==General commands==
-	~~NAME is a soundfile relative to the {{path\|sounds}} directory.~~	+
-		+
-	~~==music NAME==~~	+
-	~~NAME is a musicfile relative to the {{path\|music}} directory.~~	+
-		+
-	~~==cmd COMMAND==~~	+
-	~~COMMAND is any console command string~~	+
-		+
-	~~==click==~~	+
-	~~Will halt the sequence execution until the user clicked a mouse button~~	+
-		+
-	~~==rem ENTNAME==~~	+
-	~~Frees a sequence entity~~	+
-		+
-	==General==	+
	* '''wait''': [[V_FLOAT]]		* '''wait''': [[V_FLOAT]]
	: value of seconds to wait		: value of seconds to wait
	* '''cmd''': [[V_STRING]]		* '''cmd''': [[V_STRING]]
	: command to execute		: command to execute
-	* '''rem''': [[V_STRING]]	+	* '''rem''': see <code>delete</code>
		+	* '''delete''': [[V_STRING]]
	: remove a ressource - string is the NAME of the ressource to remove		: remove a ressource - string is the NAME of the ressource to remove
	* '''animspeed''': [[V_INT]]		* '''animspeed''': [[V_INT]]
	: set the speed used for animation of models. The default value is 1000 milliseconds. A smaller value will set a slower animation.		: set the speed used for animation of models. The default value is 1000 milliseconds. A smaller value will set a slower animation.
		+	* '''click'''
		+	:Will halt the sequence execution until the user clicked a mouse button
		+	* '''sound''' NAME
		+	:NAME is a soundfile relative to the {{path\|sounds}} directory.
		+	* '''music''' NAME
		+	:NAME is a musicfile relative to the {{path\|music}} directory.

	===Example===		===Example===
	<pre>		<pre>
	wait 0.2		wait 0.2
-	~~rem~~ herby_body	+	delete herby_body
-	~~rem~~ herby_head	+	delete herby_head
-	~~rem~~ herby_text	+	delete herby_text
	</pre>		</pre>

Line 200:		Line 190:
	wait 200.0		wait 200.0

-	~~rem~~ i_sentence1	+	delete i_sentence1
-	~~rem~~ i_sentence2	+	delete i_sentence2
-	~~rem~~ i_sentence3	+	delete i_sentence3
-	~~rem~~ i_sentence4	+	delete i_sentence4
-	~~rem~~ i_sentence5	+	delete i_sentence5
	}		}
	</pre>		</pre>

		+	==Tool==
		+	The command <code>seq_start</code> allow to display a random sequence in fullscreen.
		+
		+	Open the console and type:
		+	<pre>
		+	seq_start NAME_OF_THE_SEQUENCE
		+	</pre>

	[[Category:Contribute]]		[[Category:Contribute]]
	[[Category:UFO-Scripts]]		[[Category:UFO-Scripts]]

How to script UI

Bayo — Tue, 07 Sep 2010 14:40:35 GMT

String or number comparison?

← Older revision		Revision as of 14:40, 7 September 2010
(One intermediate revision not shown)
Line 77:		Line 77:
	</pre>		</pre>

-	==How to use ~~a confunc param~~ into a condition?==	+	==How to use params into condition?==
-	~~We can't~~ use <code><...></code> ~~into~~ a ~~condition, but~~ we ~~can~~ use a ~~cvar~~. ~~We just need to init~~ the ~~cvar before the condition~~.	+	ATM there is 2 way to use params. The first way is to use <code><...></code> with a number. <code><1></code> mean we use the first param of a function (<code>func</code>, <code>confunc</code>). It is deprecated, but it is the only way ATM to concatenate text with param (for example <code>"Welcome to my <1>"</code>).
		+
		+	The second way is to use reserved word <code>param1</code>... Then with an example:
		+
	<pre>		<pre>
-	*cvar:foo = <1>	+	if (param1 != 0) { ... }
-	if ( *cvar:foo != 0 ) { ... }	+	</pre>
-	~~delete *cvar:foo~~	+
		+	==String or number comparison?==
		+	We dont use the same operator for string and number (because it is more easy to compile it like that :-). Patch to remove that is anyway welcome.
		+
		+	If we want to compare the param with a string we must use <code>eq</code> or <code>ne</code>.
		+	<pre>
		+	if (param1 eq "foo") { ... }
		+	</pre>
		+
		+	If we want to compare the param with a number we must use <code>==</code>, <code>!=</code>, <code><=</code>, <code><</code>...
		+	<pre>
		+	if (param1 == 0) { ... }
	</pre>		</pre>

Tutorials

Bayo — Tue, 07 Sep 2010 14:26:56 GMT

rework the content

← Older revision		Revision as of 14:26, 7 September 2010
Line 1:		Line 1:
-	==~~About~~==	+	This page links tutorials.
-	~~The tutorials shown up in the main menu should give a short introduction to the game. These tutorials are~~ [[UFO-Scripts/seq_*.ufo\|~~sequences~~]] ([[~~UFO-Scripts~~]])	+
		+	==Tutorials==
		+	[[UFO-Scripts/seq_.ufo\|First step with sequence script]]
		+	*[[How to script UI\|Some tips with UI script]]

	==Needed tutorials==		==Needed tutorials==

UFO-Scripts/seq *.ufo

Bayo — Tue, 07 Sep 2010 14:21:05 GMT

General: fix link

← Older revision		Revision as of 14:21, 7 September 2010
(3 intermediate revisions not shown)
Line 1:		Line 1:
	==General==		==General==
-	The [[tutorials]] shown in the main [[UFO-Scripts/~~menu_~~*.ufo\|~~menu~~]] are sequences. See [[TODO]].	+	The [[tutorials]] shown in the main [[UFO-Scripts/ui/*.ufo\|UI]] are sequences. See [[TODO]].

	==Sequences==		==Sequences==
Line 140:		Line 140:
	* '''rem''': [[V_STRING]]		* '''rem''': [[V_STRING]]
	: remove a ressource - string is the NAME of the ressource to remove		: remove a ressource - string is the NAME of the ressource to remove
		+	* '''animspeed''': [[V_INT]]
		+	: set the speed used for animation of models. The default value is 1000 milliseconds. A smaller value will set a slower animation.

	===Example===		===Example===
Line 153:		Line 155:
	sequence intro		sequence intro
	{		{
-	~~cmd "snd_music~~ mission;"	+	music mission
-	~~cmd "seq_animspeed~~ 100;"	+	animspeed 100

	2dobj i_sentence1		2dobj i_sentence1

List of msgid/Aircraft Equipment

DarkRain — Mon, 06 Sep 2010 23:18:35 GMT

Aircraft Equipment:

← Older revision		Revision as of 23:18, 6 September 2010
Line 842:		Line 842:
	\|		\|
	* wiki: [[Equipamiento_para_Aeronaves/Armas/Cañón_Láser\|Cañón Láser]]		* wiki: [[Equipamiento_para_Aeronaves/Armas/Cañón_Láser\|Cañón Láser]]
-	* po: {{~~open~~}}	+	* po: {{done}}
	\|		\|
	* wiki: {{open}}		* wiki: {{open}}

Equipamiento para Aeronaves/Armas/Cañón Láser

DarkRain — Mon, 06 Sep 2010 23:17:05 GMT

Created page with '= Entrada de la OVNIpedia = == Propuesta == '''PARA:''' Comandante de la Base, PHALANX, Comando de Operaciones Atlánticas '''DE:''' Cte. Paul Navarre, I+D: División de Inge…'

New page

= Entrada de la OVNIpedia =

== Propuesta ==

'''PARA:''' Comandante de la Base, PHALANX, Comando de Operaciones Atlánticas

'''DE:''' Cte. Paul Navarre, I+D: División de Ingeniería, PHALANX, Comando de Operaciones Atlánticas

'''FECHA:''' %02i %s %i

'''ASUNTO:''' Propuesta: Cañón Láser

Esta es una de las varias propuestas que le estoy enviando para la investigación y desarrollo del nuevo armamento láser. Cada una de estas tendrá que ser desarrollada por separado debido a las diferencias de tamaño, niveles de potencia y complejidad de los sistemas involucrados.

El Cañón Láser es el más grande y potente de nuestros nuevos diseños de láseres. Tal como nuestras armas de infantería está basado en la reacción de fluoruro de deuterio, pero a una escala mucho mayor y amplificado por el propio sistema eléctrico de la aeronave. Estamos considerando varias ideas prometedoras.

No solo se trata del más grande, también podría ser el más difícil de crear. Cualquier canon para aeronaves tendrá que ser capaz de disparar a través de varios kilómetros de atmosfera – y la consecuente difusión atmosférica – y aún tener suficiente potencia para atravesar el fuselaje de un OVNI. Esos niveles de potencia se han logrado antes usando dispositivos masivos montados en aviones jumbo, pero nunca en dispositivos de un tamaño adecuado para montarse en cazas de combate.

El producto final deberá ser capaz de alcanzar OVNIs con una gran precisión a distancias mayores que el cañón SHIVA, y aunque el daño causado puede ser bajo, esperamos que la habilidad de mantener a las aeronaves enemigas bajo fuego y presión continuos será muy útil en el futuro.

Por favor apruebe el tiempo de laboratorio y el presupuesto cuando esté listo, Comandante.

--Cte. Navarre

== Resultado ==

'''PARA:''' Comandante de la Base, PHALANX, Comando de Operaciones Atlánticas

'''DE:''' Cte. Paul Navarre, I+D: División de Ingeniería, PHALANX, Comando de Operaciones Atlánticas

'''FECHA:''' %02i %s %i

'''ASUNTO:''' Re: Cañón Láser

Comandante, he completado mi reporte sobre nuestro más reciente programa láser. Hemos completado exitosamente el prototipo del Cañón Láser y estamos listos para iniciar su producción.

Hemos logrado lo que nos propusimos: crear un láser de onda continua, basado en la reacción de fluoruro de deuterio con una potencia de varios mega wat, capaz de rastrear y alcanzar OVNIs a una distancia de hasta 5km. La precisión es excelente, estorbada solo por las CME (Contra-Medidas Electrónicas) del enemigo, y a diferencia de todas nuestras otras armas no le afecta la distancia. El láser viaja en línea recta y atraviesa la distancia entre el arma y el objetivo de forma casi instantánea. Es difícil fallar con el.

Desafortunadamente la difusión atmosférica aún es un problema, y el láser pierde potencia rápidamente conforme aumenta la distancia hasta el objetivo. A su máximo alcance, 5 kilómetros, toma 32 segundos de fuego continuo en el mismo punto para atravesar el casco de un OVNI. Raramente tendremos tanto tiempo para esperar. La distancia ideal para esta arma está entre los 2 y los 3 kilómetros donde alcanza un buen balance entre daño y distancia. El daño promedio por Segundo es un poco menor que el del Cañón Giratorio SHIVA, pero el alcance es mayor por cerca de 1.5 kilómetros. Aún más que nuestras anteriores armas, el Cañón Láser es ideal para conducir y suprimir al enemigo con una andanada de disparos.

El canon cuenta con un cartucho de fluoruro de deuterio integrado el cual le permite disparar hasta por treinta minutes continuos. Ya que el fluoruro de deuterio es muy peligroso para almacenarlo en la base, y tenemos acceso a grandes reservas de los componentes necesarios en almacenes externos, no necesitaremos mantener municiones para el cañón láser en nuestros almacenes.

El uso de esta arma se deja a su discreción, Comandante, pero me gustaría recomendarle que remplace los cañones SHIVA de nuestras aeronaves por cañones láser excepto en aquellas aeronaves especialmente equipadas para combate cerrado. Cualquier cosa que sea menos maniobrable que un OVNI tendrá problemas para mantener el objetivo bajo fuego con cañones SHIVA, así que el láser ofrece una mejor solución con casi la misma capacidad de municiones.

--Cdr. Navarre

==Links==

= Research Tree Data =

'''(This information for reference only; do not translate or include in-game.)'''

''Prerequisites:''
[[Research/Continuous_Wave_Laser_Operation|Continuous Wave Laser Operation]]

''Opens:''
Enables production -- Aerial Laser Cannon

[[Category:General]]
[[Category:Aircraft]]

User:RolandPur

RolandPur — Mon, 06 Sep 2010 18:06:43 GMT

New user account

New page

Correo/Cabeceras

DarkRain — Mon, 06 Sep 2010 16:44:17 GMT

← Older revision		Revision as of 16:44, 6 September 2010
Line 1:		Line 1:
-	[mail_to_base_commander] Comandante de la Base, PHALANX, ~~Centro~~ de Operaciones del Atlántico	+	[mail_to_base_commander] Comandante de la Base, PHALANX, Comando de Operaciones del Atlántico

-	[mail_from_paul_navarre] Cte. Paul Navarre, I+D: División de Ingeniería, PHALANX, ~~Centro~~ de Operaciones del Atlántico	+	[mail_from_paul_navarre] Cte. Paul Navarre, I+D: División de Ingeniería, PHALANX, Comando de Operaciones del Atlántico

-	[mail_from_col_falkland] Col. Ingrid Falkland, División de Inteligencia, PHALANX, ~~Centro~~ de Operaciones del Atlántico	+	[mail_from_col_falkland] Col. Ingrid Falkland, División de Inteligencia, PHALANX, Comando de Operaciones del Atlántico

-	[mail_from_dr_connor] Dr. Connor, I+D: División Biología y Contención, PHALANX, ~~Centro~~ de Operaciones del Atlántico	+	[mail_from_dr_connor] Dr. Connor, I+D: División Biología y Contención, PHALANX, Comando de Operaciones del Atlántico

-	[mail_from_air_cdr] Cte. (Aire) Subakh al-Kuhar, Fuerza Aérea, PHALANX, ~~Centro~~ de Operaciones del Atlántico	+	[mail_from_air_cdr] Cte. (Aire) Subakh al-Kuhar, Fuerza Aérea, PHALANX, Comando de Operaciones del Atlántico

-	[mail_from_xo] Of. Ejec. Abel S. Howard, Comando y Control, PHALANX, ~~Centro~~ de Operaciones del Atlántico	+	[mail_from_xo] Of. Ejec. Abel S. Howard, Comando y Control, PHALANX, Comando de Operaciones del Atlántico

-	[mail_from_surgeon] Cirujano Capitán Helen Floydd, División Médica, PHALANX, ~~Centro~~ de Operaciones del Atlántico	+	[mail_from_surgeon] Cirujano Capitán Helen Floydd, División Médica, PHALANX, Comando de Operaciones del Atlántico

	[mail_from_un] Sec. Gen. Mahouf Serra, Naciones Unidas, Ciudad de Nueva York		[mail_from_un] Sec. Gen. Mahouf Serra, Naciones Unidas, Ciudad de Nueva York

	[[Category:Translating]]		[[Category:Translating]]

Campañas/Campaña Normal

DarkRain — Mon, 06 Sep 2010 16:36:24 GMT

← Older revision		Revision as of 16:36, 6 September 2010
Line 1:		Line 1:
	== Descripción de las Campañas ==		== Descripción de las Campañas ==
		+

	'''[txt_standard_campaign]'''		'''[txt_standard_campaign]'''
Line 6:		Line 7:

	Esta campaña está disponible en varios niveles de dificultad. Esta opción representa el nivel de dificultad Normal, y es la recomendada para los jugadores novatos que busquen un desafío.		Esta campaña está disponible en varios niveles de dificultad. Esta opción representa el nivel de dificultad Normal, y es la recomendada para los jugadores novatos que busquen un desafío.
		+

	'''[txt_hard_campaign]'''		'''[txt_hard_campaign]'''
Line 12:		Line 14:

	Esta opción representa el nivel Difícil, y es la recomendada para los jugadores expertos.		Esta opción representa el nivel Difícil, y es la recomendada para los jugadores expertos.
		+

	'''[txt_veryhard_campaign]'''		'''[txt_veryhard_campaign]'''
Line 18:		Line 21:

	Esta opción representa el nivel Muy Difícil, y es la recomendada para aquellos que han conseguido terminar la campaña Difícil y todavía sienten la necesidad de castigarse a sí mismos.		Esta opción representa el nivel Muy Difícil, y es la recomendada para aquellos que han conseguido terminar la campaña Difícil y todavía sienten la necesidad de castigarse a sí mismos.
		+

	'''[txt_easy_campaign]'''		'''[txt_easy_campaign]'''
Line 24:		Line 28:

	Esta campaña representa el nivel Fácil, y es la opción para los jugadores novatos que prefieren una partida más tranquila que la ofrecida por la Campaña Normal.		Esta campaña representa el nivel Fácil, y es la opción para los jugadores novatos que prefieren una partida más tranquila que la ofrecida por la Campaña Normal.
		+

	'''[txt_veryeasy_campaign]'''		'''[txt_veryeasy_campaign]'''
Line 30:		Line 35:

	Esta campaña representa el nivel Muy Fácil, y es la opción para los jugadores novatos que simplemente quieran saber en qué consiste UFO:AI.		Esta campaña representa el nivel Muy Fácil, y es la opción para los jugadores novatos que simplemente quieran saber en qué consiste UFO:AI.
		+

	[[Category:Translating]]		[[Category:Translating]]
	[[Category:Campaigns]]		[[Category:Campaigns]]

Category:UFO:AI Team

H-hour — Mon, 06 Sep 2010 15:40:38 GMT

Links: Fixed link to list of contributors

← Older revision		Revision as of 15:40, 6 September 2010
Line 6:		Line 6:
	* [http://www.ohloh.net/p/3949/analyses/latest Ohloh.net]		* [http://www.ohloh.net/p/3949/analyses/latest Ohloh.net]

-	There is also a [[~~Contribute~~\|list of contributors]].	+	There is also a [[Contributors\|list of contributors]].
	[[Category:Root]]		[[Category:Root]]

Modelling/Tags

Mattn — Mon, 06 Sep 2010 12:18:47 GMT

← Older revision		Revision as of 12:18, 6 September 2010
(One intermediate revision not shown)
Line 1:		Line 1:
-	We are using ''tags'' for [[Modelling/Character_Animation\|character models]] to tell the engine where to place the head and the weapons.	+	We are using ''tags'' for [[Modelling/Character_Animation\|character models]] to tell the engine where to place the head and the weapons and where the floor for the model is. Besides characters our weapons can have a tag assigned to determine the position of the muzzle particle.

-	These tags will be a ~~seperate~~ file besides the exported [[md2]] file with the ~~fileending~~ ''*.tag''.	+	These tags will be a separate file besides the exported [[md2]] file with the file ending ''*.tag''.

-	List of tags we need:	+	List of tags we need for characters:
	* tag_floor (only for internal usage - for calculating the other tags positions)		* tag_floor (only for internal usage - for calculating the other tags positions)
	* tag_head		* tag_head
	* tag_rweapon		* tag_rweapon
	* tag_lweapon		* tag_lweapon
		+
		+	List of tags we need for weapons:
		+	* tag_muzzle

	We have exporters for the following model softwares:		We have exporters for the following model softwares:

List of msgid/Aircraft Equipment

DarkRain — Sun, 05 Sep 2010 23:53:40 GMT

Aircraft Equipment:

← Older revision		Revision as of 23:53, 5 September 2010
Line 789:		Line 789:
	\|		\|
	* wiki: [[Equipamiento_para_Aeronaves/Blindaje/Recubrimiento_Alienígena_para_Aeronaves\|Recubrimiento Alienígena para Aeronaves]]		* wiki: [[Equipamiento_para_Aeronaves/Blindaje/Recubrimiento_Alienígena_para_Aeronaves\|Recubrimiento Alienígena para Aeronaves]]
-	* po: {{~~open~~}}	+	* po: {{done}}
	\|		\|
	* wiki: {{open}}		* wiki: {{open}}

Equipamiento para Aeronaves/Blindaje/Recubrimiento Alienígena para Aeronaves

DarkRain — Sun, 05 Sep 2010 23:52:41 GMT

Created page with '= Entrada de la OVNIpedia = == Propuesta == '''PARA:''' Comandante de la Base, PHALANX, Comando de Operaciones Atlánticas '''DE:''' Cte. Paul Navarre, I+D: División Ingeni…'

New page

= Entrada de la OVNIpedia =

== Propuesta ==

'''PARA:''' Comandante de la Base, PHALANX, Comando de Operaciones Atlánticas

'''DE:''' Cte. Paul Navarre, I+D: División Ingeniería, PHALANX, Comando de Operaciones Atlánticas

'''FECHA:''' %02i %s %i

'''ASUNTO:''' Propuesta: Recubrimiento Alienígena para Aeronaves

Comandante, ahora que tenemos la capacidad para producir y trabajar con los materiales alienígenas, tenemos una gran cantidad de nuevas opciones disponibles. Estos materiales son tan fuertes y flexibles que pueden utilizarse para casi cualquier cosa. Sin embargo, su aplicación más prometedora, es en el diseño de aeronaves -- especialmente el blindaje.

Hemos tenido serias dificultades para derribar a los OVNIs debido a la extrema resistencia de su recubrimiento exterior de materiales alienígenas. Desafortunadamente no podemos simplemente aplicar el mismo recubrimiento a nuestras aeronaves ya que los materiales alienígenas son demasiado pesados. Nuestras aeronaves tendrían dificultades tan solo para despegar. Sin embargo, eso no necesariamente debe detenernos.

Comandante, si nos permite realizar una investigación, creo que podemos encontrar algún patrón de blindaje que – aunque puede reducir la velocidad y aumentar el consumo de combustible un poco – debería darle a nuestras aeronaves una mayor probabilidad de supervivencia contra las armas alienígenas durante las intercepciones. De acuerdo con nuestros cálculos, las aeronaves equipadas con este tipo de blindaje podrían resistir varios impactos del arma de flujo de partículas y ser capaces de continuar el combate.

Es una posibilidad muy prometedora, Comandante, y definitivamente merece ser investigada.

--Cte. Navarre

== Resultado ==

'''PARA:''' Comandante de la Base, PHALANX, Comando de Operaciones Atlánticas

'''DE:''' Cte. Paul Navarre, I+D: División Ingeniería, PHALANX, Comando de Operaciones Atlánticas

'''FECHA:''' %02i %s %i

'''ASUNTO:''' Propuesta: Recubrimiento Alienígena para Aeronaves

Comandante, tenemos buenas noticias. Mi equipo y yo hemos completado el prototipo de nuestro proyecto de recubrimiento alienígena para aeronaves. Nuestro Nuevo blindaje está listo para entrar en producción.

Este ha sido un proyecto difícil desde el principio. Hemos tenido grandes dificultades para diseñar un equipo capaz de forjar los materiales alienígenas con la forma deseada, y “programar” los materiales para que cambien de forma en el momento y modo que deseemos. Al final logramos superar esos obstáculos, pero hemos tenido que lidiar con las limitaciones naturales del material.

La principal desventaja de los materiales alienígenas es su peso. Son significativamente más pesados que los materiales de que están hechas las aeronaves humanas modernas, y cualquier cosa que fabriquemos a partir de ellos sufrirá por el peso extra. La única forma en que los alienígenas logran mantener a sus OVNIs en el aire sin alas es la enorme potencia de sus propulsores. La velocidad, la maniobrabilidad, el consumo de combustible, y el máximo alcance operacional – todos se verán afectados negativamente al poner materiales alienígenas en la aeronave.

Sin embargo, no tenemos otra opción que hacer este sacrificio. Incluso un recubrimiento muy delgado de materiales alienígenas ofrece un considerable aumento en la protección, siendo capaz de soportar impactos que destruirían a nuestro Blindaje de Polímero para Aeronaves. Durante las pruebas de nuestro Nuevo blindaje, uno de nuestros propios misiles "Sparrowhawk" – los cuales pueden derribar a la mayoría de las aeronaves construidas en la Tierra con un solo impacto – fue incapaz de infligir un daño significativo en la aeronave de prueba. No es una broma. Hemos recolectado media hora de grabaciones en video que prueban lo que acabo de decir.

EL Nuevo recubrimiento que hemos diseñado toma ventaja de estas características y demuestra la enorme resistencia de los materiales alienígenas. El blindaje puede resistir impactos del Arma de Flujo de Partículas a corta distancia sin ser destruido. Por primera vez, nuestras aeronaves serán capaces de soportar grandes cantidades de daño y permanecer en el aire tal como lo hacen los alienígenas. Aún no estamos a su mismo nivel, pero nos estamos acercando.

Puede que solo sea factible utilizar este blindaje en aeronaves equipadas con propulsión alienígena o motores mejorados de alguna manera, debido al aumento de peso y la reducción de la velocidad y el alcance. Aun así, si ese llega a ser el caso, el nuevo recubrimiento sera esencial para mantener a nuestra flota aérea actual en posición de combatir la creciente amenaza alienígena. Usted y yo sabemos el costo de una aeronave nueva, Comandante – no podemos permitir que ninguna de nuestras aeronaves se vuelva obsoleta.

--Cte. Navarre

==Links==

= Research Tree Data =

'''(This information for reference only; do not translate or include in-game.)'''

''Prerequisites:''
[[Research/Alien Materials|Alien Materials]]

''Opens:''
Enables production -- Alien Aircraft Plating

[[Category:General]]
[[Category:Armour]]

User:Tron

Mattn — Sun, 05 Sep 2010 17:54:38 GMT

Created page with 'Category:UFO:AI Team'

New page

[[Category:UFO:AI Team]]

Getting the source

Tron — Sun, 05 Sep 2010 14:42:57 GMT

Getting the source:

← Older revision		Revision as of 14:42, 5 September 2010
Line 15:		Line 15:
	The repository includes data_source, all branches and all tags. It's often enough to only check out the master branch - which is the current state of development.		The repository includes data_source, all branches and all tags. It's often enough to only check out the master branch - which is the current state of development.

-	~~====Also getting data_source====~~
-	~~Not everyone might be interested in the data_source data, so by default it's skipped for a clone. To also download data_source just type:~~
-	~~git config --add remote.origin.fetch '+refs/other/:refs/remotes/origin/'~~
-
-	~~====Getting the whole repository====~~
	Check out the repository with:		Check out the repository with:
	git clone git://ufoai.git.sourceforge.net/gitroot/ufoai/ufoai		git clone git://ufoai.git.sourceforge.net/gitroot/ufoai/ufoai
	to download the source. This is a read-only checkout until now. To get the repository with write support, type:		to download the source. This is a read-only checkout until now. To get the repository with write support, type:
	git remote set-url --push origin ssh://USER@ufoai.git.sourceforge.net/gitroot/ufoai/ufoai		git remote set-url --push origin ssh://USER@ufoai.git.sourceforge.net/gitroot/ufoai/ufoai
		+
		+	====Also getting data_source====
		+	Not everyone might be interested in the data_source data, so by default it's skipped for a clone. To also download data_source just type:
		+	git config --add remote.origin.fetch '+refs/other/:refs/remotes/origin/'
		+	Run git fetch afterwards to get the branch.

	====Config====		====Config====

Getting the source

Mattn — Sun, 05 Sep 2010 14:15:57 GMT

Getting a specific branch:

← Older revision		Revision as of 14:15, 5 September 2010
(One intermediate revision not shown)
Line 15:		Line 15:
	The repository includes data_source, all branches and all tags. It's often enough to only check out the master branch - which is the current state of development.		The repository includes data_source, all branches and all tags. It's often enough to only check out the master branch - which is the current state of development.

-	====~~Getting a specific branch~~====	+	====Also getting data_source====
-	~~git init ufoai~~	+	Not everyone might be interested in the data_source data, so by default it's skipped for a clone. To also download data_source just type:
-	~~cd ufoai~~	+
-	~~git remote add -t master origin git://ufoai~~.~~git.sourceforge.net/gitroot/ufoai/ufoai~~	+
-	~~git fetch~~	+
-	~~git checkout -t origin/master~~	+
-		+
-	to also download data_source	+
	git config --add remote.origin.fetch '+refs/other/:refs/remotes/origin/'		git config --add remote.origin.fetch '+refs/other/:refs/remotes/origin/'

Line 28:		Line 22:
	Check out the repository with:		Check out the repository with:
	git clone git://ufoai.git.sourceforge.net/gitroot/ufoai/ufoai		git clone git://ufoai.git.sourceforge.net/gitroot/ufoai/ufoai
-	to download the source. This is a read-only checkout. To get the repository with write support, type:	+	to download the source. This is a read-only checkout until now. To get the repository with write support, type:
-	git ~~clone~~ ssh://USER~~@ufoai.git.sourceforge.net/gitroot/ufoai/ufoai (write access)~~	+	git remote set-url --push origin ssh://USER@ufoai.git.sourceforge.net/gitroot/ufoai/ufoai
-	~~both commands will create a directory named {{path\|ufoai}}.~~	+
-		+
-	~~=====Speed up fetches for write access checkouts=====~~	+
-	To speed up fetches you can change the fetch url to the git:// schema and only keep the ssh style url for the pushes. To do this, you have to edit the file in your ufoai checkout at ufoai/.git/config. There is already a line with the url, you should remove that line and the following two (of course replace your username)	+
-	~~url = git://ufoai.git.sourceforge.net/gitroot/ufoai/ufoai~~	+
-	~~pushurl = ssh://USERNAME~~@ufoai.git.sourceforge.net/gitroot/ufoai/ufoai	+

	====Config====		====Config====

User:Tron

Tron — Sun, 05 Sep 2010 14:12:04 GMT

New user account

New page

TODO/General

H-hour — Sun, 05 Sep 2010 09:23:47 GMT

artwork typo ;)

← Older revision		Revision as of 09:23, 5 September 2010
Line 7:		Line 7:
	==Artwork==		==Artwork==

-	===2D ~~artworks~~===	+	===2D artwork===
	* {{open}} We must find GPL'd replacements for a long list of textures. [http://ufoai.ninex.info/forum/index.php?topic=5301.0 See forum which tracks the changes].		* {{open}} We must find GPL'd replacements for a long list of textures. [http://ufoai.ninex.info/forum/index.php?topic=5301.0 See forum which tracks the changes].
	* {{open}} Alternate skins for existing civilians, scientists, pilots, etc.		* {{open}} Alternate skins for existing civilians, scientists, pilots, etc.

Getting the source

Bayo — Sat, 04 Sep 2010 22:39:00 GMT

Getting git: typo

← Older revision		Revision as of 22:39, 4 September 2010
Line 1:		Line 1:
	==Source==		==Source==
-	===Getting ~~git~~===	+	===Getting Git===
	====Windows====		====Windows====
	Install [http://code.google.com/p/msysgit/ msysGit] and [http://code.google.com/p/tortoisegit/ TortoiseGIT].		Install [http://code.google.com/p/msysgit/ msysGit] and [http://code.google.com/p/tortoisegit/ TortoiseGIT].

-	Use the msys batch file in the msysGit directory to get the mingw shell and execute all the commands below (if you are not using TortoiseGit and would like to deal with ~~git~~ on the commandline)	+	Use the msys batch file in the msysGit directory to get the mingw shell and execute all the commands below (if you are not using TortoiseGit and would like to deal with Git on the commandline)

	====Mac OS X====		====Mac OS X====

File:Feed-icon.png

Bayo — Sat, 04 Sep 2010 22:38:03 GMT

deleted "[[File:Feed-icon.png]]"

New page

TODO/General

Bayo — Sat, 04 Sep 2010 14:47:10 GMT

Equipment menu and team handling: typo

← Older revision		Revision as of 14:47, 4 September 2010
(2 intermediate revisions not shown)
Line 7:		Line 7:
	==Artwork==		==Artwork==

-	===~~2d Artwork~~===	+	===2D artworks===
	* {{open}} We must find GPL'd replacements for a long list of textures. [http://ufoai.ninex.info/forum/index.php?topic=5301.0 See forum which tracks the changes].		* {{open}} We must find GPL'd replacements for a long list of textures. [http://ufoai.ninex.info/forum/index.php?topic=5301.0 See forum which tracks the changes].
	* {{open}} Alternate skins for existing civilians, scientists, pilots, etc.		* {{open}} Alternate skins for existing civilians, scientists, pilots, etc.
	* {{open}} We need normalmaps, specular maps, glow maps, etc. for a lot of our existing artwork. See [[Artwork]] for more details and use the forums to coordinate work.		* {{open}} We need normalmaps, specular maps, glow maps, etc. for a lot of our existing artwork. See [[Artwork]] for more details and use the forums to coordinate work.

-	===~~3d Models~~ (other than maps)===	+	===3D models (other than maps)===
	* {{open}} We need models for the geoscape indicating specific mission types:		* {{open}} We need models for the geoscape indicating specific mission types:
	** {{open}} Story-related mission		** {{open}} Story-related mission
Line 37:		Line 37:
	* {{open}} New map themes and more tiles for [http://ufoai.ninex.info/wiki/index.php/Mapping/List_of_Maps existing themes]. [http://ufoai.ninex.info/wiki/index.php/Mapping/Suggestions See suggestions].		* {{open}} New map themes and more tiles for [http://ufoai.ninex.info/wiki/index.php/Mapping/List_of_Maps existing themes]. [http://ufoai.ninex.info/wiki/index.php/Mapping/Suggestions See suggestions].

-	==Equipment ~~menu~~ and team handling==	+	==Equipment interface and team handling==
	* {{open}} equip screen before mission start, after map load, which will allow to adjust soldiers' equipment after reading mission briefing		* {{open}} equip screen before mission start, after map load, which will allow to adjust soldiers' equipment after reading mission briefing
	** {{done}} Allow spawning actors after the map was loaded		** {{done}} Allow spawning actors after the map was loaded

Getting the source

Mattn — Sat, 04 Sep 2010 13:31:22 GMT

← Older revision		Revision as of 13:31, 4 September 2010
Line 31:		Line 31:
	git clone ssh://USER@ufoai.git.sourceforge.net/gitroot/ufoai/ufoai (write access)		git clone ssh://USER@ufoai.git.sourceforge.net/gitroot/ufoai/ufoai (write access)
	both commands will create a directory named {{path\|ufoai}}.		both commands will create a directory named {{path\|ufoai}}.
		+
		+	=====Speed up fetches for write access checkouts=====
		+	To speed up fetches you can change the fetch url to the git:// schema and only keep the ssh style url for the pushes. To do this, you have to edit the file in your ufoai checkout at ufoai/.git/config. There is already a line with the url, you should remove that line and the following two (of course replace your username)
		+	url = git://ufoai.git.sourceforge.net/gitroot/ufoai/ufoai
		+	pushurl = ssh://USERNAME@ufoai.git.sourceforge.net/gitroot/ufoai/ufoai

	====Config====		====Config====

TODO/2.4

Bayo — Sat, 04 Sep 2010 13:24:09 GMT

Leftovers from TODO/2.3: +TODO/2.3

← Older revision		Revision as of 13:24, 4 September 2010
Line 1:		Line 1:
	== Leftovers from TODO/2.3 ==		== Leftovers from TODO/2.3 ==
		+	* See [[TODO/2.3]]
		+
	== Code ==		== Code ==
	=== Ufopedia & Research ===		=== Ufopedia & Research ===

TODO/2.4

H-hour — Sat, 04 Sep 2010 13:22:27 GMT

← Older revision		Revision as of 13:22, 4 September 2010
Line 27:		Line 27:
	===Maps===		===Maps===
	* {{wip}} Alien base map. [http://ufoai.ninex.info/forum/index.php?topic=4979.0 See forum for development].		* {{wip}} Alien base map. [http://ufoai.ninex.info/forum/index.php?topic=4979.0 See forum for development].
-
-	~~==Models & Particles==~~
-	* {{open}} Models and textures for every missing projectile on geoscape
-	** {{open}} Change current SHIVA ammo models on geoscape to particles
-	~~==Maps==~~
-	* {{wip}} [[TODO/Alien_Base_Map\|alien base]]

	[[Category:Contribute]]		[[Category:Contribute]]

TODO/General

H-hour — Sat, 04 Sep 2010 11:38:03 GMT

2d Artwork:

← Older revision		Revision as of 11:38, 4 September 2010
Line 10:		Line 10:
	* {{open}} We must find GPL'd replacements for a long list of textures. [http://ufoai.ninex.info/forum/index.php?topic=5301.0 See forum which tracks the changes].		* {{open}} We must find GPL'd replacements for a long list of textures. [http://ufoai.ninex.info/forum/index.php?topic=5301.0 See forum which tracks the changes].
	* {{open}} Alternate skins for existing civilians, scientists, pilots, etc.		* {{open}} Alternate skins for existing civilians, scientists, pilots, etc.
		+	* {{open}} We need normalmaps, specular maps, glow maps, etc. for a lot of our existing artwork. See [[Artwork]] for more details and use the forums to coordinate work.

	===3d Models (other than maps)===		===3d Models (other than maps)===

TODO/2.4

H-hour — Sat, 04 Sep 2010 11:25:36 GMT

← Older revision		Revision as of 11:25, 4 September 2010
Line 12:		Line 12:
	** Taking a second approach to [[TODO/2.3/CharacterGeneration\|CharacterGeneration]]--26, February 2008		** Taking a second approach to [[TODO/2.3/CharacterGeneration\|CharacterGeneration]]--26, February 2008
	* {{open}} leak in socket handling (at least for the dedicated server)		* {{open}} leak in socket handling (at least for the dedicated server)
		+
		+	==Artwork==
		+
		+	===2d Artwork===
		+	* Images for research topics:
		+	** {{open}} Bloodspider autopsy. See [[Aliens/Bloodspider]], {{svn\|data_source/images/techs/bloodspider_dead.xcf.bz2\|Gimp-source for dead bloodspider}}, and [http://ufoai.ninex.info/forum/index.php?topic=2890.msg36452#msg36452 submitted PNG on forums with no source/license].
		+	** {{open}} Orbital UFO Activity
		+	** {{open}} Alien Infiltration
		+	** {{open}} Alien Body Armour & Alien Medium Armour (see /base/pics/armour for usable images of armour)
		+
		+	===3d Artwork (other than maps)===
		+	* {{open}} Crash models for two remaining interceptors: Stiletto and stingray
		+
		+	===Maps===
		+	* {{wip}} Alien base map. [http://ufoai.ninex.info/forum/index.php?topic=4979.0 See forum for development].

	==Models & Particles==		==Models & Particles==
Line 18:		Line 33:
	==Maps==		==Maps==
	* {{wip}} [[TODO/Alien_Base_Map\|alien base]]		* {{wip}} [[TODO/Alien_Base_Map\|alien base]]
-	~~==Artwork==~~
-	* Images for alien autopsies
-	** {{open}} [[Aliens/Bloodspider]] {{svn\|data_source/images/techs/bloodspider_dead.xcf.bz2\|Gimp-source}} (dead bloodspider, autopsy is still missing)
-	* Images for some research topics
-	** {{open}} Orbital UFO Activity
-	** {{open}} Alien Infiltration
-	** {{open}} Alien Body Armour & Alien Medium Armour (Should be render shots from the character models - see {{svn\|trunk/base/pics/armour\|existing images}} as reference)

	[[Category:Contribute]]		[[Category:Contribute]]

TODO/General

H-hour — Sat, 04 Sep 2010 11:19:39 GMT

Show changes

Download

Bayo — Sat, 04 Sep 2010 09:37:14 GMT

Development (last): latest

← Older revision		Revision as of 09:37, 4 September 2010
(2 intermediate revisions not shown)
Line 20:		Line 20:
	\|}		\|}

-	==Development (~~trunk~~)==	+	==Development (latest)==
-	Version 2.4-dev is the work in process version. It is considered unstable. It is only officially available through ~~SVN~~.	+	Version 2.4-dev is the work in process version. It is considered unstable. It is only officially available through Git.
	{\| class="ufotable" width="100%"		{\| class="ufotable" width="100%"
	! width="10%" \| [[File:Source icon.svg\|40px\|alt=Source code\|Source\|link=]]		! width="10%" \| [[File:Source icon.svg\|40px\|alt=Source code\|Source\|link=]]
-	\| <pre>~~svn co https~~://ufoai.~~svn~~.sourceforge.net/~~svnroot~~/ufoai/ufoai/~~trunk ufoai~~</pre>	+	\| <pre>
-	See [[Coding#Compiling_the_source\|compiling ~~the source~~]].	+	git init ufoai
		+	cd ufoai
		+	git remote add -t master origin git://ufoai.git.sourceforge.net/gitroot/ufoai/ufoai
		+	git fetch
		+	git checkout -t origin/master
		+	</pre>
		+	See how to [[getting the source\|get the source]] and [[Coding#Compiling_the_source\|compiling]].
	\|}		\|}
	The community provides binaries, though these binaries are often quickly outdated.		The community provides binaries, though these binaries are often quickly outdated.

Getting the source

Mattn — Fri, 03 Sep 2010 21:06:22 GMT

Subsequent uses of the command:

← Older revision		Revision as of 21:06, 3 September 2010
(4 intermediate revisions not shown)
Line 33:		Line 33:

	====Config====		====Config====
-	For ~~none~~ global options you have to {{command\|cd}} into your git checkout directory first.	+	For non-global options you have to {{command\|cd}} into your git checkout directory first.
	git config --global user.name "Your Name"		git config --global user.name "Your Name"
	git config --global user.email mail@example.com		git config --global user.email mail@example.com
	git config --global alias.upbase "rebase '@{u}'"		git config --global alias.upbase "rebase '@{u}'"
		+	git config --global push.default tracking
	git config --global core.excludesfile '~/.gitignore'		git config --global core.excludesfile '~/.gitignore'
	echo "*~" >> ~/.gitignore		echo "*~" >> ~/.gitignore
-
-	~~git config push.default tracking~~

	====Creating a patch====		====Creating a patch====
Line 60:		Line 59:
	git fetch		git fetch
	will update your copy of the source and		will update your copy of the source and
-	git ~~rebase~~	+	git upbase
	will merge your changes in. If there are conflicts you have to resolve them and call		will merge your changes in. If there are conflicts you have to resolve them and call
	git add FILE		git add FILE
Line 72:		Line 71:
	git push		git push
	pushes your commits to the global git repository.		pushes your commits to the global git repository.
		+	git checkout .
		+	reverts your local/uncommited changes.
		+	git reset --hard HEAD~
		+	completely reverts the last commit in your local repository to the predecessor of HEAD (branch, index and working copy)

	====Getting help====		====Getting help====
Line 142:		Line 145:
	==Links==		==Links==
	* [http://git.or.cz/course/svn.html For SVN users]		* [http://git.or.cz/course/svn.html For SVN users]
		+	* [http://progit.org/book/ Git Book]

	[[Category:Contribute]]		[[Category:Contribute]]
	[[Category:Coding]]		[[Category:Coding]]
	[[Category:Development]]		[[Category:Development]]

User:Jennifer987

Jennifer987 — Fri, 03 Sep 2010 12:21:52 GMT

New user account

New page

Talk:Coding/Guidelines

Bayo — Fri, 03 Sep 2010 11:21:01 GMT

about "int a"

← Older revision		Revision as of 11:21, 3 September 2010
Line 1:		Line 1:
-	==~~Doxygen~~==	+	==Struct==
-	~~Hello~~. ~~We can see~~ this ~~line in the page~~.	+	typedef struct menuNode_s {
		+	int blah; /*< This is a documentation comment. /
		+	int a; /* armour / /< Calling this 'a' then putting a comment immediately after is just dumb. Don't do it; use meaningful names /
		+	int blahBlah; /*< The total number of blahs. /
		+	} menuNode_t;

-	* @param[in~~] distance) <What distance) is~~.>	+	Can we avoid thing like '''int a''' in structs. The code looks often hard to understand. Here we can use ''armour''. I especially thing about the inventory code. [[User:Bayo\|Bayo]] 11:21, 3 September 2010 (UTC)
-		+
-	~~This ")" look strange here, no ?~~ [[User:Bayo\|Bayo]] 12:57, 15 September ~~2008~~ (UTC)	+

Coding/Guidelines

Mattn — Fri, 03 Sep 2010 10:16:14 GMT

← Older revision		Revision as of 10:16, 3 September 2010
Line 221:		Line 221:

	<pre>		<pre>
-	* ~~This~~ commit ~~fixed a really nasty bug~~.	+	* The first line summarises the effect of the commit. After this follows an empty line.

	* Details are written here. The above line is just the commit summary. And such		* Details are written here. The above line is just the commit summary. And such
	a comment may also be on more than one line if the text is too long. But each subtopic		a comment may also be on more than one line if the text is too long. But each subtopic
	should start with a * in front of it.		should start with a * in front of it.
-	* The newline between the summary and the details is needed.	+	* The newline between the summary and the details is needed.
	* Details are optional.		* Details are optional.
	</pre>		</pre>

Compile for Mac

Mattn — Fri, 03 Sep 2010 10:12:57 GMT

← Older revision		Revision as of 10:12, 3 September 2010
Line 4:		Line 4:
	==None universal binaries==		==None universal binaries==

-	Step 1. Install macports.	+	===Step 1. Install macports===

	Instructions are at http://guide.macports.org/#installing		Instructions are at http://guide.macports.org/#installing
	This will have you install Apple's X11 (not sure why it is needed), the xcode development environment (needed for the compiler, etc), and the macports program.		This will have you install Apple's X11 (not sure why it is needed), the xcode development environment (needed for the compiler, etc), and the macports program.

-	Step 2: Install SDL	+	===Step 2: Install SDL===

	As of june 2010, SDL in macports is broken on PPC. It always defines the byteorder as x86 (backwards).		As of june 2010, SDL in macports is broken on PPC. It always defines the byteorder as x86 (backwards).
Line 15:		Line 15:
	To fix this:		To fix this:

-	1. sudo port configure libsdl +universal	+	sudo port configure libsdl +universal

-	2. Edit the SDL_config.h in both the ppc and i386 directory. Delete the lines for BYTEORDER -- this will cause the other headers to check the actual cpu type and set it correctly.	+	Edit the SDL_config.h in both the ppc and i386 directory. Delete the lines for BYTEORDER -- this will cause the other headers to check the actual cpu type and set it correctly.

	Underneath /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/libsdl		Underneath /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/libsdl
		+	sudo port install libsdl-framework
		+	sudo port install libsdl_mixer-framework libsdl_ttf-framework libsdl_image-framework

-	3. sudo port install ~~libsdl~~-~~framework +universal~~	+	===Step 3: Install other libs and tools===
		+	sudo port install libtheora XviD git-core p7zip

-	~~4. sudo port install libsdl_mixer-framework +universal libsdl_ttf-framework +universal libsdl_image-framework +universal~~	+	Now you should be able to [[Getting the source\|fetch UFO-AI]] and compile it.
-		+
-	~~5. (Are these still needed by the code with no intro movie?)~~	+
-		+
-	~~sudo port install libtheora +universal XviD +universal~~	+
-		+
-	Now you should be able to fetch ~~Ufo~~-~~Ai with svn co, configure, make,~~ and ~~make maps~~.	+
-		+
-	~~6. To make a .dmg, you'll need this last one~~	+
-		+
-	~~sudo port install p7zip~~	+

	==Universal binaries==		==Universal binaries==