Unreal Wiki - User contributions [en]

User:Solarsys

2014-08-08T17:20:38Z

Solarsys: Blanked the page

User:Solarsys

2014-08-08T17:20:29Z

Solarsys: /* My Maps */

User:Solarsys

2014-08-08T17:20:21Z

Solarsys: /* UT3 Converter */

UE1:LevelInfo (UT)

2010-07-11T07:37:55Z

Solarsys: /* VisibleGroups */

{{infobox class
| package = Engine
| parent1 = ZoneInfo
| parent2 = Info
| parent3 = Actor
| parent4 = Object
}}
{{autogenerated}}
LevelInfo contains information about the current level. There should
be one per level and it should be actor 0. UnrealEd creates each level's
LevelInfo automatically so you should never have to place one
manually.

The ZoneInfo properties in the LevelInfo are used to define
the properties of all zones which don't themselves have ZoneInfo.

==Properties==
===Property group 'Audio'===
====CdTrack====
'''Type:''' [[byte]]

'''[[Variables#Modifiers|Modifiers]]:''' const

Default CD track for level.

'''Default value:''' 255

====PlayerDoppler====
'''Type:''' [[float]]



====Song====
'''Type:''' {{cl|Music}}

'''[[Variables#Modifiers|Modifiers]]:''' const

Default song for level.

====SongSection====
'''Type:''' [[byte]]

'''[[Variables#Modifiers|Modifiers]]:''' const

Default song order for level.

===Property group 'LevelInfo'===
====Author====
'''Type:''' [[string]]

Who built it.

====bCheckWalkSurfaces====
'''Type:''' [[bool]]



====bHumansOnly====
'''Type:''' [[bool]]

Only allow "human" player pawns in this level

====bLonePlayer====
'''Type:''' [[bool]]

No multiplayer coordination, i.e. for entranceways.

====bNeverPrecache====
'''Type:''' [[bool]]



====Brightness====
'''Type:''' [[float]]



'''Default value:''' 1.0

====DefaultGameType====
'''Type:''' [[class]]<{{cl|GameInfo}}>



====IdealPlayerCount====
'''Type:''' [[string]]

'''[[Variables#Modifiers|Modifiers]]:''' localized

Ideal number of players for this level. I.E.: 6-8

====LevelEnterText====
'''Type:''' [[string]]

'''[[Variables#Modifiers|Modifiers]]:''' localized

Message to tell players when they enter.

====LocalizedPkg====
'''Type:''' [[string]]

Package to look in for localizations.

====RecommendedEnemies====
'''Type:''' [[int]]

number of enemy bots recommended (used by rated games)

====RecommendedTeammates====
'''Type:''' [[int]]

number of friendly bots recommended (used by rated games)

====Screenshot====
'''Type:''' {{cl|Texture}}



====TimeDilation====
'''Type:''' [[float]]



'''Default value:''' 1.0

====Title====
'''Type:''' [[string]]

'''[[Variables#Modifiers|Modifiers]]:''' localized



'''Default value:''' "Untitled"

===Internal variables===
====AIProfile====
'''Type:''' [[int]]

'''[[Static arrays|Array size]]:''' 8

TEMP statistics

====AvgAITime====
'''Type:''' [[float]]



====bAggressiveLOD====
'''Type:''' [[bool]]

frame rate is well below DesiredFrameRate, so make LOD more aggressive

====bAllowFOV====
'''Type:''' [[bool]]



====bBegunPlay====
'''Type:''' [[bool]]

Whether gameplay has begun.

====bDropDetail====
'''Type:''' [[bool]]

frame rate is below DesiredFrameRate, so drop high detail actors

====bHighDetailMode====
'''Type:''' [[bool]]

Client high-detail mode.

'''Default value:''' True

====bLowRes====
'''Type:''' [[bool]]

'''[[Variables#Modifiers|Modifiers]]:''' config



====bNextItems====
'''Type:''' [[bool]]



====bNoCheating====
'''Type:''' [[bool]]



====bPlayersOnly====
'''Type:''' [[bool]]

Only update players.

====bStartup====
'''Type:''' [[bool]]

Starting gameplay.

====ComputerName====
'''Type:''' [[string]]

Machine's name according to the OS.

====Day====
'''Type:''' [[int]]

'''[[Variables#Modifiers|Modifiers]]:''' transient

Day of month.

====DayOfWeek====
'''Type:''' [[int]]

'''[[Variables#Modifiers|Modifiers]]:''' transient

Day of week.

====DefaultTexture====
'''Type:''' {{cl|Texture}}



'''Default value:''' {{cl|Texture}}'Engine.DefaultTexture'

====EngineVersion====
'''Type:''' [[string]]

Engine version.

====Game====
'''Type:''' {{cl|GameInfo}}



====Hour====
'''Type:''' [[int]]

'''[[Variables#Modifiers|Modifiers]]:''' transient

Hour.

====HubStackLevel====
'''Type:''' [[int]]



====LevelAction====
'''Type:''' {{tl|ELevelAction}}

'''[[Variables#Modifiers|Modifiers]]:''' transient



====Millisecond====
'''Type:''' [[int]]

'''[[Variables#Modifiers|Modifiers]]:''' transient



====MinNetVersion====
'''Type:''' [[string]]



====Minute====
'''Type:''' [[int]]

'''[[Variables#Modifiers|Modifiers]]:''' transient

Minute.

====Month====
'''Type:''' [[int]]

'''[[Variables#Modifiers|Modifiers]]:''' transient

Month.

====NavigationPointList====
'''Type:''' {{cl|NavigationPoint}}

'''[[Variables#Modifiers|Modifiers]]:''' const



====NetMode====
'''Type:''' {{tl|ENetMode}}



====NextSwitchCountdown====
'''Type:''' [[float]]



====NextURL====
'''Type:''' [[string]]



====Pauser====
'''Type:''' [[string]]

If paused, name of person pausing the game.

====PawnList====
'''Type:''' {{cl|Pawn}}

'''[[Variables#Modifiers|Modifiers]]:''' const



====Second====
'''Type:''' [[int]]

'''[[Variables#Modifiers|Modifiers]]:''' transient

Second.

====SpawnNotify====
'''Type:''' {{cl|SpawnNotify}}



====Summary====
'''Type:''' {{cl|LevelSummary}}



====TimeSeconds====
'''Type:''' [[float]]

Time in seconds since level began play.

====VisibleGroups====
'''Type:''' [[string]]

Set which actors with this groupname will be displayed in UnrealEd. If set to "", no actors will be visible within UnrealEd.

'''Default value:''' "None"

====Year====
'''Type:''' [[int]]

'''[[Variables#Modifiers|Modifiers]]:''' transient

Year.

===Default values===
{| class="list defaults"
! Property
! Value
|-
| {{tl|bHiddenEd||Actor properties}}
| True
|}

==Enums==
====ELevelAction====

; LEVACT_None : 
; LEVACT_Loading : 
; LEVACT_Saving : 
; LEVACT_Connecting : 
; LEVACT_Precaching : 

====ENetMode====

; NM_Standalone : Standalone game.
; NM_DedicatedServer : Dedicated server, no local client.
; NM_ListenServer : Listen server.
; NM_Client : Client only, no local server.

==Functions==
===Native functions===
====GetAddressURL====
{{code|native simulated function [[string]] '''GetAddressURL''' ()}}



====GetLocalURL====
{{code|native simulated function [[string]] '''GetLocalURL''' ()}}



===Events===
====ServerTravel====
{{code|event '''ServerTravel''' ([[string]] '''URL''', [[bool]] '''bItems''')}}

Legacy:T3D StaticMesh

2009-10-19T07:24:48Z

Solarsys: ucc cmd fix

T3D Staticmeshes files are generated with the UCC command in order to export all StaticMeshes data from package or level.
It creates one .t3d file for each unique staticmesh found in the package.
They are exported using this command: 
<uscript>ucc batchexport myPackage StaticMesh T3D</uscript>

Sample File: Some basic triangle in Unreal Editor

[[File:T3DSM_TriangleUED.png]]

<uscript>
Begin StaticMesh Name=TriOriginal
Version=2.000000 BoundingBox.Min.X=-128.000000 BoundingBox.Min.Y=-128.000000 BoundingBox.Min.Z=0.000000 BoundingBox.Max.X=128.000000 BoundingBox.Max.Y=128.000000 BoundingBox.Max.Z=0.000000 //Unknown effect
Begin Triangle
Texture SMTest.Tex.256x256 //Texture applied to the triangle
SmoothingMask 0 //Unknown effect
Vertex 0 128.000000 128.000000 0.000000 1.000000 0.000000 //Vertex Coordinates (x,y,z)+ Texture U,V data
Vertex 1 -128.000000 -128.000000 0.000000 0.000000 -1.000000
Vertex 2 -128.000000 128.000000 0.000000 0.000000 0.000000
End Triangle
End StaticMesh
</uscript>

The vertices are ordered differently from the last one to the first one if we compare with T3D brush.

T3D Brush Drawing: 
[[File:T3DSM_BrushDraw.png]] 
T3D Brush data: 
<uscript> Vertex -00128.000000,+00128.000000,+00000.000000
Vertex -00128.000000,-00128.000000,+00000.000000
Vertex +00128.000000,+00128.000000,+00000.000000</uscript>

T3D StaticMesh Drawing: 
[[File:T3DSM_Draw.png]]

== Converting T3D StaticMeshes to ASE file ==
These T3D files can be used and converted as ASE (3D Ascii Scene) files in order to convert staticmeshes to UT3 as the UT3 editor
allows to import .ase files.

Here is the algorithm to use (.ase file data):
<uscript>
*3DSMAX_ASCIIEXPORT 200
*MATERIAL_LIST {
*MATERIAL_COUNT 1 //Always 1
*MATERIAL 0 {
*MATERIAL_NAME "Default Material"
*MATERIAL_CLASS "Multi/Sub-Object"
*MATERIAL_AMBIENT 1.0000 1.0000 1.0000
*MATERIAL_DIFFUSE 1.0000 1.0000 1.0000
*MATERIAL_SPECULAR 1.0000 1.0000 1.0000
*NUMSUBMTLS 1 //Num of unique different textures used in the staticmesh
*SUBMATERIAL 0 {
*MATERIAL_NAME "256x256" //Name of the texture used (without group and package info)
*MATERIAL_AMBIENT 1 1 1
*MATERIAL_DIFFUSE 1 1 1
*MATERIAL_SPECULAR 1 1 1
*MAP_DIFFUSE {
*MAP_NAME "Map #0"
*MAP_CLASS "Bitmap"
*MAP_SUBNO 1
*MAP_AMOUNT 1
*BITMAP "256x256" //Name of the texture used (without group and package info)
*MAP_TYPE Screen
*UVW_U_OFFSET 0.000000
*UVW_V_OFFSET 0.000000
*UVW_U_TILING 1.000000
*UVW_V_TILING 1.000000
*UVW_ANGLE 0.000000
*UVW_BLUR 1.000000
*UVW_BLUR_OFFSET 0.000000
*UVW_NOUSE_AMT 1.000000
*UVW_NOISE_SIZE 1.000000
*UVW_NOISE_LEVEL 1
*UVW_NOISE_PHASE 0.000000
*BITMAP_FILTER Pyramidal
}
}
}
}
*GEOMOBJECT {
*MESH {
*TIMEVALUE 0
*MESH_NUMVERTEX 3 //Num of vertices in the staticmesh
*MESH_NUMFACES 1 //Num of triangle in the staticmesh (normally equals to NUMVERTEX/NUMTRIANGLES)
*MESH_VERTEX_LIST {
*MESH_VERTEX 0 128.0 -128.0 0.0 //V1x(Triangle) -V1y V1z (axis Y direction in unreal editor is from top to bottom)
*MESH_VERTEX 1 -128.0 128.0 0.0 //V2x(Triangle) -V2y V2z
*MESH_VERTEX 2 -128.0 -128.0 0.0 //V3x(Triangle) -V3y V3z
}
*MESH_FACE_LIST {
*MESH_FACE 0: A: 0 B: 1 C: 2 AB: 1 BC: 0 CA: 1 *MESH_SMOOTHING 1 *MESH_MTLID 0 (=material id given in SUBMATERIAL section)
//*MESH_FACE 1: A: 1 B: 2 C: 3 AB: 1 BC: 0 CA: 1 *MESH_SMOOTHING 1 *MESH_MTLID 0 for triangle 2 ...
}
*MESH_NUMTVERTEX 3 //Num of triangles*3
*MESH_TVERTLIST {
*MESH_TVERT 0 1.0 -0.0 1 //Triangle 1: UV Values of Vertex 1: Uv1 -Vv1 1
*MESH_TVERT 1 0.0 1.0 1 //Triangle 1: UV Values of Vertex 2: Uv2 -Vv2 1
*MESH_TVERT 2 0.0 -0.0 1 //Triangle 1: UV Values of Vertex 2: Uv2 -Vv2 1
}
*MESH_NUMTVFACES 1 // Num of triangles
*MESH_TFACELIST {
*MESH_TFACE 0 0 1 2 //0,1,2 for triangle 1
//*MESH_TFACE 1 3 4 5 // for triangle 2 ...
}
}
*MATERIAL_REF 0 //Do not change this
}</uscript>

Legacy:T3D StaticMesh

2009-10-17T07:10:14Z

Solarsys:

T3D Staticmeshes files are generated with the UCC command in order to export all StaticMeshes data from package or level.
It creates one .t3d file for each unique staticmesh found in the package.
They are exported using this command: 
<uscript>ucc batchexport myPackage T3D StaticMesh</uscript>

Sample File: Some basic triangle in Unreal Editor

[[File:T3DSM_TriangleUED.png]]

<uscript>
Begin StaticMesh Name=TriOriginal
Version=2.000000 BoundingBox.Min.X=-128.000000 BoundingBox.Min.Y=-128.000000 BoundingBox.Min.Z=0.000000 BoundingBox.Max.X=128.000000 BoundingBox.Max.Y=128.000000 BoundingBox.Max.Z=0.000000 //Unknown effect
Begin Triangle
Texture SMTest.Tex.256x256 //Texture applied to the triangle
SmoothingMask 0 //Unknown effect
Vertex 0 128.000000 128.000000 0.000000 1.000000 0.000000 //Vertex Coordinates (x,y,z)+ Texture U,V data
Vertex 1 -128.000000 -128.000000 0.000000 0.000000 -1.000000
Vertex 2 -128.000000 128.000000 0.000000 0.000000 0.000000
End Triangle
End StaticMesh
</uscript>

The vertices are ordered differently from the last one to the first one if we compare with T3D brush.

T3D Brush Drawing: 
[[File:T3DSM_BrushDraw.png]] 
T3D Brush data: 
<uscript> Vertex -00128.000000,+00128.000000,+00000.000000
Vertex -00128.000000,-00128.000000,+00000.000000
Vertex +00128.000000,+00128.000000,+00000.000000</uscript>

T3D StaticMesh Drawing: 
[[File:T3DSM_Draw.png]]

== Converting T3D StaticMeshes to ASE file ==
These T3D files can be used and converted as ASE (3D Ascii Scene) files in order to convert staticmeshes to UT3 as the UT3 editor
allows to import .ase files.

Here is the algorithm to use (.ase file data):
<uscript>
*3DSMAX_ASCIIEXPORT 200
*MATERIAL_LIST {
*MATERIAL_COUNT 1 //Always 1
*MATERIAL 0 {
*MATERIAL_NAME "Default Material"
*MATERIAL_CLASS "Multi/Sub-Object"
*MATERIAL_AMBIENT 1.0000 1.0000 1.0000
*MATERIAL_DIFFUSE 1.0000 1.0000 1.0000
*MATERIAL_SPECULAR 1.0000 1.0000 1.0000
*NUMSUBMTLS 1 //Num of unique different textures used in the staticmesh
*SUBMATERIAL 0 {
*MATERIAL_NAME "256x256" //Name of the texture used (without group and package info)
*MATERIAL_AMBIENT 1 1 1
*MATERIAL_DIFFUSE 1 1 1
*MATERIAL_SPECULAR 1 1 1
*MAP_DIFFUSE {
*MAP_NAME "Map #0"
*MAP_CLASS "Bitmap"
*MAP_SUBNO 1
*MAP_AMOUNT 1
*BITMAP "256x256" //Name of the texture used (without group and package info)
*MAP_TYPE Screen
*UVW_U_OFFSET 0.000000
*UVW_V_OFFSET 0.000000
*UVW_U_TILING 1.000000
*UVW_V_TILING 1.000000
*UVW_ANGLE 0.000000
*UVW_BLUR 1.000000
*UVW_BLUR_OFFSET 0.000000
*UVW_NOUSE_AMT 1.000000
*UVW_NOISE_SIZE 1.000000
*UVW_NOISE_LEVEL 1
*UVW_NOISE_PHASE 0.000000
*BITMAP_FILTER Pyramidal
}
}
}
}
*GEOMOBJECT {
*MESH {
*TIMEVALUE 0
*MESH_NUMVERTEX 3 //Num of vertices in the staticmesh
*MESH_NUMFACES 1 //Num of triangle in the staticmesh (normally equals to NUMVERTEX/NUMTRIANGLES)
*MESH_VERTEX_LIST {
*MESH_VERTEX 0 128.0 -128.0 0.0 //V1x(Triangle) -V1y V1z (axis Y direction in unreal editor is from top to bottom)
*MESH_VERTEX 1 -128.0 128.0 0.0 //V2x(Triangle) -V2y V2z
*MESH_VERTEX 2 -128.0 -128.0 0.0 //V3x(Triangle) -V3y V3z
}
*MESH_FACE_LIST {
*MESH_FACE 0: A: 0 B: 1 C: 2 AB: 1 BC: 0 CA: 1 *MESH_SMOOTHING 1 *MESH_MTLID 0 (=material id given in SUBMATERIAL section)
//*MESH_FACE 1: A: 1 B: 2 C: 3 AB: 1 BC: 0 CA: 1 *MESH_SMOOTHING 1 *MESH_MTLID 0 for triangle 2 ...
}
*MESH_NUMTVERTEX 3 //Num of triangles*3
*MESH_TVERTLIST {
*MESH_TVERT 0 1.0 -0.0 1 //Triangle 1: UV Values of Vertex 1: Uv1 -Vv1 1
*MESH_TVERT 1 0.0 1.0 1 //Triangle 1: UV Values of Vertex 2: Uv2 -Vv2 1
*MESH_TVERT 2 0.0 -0.0 1 //Triangle 1: UV Values of Vertex 2: Uv2 -Vv2 1
}
*MESH_NUMTVFACES 1 // Num of triangles
*MESH_TFACELIST {
*MESH_TFACE 0 0 1 2 //0,1,2 for triangle 1
//*MESH_TFACE 1 3 4 5 // for triangle 2 ...
}
}
*MATERIAL_REF 0 //Do not change this
}</uscript>

Legacy:T3D StaticMesh

2009-10-17T07:06:56Z

Solarsys: Adding some info to convert T3D SM to .ASE Files

T3D Staticmeshes files are generated with the UCC command in order to export all StaticMeshes data from package or level.
It creates one .t3d file for each unique staticmesh found in the package.
They are exported using this command: 
<uscript>ucc batchexport myPackage T3D StaticMesh</uscript>

Sample File: Some basic triangle in Unreal Editor

[[File:T3DSM_TriangleUED.png]]

<uscript>
Begin StaticMesh Name=TriOriginal
Version=2.000000 BoundingBox.Min.X=-128.000000 BoundingBox.Min.Y=-128.000000 BoundingBox.Min.Z=0.000000 BoundingBox.Max.X=128.000000 BoundingBox.Max.Y=128.000000 BoundingBox.Max.Z=0.000000 //Unknown effect
Begin Triangle
Texture SMTest.Tex.256x256 //Texture applied to the triangle
SmoothingMask 0 //Unknown effect
Vertex 0 128.000000 128.000000 0.000000 1.000000 0.000000 //Vertex Coordinates (x,y,z)+ Texture U,V data
Vertex 1 -128.000000 -128.000000 0.000000 0.000000 -1.000000
Vertex 2 -128.000000 128.000000 0.000000 0.000000 0.000000
End Triangle
End StaticMesh
</uscript>

The vertices are ordered differently from the last one to the first one if we compare with T3D brush.

T3D Brush Drawing: 
[[File:T3DSM_BrushDraw.png]] 
T3D Brush data: 
<uscript> Vertex -00128.000000,+00128.000000,+00000.000000
Vertex -00128.000000,-00128.000000,+00000.000000
Vertex +00128.000000,+00128.000000,+00000.000000</uscript>

T3D StaticMesh Drawing: 
[[File:T3DSM_Draw.png]]

== Converting T3D StaticMeshes to ASE file ==
These T3D files can be used and converted as ASE (3D Ascii Scene) files in order to convert staticmeshes to UT3 as the UT3 editor
allows to import .ase files.

Here is the algorithm to use (.ase file data):
<uscript>
*3DSMAX_ASCIIEXPORT 200
*MATERIAL_LIST {
*MATERIAL_COUNT 1 //Always 1
*MATERIAL 0 {
*MATERIAL_NAME "Default Material"
*MATERIAL_CLASS "Multi/Sub-Object"
*MATERIAL_AMBIENT 1.0000 1.0000 1.0000
*MATERIAL_DIFFUSE 1.0000 1.0000 1.0000
*MATERIAL_SPECULAR 1.0000 1.0000 1.0000
*NUMSUBMTLS 1 //Num of unique different textures used in the staticmesh
*SUBMATERIAL 0 {
*MATERIAL_NAME "256x256" //Name of the texture used (without group and package info)
*MATERIAL_AMBIENT 1 1 1
*MATERIAL_DIFFUSE 1 1 1
*MATERIAL_SPECULAR 1 1 1
*MAP_DIFFUSE {
*MAP_NAME "Map #0"
*MAP_CLASS "Bitmap"
*MAP_SUBNO 1
*MAP_AMOUNT 1
*BITMAP "256x256" //Name of the texture used (without group and package info)
*MAP_TYPE Screen
*UVW_U_OFFSET 0.000000
*UVW_V_OFFSET 0.000000
*UVW_U_TILING 1.000000
*UVW_V_TILING 1.000000
*UVW_ANGLE 0.000000
*UVW_BLUR 1.000000
*UVW_BLUR_OFFSET 0.000000
*UVW_NOUSE_AMT 1.000000
*UVW_NOISE_SIZE 1.000000
*UVW_NOISE_LEVEL 1
*UVW_NOISE_PHASE 0.000000
*BITMAP_FILTER Pyramidal
}
}
}
}
*GEOMOBJECT {
*MESH {
*TIMEVALUE 0
*MESH_NUMVERTEX 3 //Num of vertices in the staticmesh
*MESH_NUMFACES 1 //Num of triangle in the staticmesh (normally equals to NUMVERTEX/NUMTRIANGLES)
*MESH_VERTEX_LIST {
*MESH_VERTEX 0 128.0 -128.0 0.0 //V1x(Triangle) -V1y V1z (axis Y direction in unreal editor is from top to bottom)
*MESH_VERTEX 1 -128.0 128.0 0.0 //V2x(Triangle) -V2y V2z
*MESH_VERTEX 2 -128.0 -128.0 0.0 //V3x(Triangle) -V3y V3z
}
*MESH_FACE_LIST {
*MESH_FACE 0: A: 0 B: 1 C: 2 AB: 1 BC: 0 CA: 1 *MESH_SMOOTHING 1 *MESH_MTLID 0
}
*MESH_NUMTVERTEX 3 //Num of triangles*3
*MESH_TVERTLIST {
*MESH_TVERT 0 1.0 -0.0 1 //Triangle 1: UV Values of Vertex 1: Uv1 -Vv1 1
*MESH_TVERT 1 0.0 1.0 1 //Triangle 1: UV Values of Vertex 2: Uv2 -Vv2 1
*MESH_TVERT 2 0.0 -0.0 1 //Triangle 1: UV Values of Vertex 2: Uv2 -Vv2 1
}
*MESH_NUMTVFACES 1 // Num of triangles
*MESH_TFACELIST {
*MESH_TFACE 0 0 1 2 //0,1,2 for triangle 1
//*MESH_TFACE 0 3 4 5 // for triangle 2 ...
}
}
*MATERIAL_REF 0 //Do not change this
}</uscript>

Legacy:T3D StaticMesh

2009-10-15T09:03:11Z

Solarsys: T3D sample Brush data added

Legacy:T3D StaticMesh

2009-10-15T08:59:54Z

Solarsys:

Legacy:T3D StaticMesh

2009-10-15T08:58:53Z

Solarsys: Fixing images not aligned

T3D Staticmeshes files are generated with the UCC command in order to export all StaticMeshes data from package or level.
It created one .t3d file for each unique staticmesh found in the package.
They are exported using this command:
ucc batchexport myPackage T3D StaticMesh

Sample File: (some basic triangle)
Triangle in Unreal Editor:

[[File:T3DSM_TriangleUED.png]]

<uscript>
Begin StaticMesh Name=TriOriginal
Version=2.000000 BoundingBox.Min.X=-128.000000 BoundingBox.Min.Y=-128.000000 BoundingBox.Min.Z=0.000000 BoundingBox.Max.X=128.000000 BoundingBox.Max.Y=128.000000 BoundingBox.Max.Z=0.000000
Begin Triangle
Texture SMTest.Tex.256x256 //Texture applied to the triangle
SmoothingMask 0 //Unknown effect
Vertex 0 128.000000 128.000000 0.000000 1.000000 0.000000 //Vertex Coordinates (x,y,z)+ Texture U,V data
Vertex 1 -128.000000 -128.000000 0.000000 0.000000 -1.000000
Vertex 2 -128.000000 128.000000 0.000000 0.000000 0.000000
End Triangle
End StaticMesh
</uscript>

The vertices are ordered differently from the last one to the first one if we compare with T3D brush.

T3D Brush Drawing: 
[[File:T3DSM_BrushDraw.png]]

T3D StaticMesh Drawing: 
[[File:T3DSM_Draw.png]]

File:T3DSM Draw.png

2009-10-15T08:57:41Z

Solarsys: How the vertices are ordering for a simple T3D Triangle staticmesh.

== Summary ==
How the vertices are ordering for a simple T3D Triangle staticmesh.
== Licensing: ==
{{Unknown}}

File:T3DSM BrushDraw.png

2009-10-15T08:57:13Z

Solarsys: How the vertices are ordering for a simple T3D Triangle brush

== Summary ==
How the vertices are ordering for a simple T3D Triangle brush
== Licensing: ==
{{Unknown}}

File:T3DSM TriangleUED.png

2009-10-15T08:56:14Z

Solarsys: Some basic triangle created with the UT2004 Unreal Editor

== Summary ==
Some basic triangle created with the UT2004 Unreal Editor
== Licensing: ==
{{Unknown}}

Legacy:T3D StaticMesh

2009-10-15T08:55:21Z

Solarsys: Adding T3D Staticmesh fileformat info

T3D Staticmeshes files are generated with the UCC command in order to export all StaticMeshes data from package or level.
It created one .t3d file for each unique staticmesh found in the package.
They are exported using this command:
ucc batchexport myPackage T3D StaticMesh

Sample File: (some basic triangle)
Triangle in Unreal Editor:
[[File:T3DSM_TriangleUED.png]]

<uscript>
Begin StaticMesh Name=TriOriginal
Version=2.000000 BoundingBox.Min.X=-128.000000 BoundingBox.Min.Y=-128.000000 BoundingBox.Min.Z=0.000000 BoundingBox.Max.X=128.000000 BoundingBox.Max.Y=128.000000 BoundingBox.Max.Z=0.000000
Begin Triangle
Texture SMTest.Tex.256x256 //Texture applied to the triangle
SmoothingMask 0 //Unknown effect
Vertex 0 128.000000 128.000000 0.000000 1.000000 0.000000 //Vertex Coordinates (x,y,z)+ Texture U,V data
Vertex 1 -128.000000 -128.000000 0.000000 0.000000 -1.000000
Vertex 2 -128.000000 128.000000 0.000000 0.000000 0.000000
End Triangle
End StaticMesh
</uscript>

The vertices are ordered differently from the last one to the first one if we compare with T3D brush.
T3D Brush Drawing:
[[File:T3DSM_BrushDraw.png]]

T3D StaticMesh Drawing:
[[File:T3DSM_Draw.png]]

Legacy:T3D Brush

2009-10-15T08:35:54Z

Solarsys: Adding extra info about PanU,PanV

A T3D Brush is geometry information contained into [http://wiki.beyondunreal.com/Legacy:T3D_File[T3D Files]].

The following actors used as brushes in T3D files:
*[http://wiki.beyondunreal.com/Legacy:Brush[Brushes]]
*[http://wiki.beyondunreal.com/Legacy:Mover[Movers]] (only in Unreal 1 and Unreal Tournament)

=== Actor structure ===
<uscript>Begin Actor Class=Brush Name=Brush0
MainScale=(SheerAxis=SHEER_ZX)
PostScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
TempScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
Level=LevelInfo'Entry.LevelInfo0'
Tag=Brush
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=464.000000,Y=-16.000000,Z=64.000000)
Rotation=(Yaw=49152)
Begin Brush Name=Brush
Begin PolyList
Begin Polygon Item=OUTSIDE Texture=black1 Flags=4194304 Link=0
Origin -00160.000000,+00000.000000,+00128.000000
Normal +00000.000000,+00000.000000,+00001.000000
TextureU +00004.000000,+00000.000000,+00000.000000
TextureV +00000.000000,+00004.000000,+00000.000000
Vertex -00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,+00128.000000,+00128.000000
Vertex -00128.000000,+00128.000000,+00128.000000
End Polygon
...
End PolyList
End Brush
Brush=Model'Entry.Brush'
Name=Brush0
End Actor</uscript>

*MainScale: scales up or down current brush before make it rotate.
*PostScale: scales up or down current brush after make it rotate.
*TempScale: unknown effect
*Location: where the brush is located in the map
*Rotation: contains up to 3 values
**Roll: X axis rotation
**Pitch: Y axis rotation
**Yaw: Z axis rotation
*Begin Polygon Item=OUTSIDE Texture=black1 Flags=4194304 Link=0
**Texture: texture applied to the current polygon with formatted string.
***[TextureName] for Unreal 1 / Unreal Tournament maps
***[PackageName.TextureName] for other UTx games.
**Origin: where the texture is centered
**Normal: normally, the perpendicular vector of the surface where the texture is applied
**Texture U,V: contains information about scaling and texture rotation
**PanU,PanV: only used in Unreal Tournament and Unreal 1. Changes the texture origin coordinates.
**Vertex: X,Y,Z coordinates of the specified vertex

Note: NumTriangles = NumVertices-Floor(NumVertices/3)

[[Image:texinfot3d.jpg]]

===Loading T3D brush geometry===

You must parse those informations correctly: PrePivot, Location, Rotation, MainScale, PostScale, TempScale, Polygon / Vertexes

<uscript>
FOR each vertex of each polygon of parsed brush DO:
do MainScale ... x *= MainScale[x], y *= MainScale[y], z *= MainScale[z]
do translation (-PrePivot[x], -PrePivot[y], -PrePivot[z])
do rotation Yaw, Pitch, Roll
do PostScale ... x *= PostScale[x], y *= PostScale[y], z *= PostScale[z]
do TempScale ... x *= TempScale[x], y *= TempScale[y], z *= TempScale[z]
do translation (Location[x], Location[y], Location[z])
ENDFOR
</uscript>

Note:
For Unreal Engine 3.x based maps (Unreal Tournament 2004 and 2003),PostScale,MainScale,TempScale and Rotation values are always null as the editor automatically updates vertices,origin and normal values when scaling up/down or rotating a brush.

Rotation matrix are the following:

<uscript>Roll Matrix-X Axis:
1, 0, 0, 0,
0, cos(roll),-sin(roll), 0,
0, sin(roll),cos(roll), 0,
0, 0, 0, 1</uscript>

<uscript>Pitch Matrix-Y Axis:
cos(pitch), 0, sin(pitch), 0,
0, 1, 0, 0,
-sin(pitch), 0,cos(pitch), 0,
0, 0, 0, 1)</uscript>

<uscript>Yaw Matrix-Z Axis:
cos(yaw), sin(yaw), 0, 0,
-sin(yaw), cos(yaw), 0, 0,
0, 0, 1, 0,
0, 0, 0, 1</uscript>

<uscript>Global Rotation Matrix=(Roll Matrix)*(Pitch Matrix)*(Yaw Matrix)</uscript>

Yaw, Roll and Pitch values are in radians. Original values from t3d files are in "Unreal format" where 2 rad = 65536.
For more information about Yaw, Pitch, Roll rotation matrix see http://mathworld.wolfram.com/EulerAngles.html.

=== Scaling up/down brushes ===
This operation is mainly needed when you want to port Unreal 1 or Unreal Tournament map to Unreal Tournament 2004 or Unreal Tournament 3.

To do so,considering ScaleFactor:
<uscript>
set Location = ScaleFactor*Location
set PrePivot = ScaleFactor*PrePivot
For each polygon
set Origin = ScaleFactor*Origin
For each vertex
set Vertex = ScaleFactor*Vertex
</uscript>

Usually scale factor values:
Unreal 1/Unreal Tournament to UT2003/UT2004/UT3: 1.25

=== Tools ===
*Python T3D loader (doesn't care about texture informations): http://carolina.mff.cuni.cz/~gib/ut_utils/unreal_t3d_loader.zip see readme.txt in zip file
*[[Legacy:MapScale|MapScale]] scales an entire .t3d file (only works for UT/U1 maps)

Talk:Main Page

2009-04-22T11:47:29Z

Solarsys: Undo revision 34357 by 194.85.80.75 (Talk)

== General layout ==

I've tried to come up with a compact initial layout and topic list. Suggestions for improvements are welcome. [[User:Wormbo|Wormbo]] 06:31, 13 March 2008 (EDT)

Actually, we need to come up with an easy-to-browse structure for overview pages of the various parts of Unreal modding. The problem here will be that either this kind of page tends to get too long or there are too many pages to click through before reaching actual content. We need to find a good mix between an sophisticated structure and quick access. The topic pages can be accompanied by [[Project:categories|categories]], navigation/info boxes (an example can be found e.g. on [[Literals]]) and disambiguation links/pages for when a user uses the Go button of the search box in the sidebar. I hope this will give you an overview of the new tools we can use to structure the Unreal Wiki. -[[User:Wormbo|Wormbo]] 07:58, 16 April 2008 (UTC)

I think we can now all agree this should have been discussed openly and decided much earlier, before the switch to MediaWiki and the subsequent disconnect with Legacy content. This discussion will likely last a while and not get the input of the entire wiki community. Seeing as I was an instrumental contributor of the old organization (which has been widely criticized as poor or no organization), I will step back, keep an eye on the progress and wait for the dust to settle. Good luck. -[[User:SuperApe|SuperApe]] 08:57 PST, 16 April 2008

Under the UnrealScript Reference topics, seeing 'Programming tutorials' seems a little out of place. Since most if not all the programming tutorials we have here will deal with UnrealScript, why not change it and the category to UnrealScript Tutorials? -[[User:DalinSeivewright|DalinSeivewright]] 15:14, 17 April 2008 (UTC)

These category things are working arnt they? Ive been around the site acouple of times now and I dont think Ive seen anything in any of the expanded tree's. Just wondering anyways, perhaps we could get some templates in there with correct names for the time being. -[[User:OlympusMons|OlympusMons]] 22:49, 17 April 2008 (UTC)

Those tree widgets only show subcategories, not pages or media. Just imagine [[:Category:UT2004-specific classes]] displaying all old UT2004 classes when you expand its subcategory [[:Category:Legacy Class (UT2004)]]! If you mean the actual categories, don't worry. I'll import the wikified class pages for UT, UT2003/4, UT3 and UE2Runtime some time this week. -[[User:Wormbo|Wormbo]] 08:35, 21 April 2008 (UTC)

Yeah I noticed that an hour or so after making that comment, I thought classes were meant to be shown in the category class tree's but they arnt, it seems to function more like a search criterea. Yeah hope things are going well on the new wikifier, should save alot of time. :)
Actually on the Topic of class tree's since Im there, whats going to happen in that respect now? Are we going to have a class tree page anymore? I imagine alot can be done with tree views now so Id wonder if it is possible to have a class tree which is actually expandable/collapsable now, since the categories dont show the classes right under their package or superclass etc -[[User:OlympusMons|OlympusMons]] 23:29, 21 April 2008 (UTC)

:Double post looolz, anyways to expand on class tree's I had a play over here: [[Unreal_Wiki:Sandbox|Sandbox]] but I think it'll need its own template or something and Im not well versed on this new wiki stuff just yet. This category list shows the pages though under the categories they fall but I couldnt get the parent class showing as a category which is why I thought it'd need a template. -[[User:OlympusMons|OlympusMons]] 16:51, 27 April 2008 (UTC)

== New wiki software / Organization ==
Various people have had questions, comments, or criticisms of this move to MediaWiki. This seems as good a place as any to discuss it, so feel free to add anything here. – [[User:Haarg|Haarg]] 21:32, 3 April 2008 (UTC)

:Well I guess my biggest concern is the wealth of existing information (namely the tutorials and class hierarchy pages) that we can't simply move over. Most if not all the pages have had at least one contributor to the page that has done at least a minor edit. Then there's the problem of not having a complete history of the older pages so while it may appear that only one individual has worked on a given page, the truth could be that at least two have worked on it but the history of the page has been lost. Then theres the problem of what we can do with new content for the older engines as we cannot add new content to these legacy pages. IMO, the class hierarchy at least could be moved over as most of the pages are simply descriptions of what the class does (which really, Copyrights should have no hold over because there's only so many ways you can describe what a class is responsible for) and have listings for each method and variable and what they're used for.

:If that really is not an option then we could go through class by class and (re-) create a class page for each of them by source. So we could have a category for each game and have a hierarchy of classes from each package. It '''would''' take a fair bit of time to complete and a decent format would need to be made up. I personally didn't like how the old formats were set up. It seemed like too much information was being thrown at you for classes such as Actor, where there are a lot of variables and methods to go through. I guess we'd have to look at how much more information we could add in the end. I'm not sure how 'definitive' our class pages were, but I'm positive we didn't have many pages for certain classes.

:On the topic of tutorials, is there any reason why we can't re-write them? If a tutorial explains how to make a new weapon based on the shock rifle (which has been over done already) we could just reinvent the wheel. The other more advanced tutorials (such as the RPG Class tutorials) could be re-written with a similar basis.

:In the end, I think keeping the older content up-to-date and easy to find/navigate through is important as many level designers and modders most likely have not moved over to UE3 and UE2 still has plenty of life left in it.

:-[[User:DalinSeivewright|DalinSeivewright]] 12:03, 4 April 2008 (UTC)
::Most of the class hierarchy could be moved over or recreated pretty simply. As for tutorials, rewriting them is probably the best solution. While that may seem like wasted effort, I don't see a better solution given the licensing issues. – [[User:Haarg|Haarg]] 17:17, 5 April 2008 (UTC)
:wow. Unreal Wiki had a makeover... This will be confusing for a while...--[[User:JeffMOD|JeffMOD]] 14:56, 5 April 2008 (UTC)
:A comment on user accounts: It probably could have been explained better, but the user accounts from the old wiki weren't converted to the new software. First, I somewhat doubt it would have been possibly technically But mainly, there was barely any information attached to the old accounts that have been worth keeping. So everyone has to create new user accounts. Additionally, anonymous edits are turned off. I would be interested in feedback on that as well. – [[User:Haarg|Haarg]] 17:17, 5 April 2008 (UTC)
::I think its a great idea. Its a good anti-spam addition that works well for the most part, although it could end up generating a lot of accounts that would only be used once (as I've found a lot of people often to go to a site where they need to sign up to contribute and only ever change one thing they've found). Also, spam bots have been known to sign up a lot so perhaps you could add CAPTCHA to the account creation process. -[[User:DalinSeivewright|DalinSeivewright]] 02:30, 6 April 2008 (UTC)
:::I don't think we need to add a captcha at this point, but that could be revisited if spam becomes a problem. – [[User:Haarg|Haarg]] 02:36, 6 April 2008 (UTC)

Two things. Having the Legacy article show up in the search kind of makes it look incredibly messy, unorganized and hard to follow. I understand that its important to stress that Users probably shouldn't do major edits to Legacy pages but somehow hiding the Legacy part of the article name would help things considerably.

Secondly I was comparing the Actor class of UT2003 with that of UT2004 and there are several differences in each. I think we should have at least one Actor page for each generation but what about games within the same generation? Should we have seperate Actor pages for UT2003 and UT2004 within the UE2 namespace or UT2003/UT2004 namespaces or should we have one full page for UT2004 and have a seperate page for the Actor class in UT2003 that just sites the major differences? -[[User:DalinSeivewright|DalinSeivewright]] 01:32, 15 April 2008 (UTC)
:Well on the topic of UE2 Id think the best option might be to have a seperate section relating to UE2.5 since its an upgrade on the engine. Both UT2003 and UT2004 are UE2 though but other engines picked up support at UE2.5 where some are based on UE2. I do know there was alittle bit of a hastle with the class tree pages because it contained info from both UE2-2.5 so each difference had to be tagged. I guess it wasnt so bad since some classes are identical between the two, the last idea sounds good to me to do full page on UT2004's Actor and a differences page for UT2003. - [[User:OlympusMons|OlympusMons]]

:::I actually change my mind. I think we should have an actor page for each version of the engine/game. This would be considerably more work (unless Wormbo finishes his class wikifier?) but it would be much 'cleaner' and dare I say sexier. Plus users won't be too confused on whether or not their on the right page if the page just sites the differences. -[[User:DalinSeivewright|DalinSeivewright]] 00:11, 17 April 2008 (UTC)

::::Might be the go hey since there are sometimes differences between builds as well so it might get very confusing later, duplicating material isnt too good but I dont think it can be helped much since of the nature of UE. -[[User:OlympusMons|OlympusMons]] 22:51, 17 April 2008 (UTC)

:::I agree with Dalin here. Each "game" (including UE2Runtime) gets its own set of class pages and corresponding categories. If the classes really have exactly the same content, we can take advantage of the template features and simply include the newest game's version of the page on all older games' versions of the same page. I already demonstrated this on [[UE2:DMRosterBeatTeam (UT2003)]], which only includes the content from [[UE2:DMRosterBeatTeam (UT2004)]]. The templates [[Template:Infobox class]] (and [[Template:Infobox class part]]) and [[Template:samegame]] used there automatically set up links to point to pages of the same game. On a semi-related note: Do we want to document defaultproperties, possibly including subobjects, on the class pages? -[[User:Wormbo|Wormbo]] 08:35, 21 April 2008 (UTC)

::::I'm in favor of having any documentation of the default properties in where the variables are documented (if at all). It would seem reasonable to have the 'default' or accepted values for a given variable where we've explained what the variable is for. I think subobjects should be included too, just as long as we can have a seperate page for that sub-object if it is really important. For example, the KPhysics object in xPawn. Without it, your Pawn fails. -[[User:DalinSeivewright|DalinSeivewright]] 05:49, 22 April 2008 (UTC)

::::Please have a look at [[UE3:UIObject (UT3)]], I've updated it with the basic default value and subobject output of the wikifier. I still need to add special parsing for struct values to link any enums or subobjects used there. Suggestions about the output are welcome. -[[User:Wormbo|Wormbo]] 09:23, 27 April 2008 (UTC)

== Mod ideas ==

I dont know where to add mod ideas...

The mod ideas section didn't really work out on the old wiki, IMHO. Would it really make sense to revive that? -[[User:Wormbo|Wormbo]] 05:54, 25 April 2008 (UTC)
:I was actually thinking the same thing and wasn't going to add it to the main page, but then I thought I'd add it anyways and see what anyone else thought. The old Mod ideas was an okay source for ideas but it ended up being a list of abandoned pages with half being discussions on the Mod idea itself and the other half being discussions on the progress of the mod, as if it was no longer an open source idea but being worked on. I'm fine with not reviving the page, but where would these mod ideas go now? -[[User:DalinSeivewright|DalinSeivewright]] 06:26, 25 April 2008 (UTC)
::Better leave mod ideas to ppl's own wiki pages -[[User:0 Kelvin|0 Kelvin]]
:::That's a pretty good idea actually. There could be a category like [[:Category:Mod ideas]] or something similar, and it could go over what to have in mind of you are proposing a mod idea. Ideas could then be posted as sub-pages of user pages. If an idea actually took off, it could be moved into a different namespace easily. – [[User:Haarg|Haarg]] 15:47, 25 April 2008 (UTC)
::::Lets go with that then :) What about Licensing issues though? Will the 'concept' of Mod Ideas have to be reworked? If a user has a great concept and someone came and used that idea down to the exact details would there be any problems/need to cite references etc. ? I'm pretty sure copyright doesn't have a hold over 'ideas', although I could be wrong. -[[User:DalinSeivewright|DalinSeivewright]] 16:09, 25 April 2008 (UTC)
::::Isn't the entire point of posting mod ideas that ''others'' should pick them up? -[[User:Wormbo|Wormbo]] 16:59, 25 April 2008 (UTC)
:::::Yes of course, but since its under the Wiki license I'm simply wondering if there should be a seperate license for the idea pages, or if there would even be a need for that. I'm guessing by your comment, there should be no problem with the licensing then? :) -[[User:DalinSeivewright|DalinSeivewright]] 18:23, 25 April 2008 (UTC)

I've removed the [[Modding ideas]] link from the main page. That page should really be dissolved and the individual ideas should be posted on the contributing users' personal pages. Once that is done, [[:Category:Mod ideas]] could be linked from [[Modding overview]], but not from the main page. —[[User:Wormbo|Wormbo]] 20:16, 21 November 2008 (UTC)

==Category link description==
Do the Wiki Categories currently support descriptions for each page associated to the category? What I mean is, is there currently a way to associate a description of a page within a category and have that description appear in the list of pages for said category? For example:
<pre>
A
[[Apple]] - This page describes what an apple is.
O
[[Orange]] - This page describes what an orange is.
</pre>
These descriptions would be added on the page with perhaps a little tag? I'm just curious and don't really feel they're neccesary... at least at the moment. -[[User:DalinSeivewright|DalinSeivewright]] 16:23, 25 April 2008 (UTC)

No, that's not supported. This type of description needs to go in the page text, either of the category page or a more suitable topic page. -[[User:Wormbo|Wormbo]] 16:54, 25 April 2008 (UTC)

Some form of this could be done using a DPL report:<dpl>
category = Custom UE2-specific classes
include={Infobox class}:parent1
includematch=/./
secseparators= \n- Subclass of ,
</dpl>
But that would be built as a specific list, and not part of the general category page. – [[User:Haarg|Haarg]] 17:49, 25 April 2008 (UTC)

== 3rd Party / open source scripts ==

Where do they go? (O Kelvin)

: As a page with the the appropriate namespace and page name. [[UE1:RJumpPad]] for example. With a class infobox, it will be added to the appropriate categories. – [[User:Haarg|Haarg]] 23:30, 27 April 2008 (UTC)

:: Ops... I made edits to the Legacy:Third party components page -_- [[User:0 Kelvin]]
:: How about adding a "Projects" starting point ? It would be ideal for grouping all the third-party code detailed on the wiki and make it easily accessible. I mean, think of those people who are getting started with unrealscript. Documentation sometimes isn't enough and snippets of code could serve as examples. At the moment, it's a pain finding anything and one usually has to type random phrases in Google to get access to anything interesting. --[[User:Azura|Azura]] 01:14, 6 April 2009 (UTC)

Unreal Wiki:Community portal

2009-01-22T15:47:42Z

Solarsys: Removing spam link again .. :/

Welcome to the '''{{SITENAME}} Community Portal'''. This is the place to find out what's happening on Unreal Wiki and what you can do to help.
__NOTOC__
== News ==
===Unreal Wiki reloaded===
As you may have noticed, '''{{SITENAME}}''' has migrated from the old [[wp:UseModWiki|UseModWiki]] software to a recent version of [[wp:MediaWiki|MediaWiki]].

Currently we are in the process of getting (re-)started with content. Pages and images have been imported from the [[Legacy:Home_Page|old Unreal Wiki]] and can be browsed as before. Old links via <code><nowiki>/wiki/Page_Name</nowiki></code> now redirect to <code><nowiki>/Legacy:Page_Name</nowiki></code> for normal pages or <code><nowiki>/Category:Legacy_Page_Name</nowiki></code> for categories and category-like pages. We've made best effort to compensate the different ways UseModWiki and MediaWiki normalize page names, so external links should not be broken. If you still find such a link, please tell the external site's admin to link to the new page instead.

As part of the restart, we want to create a better topic structure for the old and new knowledge to be documented. See the [[#Help out|Help out]] section below to find out how you can help in this process.

== General ==
What is the Unreal Wiki and how can you use it?
* [[Unreal Wiki:About|About the Unreal Wiki]]
* [[Unreal Wiki:Getting started|How to get started]]

=== Help out ===
Unreal Wiki is seeking to provide comprehensive documentation about the [[Unreal Editor]] and [[Unreal Engine]] games as well as tutorials for creating content for them. You can help out in a number of ways, for example by writing tutorials, documenting engine features and, most importantly, improve existing documentation.
* [[Unreal Wiki:Helping out|How do I help?]]
* [[Unreal Wiki:Task list|What needs to be done?]]

=== Need help? ===
If you have questions about Unreal Wiki that these pages do not answer, feel free to use an [[wikipedia:IRC Client|IRC Client]] to join our channel [irc://irc.enterthegame.com/unrealwiki #unrealwiki] on the EnterTheGame network. Or just browse over to the [http://forums.beyondunreal.com/forumdisplay.php?forumid=249 Unreal Wiki forum] at the BeyondUnreal Forums.

Unreal Wiki:Community portal

2009-01-22T07:48:52Z

Solarsys: Removing spam link

Legacy:T3D File

2009-01-20T10:07:04Z

Solarsys: /* Related Topics */

The '''T3D file format''' or '''Unreal Text File''' holds a text list of Unreal map objects. An entire map can be saved as this file format, or just a single actor or brush.

Note that while brushes, their applied textures and light actors are saved, the [[Legacy:Unreal Geometry|Unreal Geometry]] itself is not saved: upon importing a T3D file the map must be built.

Copying objects from UnrealEd and pasting into a text editor produces the same format.

Unreal Text format

Exported brushes and (other) actors. See [[Legacy:T3D File|T3D file]].
* Created by:
** UnrealEd's File -> Import command
** UnrealEd's Brush -> Import command (see [[Legacy:Data Import And Export|Data Import and Export]] for more on both these commands).
** is this created by external stuff too?

===Exporting T3D ===
* Export the whole map
** File -> Export... (UnrealEd 1,2,3)
** File -> Export -> All.. (UnrealEd 4 - UT3)
* Export selected actors: File-> Export-> Selected Only ... (UnrealEd 4 only - UT3)
* Export one brush: Brush -> Export ...
* Copy/Paste: can copy paste any actor from any UnrealEd version to another one (Except for UnrealEd 4) or to any text editor such as notepad (Windows)

===Importing T3D ===

File -> Import...

(note importing may take a LONG time)

Overheard on #utjb... :-)

<tarquin> t3d stores brushes & actors but not texturing, right?
<Mychaeel> Texturing as well.
(melds into the opening speech from Reservoir Dogs...)
<DaveA>Stores links to textures, and texture transforms, but not the pixels themselves

The T3D format is a text file which stores information about map actors. It's in fact identical to what can be copied from UnrealEd to a text editor. An exported map looks like this:

<uscript>
Begin Map
Begin Actor Class=LevelInfo Name=LevelInfo0
TimeSeconds=17.008888
Summary=LevelSummary'Entry.LevelSummary'
DefaultGameType=Class'Botpack.UTIntro'
AIProfile(0)=23784352
AIProfile(1)=52
AIProfile(2)=41
AIProfile(3)=42
AIProfile(4)=40
AIProfile(5)=44
AIProfile(6)=45
AIProfile(7)=21846171
AvgAITime=0.000000
Level=LevelInfo'Entry.LevelInfo0'
Tag=LevelInfo
Region=(Zone=LevelInfo'Entry.LevelInfo0',iLeaf=-1)
Name=LevelInfo0
End Actor
Begin Actor Class=Brush Name=Brush0
MainScale=(SheerAxis=SHEER_ZX)
PostScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
TempScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
Level=LevelInfo'Entry.LevelInfo0'
Tag=Brush
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=464.000000,Y=-16.000000,Z=64.000000)
Begin Brush Name=Brush
Begin PolyList
Begin Polygon Item=OUTSIDE Texture=black1 Flags=4194304 Link=0
Origin -00160.000000,+00000.000000,+00128.000000
Normal +00000.000000,+00000.000000,+00001.000000
TextureU +00004.000000,+00000.000000,+00000.000000
TextureV +00000.000000,+00004.000000,+00000.000000
Vertex -00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,+00128.000000,+00128.000000
Vertex -00128.000000,+00128.000000,+00128.000000
End Polygon
...
End PolyList
End Brush
Brush=Model'Entry.Brush'
Name=Brush0
End Actor
Begin Actor Class=PlayerStart Name=PlayerStart0
Level=LevelInfo'Entry.LevelInfo0'
Tag=PlayerStart
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=183.134430,Y=-987.334167,Z=33.978027)
OldLocation=(X=-217.561523,Y=-44.538128,Z=-87.899948)
Name=PlayerStart0
End Actor
...
End Map</uscript>

External link: http://unreal.jall.org/tutorials/t3d.html (new URL)

=== T3D File Structure ===
== Ux,UT,UT200x Maps ==
<uscript>
Begin Map
Begin Actor Class=<ClassName>
...
End Actor
Begin Actor Class=<ClassName>
...
End Actor
...
End Map
</uscript>

== UT3 Maps ==
<uscript>
Begin Map
Begin Level NAME=PersistentLevel
Begin Actor Class=<ClassName>
...
End Actor
Begin Actor Class=<ClassName>
...
End Actor
...
End Level
Begin Surface
End Surface
End Map
</uscript>

Note: as UT3 T3D files have different header, any other not-UT3 t3d file can't be imported into UT3 editor (UnrealEd 4)

===T3D brush geometry===
Information geometry is contained in the following actors:
*Brush
*Mover (only UT and U1 game)

For more information about T3D brushes, see [http://wiki.beyondunreal.com/Legacy:T3D_Brush[T3D Brush]]

==T3D Utilities ==
* [[Legacy:MapScale|MapScale]] scales an entire .t3d file
* [[Legacy:MeshMaker|MeshMaker]] converts a prefab in .t3d format to a [[Legacy:Decoration|decoration]]
* [http://www.unrealroc.com/Converter.html UnrealROC] converters: from 3DMF, to VRML/X3D/OBJ (including textures et al).

==Related Topics ==
* [[Legacy:Data Import And Export|Data Import and Export]]
* [[Legacy:Brush Exporting And Importing|Brush Exporting And Importing]]
* [[Legacy:Brush Hacking|Brush Hacking]]
* [[Legacy:T3D Brush|T3D Brush]]

'''Kefik:''' There can be also a tag 'CsgOper' which have one of two values ... 'CSG_Subtract' -> subtract the brush from space or 'CSG_Add' -> add this brush to shape.

'''Sobiwan:''' New to WIKI editing, but not using it. I was searching for the actual format of T3D and found [http://users.skynet.be/fa550206/Slug-Production/Data/OpenGL-Documents/T3D-File-Format/T3D-File-Format.htm Mongo's description] of [http://www.planetunreal.com Planetunreal] to be extremely helpful. I'll ask him (mongo@planetunreal.com) if we can use and/or edit his description here. The format is much more involved than described here. We can even supply examples of how to do particular hacks.

'''MadNad:''' Interestingly, I was able to convert a [http://madnad.com/ut2k3/Screenshots/q3dm7.jpg?link Quake3_Level] into a unreal map. Quite interesting. First i converted a *.bsp to a *.map in quake, then I made a level that was just a huge cube and converted it to *.t3d. With an external app (i'll have to find the name of it ) I was able to merge these two together. After some scaling and switching additive brushes in quake to subtractive brushes in ued and subtractive to additive, I compiled and had q3dm7 geometry. I don't necessarily recommend doing this, as it will take more time to fix than create it from scratch, but I thought I would share a little experience I had with this.

Legacy:T3D File

2009-01-20T10:05:48Z

Solarsys: /* Ux,UT,UT200x Maps */

The '''T3D file format''' or '''Unreal Text File''' holds a text list of Unreal map objects. An entire map can be saved as this file format, or just a single actor or brush.

Note that while brushes, their applied textures and light actors are saved, the [[Legacy:Unreal Geometry|Unreal Geometry]] itself is not saved: upon importing a T3D file the map must be built.

Copying objects from UnrealEd and pasting into a text editor produces the same format.

Unreal Text format

Exported brushes and (other) actors. See [[Legacy:T3D File|T3D file]].
* Created by:
** UnrealEd's File -> Import command
** UnrealEd's Brush -> Import command (see [[Legacy:Data Import And Export|Data Import and Export]] for more on both these commands).
** is this created by external stuff too?

===Exporting T3D ===
* Export the whole map
** File -> Export... (UnrealEd 1,2,3)
** File -> Export -> All.. (UnrealEd 4 - UT3)
* Export selected actors: File-> Export-> Selected Only ... (UnrealEd 4 only - UT3)
* Export one brush: Brush -> Export ...
* Copy/Paste: can copy paste any actor from any UnrealEd version to another one (Except for UnrealEd 4) or to any text editor such as notepad (Windows)

===Importing T3D ===

File -> Import...

(note importing may take a LONG time)

Overheard on #utjb... :-)

<tarquin> t3d stores brushes & actors but not texturing, right?
<Mychaeel> Texturing as well.
(melds into the opening speech from Reservoir Dogs...)
<DaveA>Stores links to textures, and texture transforms, but not the pixels themselves

The T3D format is a text file which stores information about map actors. It's in fact identical to what can be copied from UnrealEd to a text editor. An exported map looks like this:

<uscript>
Begin Map
Begin Actor Class=LevelInfo Name=LevelInfo0
TimeSeconds=17.008888
Summary=LevelSummary'Entry.LevelSummary'
DefaultGameType=Class'Botpack.UTIntro'
AIProfile(0)=23784352
AIProfile(1)=52
AIProfile(2)=41
AIProfile(3)=42
AIProfile(4)=40
AIProfile(5)=44
AIProfile(6)=45
AIProfile(7)=21846171
AvgAITime=0.000000
Level=LevelInfo'Entry.LevelInfo0'
Tag=LevelInfo
Region=(Zone=LevelInfo'Entry.LevelInfo0',iLeaf=-1)
Name=LevelInfo0
End Actor
Begin Actor Class=Brush Name=Brush0
MainScale=(SheerAxis=SHEER_ZX)
PostScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
TempScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
Level=LevelInfo'Entry.LevelInfo0'
Tag=Brush
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=464.000000,Y=-16.000000,Z=64.000000)
Begin Brush Name=Brush
Begin PolyList
Begin Polygon Item=OUTSIDE Texture=black1 Flags=4194304 Link=0
Origin -00160.000000,+00000.000000,+00128.000000
Normal +00000.000000,+00000.000000,+00001.000000
TextureU +00004.000000,+00000.000000,+00000.000000
TextureV +00000.000000,+00004.000000,+00000.000000
Vertex -00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,+00128.000000,+00128.000000
Vertex -00128.000000,+00128.000000,+00128.000000
End Polygon
...
End PolyList
End Brush
Brush=Model'Entry.Brush'
Name=Brush0
End Actor
Begin Actor Class=PlayerStart Name=PlayerStart0
Level=LevelInfo'Entry.LevelInfo0'
Tag=PlayerStart
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=183.134430,Y=-987.334167,Z=33.978027)
OldLocation=(X=-217.561523,Y=-44.538128,Z=-87.899948)
Name=PlayerStart0
End Actor
...
End Map</uscript>

External link: http://unreal.jall.org/tutorials/t3d.html (new URL)

=== T3D File Structure ===
== Ux,UT,UT200x Maps ==
<uscript>
Begin Map
Begin Actor Class=<ClassName>
...
End Actor
Begin Actor Class=<ClassName>
...
End Actor
...
End Map
</uscript>

== UT3 Maps ==
<uscript>
Begin Map
Begin Level NAME=PersistentLevel
Begin Actor Class=<ClassName>
...
End Actor
Begin Actor Class=<ClassName>
...
End Actor
...
End Level
Begin Surface
End Surface
End Map
</uscript>

Note: as UT3 T3D files have different header, any other not-UT3 t3d file can't be imported into UT3 editor (UnrealEd 4)

===T3D brush geometry===
Information geometry is contained in the following actors:
*Brush
*Mover (only UT and U1 game)

For more information about T3D brushes, see [http://wiki.beyondunreal.com/Legacy:T3D_Brush[T3D Brush]]

==T3D Utilities ==
* [[Legacy:MapScale|MapScale]] scales an entire .t3d file
* [[Legacy:MeshMaker|MeshMaker]] converts a prefab in .t3d format to a [[Legacy:Decoration|decoration]]
* [http://www.unrealroc.com/Converter.html UnrealROC] converters: from 3DMF, to VRML/X3D/OBJ (including textures et al).

==Related Topics ==
* [[Legacy:Data Import And Export|Data Import and Export]]
* [[Legacy:Brush Exporting And Importing|Brush Exporting And Importing]]
* [[Legacy:Brush Hacking|Brush Hacking]]
* [http://wiki.beyondunreal.com/Legacy:T3D_Brush[T3D Brush]]

'''Kefik:''' There can be also a tag 'CsgOper' which have one of two values ... 'CSG_Subtract' -> subtract the brush from space or 'CSG_Add' -> add this brush to shape.

'''Sobiwan:''' New to WIKI editing, but not using it. I was searching for the actual format of T3D and found [http://users.skynet.be/fa550206/Slug-Production/Data/OpenGL-Documents/T3D-File-Format/T3D-File-Format.htm Mongo's description] of [http://www.planetunreal.com Planetunreal] to be extremely helpful. I'll ask him (mongo@planetunreal.com) if we can use and/or edit his description here. The format is much more involved than described here. We can even supply examples of how to do particular hacks.

'''MadNad:''' Interestingly, I was able to convert a [http://madnad.com/ut2k3/Screenshots/q3dm7.jpg?link Quake3_Level] into a unreal map. Quite interesting. First i converted a *.bsp to a *.map in quake, then I made a level that was just a huge cube and converted it to *.t3d. With an external app (i'll have to find the name of it ) I was able to merge these two together. After some scaling and switching additive brushes in quake to subtractive brushes in ued and subtractive to additive, I compiled and had q3dm7 geometry. I don't necessarily recommend doing this, as it will take more time to fix than create it from scratch, but I thought I would share a little experience I had with this.

Legacy:T3D File

2009-01-20T10:04:19Z

Solarsys: Splitting T3D File to T3D Brush v2

The '''T3D file format''' or '''Unreal Text File''' holds a text list of Unreal map objects. An entire map can be saved as this file format, or just a single actor or brush.

Note that while brushes, their applied textures and light actors are saved, the [[Legacy:Unreal Geometry|Unreal Geometry]] itself is not saved: upon importing a T3D file the map must be built.

Copying objects from UnrealEd and pasting into a text editor produces the same format.

Unreal Text format

Exported brushes and (other) actors. See [[Legacy:T3D File|T3D file]].
* Created by:
** UnrealEd's File -> Import command
** UnrealEd's Brush -> Import command (see [[Legacy:Data Import And Export|Data Import and Export]] for more on both these commands).
** is this created by external stuff too?

===Exporting T3D ===
* Export the whole map
** File -> Export... (UnrealEd 1,2,3)
** File -> Export -> All.. (UnrealEd 4 - UT3)
* Export selected actors: File-> Export-> Selected Only ... (UnrealEd 4 only - UT3)
* Export one brush: Brush -> Export ...
* Copy/Paste: can copy paste any actor from any UnrealEd version to another one (Except for UnrealEd 4) or to any text editor such as notepad (Windows)

===Importing T3D ===

File -> Import...

(note importing may take a LONG time)

Overheard on #utjb... :-)

<tarquin> t3d stores brushes & actors but not texturing, right?
<Mychaeel> Texturing as well.
(melds into the opening speech from Reservoir Dogs...)
<DaveA>Stores links to textures, and texture transforms, but not the pixels themselves

The T3D format is a text file which stores information about map actors. It's in fact identical to what can be copied from UnrealEd to a text editor. An exported map looks like this:

<uscript>
Begin Map
Begin Actor Class=LevelInfo Name=LevelInfo0
TimeSeconds=17.008888
Summary=LevelSummary'Entry.LevelSummary'
DefaultGameType=Class'Botpack.UTIntro'
AIProfile(0)=23784352
AIProfile(1)=52
AIProfile(2)=41
AIProfile(3)=42
AIProfile(4)=40
AIProfile(5)=44
AIProfile(6)=45
AIProfile(7)=21846171
AvgAITime=0.000000
Level=LevelInfo'Entry.LevelInfo0'
Tag=LevelInfo
Region=(Zone=LevelInfo'Entry.LevelInfo0',iLeaf=-1)
Name=LevelInfo0
End Actor
Begin Actor Class=Brush Name=Brush0
MainScale=(SheerAxis=SHEER_ZX)
PostScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
TempScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
Level=LevelInfo'Entry.LevelInfo0'
Tag=Brush
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=464.000000,Y=-16.000000,Z=64.000000)
Begin Brush Name=Brush
Begin PolyList
Begin Polygon Item=OUTSIDE Texture=black1 Flags=4194304 Link=0
Origin -00160.000000,+00000.000000,+00128.000000
Normal +00000.000000,+00000.000000,+00001.000000
TextureU +00004.000000,+00000.000000,+00000.000000
TextureV +00000.000000,+00004.000000,+00000.000000
Vertex -00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,+00128.000000,+00128.000000
Vertex -00128.000000,+00128.000000,+00128.000000
End Polygon
...
End PolyList
End Brush
Brush=Model'Entry.Brush'
Name=Brush0
End Actor
Begin Actor Class=PlayerStart Name=PlayerStart0
Level=LevelInfo'Entry.LevelInfo0'
Tag=PlayerStart
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=183.134430,Y=-987.334167,Z=33.978027)
OldLocation=(X=-217.561523,Y=-44.538128,Z=-87.899948)
Name=PlayerStart0
End Actor
...
End Map</uscript>

External link: http://unreal.jall.org/tutorials/t3d.html (new URL)

=== T3D File Structure ===
== Ux,UT,UT200x Maps ==
<uscript>
Begin Map
Begin Actor Class=<ClassName>
...
End Actor
Begin Actor Class=<ClassName>
...
End Actor
...
End Level
End Map
</uscript>
== UT3 Maps ==
<uscript>
Begin Map
Begin Level NAME=PersistentLevel
Begin Actor Class=<ClassName>
...
End Actor
Begin Actor Class=<ClassName>
...
End Actor
...
End Level
Begin Surface
End Surface
End Map
</uscript>

Note: as UT3 T3D files have different header, any other not-UT3 t3d file can't be imported into UT3 editor (UnrealEd 4)

===T3D brush geometry===
Information geometry is contained in the following actors:
*Brush
*Mover (only UT and U1 game)

For more information about T3D brushes, see [http://wiki.beyondunreal.com/Legacy:T3D_Brush[T3D Brush]]

==T3D Utilities ==
* [[Legacy:MapScale|MapScale]] scales an entire .t3d file
* [[Legacy:MeshMaker|MeshMaker]] converts a prefab in .t3d format to a [[Legacy:Decoration|decoration]]
* [http://www.unrealroc.com/Converter.html UnrealROC] converters: from 3DMF, to VRML/X3D/OBJ (including textures et al).

==Related Topics ==
* [[Legacy:Data Import And Export|Data Import and Export]]
* [[Legacy:Brush Exporting And Importing|Brush Exporting And Importing]]
* [[Legacy:Brush Hacking|Brush Hacking]]
* [http://wiki.beyondunreal.com/Legacy:T3D_Brush[T3D Brush]]

'''Kefik:''' There can be also a tag 'CsgOper' which have one of two values ... 'CSG_Subtract' -> subtract the brush from space or 'CSG_Add' -> add this brush to shape.

'''Sobiwan:''' New to WIKI editing, but not using it. I was searching for the actual format of T3D and found [http://users.skynet.be/fa550206/Slug-Production/Data/OpenGL-Documents/T3D-File-Format/T3D-File-Format.htm Mongo's description] of [http://www.planetunreal.com Planetunreal] to be extremely helpful. I'll ask him (mongo@planetunreal.com) if we can use and/or edit his description here. The format is much more involved than described here. We can even supply examples of how to do particular hacks.

'''MadNad:''' Interestingly, I was able to convert a [http://madnad.com/ut2k3/Screenshots/q3dm7.jpg?link Quake3_Level] into a unreal map. Quite interesting. First i converted a *.bsp to a *.map in quake, then I made a level that was just a huge cube and converted it to *.t3d. With an external app (i'll have to find the name of it ) I was able to merge these two together. After some scaling and switching additive brushes in quake to subtractive brushes in ued and subtractive to additive, I compiled and had q3dm7 geometry. I don't necessarily recommend doing this, as it will take more time to fix than create it from scratch, but I thought I would share a little experience I had with this.

Legacy:T3D Brush

2009-01-20T09:44:03Z

Solarsys: /* Scaling up/down brushes */

A T3D Brush is geometry information contained into [http://wiki.beyondunreal.com/Legacy:T3D_File[T3D Files]].

The following actors used as brushes in T3D files:
*[http://wiki.beyondunreal.com/Legacy:Brush[Brushes]]
*[http://wiki.beyondunreal.com/Legacy:Mover[Movers]] (only in Unreal 1 and Unreal Tournament)

=== Actor structure ===
<uscript>Begin Actor Class=Brush Name=Brush0
MainScale=(SheerAxis=SHEER_ZX)
PostScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
TempScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
Level=LevelInfo'Entry.LevelInfo0'
Tag=Brush
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=464.000000,Y=-16.000000,Z=64.000000)
Rotation=(Yaw=49152)
Begin Brush Name=Brush
Begin PolyList
Begin Polygon Item=OUTSIDE Texture=black1 Flags=4194304 Link=0
Origin -00160.000000,+00000.000000,+00128.000000
Normal +00000.000000,+00000.000000,+00001.000000
TextureU +00004.000000,+00000.000000,+00000.000000
TextureV +00000.000000,+00004.000000,+00000.000000
Vertex -00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,+00128.000000,+00128.000000
Vertex -00128.000000,+00128.000000,+00128.000000
End Polygon
...
End PolyList
End Brush
Brush=Model'Entry.Brush'
Name=Brush0
End Actor</uscript>

*MainScale: scales up or down current brush before make it rotate.
*PostScale: scales up or down current brush after make it rotate.
*TempScale: unknown effect
*Location: where the brush is located in the map
*Rotation: contains up to 3 values
**Roll: X axis rotation
**Pitch: Y axis rotation
**Yaw: Z axis rotation
*Begin Polygon Item=OUTSIDE Texture=black1 Flags=4194304 Link=0
**Texture: texture applied to the current polygon with formatted string.
***[TextureName] for Unreal 1 / Unreal Tournament maps
***[PackageName.TextureName] for other UTx games.
**Origin: where the texture is centered
**Normal: normally, the perpendicular vector of the surface where the texture is applied
**Texture U,V: contains information about scaling and texture rotation
**PanU,PanV: only used in Unreal Tournament and Unreal 1
**Vertex: X,Y,Z coordinates of the specified vertex

Note: NumTriangles = NumVertices-Floor(NumVertices/3)

[[Image:texinfot3d.jpg]]

===Loading T3D brush geometry===

You must parse those informations correctly: PrePivot, Location, Rotation, MainScale, PostScale, TempScale, Polygon / Vertexes

<uscript>
FOR each vertex of each polygon of parsed brush DO:
do MainScale ... x *= MainScale[x], y *= MainScale[y], z *= MainScale[z]
do translation (-PrePivot[x], -PrePivot[y], -PrePivot[z])
do rotation Yaw, Pitch, Roll
do PostScale ... x *= PostScale[x], y *= PostScale[y], z *= PostScale[z]
do TempScale ... x *= TempScale[x], y *= TempScale[y], z *= TempScale[z]
do translation (Location[x], Location[y], Location[z])
ENDFOR
</uscript>

Note:
For Unreal Engine 3.x based maps (Unreal Tournament 2004 and 2003),PostScale,MainScale,TempScale and Rotation values are always null as the editor automatically updates vertices,origin and normal values when scaling up/down or rotating a brush.

Rotation matrix are the following:

<uscript>Roll Matrix-X Axis:
1, 0, 0, 0,
0, cos(roll),-sin(roll), 0,
0, sin(roll),cos(roll), 0,
0, 0, 0, 1</uscript>

<uscript>Pitch Matrix-Y Axis:
cos(pitch), 0, sin(pitch), 0,
0, 1, 0, 0,
-sin(pitch), 0,cos(pitch), 0,
0, 0, 0, 1)</uscript>

<uscript>Yaw Matrix-Z Axis:
cos(yaw), sin(yaw), 0, 0,
-sin(yaw), cos(yaw), 0, 0,
0, 0, 1, 0,
0, 0, 0, 1</uscript>

<uscript>Global Rotation Matrix=(Roll Matrix)*(Pitch Matrix)*(Yaw Matrix)</uscript>

Yaw, Roll and Pitch values are in radians. Original values from t3d files are in "Unreal format" where 2 rad = 65536.
For more information about Yaw, Pitch, Roll rotation matrix see http://mathworld.wolfram.com/EulerAngles.html.

=== Scaling up/down brushes ===
This operation is mainly needed when you want to port Unreal 1 or Unreal Tournament map to Unreal Tournament 2004 or Unreal Tournament 3.

To do so,considering ScaleFactor:
<uscript>
set Location = ScaleFactor*Location
set PrePivot = ScaleFactor*PrePivot
For each polygon
set Origin = ScaleFactor*Origin
For each vertex
set Vertex = ScaleFactor*Vertex
</uscript>

Usually scale factor values:
Unreal 1/Unreal Tournament to UT2003/UT2004/UT3: 1.25

=== Tools ===
*Python T3D loader (doesn't care about texture informations): http://carolina.mff.cuni.cz/~gib/ut_utils/unreal_t3d_loader.zip see readme.txt in zip file
*[[Legacy:MapScale|MapScale]] scales an entire .t3d file (only works for UT/U1 maps)

Legacy:T3D Brush

2009-01-20T09:39:25Z

Solarsys: Splitting T3D File to T3D Brush

A T3D Brush is geometry information contained into [http://wiki.beyondunreal.com/Legacy:T3D_File[T3D Files]].

The following actors used as brushes in T3D files:
*[http://wiki.beyondunreal.com/Legacy:Brush[Brushes]]
*[http://wiki.beyondunreal.com/Legacy:Mover[Movers]] (only in Unreal 1 and Unreal Tournament)

=== Actor structure ===
<uscript>Begin Actor Class=Brush Name=Brush0
MainScale=(SheerAxis=SHEER_ZX)
PostScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
TempScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
Level=LevelInfo'Entry.LevelInfo0'
Tag=Brush
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=464.000000,Y=-16.000000,Z=64.000000)
Rotation=(Yaw=49152)
Begin Brush Name=Brush
Begin PolyList
Begin Polygon Item=OUTSIDE Texture=black1 Flags=4194304 Link=0
Origin -00160.000000,+00000.000000,+00128.000000
Normal +00000.000000,+00000.000000,+00001.000000
TextureU +00004.000000,+00000.000000,+00000.000000
TextureV +00000.000000,+00004.000000,+00000.000000
Vertex -00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,+00128.000000,+00128.000000
Vertex -00128.000000,+00128.000000,+00128.000000
End Polygon
...
End PolyList
End Brush
Brush=Model'Entry.Brush'
Name=Brush0
End Actor</uscript>

*MainScale: scales up or down current brush before make it rotate.
*PostScale: scales up or down current brush after make it rotate.
*TempScale: unknown effect
*Location: where the brush is located in the map
*Rotation: contains up to 3 values
**Roll: X axis rotation
**Pitch: Y axis rotation
**Yaw: Z axis rotation
*Begin Polygon Item=OUTSIDE Texture=black1 Flags=4194304 Link=0
**Texture: texture applied to the current polygon with formatted string.
***[TextureName] for Unreal 1 / Unreal Tournament maps
***[PackageName.TextureName] for other UTx games.
**Origin: where the texture is centered
**Normal: normally, the perpendicular vector of the surface where the texture is applied
**Texture U,V: contains information about scaling and texture rotation
**PanU,PanV: only used in Unreal Tournament and Unreal 1
**Vertex: X,Y,Z coordinates of the specified vertex

Note: NumTriangles = NumVertices-Floor(NumVertices/3)

[[Image:texinfot3d.jpg]]

===Loading T3D brush geometry===

You must parse those informations correctly: PrePivot, Location, Rotation, MainScale, PostScale, TempScale, Polygon / Vertexes

<uscript>
FOR each vertex of each polygon of parsed brush DO:
do MainScale ... x *= MainScale[x], y *= MainScale[y], z *= MainScale[z]
do translation (-PrePivot[x], -PrePivot[y], -PrePivot[z])
do rotation Yaw, Pitch, Roll
do PostScale ... x *= PostScale[x], y *= PostScale[y], z *= PostScale[z]
do TempScale ... x *= TempScale[x], y *= TempScale[y], z *= TempScale[z]
do translation (Location[x], Location[y], Location[z])
ENDFOR
</uscript>

Note:
For Unreal Engine 3.x based maps (Unreal Tournament 2004 and 2003),PostScale,MainScale,TempScale and Rotation values are always null as the editor automatically updates vertices,origin and normal values when scaling up/down or rotating a brush.

Rotation matrix are the following:

<uscript>Roll Matrix-X Axis:
1, 0, 0, 0,
0, cos(roll),-sin(roll), 0,
0, sin(roll),cos(roll), 0,
0, 0, 0, 1</uscript>

<uscript>Pitch Matrix-Y Axis:
cos(pitch), 0, sin(pitch), 0,
0, 1, 0, 0,
-sin(pitch), 0,cos(pitch), 0,
0, 0, 0, 1)</uscript>

<uscript>Yaw Matrix-Z Axis:
cos(yaw), sin(yaw), 0, 0,
-sin(yaw), cos(yaw), 0, 0,
0, 0, 1, 0,
0, 0, 0, 1</uscript>

<uscript>Global Rotation Matrix=(Roll Matrix)*(Pitch Matrix)*(Yaw Matrix)</uscript>

Yaw, Roll and Pitch values are in radians. Original values from t3d files are in "Unreal format" where 2 rad = 65536.
For more information about Yaw, Pitch, Roll rotation matrix see http://mathworld.wolfram.com/EulerAngles.html.

=== Scaling up/down brushes ===
This operation is mainly needed when you want to port Unreal 1 or Unreal Tournament map to Unreal Tournament 2004 or Unreal Tournament 3.

To do so,considering ScaleFactor:
<uscript>For each actor in T3D File
set Location = ScaleFactor*Location
set PrePivot = ScaleFactor*PrePivot
For each polygon
set Origin = ScaleFactor*Origin
For each vertex
set Vertex = ScaleFactor*Vertex
</uscript>

Usually scale factor values:
Unreal 1/Unreal Tournament to UT2003/UT2004/UT3: 1.25

=== Tools ===
*Python T3D loader (doesn't care about texture informations): http://carolina.mff.cuni.cz/~gib/ut_utils/unreal_t3d_loader.zip see readme.txt in zip file
*[[Legacy:MapScale|MapScale]] scales an entire .t3d file (only works for UT/U1 maps)

Legacy:T3D Brush

2009-01-20T09:00:32Z

Solarsys: *MainScale: Scales up or down current brush before being rotated

Legacy:T3D File

2009-01-15T12:45:18Z

Solarsys: /* Loading T3D brush geometry */

The '''T3D file format''' or '''Unreal Text File''' holds a text list of Unreal map objects. An entire map can be saved as this file format, or just a single actor or brush.

Note that while brushes, their applied textures and light actors are saved, the [[Legacy:Unreal Geometry|Unreal Geometry]] itself is not saved: upon importing a T3D file the map must be built.

Copying objects from UnrealEd and pasting into a text editor produces the same format.

Unreal Text format

Exported brushes and (other) actors. See [[Legacy:T3D File|T3D file]].
* Created by:
** UnrealEd's File -> Import command
** UnrealEd's Brush -> Import command (see [[Legacy:Data Import And Export|Data Import and Export]] for more on both these commands).
** is this created by external stuff too?

===Exporting T3D ===
* Export the whole map: File -> Export...
* export one brush:
* export a part of a map: either save, delete discards and export as above, or select, copy, paste into a text editor and save as a T3D file

===Importing T3D ===

File -> Import...

(note importing may take a LONG time)

Overheard on #utjb... :-)

<tarquin> t3d stores brushes & actors but not texturing, right?
<Mychaeel> Texturing as well.
(melds into the opening speech from Reservoir Dogs...)
<DaveA>Stores links to textures, and texture transforms, but not the pixels themselves

The T3D format is a text file which stores information about map actors. It's in fact identical to what can be copied from UnrealEd to a text editor. An exported map looks like this:

<uscript>
Begin Map
Begin Actor Class=LevelInfo Name=LevelInfo0
TimeSeconds=17.008888
Summary=LevelSummary'Entry.LevelSummary'
DefaultGameType=Class'Botpack.UTIntro'
AIProfile(0)=23784352
AIProfile(1)=52
AIProfile(2)=41
AIProfile(3)=42
AIProfile(4)=40
AIProfile(5)=44
AIProfile(6)=45
AIProfile(7)=21846171
AvgAITime=0.000000
Level=LevelInfo'Entry.LevelInfo0'
Tag=LevelInfo
Region=(Zone=LevelInfo'Entry.LevelInfo0',iLeaf=-1)
Name=LevelInfo0
End Actor
Begin Actor Class=Brush Name=Brush0
MainScale=(SheerAxis=SHEER_ZX)
PostScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
TempScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
Level=LevelInfo'Entry.LevelInfo0'
Tag=Brush
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=464.000000,Y=-16.000000,Z=64.000000)
Begin Brush Name=Brush
Begin PolyList
Begin Polygon Item=OUTSIDE Texture=black1 Flags=4194304 Link=0
Origin -00160.000000,+00000.000000,+00128.000000
Normal +00000.000000,+00000.000000,+00001.000000
TextureU +00004.000000,+00000.000000,+00000.000000
TextureV +00000.000000,+00004.000000,+00000.000000
Vertex -00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,+00128.000000,+00128.000000
Vertex -00128.000000,+00128.000000,+00128.000000
End Polygon
...
End PolyList
End Brush
Brush=Model'Entry.Brush'
Name=Brush0
End Actor
Begin Actor Class=PlayerStart Name=PlayerStart0
Level=LevelInfo'Entry.LevelInfo0'
Tag=PlayerStart
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=183.134430,Y=-987.334167,Z=33.978027)
OldLocation=(X=-217.561523,Y=-44.538128,Z=-87.899948)
Name=PlayerStart0
End Actor
...
End Map</uscript>

External link: http://unreal.jall.org/tutorials/t3d.html (new URL)

===Loading T3D brush geometry===

You must parse those informations correctly: PrePivot, Location, Rotation, MainScale, PostScale, TempScale, Polygon / Vertexes

<uscript>
FOR each vertex of each polygon of parsed brush DO:
do MainScale ... x *= MainScale[x], y *= MainScale[y], z *= MainScale[z]
do translation (-PrePivot[x], -PrePivot[y], -PrePivot[z])
do rotation Yaw, Pitch, Roll
do PostScale ... x *= PostScale[x], y *= PostScale[y], z *= PostScale[z]
do TempScale ... x *= TempScale[x], y *= TempScale[y], z *= TempScale[z]
do translation (Location[x], Location[y], Location[z])
ENDFOR
</uscript>

Note:
For Unreal Engine 3.x based maps (Unreal Tournament 2004 and 2003),PostScale,MainScale,TempScale and Rotation values are always null as the editor automatically updates vertices,origin and normal values when scaling up/down or rotating a brush.

Rotation matrix are the following:

<uscript>Roll Matrix-X Axis:
1, 0, 0, 0,
0, cos(roll),-sin(roll), 0,
0, sin(roll),cos(roll), 0,
0, 0, 0, 1</uscript>

<uscript>Pitch Matrix-Y Axis:
cos(pitch), 0, sin(pitch), 0,
0, 1, 0, 0,
-sin(pitch), 0,cos(pitch), 0,
0, 0, 0, 1)</uscript>

<uscript>Yaw Matrix-Z Axis:
cos(yaw), sin(yaw), 0, 0,
-sin(yaw), cos(yaw), 0, 0,
0, 0, 1, 0,
0, 0, 0, 1</uscript>

<uscript>Global Rotation Matrix=(Roll Matrix)*(Pitch Matrix)*(Yaw Matrix)</uscript>

Yaw, Roll and Pitch values are in radians. Original values from t3d files are in "Unreal format" where 2 rad = 65536.
For more information about Yaw, Pitch, Roll rotation matrix see http://mathworld.wolfram.com/EulerAngles.html.

Unknown (correct) effect: SheerAxis

Texturing information: 
Texture U and Texture V: contains information about scaling and texture rotation 
PanU and PanV: only used in Unreal Tournament 
Origin: where the texture is centered 
Normal: normally, the perpendicular vector of the surface where the texture is applied. 

TextureU, TextureV, PanU, PanV, Origin and Normal are informations about how to apply texture for the polygon.

[[Image:texinfot3d.jpg]] 
Texture Scaling information is given from TexU and TexV values.
Python T3D loader (doesn't care about texture informations): http://carolina.mff.cuni.cz/~gib/ut_utils/unreal_t3d_loader.zip see readme.txt in zip file

=== Scaling up/down whole map ===
This operation is mainly needed when you want to port Unreal 1 or Unreal Tournament map to Unreal Tournament 2004 or Unreal Tournament 3.

To do so,considering ScaleFactor:
<uscript>For each actor in T3D File
set Location = ScaleFactor*Location
set PrePivot = ScaleFactor*PrePivot
If Actor==Brush
For each polygon
set Origin = ScaleFactor*Origin
For each vertex
set Vertex = ScaleFactor*Vertex
If Actor==StaticMesh
set DrawScale3D = ScaleFactor*DrawScale3D
</uscript>

Usually scale factor values:
Unreal 1/Unreal Tournament to UT2003/UT2004/UT3: 1.25

==T3D Utilities ==
* [[Legacy:MapScale|MapScale]] scales an entire .t3d file
* [[Legacy:MeshMaker|MeshMaker]] converts a prefab in .t3d format to a [[Legacy:Decoration|decoration]]
* [http://www.unrealroc.com/Converter.html UnrealROC] converters: from 3DMF, to VRML/X3D/OBJ (including textures et al).

==Related Topics ==
* [[Legacy:Data Import And Export|Data Import and Export]]
* [[Legacy:Brush Exporting And Importing|Brush Exporting And Importing]]
* [[Legacy:Brush Hacking|Brush Hacking]]

'''Kefik:''' There can be also a tag 'CsgOper' which have one of two values ... 'CSG_Subtract' -> subtract the brush from space or 'CSG_Add' -> add this brush to shape.

'''Sobiwan:''' New to WIKI editing, but not using it. I was searching for the actual format of T3D and found [http://users.skynet.be/fa550206/Slug-Production/Data/OpenGL-Documents/T3D-File-Format/T3D-File-Format.htm Mongo's description] of [http://www.planetunreal.com Planetunreal] to be extremely helpful. I'll ask him (mongo@planetunreal.com) if we can use and/or edit his description here. The format is much more involved than described here. We can even supply examples of how to do particular hacks.

'''MadNad:''' Interestingly, I was able to convert a [http://madnad.com/ut2k3/Screenshots/q3dm7.jpg?link Quake3_Level] into a unreal map. Quite interesting. First i converted a *.bsp to a *.map in quake, then I made a level that was just a huge cube and converted it to *.t3d. With an external app (i'll have to find the name of it ) I was able to merge these two together. After some scaling and switching additive brushes in quake to subtractive brushes in ued and subtractive to additive, I compiled and had q3dm7 geometry. I don't necessarily recommend doing this, as it will take more time to fix than create it from scratch, but I thought I would share a little experience I had with this.

Category:Legacy Delete Reply When You See It

2009-01-09T07:27:40Z

Solarsys:

{{Legacy category}}
A [[Legacy:WikiTag|WikiTag]].

It works like this:

:Person A writes: what does ''foo'' do?
:Person B answers: it does what it says above. [[:Category:Legacy Delete Reply When You See It]].
:''Person A reads the reply, sees the tag, and removes both question and answer from the page.''

No-one other than Person A should act on this Tag. '''However:'''
* if it's been ''weeks''... I mean ''weeks''...
* anybody who sees it might decide to change the tag to [[:Category:Legacy Refactor Me]].

Legacy:Oxygen

2009-01-09T07:27:19Z

Solarsys:

==Oxygen ==

===In Development ===

Work for the King of the Hill mutator. I'm mapping/modeling and skinning for it.

===Completed Work ===

====KH-Natico ====

It's a King of the Hill map set in a rocky, valley setting or something. Need's optimisation.

http://www.ut2003hq.com/pafiledb/pafiledb.php?action=file&id=1252

====Mutator: Low Ammo Warning ====

My first ever mutator. Basically you select the mutator, configure the ammo levels for each individual weapon and when your ammo drops below that level you get an on-screen warning.

Download ~20K - http://users.tpg.com.au/aspie/OxygenAmmoWarning.zip

Credit:
*LedZep for the Interface code (his comments are still in the source I think :rolleyes: )
*The author of the Interaction code.
*Mych and Tarquin for posting stuff in the BU forum which I found useful.
*Everyone on the Wiki and BUF-Coding and Mapping

===Bio ===

Well, technically I'm unemployed. I finished High School about 4 or 5 weeks ago and am in the period between secondary and tertiary education. I've applied to complete a Diploma in Software Development which will lead into a Bachelor of Information Technology / Commerce.

==Guest Book ==

'''EntropicLqd:''' Welcome to the Wiki - Enjoy your stay :)

'''Tarquin:''' Hello & welcome :D

'''ZxAnPhOrIaN:''' Hello and welcome to the wiki! :) :tup:

'''Oxygen:''' Thanks everyone, it's nice to be made welcome :) Group hug.

'''ZxAnPhOrIaN:''' The wiki is ALWAYS a friendly place! ;) :tup:

[[Category:Legacy Personal Page|{{PAGENAME}}]]

Legacy:Setting Up Subversion

2009-01-09T07:26:57Z

Solarsys:

This document is intended to walk you through a basic [[Legacy:Subversion|Subversion]] setup for use in developing Unreal-related projects. If you follow these instructions, in no time you will have a Subversion repository set up to track changes you make to all of your project-related files. If you will be working with other developers on the same project, you may also want to proceed to [[Legacy:Setting Up A Subversion Server|Setting up a Subversion Server]] after reading this page, to see how to make your new repository accessible to other people as well.

This document assumes you will be developing for an Unreal Tournament style of game such as [[Legacy:UT2004|UT2004]] and that you will be setting up your repository under Windows XP/2000/2003/etc. Many of the directions here will also apply to other cases, but you may need to do some tweaking.

==Download the Software==

The first step is to download the tools you'll need:

===Subversion===

This can be obtained from the Subversion web site (http://subversion.tigris.org/). A Windows installer is available under http://subversion.tigris.org/servlets/ProjectDocumentList?folderID=91 (look for the latest EXE file).

===TortoiseSVN===

While not strictly necessary (Subversion can be used as-is from the command line) you may also want to download the TortoiseSVN graphical client for Subversion, which allows Subversion to integrate nicely with the Windows file manager. This program can be obtained from the TortoiseSVN web site (http://tortoisesvn.tigris.org).

The instructions here assume you will be using TortoiseSVN in addition to the basic Subversion package.

==Install the Software==

If you downloaded one of the Windows installer files for Subversion, installing it should be a simple matter of double-clicking the installer and following the prompts. Likewise, the TortoiseSVN installer is pretty much the same deal.

'''Note:''' You will need to reboot your computer after installing TortoiseSVN.

==Create a Repository Directory==

First, you will need to create a folder to be used to hold all of your Subversion repositories. For the purposes of this example, we'll place our repositories under <tt>C:\Subversion</tt> (you may want to place this on a drive with a fair amount of spare disk space).

==Create a First Repository==

Now you will want at least one repository to store things in (that is the point of Subversion, after all). You can create as many repositories as you want under the main repository directory, but for now we'll start with one:

# Open the directory you created for repositories (<tt>C:\Subversion</tt>) in a Windows file browser window.
# Create a new folder in this directory with the name you would like to give to your new repository (<tt>UT_work</tt>).
# Once the new folder is created, right-click on it. The pop-up window which appears should contain a "TortoiseSVN" option. Under this menu item should be several choices, including "Create Repository here..."
# Choose "TortoiseSVN->Create Repository here..." from the menu. This will bring up a dialog box asking what type of repository to create.
# Choose "Native Filesystem (FSFS)" (you can really choose either one, but the Native Filesystem form is potentially faster, and in some cases easier to work with. Note: Do ''not'' use a Berkeley DB repository if it will be located on a network drive. Bad Things(tm) will happen.).

The new folder we just created is now a Subversion repository folder.

Next, we will create a "trunk" directory in our new repository (this isn't strictly required, but it is conventional to do things this way, and makes things a lot easier later when you get into sophisticated aspects of Subversion like branching). Subversion repositories aren't like normal directories, however, so we can't just create a directory using the file manager. Instead, we will need to use TortoiseSVN's "Repository Browser":

# Right click on a file or folder anywhere in your system (doesn't matter where).
# From the pop-up menu, select "TortoiseSVN->Repo-Browser".
#
A dialog box will pop up asking you for the URL of the repository to use. Type the following:
file:///C:/Subversion/UT_work

(This is the URL of our new repository, which is how we'll need to refer to it with most Subversion commands. Note that it uses forward-slashes (/), not backslashes (\))

# You should now see a "Repository Browser" window, with an expanded tree of folders (<tt>file:///C:</tt>, <tt>Subversion</tt>, and <tt>UT_work</tt>). Right click on the <tt>UT_work</tt> entry.
# From the pop-up menu, select "Create Folder...", and when it asks for the name, type <tt>trunk</tt>
# It will then ask you for a log message. This is where you describe why you're doing this for future reference. Since we're just doing initial setup here, put in something like "Intitial Setup" and click "OK".

If you now expand the <tt>UT_work</tt> entry, you should see a <tt>trunk</tt> folder underneath it. That's enough for a basic setup of our repository, time to move on to actually using it.

{{innerbox|
Alternately, you can use the Subversion command-line tools to create a new repository using the following commands:
svnadmin create C:\Subversion\UT_work –fs-type fsfs
svn mkdir file:///C:/Subversion/UT_work/trunk

(Don't create the <tt>UT_work</tt> directory first, the <tt>svnadmin create</tt> command will do it for you)

}}

==Set up Your Working Directory==

At this stage in the process, most Subversion documentation tells you that you should use the Subversion "import" command to import a current snapshot of your project tree into the repository. For most projects, this makes sense, because each project has its own separate set of directories with only its files. For Unreal development, however, the situation is a bit different because the files being worked on are usually scattered around several directories which contain a bunch of other files. If we're working on a map, for example, we don't want to import our whole <tt>Maps</tt> directory into the repository, because that would include tons of stock files that really aren't part of the project we're working on (and don't need to be tracked), making the repository huge and difficult to work with.

For this reason, we're going to diverge a bit here from the normal procedure for setting up Subversion repositories. The first thing we will do instead is just associate our working directories with the (empty) repository we just created, by doing a "checkout".

# Go into a file browser window and locate the main Unreal folder you'll be developing things under, which we want to be at the top level of our project (for example, <tt>C:\UT2004</tt>).
# Right-click on this folder and from the pop-up menu, select "Checkout..."
#
The "Checkout" dialog box will ask for the URL of the repository to use. Type the following and press "OK":
file:///C:/Subversion/UT_work/trunk

(this is the URL which refers to the "trunk" portion of the "UT_work" repository we set up in the previous step)

Once the checkout has completed, press F5 (refresh) in your file browser and you should see that the folder now shows up with a little green check-mark next to it. This indicates that the folder is associated with a Subversion repository, and that it is up to date (Note: sometimes the check mark doesn't show up in the tree view of the explorer).

The next step is to actually populate our repository with the files that are part of our project:

# Again, right-click on the working directory folder (<tt>C:\UT2004</tt>)
# You will see a new option in the pop-up menu named "Commit...". Choose this option.
# An "Enter Log Message" dialog box will appear. This is where you write a brief description of what the change is that you're applying to the repository. Enter something like "Initial Import" in the text box at the top (If you've already been doing a lot of work on this project before setting up the repository, it would probably also be a good idea to write a few notes about what the current state of things is at the moment so if you go back some time later and want to know what the state of development was at this point, you can look at the Subversion comments for this revision and get some idea.)
# In the bottom part of the "Enter Log Message" window, you will see a listing of all of the files under this directory (and all of its subdirectories), with checkboxes next to them (this display can take a while to display while TortoiseSVN goes through all the directories to see what's there, so be patient). This is where you specify what files you want to check in to Subversion. Find the files that are part of your project and check their checkboxes.
# When you've selected all of the right files, press the "OK" button. TortoiseSVN will show a "SVN Commit" dialog box with the status of the operation. Once it's completed, press "OK".

Congratulations! Your project files are now in a Subversion repository!

==Basics of Using Subversion==

There are many documents available out there which are quite good at explaining how to use Subversion and TortoiseSVN (including the help files that come with both programs, which are available under your Start Programs menu), so we won't go into a lot of detail here, but here's the basic procedure of how things should work most of the time:

* Work on your files the same way you always do.
* Periodically, commit things back to the Subversion repository by right-clicking on your work directory and using the "Commit..." option.
* If other people are working on files in the same repository, you will periodically need to update your versions to match what other people have committed to the repository. To do this, right-click on the work directory and choose "Update".
* Note that if you rename files, Subversion won't automatically know what you've done, and will just see that the files aren't there under the name it expects, and will assume they've been deleted (and mark them as such in the repository). If you want to rename a file, make sure you do the following instead:
*# Right-click on the file, and select the "TortoiseSVN" submenu.
*# Choose the "Rename" option.

==Setting up a Subversion Server==

If all you want to do is keep backups and a change history for your own work, and you're the only one who's going to need to access your repository, then you can just stop here and use things as we've set them up so far.

If, however, you are going to want other people to be able to access the repository you've just created (and thus take advantage of some of the most powerful features of Subversion), you will want to proceed to [[Legacy:Setting Up A Subversion Server|Setting up a Subversion Server]].

[[Category:Legacy Tutorial|{{PAGENAME}}]]

Help:Talk pages

2009-01-09T07:26:36Z

Solarsys:

Every wiki page has an associated talk page which can be used for discussion and communicating with other users. Talk pages can be accessed by clicking the ''Discussion'' tab at the top of the page. Simply edit the page as normal to add your comment.

A talk page is actually very similar to any other wiki page, but it is in the 'talk' namespace, to keep it separate from the articles in the 'main' namespace (See [[Help:namespaces]]) As with any wiki page, you can edit it, link to it, and view the editing history.

== Editing conventions on talk pages ==
Having discussions on a free-form wiki page will seem strange at first. It helps if everyone follows some simple editing conventions:

* Always sign your name after your comments. Use the four tildas '<tt><nowiki>~~~~</nowiki></tt>' wiki syntax (or the toolbar button)
* Start a new discussion with a <tt><nowiki>==level 2 heading==</nowiki></tt> at the bottom of the page (or use the '+' tab)
* Indent replies with colons (':') at the beginning of the line.

== Example ==
Here is an example discussion, following the talk page conventions:

{| align="center" {{Prettytable}}
|-
|{{Hl2}} |'''Wiki text'''
|{{Hl2}} |'''Formatted talk page'''
|-
|

<tt><nowiki>== More spiders information needed ==</nowiki></tt> 
<tt><nowiki>This page has a lot of detail about the web, but I really dont understand a single word of it, and it doesn't mention the spider once -- [[User:Bob Smith|Bob Smith]] 18:07, 26 August 1991 (UTC)</nowiki></tt> 
<tt><nowiki>: No no. This page is talking about the "world wide web". I have added a clarification at the top - [[User:Simon Brown|Simon Brown]] 11:21, 28 August 1991(UTC)</nowiki></tt> 
<tt><nowiki>:: Oh I see... So what's the big deal about hyperlinked documents? Seems like a stupid idea to me. -- [[User:Bob Smith|Bob Smith]] 14:11, 3 September 1991 (UTC)</nowiki></tt> 
<tt><nowiki>::: Well I think we should have some information about it here on our wiki, but you're probably right. It'll never catch on. -- [[User:Simon Brown|Simon Brown]] 21:55, 3 September 1991 (UTC)</nowiki></tt>
|
== More spiders information needed ==
This page has a lot of detail about the web, but I really dont understand a single word of it, and it doesn't mention the spider once -- [[User:Bob Smith|Bob Smith]] 18:07, 26 August 1991 (UTC)
: No no. This page is talking about the "world wide web". I have added a clarification at the top - [[User:Simon Brown|Simon Brown]] 11:21, 28 August 1991(UTC)
:: Oh I see... So what's the big deal about hyperlinked documents? Seems like a stupid idea to me. -- [[User:Bob Smith|Bob Smith]] 14:11, 3 September 1991 (UTC)
::: Well I think we should have some information about it here on our wiki, but you're probably right. It'll never catch on. -- [[User:Simon Brown|Simon Brown]] 21:55, 3 September 1991 (UTC)
|}

== Editing discussions ==
Having discussions on a free-form wiki page will seem strange at first. It has some advantages over the conventional rigid forum format, but it can get a little messy. As with other wiki pages, anyone can help with tidying up discussions, to conform to the editing conventions e.g. add signatures and headings where they are missing.

Clearly we also have the opportunity to edit other people's comments. It is generally bad etiquette to modify somebody else's wording (Better to just add your own comment with your corrections) But it can be acceptable to...

;Modify discussion headings
:Change wording or append words to the discussion headings, to better describe the topic of discussion. Note that good descriptive headings become important when many discussions start to fill the page.
;Move discussions to a different page
:If discussions are put in the wrong place on the wiki, and are better associated with different talk page, then you could just move the discussion by cut & paste. This is potentially confusing, for the people posting, but can be important for keeping things tidy. You could leave the discussion in the wrong place for a few days/weeks grace before tidying it. You could leave a link behind explaining that a discussion was moved, or if not, you should link within the edit summary.
;Delete discussions when they are out-of-date
:Discussions can often get left lying around on a talk page long after the issue is no longer relevant. It's usually a good idea to reply to saying "I think this is now resolved", but sooner or later it's time to just blow away the old discussions (they are of course preserved in the editing history)
;Split a post into several discussions
:It may appropriate to do this, if somebody has raised several points which need to be answered separately. However you should always be respectful to other people's words. Does their post still make sense if you split it up?

== Building articles - Discussing articles ==
It is usually best to keep focused on the task of building a wiki article, and use discussion pages only to support this process. The topic of conversation should generally revolve around what needs to be done to make the associated article better. Remember that editing the article itself is often a more effective means of communicating. It can be more difficult, requiring you to balance your views alongside those of others, but it can also be more rewarding. This is how the community of wiki editors will make progress. Often it will feel more natural to engage in heated debate on a talk page (or indeed any other contact channel) but in fact the wiki article itself can offer a powerful means of reaching middle-ground. Think about how to portray both sides of the argument (e.g. listing advantages and disadvantages) and you may find the debate evaporates.

== User Talk pages ==
A "user talk page" is a talk page associated with somebody's "user page" (See [[Help:User page]]) This is a place to leave messages for a particular wiki user.

This can function as a kind of messaging system. Users receive a prominent notification when new messages have been left on their talk page. They may be notified by email as well, although this cannot always be relied upon (since the email notification feature must be activated by supplying a valid email address, and clicking a confirmation link). If you don't get a response to your user talk page message, try looking for other contact details which they may have supplied on their user page.

Note that the messages are not private, and others can join in the conversation.

[[Category:Help|{{PAGENAME}}]]

Legacy:View Fog

2009-01-09T07:26:15Z

Solarsys:

'''View Fog''' is a simple method of adding [[Legacy:Fog|fog]] to a map or an area in a map. It works by simply tinting the rendered scene by a specified amount. View Fog is sometimes also referred to as "fake fog". It uses practically no rendering resources, so it is very cheap resource-wise, but it is not that realistic. Often an underwater area will have a blueish view fog.

==Setting Up View Fog in Unreal Tournament==

In [[Legacy:Unreal Tournament|Unreal Tournament]], view fog is specific to the zone containing the camera. It is specified by the ''ViewFlash'' and ''ViewFog'' variables in the zone's [[Legacy:ZoneInfo (UT)|ZoneInfo]]. Here's a sample configuration:

{|

|-
|ViewFlash X
|-0.5
|-
|ViewFlash Y
|-0.5
|-
|ViewFlash Z
|-0.5
|-
|ViewFog X
|0.5
|-
|ViewFog Y
|0.5
|-
|ViewFog Z
|0.5
|}

==Setting Up View Fog in UT2003==

View Fog does not appear to work properly in [[Legacy:UT2003|UT2003]], however, the variables for it are still present so theoretically it may still work on some graphics hardware. View Fog is controlled by [[Legacy:PhysicsVolume|PhysicsVolume]]s in UT2003. Specifically, PhysicsVolumes are used. To set up View Fog, simply set the PhysicsVolume->ViewFog property to whatever color you want the screen to be tinted.

'''Tarquin:''' so does it work or not?

'''SuperApe:''' I'm wondering if the author meant to say ViewFlash doesn't work in UT200x, not ViewFog. Distance fog seems to work fine. But the issue is confused by the properties ViewFog and FlashFog in [[Legacy:DamageType|DamageType]]. I found this page through a search for that stuff.

Legacy:Offline Wiki

2009-01-09T07:25:24Z

Solarsys:

{{innerbox|"...insanely useful..." – '''BeyondUnreal'''

}}

If you can't spend as much time surfing the Unreal Wiki as you like because your Internet provider charges you by the minute or you don't even have an Internet connection at home, we're providing the entire Unreal Wiki content as a single download for you.

* The offline Wiki allows you to conveniently '''browse the entire Unreal Wiki content''' from your local hard disk without requiring an Internet connection.

* All '''dynamic features''' (such as searching the Wiki, editing pages, and viewing older page revisions or version diffs) lead back to the live online Wiki.

* Given that dozens of pages are added and changed every day on the Unreal Wiki, your offline copy is bound to be '''outdated''' after a while. Be sure to check back for updates regularly on [[Legacy:Recent Changes|Recent Changes]].

Note that even though the content on Unreal Wiki is free for use, it is nonetheless subject to our [[Legacy:Project Copyright|copyright statement]]. The offline Wiki download is '''for private use only''' and not to be distributed commercially.

==Download the Unreal Wiki==

You can obtain the downloadable Unreal Wiki from the following location:

{|
|-
|'''BeyondUnreal.com'''
|[http://download.beyondunreal.com/fileworks.php/wiki/unrealwiki-offline.zip unrealwiki-offline.zip]
|}

'''Note:''' This version of the offline Wiki is the last-generated version of the old UseMod-powered Unreal Wiki from April 5 2008.

==Installation==

* Extract the archive you downloaded into a directory of your liking.

* Start browsing your offline Wiki copy by opening '''(start).html''' or '''(start)''' in your web browser.

Every page on the offline Wiki has a link to its live online version at the very bottom of the page, along with a timestamp telling you when the copy was generated from the live Wiki.

The offline Wiki should be compatible with all platforms that support .zip files and long file names up to 32 characters. If you have any problems downloading or using the offline Wiki, leave a message on the [[:{{SUBJECTSPACE}}:{{BASEPAGENAME}}/Discuss|discussion page]].

----

[[:{{SUBJECTSPACE}}:{{BASEPAGENAME}}/Discuss]] this page.

Legacy:Project FAQ

2009-01-09T07:24:58Z

Solarsys:

Frequently asked questions about the project. Feel free to:
* post questions about the project
* post answers to new questions
* add multiple answers to questions

; I want to write about the next generation Unreal engine? How am I to organise it, and where to put it? : Start at [[Legacy:UT2003|UT2003]]. You'll find the current page creation and editing policy on UT2003 specifics.

; What is this site? Aren't there enough Unreal Editing sites already? : Yes! But this site is not "just another tute site." This site began with the aim to consolidate a fractured knowledge base: It's now two years since Unreal Tournament has been released, and editing info is still hard to find on the web. I think we can change that. I also think that when the next generation of Unreal games is released it would be better for the mapping community if everyone's titbits of information about the new engine were grouped together, instead of scattered around. – [[Legacy:Tarquin|Tarquin]]

; Why are so many pages unfinished? : Articles don't have a single author. If a page seems unfinished to you, add to it. – [[Legacy:Tarquin|Tarquin]]

; How do I search the site? : There is a search box at the top and bottom of every page on this site. Just enter some terms (separated by blanks) and hit Enter. The Wiki will show you the pages that match your query best. (Enclose terms that contain blanks of their own in double quotes.)

; How does it work? :This is a completely open project. Everybody & anybody can contribute. You are an editor: you can edit any page by clicking the link at the bottom and you can add new pages. You have as much say the content of the site as I do. The site grows quickly because anyone can add or change material straight away. To get started, see [[Legacy:New Contributors Quick Start|New Contributors Quick Start]]. [[Legacy:Wiki Markup|Wiki markup]] is very simple to learn. Go and see [http://www.wikipedia.com/ Wikipedia] for an idea of what can be accomplished with the Wiki system. – [[Legacy:Tarquin|Tarquin]]

; What are all the ? links? : Those are links that people have made to pages that don't yet exist on the system. When you type text <nowiki>[[Legacy:Like This|like this]]</nowiki> in a page, Wiki creates a link. If the text in the double square brackets isn't the name of an existing page, the new link will lead to a form where the new page can be created. Once the page has been created, the text will become normal link. See also [[Legacy:Wiki FAQ|Wiki FAQ]] – Tarquin

; Anyone can edit my text? Ewwww! : Weird, isn't it? The first article I submitted to Wikipedia was edited within a day or so, and even though I knew it would happen, it was very strange seeing pieces of my text embedded in somebody else's. you get used to it. Changes or additions to the wiki become part of a whole that is bigger than any single writer. – Tarquin

; Isn't it all going to turn into one big ''horrible'' mess? : Probably. But it's fairly easy to re-organize pages or move material from one to another. For example, at the time of writing (only two days into the project) we have pages called "Brush" and "Brushes". We also seem to be tending towards encyclopaedia-style article headers, rather than titles like "how to apply lighting". Neither of these things is a problem. It's also fine to have articles that don't belong in a strict hierarchy. We can organize material later – if you see a link which you think would be better off in a different place, you can move it. – Tarquin

; I'm not l33t enough to contribute. :Anyone can help. If you've ever opened UnrealEd, you're bound to know something. If you've only opened it once, you have the beginner's perspective – if the articles aimed at beginners don't make sense to you, ''change'' them so they do! – [[Legacy:Tarquin|Tarquin]]

; Would you like an article on (topic)? Could you add a link to (site)? : If you think it's relevant to the content of this Wiki, then yes we probably do, but the real answer to the first question is: it's up to you. The answer to the second question is: No. You can add it yourself. :D

; What if idiots damage the site? : Other Wiki sites say that this isn't a problem. And, actually, we have a full-time Idiot-Proofer on Staff. Admittedly, gaming communities do seem to have their share of idiots. The server keeps past versions of articles, so while anyone can damage the site, anyone who spots damage can immediately fix it – look for the "View Other Revisions" link. Editing and saving a past revision over-writes the current version of a page. Admins keep zipped backups of the entire site as an extra precaution. IPs are publicly logged on the [[Legacy:Recent Changes|Recent Changes]] pages, and if necessary they can be blocked. Admins can also lock the entire site, making it read-only. – [[Legacy:Tarquin|Tarquin]]
: see also [[Legacy:Wiki Protection|Wiki Protection]] for info on how you can help

; Do I need to register? :No. Registration is optional. All it will do is show your user name on the [[Legacy:Recent Changes|Recent Changes]] list instead of your IP, and save your preferences for viewing the site. Click on ''preferences'' and enter a name and password to register. You're also invited to create a [[:Category:Legacy Personal Page|personal page]] for yourself. If you like, you can make your name in the list a wiki link and create a page for your contact details, biog, and guestbook. – [[Legacy:Tarquin|Tarquin]]

; Who invented Wiki? Who wrote this script? :The very first Wiki is the [http://www.c2.com/cgi/wiki?WelcomeVisitors Portland Pattern Repository]. It's usually called WikiWiki, or Ward's Wiki after its creator. This site runs on a perl script called [http://www.usemod.com/cgi-bin/wiki.pl?UseModWiki UseModWiki] created by Clifford Adams, with various nifty patches and Mychaeel's markup parser, [[Legacy:Wookee|Wookee]].

; Who runs this site? :You do. There's a list of people working on the site at [[:Category:Legacy Personal Page]], you're free to add your name to the list. The content of the site is decided by people who decide to contribute. The topics list on the main page is gradually being shaped by individual additions. If you want to add something that doesn't fall under one of the headings, add a new heading. (The site is hosted by BeyondUnreal, current [[Legacy:Wiki Admin|Wiki admin]]s are Tarquin and [[Legacy:Mychaeel|Mychaeel]].)

; I have an idea for a radical new organization of the site : Try it! We can always switch back if it doesn't work.

; What do admins do? : As little as possible. The only things [[Legacy:Wiki Admin|wiki admin]]s can do that you can't are:
; * Rename pages (anyone can port content to a new page, but this function renames all the links throughout the site too)
; * Delete pages (same again)
; * Ban IPs
; * Lock the entire site (see [[Legacy:Wiki Protection|Wiki Protection]])

; How do I become an admin? : Technically, by being told the admin password by another admin.
: But – why do you want to be one, in the first place? There's no special honor to it and there's little an admin can do that a "normal user" can't (see the question above). Admin privileges are a technical necessity, and they come with a responsibility; so if you want to be an Unreal Wiki admin, you'll be only likely to convince one of the current admins if there's an actual need for another admin and if they have the impression that you're trustworthy (in Unreal Wiki terms). →[[Legacy:Mychaeel|Mychaeel]]
: I don't think there's a need for new admins. I use my admin powers maybe once a week or even less, for the occasional page renaming. Editorial control is something everyone already has. →[[Legacy:Tarquin|Tarquin]]

----

Feel free to add questions, or add new answers to existing questions.

==Related Topics==
* [[Legacy:New Contributors Quick Start|New Contributors Quick Start]]
* [[Legacy:Wiki FAQ|Wiki FAQ]]
* [[Legacy:MetaTopics|MetaTopics]]
* [[Legacy:Project Discussion|Project Discussion]]
* [[Legacy:Unreal Mapping FAQ|Unreal Mapping FAQ]]

[[Category:Legacy FAQ|{{PAGENAME}}]]

Category:Legacy Delete Reply When You See It

2009-01-08T20:37:45Z

Solarsys: Undo revision 33871 by OudomZeldr (Talk)

Legacy:Offline Wiki

2009-01-08T20:36:55Z

Solarsys: Undo revision 33866 by OulilAouro (Talk)

Help:Talk pages

2009-01-08T20:36:37Z

Solarsys: Undo revision 33867 by LetonOmona (Talk)

Legacy:View Fog

2009-01-08T20:36:19Z

Solarsys: Undo revision 33868 by CnaliVisit (Talk)

Legacy:Setting Up Subversion

2009-01-08T20:36:02Z

Solarsys: Undo revision 33869 by BasliRorac (Talk)

Legacy:Project FAQ

2009-01-08T20:35:32Z

Solarsys: Undo revision 33870 by VieltGetel (Talk)

Legacy:Oxygen

2009-01-08T20:35:06Z

Solarsys: Undo revision 33865 by TrocdArcal (Talk)

Legacy:T3D File

2009-01-02T10:39:32Z

Solarsys: /* Loading T3D brush geometry */

The '''T3D file format''' or '''Unreal Text File''' holds a text list of Unreal map objects. An entire map can be saved as this file format, or just a single actor or brush.

Note that while brushes, their applied textures and light actors are saved, the [[Legacy:Unreal Geometry|Unreal Geometry]] itself is not saved: upon importing a T3D file the map must be built.

Copying objects from UnrealEd and pasting into a text editor produces the same format.

Unreal Text format

Exported brushes and (other) actors. See [[Legacy:T3D File|T3D file]].
* Created by:
** UnrealEd's File -> Import command
** UnrealEd's Brush -> Import command (see [[Legacy:Data Import And Export|Data Import and Export]] for more on both these commands).
** is this created by external stuff too?

===Exporting T3D ===
* Export the whole map: File -> Export...
* export one brush:
* export a part of a map: either save, delete discards and export as above, or select, copy, paste into a text editor and save as a T3D file

===Importing T3D ===

File -> Import...

(note importing may take a LONG time)

Overheard on #utjb... :-)

<tarquin> t3d stores brushes & actors but not texturing, right?
<Mychaeel> Texturing as well.
(melds into the opening speech from Reservoir Dogs...)
<DaveA>Stores links to textures, and texture transforms, but not the pixels themselves

The T3D format is a text file which stores information about map actors. It's in fact identical to what can be copied from UnrealEd to a text editor. An exported map looks like this:

<uscript>
Begin Map
Begin Actor Class=LevelInfo Name=LevelInfo0
TimeSeconds=17.008888
Summary=LevelSummary'Entry.LevelSummary'
DefaultGameType=Class'Botpack.UTIntro'
AIProfile(0)=23784352
AIProfile(1)=52
AIProfile(2)=41
AIProfile(3)=42
AIProfile(4)=40
AIProfile(5)=44
AIProfile(6)=45
AIProfile(7)=21846171
AvgAITime=0.000000
Level=LevelInfo'Entry.LevelInfo0'
Tag=LevelInfo
Region=(Zone=LevelInfo'Entry.LevelInfo0',iLeaf=-1)
Name=LevelInfo0
End Actor
Begin Actor Class=Brush Name=Brush0
MainScale=(SheerAxis=SHEER_ZX)
PostScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
TempScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
Level=LevelInfo'Entry.LevelInfo0'
Tag=Brush
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=464.000000,Y=-16.000000,Z=64.000000)
Begin Brush Name=Brush
Begin PolyList
Begin Polygon Item=OUTSIDE Texture=black1 Flags=4194304 Link=0
Origin -00160.000000,+00000.000000,+00128.000000
Normal +00000.000000,+00000.000000,+00001.000000
TextureU +00004.000000,+00000.000000,+00000.000000
TextureV +00000.000000,+00004.000000,+00000.000000
Vertex -00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,+00128.000000,+00128.000000
Vertex -00128.000000,+00128.000000,+00128.000000
End Polygon
...
End PolyList
End Brush
Brush=Model'Entry.Brush'
Name=Brush0
End Actor
Begin Actor Class=PlayerStart Name=PlayerStart0
Level=LevelInfo'Entry.LevelInfo0'
Tag=PlayerStart
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=183.134430,Y=-987.334167,Z=33.978027)
OldLocation=(X=-217.561523,Y=-44.538128,Z=-87.899948)
Name=PlayerStart0
End Actor
...
End Map</uscript>

External link: http://unreal.jall.org/tutorials/t3d.html (new URL)

===Loading T3D brush geometry===

You must parse those informations correctly: PrePivot, Location, Rotation, MainScale, PostScale, TempScale, Polygon / Vertexes

<uscript>
FOR each vertex of each polygon of parsed brush DO:
do MainScale ... x *= MainScale[x], y *= MainScale[y], z *= MainScale[z]
do translation (-PrePivot[x], -PrePivot[y], -PrePivot[z])
do rotation Yaw, Pitch, Roll
do PostScale ... x *= PostScale[x], y *= PostScale[y], z *= PostScale[z]
do TempScale ... x *= TempScale[x], y *= TempScale[y], z *= TempScale[z]
do translation (Location[x], Location[y], Location[z])
ENDFOR
</uscript>

Note:
For Unreal Engine 3.x based maps (Unreal Tournament 2004 and 2003),PostScale,MainScale,TempScale and Rotation values are always null as the editor automatically updates vertices,origin and normal values when scaling up/down or rotating a brush.

Rotation matrix are the following:

<uscript>Roll Matrix-X Axis:
1, 0, 0, 0,
0, cos(roll),-sin(roll), 0,
0, sin(roll),cos(roll), 0,
0, 0, 0, 1</uscript>

<uscript>Pitch Matrix-Y Axis:
cos(pitch), 0, sin(pitch), 0,
0, 1, 0, 0,
-sin(pitch), 0,cos(pitch), 0,
0, 0, 0, 1)</uscript>

<uscript>Yaw Matrix-Z Axis:
cos(yaw), sin(yaw), 0, 0,
-sin(yaw), cos(yaw), 0, 0,
0, 0, 1, 0,
0, 0, 0, 1</uscript>

<uscript>Global Rotation Matrix=(Roll Matrix)*(Pitch Matrix)*(Yaw Matrix)</uscript>

Yaw, Roll and Pitch values are in radians. Original values from t3d files are in "Unreal format" where 2 rad = 65536.
For more information about Yaw, Pitch, Roll rotation matrix see http://mathworld.wolfram.com/EulerAngles.html.

Unknown (correct) effect: SheerAxis

Texturing information: 
Texture U and Texture V: contains information about scaling and texture rotation 
PanU and PanV: only used in Unreal Tournament 
Origin: where the texture is centered 
Normal: normally, the perpendicular vector of the surface where the texture is applied. 

TextureU, TextureV, PanU, PanV, Origin and Normal are informations about how to apply texture for the polygon.

[[Image:texinfot3d.jpg]] 
Texture Scaling can be found using this formula:
<uscript>
TexScaleX=1/(TextureU_x²+TextureV_x²)
TexScaleY=1/(TextureU_y²+TextureV_y²)
TexScaleZ=1/(TextureU_z²+TextureV_z²)
</uscript>
Python T3D loader (doesn't care about texture informations): http://carolina.mff.cuni.cz/~gib/ut_utils/unreal_t3d_loader.zip see readme.txt in zip file

=== Scaling up/down whole map ===
This operation is mainly needed when you want to port Unreal 1 or Unreal Tournament map to Unreal Tournament 2004 or Unreal Tournament 3.

To do so,considering ScaleFactor:
<uscript>For each actor in T3D File
set Location = ScaleFactor*Location
set PrePivot = ScaleFactor*PrePivot
If Actor==Brush
For each polygon
set Origin = ScaleFactor*Origin
For each vertex
set Vertex = ScaleFactor*Vertex
If Actor==StaticMesh
set DrawScale3D = ScaleFactor*DrawScale3D
</uscript>

Usually scale factor values:
Unreal 1/Unreal Tournament to UT2003/UT2004/UT3: 1.25

==T3D Utilities ==
* [[Legacy:MapScale|MapScale]] scales an entire .t3d file
* [[Legacy:MeshMaker|MeshMaker]] converts a prefab in .t3d format to a [[Legacy:Decoration|decoration]]
* [http://www.unrealroc.com/Converter.html UnrealROC] converters: from 3DMF, to VRML/X3D/OBJ (including textures et al).

==Related Topics ==
* [[Legacy:Data Import And Export|Data Import and Export]]
* [[Legacy:Brush Exporting And Importing|Brush Exporting And Importing]]
* [[Legacy:Brush Hacking|Brush Hacking]]

'''Kefik:''' There can be also a tag 'CsgOper' which have one of two values ... 'CSG_Subtract' -> subtract the brush from space or 'CSG_Add' -> add this brush to shape.

'''Sobiwan:''' New to WIKI editing, but not using it. I was searching for the actual format of T3D and found [http://users.skynet.be/fa550206/Slug-Production/Data/OpenGL-Documents/T3D-File-Format/T3D-File-Format.htm Mongo's description] of [http://www.planetunreal.com Planetunreal] to be extremely helpful. I'll ask him (mongo@planetunreal.com) if we can use and/or edit his description here. The format is much more involved than described here. We can even supply examples of how to do particular hacks.

'''MadNad:''' Interestingly, I was able to convert a [http://madnad.com/ut2k3/Screenshots/q3dm7.jpg?link Quake3_Level] into a unreal map. Quite interesting. First i converted a *.bsp to a *.map in quake, then I made a level that was just a huge cube and converted it to *.t3d. With an external app (i'll have to find the name of it ) I was able to merge these two together. After some scaling and switching additive brushes in quake to subtractive brushes in ued and subtractive to additive, I compiled and had q3dm7 geometry. I don't necessarily recommend doing this, as it will take more time to fix than create it from scratch, but I thought I would share a little experience I had with this.

File:Texinfot3d.jpg

2009-01-02T10:35:11Z

Solarsys:

Legacy:T3D File

2009-01-02T10:34:54Z

Solarsys: /* Loading T3D brush geometry */

The '''T3D file format''' or '''Unreal Text File''' holds a text list of Unreal map objects. An entire map can be saved as this file format, or just a single actor or brush.

Note that while brushes, their applied textures and light actors are saved, the [[Legacy:Unreal Geometry|Unreal Geometry]] itself is not saved: upon importing a T3D file the map must be built.

Copying objects from UnrealEd and pasting into a text editor produces the same format.

Unreal Text format

Exported brushes and (other) actors. See [[Legacy:T3D File|T3D file]].
* Created by:
** UnrealEd's File -> Import command
** UnrealEd's Brush -> Import command (see [[Legacy:Data Import And Export|Data Import and Export]] for more on both these commands).
** is this created by external stuff too?

===Exporting T3D ===
* Export the whole map: File -> Export...
* export one brush:
* export a part of a map: either save, delete discards and export as above, or select, copy, paste into a text editor and save as a T3D file

===Importing T3D ===

File -> Import...

(note importing may take a LONG time)

Overheard on #utjb... :-)

<tarquin> t3d stores brushes & actors but not texturing, right?
<Mychaeel> Texturing as well.
(melds into the opening speech from Reservoir Dogs...)
<DaveA>Stores links to textures, and texture transforms, but not the pixels themselves

The T3D format is a text file which stores information about map actors. It's in fact identical to what can be copied from UnrealEd to a text editor. An exported map looks like this:

<uscript>
Begin Map
Begin Actor Class=LevelInfo Name=LevelInfo0
TimeSeconds=17.008888
Summary=LevelSummary'Entry.LevelSummary'
DefaultGameType=Class'Botpack.UTIntro'
AIProfile(0)=23784352
AIProfile(1)=52
AIProfile(2)=41
AIProfile(3)=42
AIProfile(4)=40
AIProfile(5)=44
AIProfile(6)=45
AIProfile(7)=21846171
AvgAITime=0.000000
Level=LevelInfo'Entry.LevelInfo0'
Tag=LevelInfo
Region=(Zone=LevelInfo'Entry.LevelInfo0',iLeaf=-1)
Name=LevelInfo0
End Actor
Begin Actor Class=Brush Name=Brush0
MainScale=(SheerAxis=SHEER_ZX)
PostScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
TempScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
Level=LevelInfo'Entry.LevelInfo0'
Tag=Brush
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=464.000000,Y=-16.000000,Z=64.000000)
Begin Brush Name=Brush
Begin PolyList
Begin Polygon Item=OUTSIDE Texture=black1 Flags=4194304 Link=0
Origin -00160.000000,+00000.000000,+00128.000000
Normal +00000.000000,+00000.000000,+00001.000000
TextureU +00004.000000,+00000.000000,+00000.000000
TextureV +00000.000000,+00004.000000,+00000.000000
Vertex -00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,+00128.000000,+00128.000000
Vertex -00128.000000,+00128.000000,+00128.000000
End Polygon
...
End PolyList
End Brush
Brush=Model'Entry.Brush'
Name=Brush0
End Actor
Begin Actor Class=PlayerStart Name=PlayerStart0
Level=LevelInfo'Entry.LevelInfo0'
Tag=PlayerStart
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=183.134430,Y=-987.334167,Z=33.978027)
OldLocation=(X=-217.561523,Y=-44.538128,Z=-87.899948)
Name=PlayerStart0
End Actor
...
End Map</uscript>

External link: http://unreal.jall.org/tutorials/t3d.html (new URL)

===Loading T3D brush geometry===

You must parse those informations correctly: PrePivot, Location, Rotation, MainScale, PostScale, TempScale, Polygon / Vertexes

<uscript>
FOR each vertex of each polygon of parsed brush DO:
do MainScale ... x *= MainScale[x], y *= MainScale[y], z *= MainScale[z]
do translation (-PrePivot[x], -PrePivot[y], -PrePivot[z])
do rotation Yaw, Pitch, Roll
do PostScale ... x *= PostScale[x], y *= PostScale[y], z *= PostScale[z]
do TempScale ... x *= TempScale[x], y *= TempScale[y], z *= TempScale[z]
do translation (Location[x], Location[y], Location[z])
ENDFOR
</uscript>

Note:
For Unreal Engine 3.x based maps (Unreal Tournament 2004 and 2003),PostScale,MainScale,TempScale and Rotation values are always null as the editor automatically updates vertices,origin and normal values when scaling up/down or rotating a brush.

Rotation matrix are the following:

<uscript>Roll Matrix-X Axis:
1, 0, 0, 0,
0, cos(roll),-sin(roll), 0,
0, sin(roll),cos(roll), 0,
0, 0, 0, 1</uscript>

<uscript>Pitch Matrix-Y Axis:
cos(pitch), 0, sin(pitch), 0,
0, 1, 0, 0,
-sin(pitch), 0,cos(pitch), 0,
0, 0, 0, 1)</uscript>

<uscript>Yaw Matrix-Z Axis:
cos(yaw), sin(yaw), 0, 0,
-sin(yaw), cos(yaw), 0, 0,
0, 0, 1, 0,
0, 0, 0, 1</uscript>

<uscript>Global Rotation Matrix=(Roll Matrix)*(Pitch Matrix)*(Yaw Matrix)</uscript>

Yaw, Roll and Pitch values are in radians. Original values from t3d files are in "Unreal format" where 2 rad = 65536.
For more information about Yaw, Pitch, Roll rotation matrix see http://mathworld.wolfram.com/EulerAngles.html.

Unknown (correct) effect: SheerAxis

Texturing information: 
Texture U and Texture V: contains information about scaling 
PanU and PanV: only used in Unreal Tournament 
Origin: where the texture is centered 
Normal: normally, the perpendicular vector of the surface where the texture is applied. 

TextureU, TextureV, PanU, PanV, Origin and Normal are informations about how to apply texture for the polygon.

[[Image:texinfot3d.jpg]] 
Texture Scaling can be found using this formula:
<uscript>
TexScaleX=1/(TextureU_x²+TextureV_x²)
TexScaleY=1/(TextureU_y²+TextureV_y²)
TexScaleZ=1/(TextureU_z²+TextureV_z²)
</uscript>
Python T3D loader (doesn't care about texture informations): http://carolina.mff.cuni.cz/~gib/ut_utils/unreal_t3d_loader.zip see readme.txt in zip file

=== Scaling up/down whole map ===
This operation is mainly needed when you want to port Unreal 1 or Unreal Tournament map to Unreal Tournament 2004 or Unreal Tournament 3.

To do so,considering ScaleFactor:
<uscript>For each actor in T3D File
set Location = ScaleFactor*Location
set PrePivot = ScaleFactor*PrePivot
If Actor==Brush
For each polygon
set Origin = ScaleFactor*Origin
For each vertex
set Vertex = ScaleFactor*Vertex
If Actor==StaticMesh
set DrawScale3D = ScaleFactor*DrawScale3D
</uscript>

Usually scale factor values:
Unreal 1/Unreal Tournament to UT2003/UT2004/UT3: 1.25

==T3D Utilities ==
* [[Legacy:MapScale|MapScale]] scales an entire .t3d file
* [[Legacy:MeshMaker|MeshMaker]] converts a prefab in .t3d format to a [[Legacy:Decoration|decoration]]
* [http://www.unrealroc.com/Converter.html UnrealROC] converters: from 3DMF, to VRML/X3D/OBJ (including textures et al).

==Related Topics ==
* [[Legacy:Data Import And Export|Data Import and Export]]
* [[Legacy:Brush Exporting And Importing|Brush Exporting And Importing]]
* [[Legacy:Brush Hacking|Brush Hacking]]

'''Kefik:''' There can be also a tag 'CsgOper' which have one of two values ... 'CSG_Subtract' -> subtract the brush from space or 'CSG_Add' -> add this brush to shape.

'''Sobiwan:''' New to WIKI editing, but not using it. I was searching for the actual format of T3D and found [http://users.skynet.be/fa550206/Slug-Production/Data/OpenGL-Documents/T3D-File-Format/T3D-File-Format.htm Mongo's description] of [http://www.planetunreal.com Planetunreal] to be extremely helpful. I'll ask him (mongo@planetunreal.com) if we can use and/or edit his description here. The format is much more involved than described here. We can even supply examples of how to do particular hacks.

'''MadNad:''' Interestingly, I was able to convert a [http://madnad.com/ut2k3/Screenshots/q3dm7.jpg?link Quake3_Level] into a unreal map. Quite interesting. First i converted a *.bsp to a *.map in quake, then I made a level that was just a huge cube and converted it to *.t3d. With an external app (i'll have to find the name of it ) I was able to merge these two together. After some scaling and switching additive brushes in quake to subtractive brushes in ued and subtractive to additive, I compiled and had q3dm7 geometry. I don't necessarily recommend doing this, as it will take more time to fix than create it from scratch, but I thought I would share a little experience I had with this.

Legacy:T3D File

2009-01-02T10:33:01Z

Solarsys: /* Loading T3D brush geometry */

The '''T3D file format''' or '''Unreal Text File''' holds a text list of Unreal map objects. An entire map can be saved as this file format, or just a single actor or brush.

Note that while brushes, their applied textures and light actors are saved, the [[Legacy:Unreal Geometry|Unreal Geometry]] itself is not saved: upon importing a T3D file the map must be built.

Copying objects from UnrealEd and pasting into a text editor produces the same format.

Unreal Text format

Exported brushes and (other) actors. See [[Legacy:T3D File|T3D file]].
* Created by:
** UnrealEd's File -> Import command
** UnrealEd's Brush -> Import command (see [[Legacy:Data Import And Export|Data Import and Export]] for more on both these commands).
** is this created by external stuff too?

===Exporting T3D ===
* Export the whole map: File -> Export...
* export one brush:
* export a part of a map: either save, delete discards and export as above, or select, copy, paste into a text editor and save as a T3D file

===Importing T3D ===

File -> Import...

(note importing may take a LONG time)

Overheard on #utjb... :-)

<tarquin> t3d stores brushes & actors but not texturing, right?
<Mychaeel> Texturing as well.
(melds into the opening speech from Reservoir Dogs...)
<DaveA>Stores links to textures, and texture transforms, but not the pixels themselves

The T3D format is a text file which stores information about map actors. It's in fact identical to what can be copied from UnrealEd to a text editor. An exported map looks like this:

<uscript>
Begin Map
Begin Actor Class=LevelInfo Name=LevelInfo0
TimeSeconds=17.008888
Summary=LevelSummary'Entry.LevelSummary'
DefaultGameType=Class'Botpack.UTIntro'
AIProfile(0)=23784352
AIProfile(1)=52
AIProfile(2)=41
AIProfile(3)=42
AIProfile(4)=40
AIProfile(5)=44
AIProfile(6)=45
AIProfile(7)=21846171
AvgAITime=0.000000
Level=LevelInfo'Entry.LevelInfo0'
Tag=LevelInfo
Region=(Zone=LevelInfo'Entry.LevelInfo0',iLeaf=-1)
Name=LevelInfo0
End Actor
Begin Actor Class=Brush Name=Brush0
MainScale=(SheerAxis=SHEER_ZX)
PostScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
TempScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
Level=LevelInfo'Entry.LevelInfo0'
Tag=Brush
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=464.000000,Y=-16.000000,Z=64.000000)
Begin Brush Name=Brush
Begin PolyList
Begin Polygon Item=OUTSIDE Texture=black1 Flags=4194304 Link=0
Origin -00160.000000,+00000.000000,+00128.000000
Normal +00000.000000,+00000.000000,+00001.000000
TextureU +00004.000000,+00000.000000,+00000.000000
TextureV +00000.000000,+00004.000000,+00000.000000
Vertex -00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,+00128.000000,+00128.000000
Vertex -00128.000000,+00128.000000,+00128.000000
End Polygon
...
End PolyList
End Brush
Brush=Model'Entry.Brush'
Name=Brush0
End Actor
Begin Actor Class=PlayerStart Name=PlayerStart0
Level=LevelInfo'Entry.LevelInfo0'
Tag=PlayerStart
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=183.134430,Y=-987.334167,Z=33.978027)
OldLocation=(X=-217.561523,Y=-44.538128,Z=-87.899948)
Name=PlayerStart0
End Actor
...
End Map</uscript>

External link: http://unreal.jall.org/tutorials/t3d.html (new URL)

===Loading T3D brush geometry===

You must parse those informations correctly: PrePivot, Location, Rotation, MainScale, PostScale, TempScale, Polygon / Vertexes

<uscript>
FOR each vertex of each polygon of parsed brush DO:
do MainScale ... x *= MainScale[x], y *= MainScale[y], z *= MainScale[z]
do translation (-PrePivot[x], -PrePivot[y], -PrePivot[z])
do rotation Yaw, Pitch, Roll
do PostScale ... x *= PostScale[x], y *= PostScale[y], z *= PostScale[z]
do TempScale ... x *= TempScale[x], y *= TempScale[y], z *= TempScale[z]
do translation (Location[x], Location[y], Location[z])
ENDFOR
</uscript>

Note:
For Unreal Engine 3.x based maps (Unreal Tournament 2004 and 2003),PostScale,MainScale,TempScale and Rotation values are always null as the editor automatically updates vertices,origin and normal values when scaling up/down or rotating a brush.

Rotation matrix are the following:

<uscript>Roll Matrix-X Axis:
1, 0, 0, 0,
0, cos(roll),-sin(roll), 0,
0, sin(roll),cos(roll), 0,
0, 0, 0, 1</uscript>

<uscript>Pitch Matrix-Y Axis:
cos(pitch), 0, sin(pitch), 0,
0, 1, 0, 0,
-sin(pitch), 0,cos(pitch), 0,
0, 0, 0, 1)</uscript>

<uscript>Yaw Matrix-Z Axis:
cos(yaw), sin(yaw), 0, 0,
-sin(yaw), cos(yaw), 0, 0,
0, 0, 1, 0,
0, 0, 0, 1</uscript>

<uscript>Global Rotation Matrix=(Roll Matrix)*(Pitch Matrix)*(Yaw Matrix)</uscript>

Yaw, Roll and Pitch values are in radians. Original values from t3d files are in "Unreal format" where 2 rad = 65536.
For more information about Yaw, Pitch, Roll rotation matrix see http://mathworld.wolfram.com/EulerAngles.html.

Unknown (correct) effect: SheerAxis

Texturing information: 
Texture U and Texture V: contains information about scaling 
PanU and PanV: only used in Unreal Tournament 
Origin: where the texture is centered 
Normal: normally, the perpendicular vector of the surface where the texture is applied. 

TextureU, TextureV, PanU, PanV, Origin and Normal are informations about how to apply texture for the polygon.

[[Image:TextureInfoT3DBrush]] 
Texture Scaling can be found using this formula:
<uscript>
TexScaleX=1/(TextureU_x²+TextureV_x²)
TexScaleY=1/(TextureU_y²+TextureV_y²)
TexScaleZ=1/(TextureU_z²+TextureV_z²)
</uscript>
Python T3D loader (doesn't care about texture informations): http://carolina.mff.cuni.cz/~gib/ut_utils/unreal_t3d_loader.zip see readme.txt in zip file

=== Scaling up/down whole map ===
This operation is mainly needed when you want to port Unreal 1 or Unreal Tournament map to Unreal Tournament 2004 or Unreal Tournament 3.

To do so,considering ScaleFactor:
<uscript>For each actor in T3D File
set Location = ScaleFactor*Location
set PrePivot = ScaleFactor*PrePivot
If Actor==Brush
For each polygon
set Origin = ScaleFactor*Origin
For each vertex
set Vertex = ScaleFactor*Vertex
If Actor==StaticMesh
set DrawScale3D = ScaleFactor*DrawScale3D
</uscript>

Usually scale factor values:
Unreal 1/Unreal Tournament to UT2003/UT2004/UT3: 1.25

==T3D Utilities ==
* [[Legacy:MapScale|MapScale]] scales an entire .t3d file
* [[Legacy:MeshMaker|MeshMaker]] converts a prefab in .t3d format to a [[Legacy:Decoration|decoration]]
* [http://www.unrealroc.com/Converter.html UnrealROC] converters: from 3DMF, to VRML/X3D/OBJ (including textures et al).

==Related Topics ==
* [[Legacy:Data Import And Export|Data Import and Export]]
* [[Legacy:Brush Exporting And Importing|Brush Exporting And Importing]]
* [[Legacy:Brush Hacking|Brush Hacking]]

'''Kefik:''' There can be also a tag 'CsgOper' which have one of two values ... 'CSG_Subtract' -> subtract the brush from space or 'CSG_Add' -> add this brush to shape.

'''Sobiwan:''' New to WIKI editing, but not using it. I was searching for the actual format of T3D and found [http://users.skynet.be/fa550206/Slug-Production/Data/OpenGL-Documents/T3D-File-Format/T3D-File-Format.htm Mongo's description] of [http://www.planetunreal.com Planetunreal] to be extremely helpful. I'll ask him (mongo@planetunreal.com) if we can use and/or edit his description here. The format is much more involved than described here. We can even supply examples of how to do particular hacks.

'''MadNad:''' Interestingly, I was able to convert a [http://madnad.com/ut2k3/Screenshots/q3dm7.jpg?link Quake3_Level] into a unreal map. Quite interesting. First i converted a *.bsp to a *.map in quake, then I made a level that was just a huge cube and converted it to *.t3d. With an external app (i'll have to find the name of it ) I was able to merge these two together. After some scaling and switching additive brushes in quake to subtractive brushes in ued and subtractive to additive, I compiled and had q3dm7 geometry. I don't necessarily recommend doing this, as it will take more time to fix than create it from scratch, but I thought I would share a little experience I had with this.

User:Solarsys

2009-01-02T09:08:39Z

Solarsys:

UT3 Player Name:
Solarsys

UTxx:
I got all PC Unreal games:
<li>Unreal 1 (+gold)</li>
<li>Unreal 2</li>
<li>Unreal Tournament</li>
<li>Unreal Tournament 2003</li>
<li>Unreal Tournament 2004</li>
<li>Unreal Tournament 3</li>

=== My Maps ===
Unreal Tournament 99:
None but mainly map/fixes updates (AS-BigAsteroidV3)

Unreal Tournament 2004:
<li>AS-7Co-TheEgyptianPyramid (first map)</li>
<li>AS-UT2X-Trials (aka AS-7Co-Trials)</li>
<li>AS-UT2X-DeepMines (test map with karma actors)</li>
<li>AS-UT2X-TheMayanTemple (unfinished)</li>
<li>a lot of map fixes/improvements (assault maps mainly)</li>

Unreal Tournament 3:
VCTF-TheBigDam (unfished)
=== UT3 Converter ===

More info here: http://utforums.epicgames.com/showthread.php?t=588848 
This program allows you to convert UT2004 maps to UT3.I will add support for U1 and UT soon (currently working on it) and to UT2004.
I had this idea of this tool when i first tried to import a UT2004 T3D File into UT3 editor. I thought like UT99->UT2004 it would import correctly but in UT3 it just crashed. So i started digging into the T3D format bringing brush conversion support then texturing and terrain! 
I think this is great tool because it will help mappers saving lot of time converting their maps to UT3 or UT2004 
The main problems i am currently facing to is texture alignment with U1/UT maps and exporting .dds texture from Unreal 2 packages.

User:Solarsys

2009-01-02T09:05:09Z

Solarsys: New page: UT3 Player Name: Solarsys UTxx: I got all PC Unreal games: <li>Unreal 1 (+gold)</li> <li>Unreal 2</li> <li>Unreal Tournament</li> <li>Unreal Tournament 2003</li> <li>Unreal Tournament 200...

UT3 Player Name:
Solarsys

UTxx:
I got all PC Unreal games:
<li>Unreal 1 (+gold)</li>
<li>Unreal 2</li>
<li>Unreal Tournament</li>
<li>Unreal Tournament 2003</li>
<li>Unreal Tournament 2004</li>
<li>Unreal Tournament 3</li>

My maps:
Unreal Tournament 99:
None but mainly map/fixes updates (AS-BigAsteroidV3)

Unreal Tournament 2004:
<li>AS-7Co-TheEgyptianPyramid (first map)</li>
<li>AS-UT2X-Trials (aka AS-7Co-Trials)</li>
<li>AS-UT2X-DeepMines (test map with karma actors)</li>
<li>AS-UT2X-TheMayanTemple (unfinished)</li>
<li>a lot of map fixes/improvements (assault maps mainly)</li>

Unreal Tournament 3:
VCTF-TheBigDam (unfished)

My Programs:

'''UT3 Converter''' (future name: "Unreal Map Converter"): http://utforums.epicgames.com/showthread.php?t=588848 
This program allows you to convert UT2004 maps to UT3.Will add support for U1 and UT soon (currently working on it) and to UT2004.
I had this idea of this tool when i first tried to import a UT2004 T3D File into UT3 editor. I thought like UT99->UT2004 it would import correctly but in UT3 it just crashed. So i started digging into the T3D format bringing brush conversion support then texturing and terrain! 
I think this is great tool because it will help mappers saving lot of time converting their maps to UT3 or UT2004 
The main problems i am currently facing to is texture alignment with U1/UT maps and exporting .dds texture from Unreal 2 packages.

Legacy:T3D File

2008-12-31T10:43:52Z

Solarsys: /* Loading T3D brush geometry */

The '''T3D file format''' or '''Unreal Text File''' holds a text list of Unreal map objects. An entire map can be saved as this file format, or just a single actor or brush.

Note that while brushes, their applied textures and light actors are saved, the [[Legacy:Unreal Geometry|Unreal Geometry]] itself is not saved: upon importing a T3D file the map must be built.

Copying objects from UnrealEd and pasting into a text editor produces the same format.

Unreal Text format

Exported brushes and (other) actors. See [[Legacy:T3D File|T3D file]].
* Created by:
** UnrealEd's File -> Import command
** UnrealEd's Brush -> Import command (see [[Legacy:Data Import And Export|Data Import and Export]] for more on both these commands).
** is this created by external stuff too?

===Exporting T3D ===
* Export the whole map: File -> Export...
* export one brush:
* export a part of a map: either save, delete discards and export as above, or select, copy, paste into a text editor and save as a T3D file

===Importing T3D ===

File -> Import...

(note importing may take a LONG time)

Overheard on #utjb... :-)

<tarquin> t3d stores brushes & actors but not texturing, right?
<Mychaeel> Texturing as well.
(melds into the opening speech from Reservoir Dogs...)
<DaveA>Stores links to textures, and texture transforms, but not the pixels themselves

The T3D format is a text file which stores information about map actors. It's in fact identical to what can be copied from UnrealEd to a text editor. An exported map looks like this:

<uscript>
Begin Map
Begin Actor Class=LevelInfo Name=LevelInfo0
TimeSeconds=17.008888
Summary=LevelSummary'Entry.LevelSummary'
DefaultGameType=Class'Botpack.UTIntro'
AIProfile(0)=23784352
AIProfile(1)=52
AIProfile(2)=41
AIProfile(3)=42
AIProfile(4)=40
AIProfile(5)=44
AIProfile(6)=45
AIProfile(7)=21846171
AvgAITime=0.000000
Level=LevelInfo'Entry.LevelInfo0'
Tag=LevelInfo
Region=(Zone=LevelInfo'Entry.LevelInfo0',iLeaf=-1)
Name=LevelInfo0
End Actor
Begin Actor Class=Brush Name=Brush0
MainScale=(SheerAxis=SHEER_ZX)
PostScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
TempScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
Level=LevelInfo'Entry.LevelInfo0'
Tag=Brush
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=464.000000,Y=-16.000000,Z=64.000000)
Begin Brush Name=Brush
Begin PolyList
Begin Polygon Item=OUTSIDE Texture=black1 Flags=4194304 Link=0
Origin -00160.000000,+00000.000000,+00128.000000
Normal +00000.000000,+00000.000000,+00001.000000
TextureU +00004.000000,+00000.000000,+00000.000000
TextureV +00000.000000,+00004.000000,+00000.000000
Vertex -00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,+00128.000000,+00128.000000
Vertex -00128.000000,+00128.000000,+00128.000000
End Polygon
...
End PolyList
End Brush
Brush=Model'Entry.Brush'
Name=Brush0
End Actor
Begin Actor Class=PlayerStart Name=PlayerStart0
Level=LevelInfo'Entry.LevelInfo0'
Tag=PlayerStart
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=183.134430,Y=-987.334167,Z=33.978027)
OldLocation=(X=-217.561523,Y=-44.538128,Z=-87.899948)
Name=PlayerStart0
End Actor
...
End Map</uscript>

External link: http://unreal.jall.org/tutorials/t3d.html (new URL)

===Loading T3D brush geometry===

You must parse those informations correctly: PrePivot, Location, Rotation, MainScale, PostScale, TempScale, Polygon / Vertexes

<uscript>
FOR each vertex of each polygon of parsed brush DO:
do MainScale ... x *= MainScale[x], y *= MainScale[y], z *= MainScale[z]
do translation (-PrePivot[x], -PrePivot[y], -PrePivot[z])
do rotation Yaw, Pitch, Roll
do PostScale ... x *= PostScale[x], y *= PostScale[y], z *= PostScale[z]
do TempScale ... x *= TempScale[x], y *= TempScale[y], z *= TempScale[z]
do translation (Location[x], Location[y], Location[z])
ENDFOR
</uscript>

Note:
For Unreal Engine 3.x based maps (Unreal Tournament 2004 and 2003),PostScale,MainScale,TempScale and Rotation values are always null as the editor automatically updates vertices,origin and normal values when scaling up/down or rotating a brush.

Rotation matrix are the following:

<uscript>Roll Matrix-X Axis:
1, 0, 0, 0,
0, cos(roll),-sin(roll), 0,
0, sin(roll),cos(roll), 0,
0, 0, 0, 1</uscript>

<uscript>Pitch Matrix-Y Axis:
cos(pitch), 0, sin(pitch), 0,
0, 1, 0, 0,
-sin(pitch), 0,cos(pitch), 0,
0, 0, 0, 1)</uscript>

<uscript>Yaw Matrix-Z Axis:
cos(yaw), sin(yaw), 0, 0,
-sin(yaw), cos(yaw), 0, 0,
0, 0, 1, 0,
0, 0, 0, 1</uscript>

<uscript>Global Rotation Matrix=(Roll Matrix)*(Pitch Matrix)*(Yaw Matrix)</uscript>

Yaw, Roll and Pitch values are in radians. Original values from t3d files are in "Unreal format" where 2 rad = 65536.
For more information about Yaw, Pitch, Roll rotation matrix see http://mathworld.wolfram.com/EulerAngles.html.

Unknown (correct) effect: SheerAxis

Texturing information: 
Texture U and Texture V: contains information about scaling 
PanU and PanV: only used in Unreal Tournament 
Origin: where the texture is centered 
Normal: normally, the perpendicular vector of the surface where the texture is applied. 

TextureU, TextureV, PanU, PanV, Origin and Normal are informations about how to apply texture for the polygon.

Texture Scaling can be found using this formula:
<uscript>
TexScaleX=1/(TextureU_x²+TextureV_x²)
TexScaleY=1/(TextureU_y²+TextureV_y²)
TexScaleZ=1/(TextureU_z²+TextureV_z²)
</uscript>
Python T3D loader (doesn't care about texture informations): http://carolina.mff.cuni.cz/~gib/ut_utils/unreal_t3d_loader.zip see readme.txt in zip file

=== Scaling up/down whole map ===
This operation is mainly needed when you want to port Unreal 1 or Unreal Tournament map to Unreal Tournament 2004 or Unreal Tournament 3.

To do so,considering ScaleFactor:
<uscript>For each actor in T3D File
set Location = ScaleFactor*Location
set PrePivot = ScaleFactor*PrePivot
If Actor==Brush
For each polygon
set Origin = ScaleFactor*Origin
For each vertex
set Vertex = ScaleFactor*Vertex
If Actor==StaticMesh
set DrawScale3D = ScaleFactor*DrawScale3D
</uscript>

Usually scale factor values:
Unreal 1/Unreal Tournament to UT2003/UT2004/UT3: 1.25

==T3D Utilities ==
* [[Legacy:MapScale|MapScale]] scales an entire .t3d file
* [[Legacy:MeshMaker|MeshMaker]] converts a prefab in .t3d format to a [[Legacy:Decoration|decoration]]
* [http://www.unrealroc.com/Converter.html UnrealROC] converters: from 3DMF, to VRML/X3D/OBJ (including textures et al).

==Related Topics ==
* [[Legacy:Data Import And Export|Data Import and Export]]
* [[Legacy:Brush Exporting And Importing|Brush Exporting And Importing]]
* [[Legacy:Brush Hacking|Brush Hacking]]

'''Kefik:''' There can be also a tag 'CsgOper' which have one of two values ... 'CSG_Subtract' -> subtract the brush from space or 'CSG_Add' -> add this brush to shape.

'''Sobiwan:''' New to WIKI editing, but not using it. I was searching for the actual format of T3D and found [http://users.skynet.be/fa550206/Slug-Production/Data/OpenGL-Documents/T3D-File-Format/T3D-File-Format.htm Mongo's description] of [http://www.planetunreal.com Planetunreal] to be extremely helpful. I'll ask him (mongo@planetunreal.com) if we can use and/or edit his description here. The format is much more involved than described here. We can even supply examples of how to do particular hacks.

'''MadNad:''' Interestingly, I was able to convert a [http://madnad.com/ut2k3/Screenshots/q3dm7.jpg?link Quake3_Level] into a unreal map. Quite interesting. First i converted a *.bsp to a *.map in quake, then I made a level that was just a huge cube and converted it to *.t3d. With an external app (i'll have to find the name of it ) I was able to merge these two together. After some scaling and switching additive brushes in quake to subtractive brushes in ued and subtractive to additive, I compiled and had q3dm7 geometry. I don't necessarily recommend doing this, as it will take more time to fix than create it from scratch, but I thought I would share a little experience I had with this.

Legacy:View Fog

2008-12-30T11:13:17Z

Solarsys:

Legacy:T3D File

2008-12-30T08:21:21Z

Solarsys: /* Scaling up/down whole map */

The '''T3D file format''' or '''Unreal Text File''' holds a text list of Unreal map objects. An entire map can be saved as this file format, or just a single actor or brush.

Note that while brushes, their applied textures and light actors are saved, the [[Legacy:Unreal Geometry|Unreal Geometry]] itself is not saved: upon importing a T3D file the map must be built.

Copying objects from UnrealEd and pasting into a text editor produces the same format.

Unreal Text format

Exported brushes and (other) actors. See [[Legacy:T3D File|T3D file]].
* Created by:
** UnrealEd's File -> Import command
** UnrealEd's Brush -> Import command (see [[Legacy:Data Import And Export|Data Import and Export]] for more on both these commands).
** is this created by external stuff too?

===Exporting T3D ===
* Export the whole map: File -> Export...
* export one brush:
* export a part of a map: either save, delete discards and export as above, or select, copy, paste into a text editor and save as a T3D file

===Importing T3D ===

File -> Import...

(note importing may take a LONG time)

Overheard on #utjb... :-)

<tarquin> t3d stores brushes & actors but not texturing, right?
<Mychaeel> Texturing as well.
(melds into the opening speech from Reservoir Dogs...)
<DaveA>Stores links to textures, and texture transforms, but not the pixels themselves

The T3D format is a text file which stores information about map actors. It's in fact identical to what can be copied from UnrealEd to a text editor. An exported map looks like this:

<uscript>
Begin Map
Begin Actor Class=LevelInfo Name=LevelInfo0
TimeSeconds=17.008888
Summary=LevelSummary'Entry.LevelSummary'
DefaultGameType=Class'Botpack.UTIntro'
AIProfile(0)=23784352
AIProfile(1)=52
AIProfile(2)=41
AIProfile(3)=42
AIProfile(4)=40
AIProfile(5)=44
AIProfile(6)=45
AIProfile(7)=21846171
AvgAITime=0.000000
Level=LevelInfo'Entry.LevelInfo0'
Tag=LevelInfo
Region=(Zone=LevelInfo'Entry.LevelInfo0',iLeaf=-1)
Name=LevelInfo0
End Actor
Begin Actor Class=Brush Name=Brush0
MainScale=(SheerAxis=SHEER_ZX)
PostScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
TempScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
Level=LevelInfo'Entry.LevelInfo0'
Tag=Brush
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=464.000000,Y=-16.000000,Z=64.000000)
Begin Brush Name=Brush
Begin PolyList
Begin Polygon Item=OUTSIDE Texture=black1 Flags=4194304 Link=0
Origin -00160.000000,+00000.000000,+00128.000000
Normal +00000.000000,+00000.000000,+00001.000000
TextureU +00004.000000,+00000.000000,+00000.000000
TextureV +00000.000000,+00004.000000,+00000.000000
Vertex -00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,+00128.000000,+00128.000000
Vertex -00128.000000,+00128.000000,+00128.000000
End Polygon
...
End PolyList
End Brush
Brush=Model'Entry.Brush'
Name=Brush0
End Actor
Begin Actor Class=PlayerStart Name=PlayerStart0
Level=LevelInfo'Entry.LevelInfo0'
Tag=PlayerStart
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=183.134430,Y=-987.334167,Z=33.978027)
OldLocation=(X=-217.561523,Y=-44.538128,Z=-87.899948)
Name=PlayerStart0
End Actor
...
End Map</uscript>

External link: http://unreal.jall.org/tutorials/t3d.html (new URL)

===Loading T3D brush geometry===

You must parse those informations correctly: PrePivot, Location, Rotation, MainScale, PostScale, TempScale, Polygon / Vertexes

<uscript>
FOR each vertex of each polygon of parsed brush DO:
do MainScale ... x *= MainScale[x], y *= MainScale[y], z *= MainScale[z]
do translation (-PrePivot[x], -PrePivot[y], -PrePivot[z])
do rotation Yaw, Pitch, Roll
do PostScale ... x *= PostScale[x], y *= PostScale[y], z *= PostScale[z]
do TempScale ... x *= TempScale[x], y *= TempScale[y], z *= TempScale[z]
do translation (Location[x], Location[y], Location[z])
ENDFOR
</uscript>

Note:
For Unreal Engine 3.x based maps (Unreal Tournament 2004 and 2003),PostScale,MainScale,TempScale and Rotation values are always null as the editor automatically updates vertices,origin and normal values when scaling up/down or rotating a brush.

Rotation matrix are the following:

<uscript>Roll Matrix-X Axis:
1, 0, 0, 0,
0, cos(roll),-sin(roll), 0,
0, sin(roll),cos(roll), 0,
0, 0, 0, 1</uscript>

<uscript>Pitch Matrix-Y Axis:
cos(pitch), 0, sin(pitch), 0,
0, 1, 0, 0,
-sin(pitch), 0,cos(pitch), 0,
0, 0, 0, 1)</uscript>

<uscript>Yaw Matrix-Z Axis:
cos(yaw), sin(yaw), 0, 0,
-sin(yaw), cos(yaw), 0, 0,
0, 0, 1, 0,
0, 0, 0, 1</uscript>

<uscript>Global Rotation Matrix=(Roll Matrix)*(Pitch Matrix)*(Yaw Matrix)</uscript>

Yaw, Roll and Pitch values are in radians. Original values from t3d files are in "Unreal format" where 2 rad = 65536.
For more information about Yaw, Pitch, Roll rotation matrix see http://mathworld.wolfram.com/EulerAngles.html.

Unknown (correct) effect: SheerAxis

TextureU, TextureV, PanU, PanV, Origin are information about how to apply texture for the polygon.
Python T3D loader (doesn't care about texture informations): http://carolina.mff.cuni.cz/~gib/ut_utils/unreal_t3d_loader.zip see readme.txt in zip file

=== Scaling up/down whole map ===
This operation is mainly needed when you want to port Unreal 1 or Unreal Tournament map to Unreal Tournament 2004 or Unreal Tournament 3.

To do so,considering ScaleFactor:
<uscript>For each actor in T3D File
set Location = ScaleFactor*Location
set PrePivot = ScaleFactor*PrePivot
If Actor==Brush
For each polygon
set Origin = ScaleFactor*Origin
For each vertex
set Vertex = ScaleFactor*Vertex
If Actor==StaticMesh
set DrawScale3D = ScaleFactor*DrawScale3D
</uscript>

Usually scale factor values:
Unreal 1/Unreal Tournament to UT2003/UT2004/UT3: 1.25

==T3D Utilities ==
* [[Legacy:MapScale|MapScale]] scales an entire .t3d file
* [[Legacy:MeshMaker|MeshMaker]] converts a prefab in .t3d format to a [[Legacy:Decoration|decoration]]
* [http://www.unrealroc.com/Converter.html UnrealROC] converters: from 3DMF, to VRML/X3D/OBJ (including textures et al).

==Related Topics ==
* [[Legacy:Data Import And Export|Data Import and Export]]
* [[Legacy:Brush Exporting And Importing|Brush Exporting And Importing]]
* [[Legacy:Brush Hacking|Brush Hacking]]

'''Kefik:''' There can be also a tag 'CsgOper' which have one of two values ... 'CSG_Subtract' -> subtract the brush from space or 'CSG_Add' -> add this brush to shape.

'''Sobiwan:''' New to WIKI editing, but not using it. I was searching for the actual format of T3D and found [http://users.skynet.be/fa550206/Slug-Production/Data/OpenGL-Documents/T3D-File-Format/T3D-File-Format.htm Mongo's description] of [http://www.planetunreal.com Planetunreal] to be extremely helpful. I'll ask him (mongo@planetunreal.com) if we can use and/or edit his description here. The format is much more involved than described here. We can even supply examples of how to do particular hacks.

'''MadNad:''' Interestingly, I was able to convert a [http://madnad.com/ut2k3/Screenshots/q3dm7.jpg?link Quake3_Level] into a unreal map. Quite interesting. First i converted a *.bsp to a *.map in quake, then I made a level that was just a huge cube and converted it to *.t3d. With an external app (i'll have to find the name of it ) I was able to merge these two together. After some scaling and switching additive brushes in quake to subtractive brushes in ued and subtractive to additive, I compiled and had q3dm7 geometry. I don't necessarily recommend doing this, as it will take more time to fix than create it from scratch, but I thought I would share a little experience I had with this.

Legacy:T3D File

2008-12-30T08:20:03Z

Solarsys:

The '''T3D file format''' or '''Unreal Text File''' holds a text list of Unreal map objects. An entire map can be saved as this file format, or just a single actor or brush.

Note that while brushes, their applied textures and light actors are saved, the [[Legacy:Unreal Geometry|Unreal Geometry]] itself is not saved: upon importing a T3D file the map must be built.

Copying objects from UnrealEd and pasting into a text editor produces the same format.

Unreal Text format

Exported brushes and (other) actors. See [[Legacy:T3D File|T3D file]].
* Created by:
** UnrealEd's File -> Import command
** UnrealEd's Brush -> Import command (see [[Legacy:Data Import And Export|Data Import and Export]] for more on both these commands).
** is this created by external stuff too?

===Exporting T3D ===
* Export the whole map: File -> Export...
* export one brush:
* export a part of a map: either save, delete discards and export as above, or select, copy, paste into a text editor and save as a T3D file

===Importing T3D ===

File -> Import...

(note importing may take a LONG time)

Overheard on #utjb... :-)

<tarquin> t3d stores brushes & actors but not texturing, right?
<Mychaeel> Texturing as well.
(melds into the opening speech from Reservoir Dogs...)
<DaveA>Stores links to textures, and texture transforms, but not the pixels themselves

The T3D format is a text file which stores information about map actors. It's in fact identical to what can be copied from UnrealEd to a text editor. An exported map looks like this:

<uscript>
Begin Map
Begin Actor Class=LevelInfo Name=LevelInfo0
TimeSeconds=17.008888
Summary=LevelSummary'Entry.LevelSummary'
DefaultGameType=Class'Botpack.UTIntro'
AIProfile(0)=23784352
AIProfile(1)=52
AIProfile(2)=41
AIProfile(3)=42
AIProfile(4)=40
AIProfile(5)=44
AIProfile(6)=45
AIProfile(7)=21846171
AvgAITime=0.000000
Level=LevelInfo'Entry.LevelInfo0'
Tag=LevelInfo
Region=(Zone=LevelInfo'Entry.LevelInfo0',iLeaf=-1)
Name=LevelInfo0
End Actor
Begin Actor Class=Brush Name=Brush0
MainScale=(SheerAxis=SHEER_ZX)
PostScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
TempScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
Level=LevelInfo'Entry.LevelInfo0'
Tag=Brush
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=464.000000,Y=-16.000000,Z=64.000000)
Begin Brush Name=Brush
Begin PolyList
Begin Polygon Item=OUTSIDE Texture=black1 Flags=4194304 Link=0
Origin -00160.000000,+00000.000000,+00128.000000
Normal +00000.000000,+00000.000000,+00001.000000
TextureU +00004.000000,+00000.000000,+00000.000000
TextureV +00000.000000,+00004.000000,+00000.000000
Vertex -00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,+00128.000000,+00128.000000
Vertex -00128.000000,+00128.000000,+00128.000000
End Polygon
...
End PolyList
End Brush
Brush=Model'Entry.Brush'
Name=Brush0
End Actor
Begin Actor Class=PlayerStart Name=PlayerStart0
Level=LevelInfo'Entry.LevelInfo0'
Tag=PlayerStart
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=183.134430,Y=-987.334167,Z=33.978027)
OldLocation=(X=-217.561523,Y=-44.538128,Z=-87.899948)
Name=PlayerStart0
End Actor
...
End Map</uscript>

External link: http://unreal.jall.org/tutorials/t3d.html (new URL)

===Loading T3D brush geometry===

You must parse those informations correctly: PrePivot, Location, Rotation, MainScale, PostScale, TempScale, Polygon / Vertexes

<uscript>
FOR each vertex of each polygon of parsed brush DO:
do MainScale ... x *= MainScale[x], y *= MainScale[y], z *= MainScale[z]
do translation (-PrePivot[x], -PrePivot[y], -PrePivot[z])
do rotation Yaw, Pitch, Roll
do PostScale ... x *= PostScale[x], y *= PostScale[y], z *= PostScale[z]
do TempScale ... x *= TempScale[x], y *= TempScale[y], z *= TempScale[z]
do translation (Location[x], Location[y], Location[z])
ENDFOR
</uscript>

Note:
For Unreal Engine 3.x based maps (Unreal Tournament 2004 and 2003),PostScale,MainScale,TempScale and Rotation values are always null as the editor automatically updates vertices,origin and normal values when scaling up/down or rotating a brush.

Rotation matrix are the following:

<uscript>Roll Matrix-X Axis:
1, 0, 0, 0,
0, cos(roll),-sin(roll), 0,
0, sin(roll),cos(roll), 0,
0, 0, 0, 1</uscript>

<uscript>Pitch Matrix-Y Axis:
cos(pitch), 0, sin(pitch), 0,
0, 1, 0, 0,
-sin(pitch), 0,cos(pitch), 0,
0, 0, 0, 1)</uscript>

<uscript>Yaw Matrix-Z Axis:
cos(yaw), sin(yaw), 0, 0,
-sin(yaw), cos(yaw), 0, 0,
0, 0, 1, 0,
0, 0, 0, 1</uscript>

<uscript>Global Rotation Matrix=(Roll Matrix)*(Pitch Matrix)*(Yaw Matrix)</uscript>

Yaw, Roll and Pitch values are in radians. Original values from t3d files are in "Unreal format" where 2 rad = 65536.
For more information about Yaw, Pitch, Roll rotation matrix see http://mathworld.wolfram.com/EulerAngles.html.

Unknown (correct) effect: SheerAxis

TextureU, TextureV, PanU, PanV, Origin are information about how to apply texture for the polygon.
Python T3D loader (doesn't care about texture informations): http://carolina.mff.cuni.cz/~gib/ut_utils/unreal_t3d_loader.zip see readme.txt in zip file

=== Scaling up/down whole map ===
This operation is mainly needed when you want to port Unreal 1 or Unreal Tournament map to Unreal Tournament 2004 or Unreal Tournament 3.

To do so,considering ScaleFactor:
<uscript>For each actor in T3D File
set Location = ScaleFactor*Location
set PrePivot = ScaleFactor*PrePivot
If Actor==Brush
For each polygon
set Origin = ScaleFactor*Origin
For each vertex
set Vertex = ScaleFactor*Vertex
If Actor==StaticMesh
set DrawScale3D = ScaleFactor*DrawScale3D
</uscript>

Know scale factor values:
Unreal 1/Unreal Tournament to UT2003/UT2004/UT3: 1.25

==T3D Utilities ==
* [[Legacy:MapScale|MapScale]] scales an entire .t3d file
* [[Legacy:MeshMaker|MeshMaker]] converts a prefab in .t3d format to a [[Legacy:Decoration|decoration]]
* [http://www.unrealroc.com/Converter.html UnrealROC] converters: from 3DMF, to VRML/X3D/OBJ (including textures et al).

==Related Topics ==
* [[Legacy:Data Import And Export|Data Import and Export]]
* [[Legacy:Brush Exporting And Importing|Brush Exporting And Importing]]
* [[Legacy:Brush Hacking|Brush Hacking]]

'''Kefik:''' There can be also a tag 'CsgOper' which have one of two values ... 'CSG_Subtract' -> subtract the brush from space or 'CSG_Add' -> add this brush to shape.

'''Sobiwan:''' New to WIKI editing, but not using it. I was searching for the actual format of T3D and found [http://users.skynet.be/fa550206/Slug-Production/Data/OpenGL-Documents/T3D-File-Format/T3D-File-Format.htm Mongo's description] of [http://www.planetunreal.com Planetunreal] to be extremely helpful. I'll ask him (mongo@planetunreal.com) if we can use and/or edit his description here. The format is much more involved than described here. We can even supply examples of how to do particular hacks.

'''MadNad:''' Interestingly, I was able to convert a [http://madnad.com/ut2k3/Screenshots/q3dm7.jpg?link Quake3_Level] into a unreal map. Quite interesting. First i converted a *.bsp to a *.map in quake, then I made a level that was just a huge cube and converted it to *.t3d. With an external app (i'll have to find the name of it ) I was able to merge these two together. After some scaling and switching additive brushes in quake to subtractive brushes in ued and subtractive to additive, I compiled and had q3dm7 geometry. I don't necessarily recommend doing this, as it will take more time to fix than create it from scratch, but I thought I would share a little experience I had with this.

Legacy:T3D File

2008-12-30T07:56:09Z

Solarsys: /* Loading T3D brush geometry */

The '''T3D file format''' or '''Unreal Text File''' holds a text list of Unreal map objects. An entire map can be saved as this file format, or just a single actor or brush.

Note that while brushes, their applied textures and light actors are saved, the [[Legacy:Unreal Geometry|Unreal Geometry]] itself is not saved: upon importing a T3D file the map must be built.

Copying objects from UnrealEd and pasting into a text editor produces the same format.

Unreal Text format

Exported brushes and (other) actors. See [[Legacy:T3D File|T3D file]].
* Created by:
** UnrealEd's File -> Import command
** UnrealEd's Brush -> Import command (see [[Legacy:Data Import And Export|Data Import and Export]] for more on both these commands).
** is this created by external stuff too?

===Exporting T3D ===
* Export the whole map: File -> Export...
* export one brush:
* export a part of a map: either save, delete discards and export as above, or select, copy, paste into a text editor and save as a T3D file

===Importing T3D ===

File -> Import...

(note importing may take a LONG time)

Overheard on #utjb... :-)

<tarquin> t3d stores brushes & actors but not texturing, right?
<Mychaeel> Texturing as well.
(melds into the opening speech from Reservoir Dogs...)
<DaveA>Stores links to textures, and texture transforms, but not the pixels themselves

The T3D format is a text file which stores information about map actors. It's in fact identical to what can be copied from UnrealEd to a text editor. An exported map looks like this:

<uscript>
Begin Map
Begin Actor Class=LevelInfo Name=LevelInfo0
TimeSeconds=17.008888
Summary=LevelSummary'Entry.LevelSummary'
DefaultGameType=Class'Botpack.UTIntro'
AIProfile(0)=23784352
AIProfile(1)=52
AIProfile(2)=41
AIProfile(3)=42
AIProfile(4)=40
AIProfile(5)=44
AIProfile(6)=45
AIProfile(7)=21846171
AvgAITime=0.000000
Level=LevelInfo'Entry.LevelInfo0'
Tag=LevelInfo
Region=(Zone=LevelInfo'Entry.LevelInfo0',iLeaf=-1)
Name=LevelInfo0
End Actor
Begin Actor Class=Brush Name=Brush0
MainScale=(SheerAxis=SHEER_ZX)
PostScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
TempScale=(Scale=(X=0.250000,Y=8.000000,Z=3.000000),SheerAxis=SHEER_ZX)
Level=LevelInfo'Entry.LevelInfo0'
Tag=Brush
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=464.000000,Y=-16.000000,Z=64.000000)
Begin Brush Name=Brush
Begin PolyList
Begin Polygon Item=OUTSIDE Texture=black1 Flags=4194304 Link=0
Origin -00160.000000,+00000.000000,+00128.000000
Normal +00000.000000,+00000.000000,+00001.000000
TextureU +00004.000000,+00000.000000,+00000.000000
TextureV +00000.000000,+00004.000000,+00000.000000
Vertex -00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,-00128.000000,+00128.000000
Vertex +00128.000000,+00128.000000,+00128.000000
Vertex -00128.000000,+00128.000000,+00128.000000
End Polygon
...
End PolyList
End Brush
Brush=Model'Entry.Brush'
Name=Brush0
End Actor
Begin Actor Class=PlayerStart Name=PlayerStart0
Level=LevelInfo'Entry.LevelInfo0'
Tag=PlayerStart
Region=(Zone=ZoneInfo'Entry.ZoneInfo0',iLeaf=1,ZoneNumber=1)
Location=(X=183.134430,Y=-987.334167,Z=33.978027)
OldLocation=(X=-217.561523,Y=-44.538128,Z=-87.899948)
Name=PlayerStart0
End Actor
...
End Map</uscript>

External link: http://unreal.jall.org/tutorials/t3d.html (new URL)

===Loading T3D brush geometry===

You must parse those informations correctly: PrePivot, Location, Rotation, MainScale, PostScale, TempScale, Polygon / Vertexes

<uscript>
FOR each vertex of each polygon of parsed brush DO:
do MainScale ... x *= MainScale[x], y *= MainScale[y], z *= MainScale[z]
do translation (-PrePivot[x], -PrePivot[y], -PrePivot[z])
do rotation Yaw, Pitch, Roll
do PostScale ... x *= PostScale[x], y *= PostScale[y], z *= PostScale[z]
do TempScale ... x *= TempScale[x], y *= TempScale[y], z *= TempScale[z]
do translation (Location[x], Location[y], Location[z])
ENDFOR
</uscript>

Note:
For Unreal Engine 3.x based maps (Unreal Tournament 2004 and 2003),PostScale,MainScale,TempScale and Rotation values are always null as the editor automatically updates vertices,origin and normal values when scaling up/down or rotating a brush.

Rotation matrix are the following:

<uscript>Roll Matrix-X Axis:
1, 0, 0, 0,
0, cos(roll),-sin(roll), 0,
0, sin(roll),cos(roll), 0,
0, 0, 0, 1</uscript>

<uscript>Pitch Matrix-Y Axis:
cos(pitch), 0, sin(pitch), 0,
0, 1, 0, 0,
-sin(pitch), 0,cos(pitch), 0,
0, 0, 0, 1)</uscript>

<uscript>Yaw Matrix-Z Axis:
cos(yaw), sin(yaw), 0, 0,
-sin(yaw), cos(yaw), 0, 0,
0, 0, 1, 0,
0, 0, 0, 1</uscript>

<uscript>Global Rotation Matrix=(Roll Matrix)*(Pitch Matrix)*(Yaw Matrix)</uscript>

Yaw, Roll and Pitch values are in radians. Original values from t3d files are in "Unreal format" where 2 rad = 65536.
For more information about Yaw, Pitch, Roll rotation matrix see http://mathworld.wolfram.com/EulerAngles.html.

Unknown (correct) effect: SheerAxis

TextureU, TextureV, PanU, PanV, Origin are information about how to apply texture for the polygon.

Python T3D loader (doesn't care about texture informations): http://carolina.mff.cuni.cz/~gib/ut_utils/unreal_t3d_loader.zip see readme.txt in zip file

==T3D Utilities ==
* [[Legacy:MapScale|MapScale]] scales an entire .t3d file
* [[Legacy:MeshMaker|MeshMaker]] converts a prefab in .t3d format to a [[Legacy:Decoration|decoration]]
* [http://www.unrealroc.com/Converter.html UnrealROC] converters: from 3DMF, to VRML/X3D/OBJ (including textures et al).

==Related Topics ==
* [[Legacy:Data Import And Export|Data Import and Export]]
* [[Legacy:Brush Exporting And Importing|Brush Exporting And Importing]]
* [[Legacy:Brush Hacking|Brush Hacking]]

'''Kefik:''' There can be also a tag 'CsgOper' which have one of two values ... 'CSG_Subtract' -> subtract the brush from space or 'CSG_Add' -> add this brush to shape.

'''Sobiwan:''' New to WIKI editing, but not using it. I was searching for the actual format of T3D and found [http://users.skynet.be/fa550206/Slug-Production/Data/OpenGL-Documents/T3D-File-Format/T3D-File-Format.htm Mongo's description] of [http://www.planetunreal.com Planetunreal] to be extremely helpful. I'll ask him (mongo@planetunreal.com) if we can use and/or edit his description here. The format is much more involved than described here. We can even supply examples of how to do particular hacks.

'''MadNad:''' Interestingly, I was able to convert a [http://madnad.com/ut2k3/Screenshots/q3dm7.jpg?link Quake3_Level] into a unreal map. Quite interesting. First i converted a *.bsp to a *.map in quake, then I made a level that was just a huge cube and converted it to *.t3d. With an external app (i'll have to find the name of it ) I was able to merge these two together. After some scaling and switching additive brushes in quake to subtractive brushes in ued and subtractive to additive, I compiled and had q3dm7 geometry. I don't necessarily recommend doing this, as it will take more time to fix than create it from scratch, but I thought I would share a little experience I had with this.