The DarkMod Wiki - User contributions [en]

What's new in TDM 1.01

2010-01-30T22:32:47Z

Ishtvan: /* Bugs fixed */

This article is a work-in-progress and can change before the final release. There are '''no promises''' here. Features may be postponed or removed even if they appear on this list, and regressions may re-introduce bugs after they've been fixed internally. See also the changelog on our bugtracker page: [http://bugs.angua.at/changelog_page.php?project_id=2 Changelog].

== Bugs fixed ==
* [http://bugs.angua.at/view.php?id=1921 #1921]: HUD Font reverts to Doom 3 font after fresh gamesave load.
* [http://bugs.angua.at/view.php?id=1963 #1963]: Double doors sometimes highlight at a distance.
* [http://bugs.angua.at/view.php?id=1968 #1968] Blackjack no longer makes metallic clang when hitting world
* [http://bugs.angua.at/view.php?id=1970 #1970]: Chests went non-solid when frobbed
* [http://bugs.angua.at/view.php?id=1976 #1976]: Shop items get duplicated on "Restart" after dying
* [http://bugs.angua.at/view.php?id=1990 #1990]: No SOUND on TDM after installing a mission, added CVAR (tdm_fm_restart_delay) to issue a delay request to tdmlauncher.
* [http://bugs.angua.at/view.php?id=1996 #1996]: Fixed bug that made shouldered bodies undroppable
* [http://bugs.angua.at/view.php?id=2007 #2007]: Fixed: Location settings did igore the "music volume" slider
* [http://bugs.angua.at/view.php?id=2067 #2067]: Fixed bug when using shop_skip 1 in FMs.
* [http://bugs.angua.at/view.php?id=2072 #2072]: Rats (and other small animals) could be shouldered
* [http://bugs.angua.at/view.php?id=2075 #2075]: AI were alerted when they took falling damage
* [http://bugs.angua.at/view.php?id=2083 #2083]: Small items like candles, candle holders, rocks etc floated on water instead of sinking
* [http://bugs.angua.at/view.php?id=2093 #2093]: Fireplace_arch was missing its texture
* [http://bugs.angua.at/view.php?id=2117 #2117]: frob_peer hilite does not sync.
* [http://bugs.angua.at/view.php?id=2119 #2119]: Player's run footfall sounds are played while shouldering a body
* Fixed savegames getting to huge sizes, leading to out-of-memory or crashes
* Fixed a few crashes and memory errors
* Fixed: Crash with ATI cards when viewing certain models (like the marble column)
* Fixed: Location settings did not work with "fast" ambient method
* Melee controls now more responsive
* Fixed blackjack bug where player could hit low ceilings
* Fixed archer bows blocking blackjack attempts
* Fixed bug where some close-range melee attacks neglected armor
* Altered sword thrust collision physics to match up better with visible sword model
* Minor fixes to models and textures (e.g. inverted normals)
* Added a bunch of missing editor images for models (STiFU).

== Features added ==
* [http://bugs.angua.at/view.php?id=2123 #2123]: In-game objectives display
* A lot new skins for: dirty fireplaces, unlit lamps etc.
* New script events for: get/setDroppable, isEntityHidden, Melee etc.
* Support for "skin_unlit" and "skin_lit" on light entities
* New "unbindOnAlertIndex" spawnarg on attached entities, to make AI drop them when alerted
* Crouch indicator: Lightgem "wings" squash down slightly when crouch mode is on (helpful when climbing)
* AI have a combat skill level now: novice, trained, skilled
* added Difficulty Slider for combat in menu
* [http://bugs.angua.at/view.php?id=2024 AI can be set to drop attached objects on alert]
* greater flexibility added to absence markers
* [http://bugs.angua.at/view.php?id=2012 #2012]: GC's movetype-specific metal footstep sounds are in-game
* [http://bugs.angua.at/view.php?id=2015 #2015]: Added console commands to control logging to darkmod.log
* [http://bugs.angua.at/view.php?id=2002 #2002]: FM Installer Code checks required version of Mission to be installed, information can be added to darkmod.txt in the FM package.
* [http://bugs.angua.at/view.php?id=1977 #1977]: FM Installer Code considers ZIP files as well as PK4s now
* [http://bugs.angua.at/view.php?id=1984 #1984]: FM Installer Code needs to replace dashes with underscores on creating the fms subfolder
* [http://bugs.angua.at/view.php?id=2080 #2080]: Doors have a larger sound radius now.

== AI added ==

* added two zombie types with various skins, as well as "sleeping" behaviour
* added spiders and spider children
* added new elite guard character
* added elite guard helmet (immune to KOs)
* added skeleton AI
* added revenant character
* added male beggar character
* added male pagan character

== Entities added ==

* A lot of new [[combo entities]] have been added:
** fireplaces,
** static torches,
** statues with torch in hand,
** campfires, bucket and bonfires,
** electric streetlights,
** wall-mounted lamps and torches,
** geodes with pulsating light,
** bottles+candle,
** skulls+candle etc.
* new colored torch flames: blue, green, orange
* new fireflames: white and black smoking, smouldering ones, large and huge bonfires, bucketfire
* a few new model props (eg, saw, wall-light)
* climbable ragdoll chains
* [http://bugs.angua.at/view.php?id=2110 Bug #2110] [[Loot paintings]]

== Sounds ==

* changed AI footsteps to mono (so the direction of sound is accurate)
* reduced volume of player footsteps
* increased sound radius of doors

Added Dario D's ambient sound contributions.

* Ambient Shaders added
** animal_crickets_birds01, animal_crickets04, animal_crickets05, animal_dog03, animal_frog03, animal_night_bird01, animal_owl04, animal_owl05, animal_owl06
** machine_sparks01
** music_harp01, music_harp02, music_bum_bum01, music_bum_bum02
** weather_thunder04, weather_thunder05
* Environmental Sound Shaders added
** drone01, drone02, drone03a, drone03b, drone05a, drone05b
** hit01a, hit02b, hit03a, hit03b
** hum01, hum01b, hum02, hum03, hum04, hum05_loop, hum05_loop_b, hum06_loop, hum06_loop_b, hum07_loop, hum07_loop_b, hum08

== Textures ==
Added STiFU's, Renzatic's and Baddcog's textures, including the following shaders:
STiFU:
* textures/darkmod/door/wood/board_brown_nails_hinge
* textures/darkmod/metal/detailed/threadplate_large_dirty
* textures/darkmod/roof/slate_cracked_large_greyblue
* textures/darkmod/roof/slate_cracked_large_greyblue_shiny
* textures/darkmod/stone/brick/tiling_1d/poolwall_large_dirty_weathered_greengrey
* textures/darkmod/stone/brick/tiling_1d/poolwall_large_dirty_weathered_greengrey_wet
* textures/darkmod/stone/cobblestones/cobblestones_large_uneven_darkgrey
* textures/darkmod/stone/cobblestones/cobblestones_large_uneven_darkgrey_wet
* textures/darkmod/stone/flat/tiles_ceramic_large_clean_even
* textures/darkmod/stone/flat/tiles_ceramic_large_clean_rough
* textures/darkmod/stone/flat/tiles_ceramic_large_ornate_old_blue
* textures/darkmod/stone/flat/tiles_large_dirty_cracked
* textures/darkmod/stone/flat/tiles_large_dirty_cracked_greasy
* textures/darkmod/stone/natural/rock_large_rough_grey
* textures/darkmod/stone/natural/rock_large_rough_grey_greasy
* textures/darkmod/stone/natural/rock_large_cracked_holey_grey
* textures/darkmod/stone/natural/rock_large_cracked_holey_grey_greasy
* textures/darkmod/stone/sculpted/tiling_1d/trim_large_ornate_old_bright
* textures/darkmod/stone/sculpted/tiling_1d/trim_large_ornate_old_bright_greasy
* textures/darkmod/stone/sculpted/tiling_1d/trim_large_ornate_old_dark_bluered
* textures/darkmod/stone/sculpted/tiling_1d/trim_large_ornate_old_dark_bluered_greasy
* textures/darkmod/stone/sculpted/tiling_1d/trim_small_ornate_old
* textures/darkmod/stone/sculpted/tiling_1d/trim_small_ornate_old_greasy
* textures/darkmod/wood/boards/polished_shiny_large_red
* textures/darkmod/wood/boards/rough_wood_large_brown
* textures/darkmod/wood/boards/rough_wood_large_brown_glossy
* textures/darkmod/wood/boards/planks_wood_large_worn_rough_bright
* textures/darkmod/wood/boards/planks_wood_large_worn_rough_bright_glossy
* textures/darkmod/wood/boards/planks_wood_large_worn_rough_dark
* textures/darkmod/wood/boards/planks_wood_large_worn_rough_dark_glossy
* textures/darkmod/wood/boards/roof_framework_boards_large_old_brown
* textures/darkmod/wood/boards/roof_framework_boards_large_old_green
* textures/darkmod/roof/shingles_blue
* textures/darkmod/roof/shingles_blue_shiny
* textures/darkmod/roof/shingles_red_shiny
* Improved: textures/darkmod/roof/shingles_red
* textures/darkmod/nature/bones/skull_panels_dirty
* textures/darkmod/nature/bones/bone_wall
* textures/darkmod/nature/bones/tiling_1d/trim_bones
Baddcog:
* textures/darkmod/roof/rooftiles_ceramic_blue
* textures/darkmod/roof/rooftiles_ceramic_brown
* textures/darkmod/roof/rooftiles_ceramic_red
Renzatic:
* textures/darkmod/plaster/tiling_1d/plaster_rot01
* textures/darkmod/nature/dirt/dirt_packed_grey
* textures/darkmod/stone/brick/bricks_ind_grey
* textures/darkmod/stone/brick/bricks_mossy01
* textures/darkmod/stone/brick/stone_rough_segmented
* textures/darkmod/stone/cobblestones/cobblestone_vert_grey
* textures/darkmod/stone/sculpted/tiling_1d/concrete_trim01
* textures/darkmod/wood/boards/wood_rot_planks01
* textures/darkmod/wood/boards/wood_rot_planks02
* textures/darkmod/wood/panels/tiling_1d/wood_old_trim01
* textures/darkmod/wood/panels/tiling_1d/wood_rot_trim01

== See also ==

* [http://thedarkmod.com/downloads.php Download TDM]

What's new in TDM 1.01

2010-01-30T22:31:08Z

Ishtvan:

This article is a work-in-progress and can change before the final release. There are '''no promises''' here. Features may be postponed or removed even if they appear on this list, and regressions may re-introduce bugs after they've been fixed internally. See also the changelog on our bugtracker page: [http://bugs.angua.at/changelog_page.php?project_id=2 Changelog].

== Bugs fixed ==
* [http://bugs.angua.at/view.php?id=1921 #1921]: HUD Font reverts to Doom 3 font after fresh gamesave load.
* [http://bugs.angua.at/view.php?id=1963 #1963]: Double doors sometimes highlight at a distance.
* [http://bugs.angua.at/view.php?id=1968 #1968] Blackjack no longer makes metallic clang when hitting world
* [http://bugs.angua.at/view.php?id=1970 #1970]: Chests went non-solid when frobbed
* [http://bugs.angua.at/view.php?id=1976 #1976]: Shop items get duplicated on "Restart" after dying
* [http://bugs.angua.at/view.php?id=1990 #1990]: No SOUND on TDM after installing a mission, added CVAR (tdm_fm_restart_delay) to issue a delay request to tdmlauncher.
* [http://bugs.angua.at/view.php?id=1996 #1996]: Fixed bug that made shouldered bodies undroppable
* [http://bugs.angua.at/view.php?id=2007 #2007]: Fixed: Location settings did igore the "music volume" slider
* [http://bugs.angua.at/view.php?id=2067 #2067]: Fixed bug when using shop_skip 1 in FMs.
* [http://bugs.angua.at/view.php?id=2072 #2072]: Rats (and other small animals) could be shouldered
* [http://bugs.angua.at/view.php?id=2075 #2075]: AI were alerted when they took falling damage
* [http://bugs.angua.at/view.php?id=2083 #2083]: Small items like candles, candle holders, rocks etc floated on water instead of sinking
* [http://bugs.angua.at/view.php?id=2093 #2093]: Fireplace_arch was missing its texture
* [http://bugs.angua.at/view.php?id=2117 #2117]: frob_peer hilite does not sync.
* [http://bugs.angua.at/view.php?id=2119 #2119]: Player's run footfall sounds are played while shouldering a body
* Fixed savegames getting to huge sizes, leading to out-of-memory or crashes
* Fixed a few crashes and memory errors
* Fixed: Crash with ATI cards when viewing certain models (like the marble column)
* Fixed: Location settings did not work with "fast" ambient method
* Melee controls now more responsive
* Fixed blackjack bug where player could hit low ceilings
* Fixed archer bows blocking blackjack attempts
* Fixed bug where some close-range melee attacks neglected armor
* Minor fixes to models and textures (e.g. inverted normals)
* Added a bunch of missing editor images for models (STiFU).

== Features added ==
* [http://bugs.angua.at/view.php?id=2123 #2123]: In-game objectives display
* A lot new skins for: dirty fireplaces, unlit lamps etc.
* New script events for: get/setDroppable, isEntityHidden, Melee etc.
* Support for "skin_unlit" and "skin_lit" on light entities
* New "unbindOnAlertIndex" spawnarg on attached entities, to make AI drop them when alerted
* Crouch indicator: Lightgem "wings" squash down slightly when crouch mode is on (helpful when climbing)
* AI have a combat skill level now: novice, trained, skilled
* added Difficulty Slider for combat in menu
* [http://bugs.angua.at/view.php?id=2024 AI can be set to drop attached objects on alert]
* greater flexibility added to absence markers
* [http://bugs.angua.at/view.php?id=2012 #2012]: GC's movetype-specific metal footstep sounds are in-game
* [http://bugs.angua.at/view.php?id=2015 #2015]: Added console commands to control logging to darkmod.log
* [http://bugs.angua.at/view.php?id=2002 #2002]: FM Installer Code checks required version of Mission to be installed, information can be added to darkmod.txt in the FM package.
* [http://bugs.angua.at/view.php?id=1977 #1977]: FM Installer Code considers ZIP files as well as PK4s now
* [http://bugs.angua.at/view.php?id=1984 #1984]: FM Installer Code needs to replace dashes with underscores on creating the fms subfolder
* [http://bugs.angua.at/view.php?id=2080 #2080]: Doors have a larger sound radius now.

== AI added ==

* added two zombie types with various skins, as well as "sleeping" behaviour
* added spiders and spider children
* added new elite guard character
* added elite guard helmet (immune to KOs)
* added skeleton AI
* added revenant character
* added male beggar character
* added male pagan character

== Entities added ==

* A lot of new [[combo entities]] have been added:
** fireplaces,
** static torches,
** statues with torch in hand,
** campfires, bucket and bonfires,
** electric streetlights,
** wall-mounted lamps and torches,
** geodes with pulsating light,
** bottles+candle,
** skulls+candle etc.
* new colored torch flames: blue, green, orange
* new fireflames: white and black smoking, smouldering ones, large and huge bonfires, bucketfire
* a few new model props (eg, saw, wall-light)
* climbable ragdoll chains
* [http://bugs.angua.at/view.php?id=2110 Bug #2110] [[Loot paintings]]

== Sounds ==

* changed AI footsteps to mono (so the direction of sound is accurate)
* reduced volume of player footsteps
* increased sound radius of doors

Added Dario D's ambient sound contributions.

* Ambient Shaders added
** animal_crickets_birds01, animal_crickets04, animal_crickets05, animal_dog03, animal_frog03, animal_night_bird01, animal_owl04, animal_owl05, animal_owl06
** machine_sparks01
** music_harp01, music_harp02, music_bum_bum01, music_bum_bum02
** weather_thunder04, weather_thunder05
* Environmental Sound Shaders added
** drone01, drone02, drone03a, drone03b, drone05a, drone05b
** hit01a, hit02b, hit03a, hit03b
** hum01, hum01b, hum02, hum03, hum04, hum05_loop, hum05_loop_b, hum06_loop, hum06_loop_b, hum07_loop, hum07_loop_b, hum08

== Textures ==
Added STiFU's, Renzatic's and Baddcog's textures, including the following shaders:
STiFU:
* textures/darkmod/door/wood/board_brown_nails_hinge
* textures/darkmod/metal/detailed/threadplate_large_dirty
* textures/darkmod/roof/slate_cracked_large_greyblue
* textures/darkmod/roof/slate_cracked_large_greyblue_shiny
* textures/darkmod/stone/brick/tiling_1d/poolwall_large_dirty_weathered_greengrey
* textures/darkmod/stone/brick/tiling_1d/poolwall_large_dirty_weathered_greengrey_wet
* textures/darkmod/stone/cobblestones/cobblestones_large_uneven_darkgrey
* textures/darkmod/stone/cobblestones/cobblestones_large_uneven_darkgrey_wet
* textures/darkmod/stone/flat/tiles_ceramic_large_clean_even
* textures/darkmod/stone/flat/tiles_ceramic_large_clean_rough
* textures/darkmod/stone/flat/tiles_ceramic_large_ornate_old_blue
* textures/darkmod/stone/flat/tiles_large_dirty_cracked
* textures/darkmod/stone/flat/tiles_large_dirty_cracked_greasy
* textures/darkmod/stone/natural/rock_large_rough_grey
* textures/darkmod/stone/natural/rock_large_rough_grey_greasy
* textures/darkmod/stone/natural/rock_large_cracked_holey_grey
* textures/darkmod/stone/natural/rock_large_cracked_holey_grey_greasy
* textures/darkmod/stone/sculpted/tiling_1d/trim_large_ornate_old_bright
* textures/darkmod/stone/sculpted/tiling_1d/trim_large_ornate_old_bright_greasy
* textures/darkmod/stone/sculpted/tiling_1d/trim_large_ornate_old_dark_bluered
* textures/darkmod/stone/sculpted/tiling_1d/trim_large_ornate_old_dark_bluered_greasy
* textures/darkmod/stone/sculpted/tiling_1d/trim_small_ornate_old
* textures/darkmod/stone/sculpted/tiling_1d/trim_small_ornate_old_greasy
* textures/darkmod/wood/boards/polished_shiny_large_red
* textures/darkmod/wood/boards/rough_wood_large_brown
* textures/darkmod/wood/boards/rough_wood_large_brown_glossy
* textures/darkmod/wood/boards/planks_wood_large_worn_rough_bright
* textures/darkmod/wood/boards/planks_wood_large_worn_rough_bright_glossy
* textures/darkmod/wood/boards/planks_wood_large_worn_rough_dark
* textures/darkmod/wood/boards/planks_wood_large_worn_rough_dark_glossy
* textures/darkmod/wood/boards/roof_framework_boards_large_old_brown
* textures/darkmod/wood/boards/roof_framework_boards_large_old_green
* textures/darkmod/roof/shingles_blue
* textures/darkmod/roof/shingles_blue_shiny
* textures/darkmod/roof/shingles_red_shiny
* Improved: textures/darkmod/roof/shingles_red
* textures/darkmod/nature/bones/skull_panels_dirty
* textures/darkmod/nature/bones/bone_wall
* textures/darkmod/nature/bones/tiling_1d/trim_bones
Baddcog:
* textures/darkmod/roof/rooftiles_ceramic_blue
* textures/darkmod/roof/rooftiles_ceramic_brown
* textures/darkmod/roof/rooftiles_ceramic_red
Renzatic:
* textures/darkmod/plaster/tiling_1d/plaster_rot01
* textures/darkmod/nature/dirt/dirt_packed_grey
* textures/darkmod/stone/brick/bricks_ind_grey
* textures/darkmod/stone/brick/bricks_mossy01
* textures/darkmod/stone/brick/stone_rough_segmented
* textures/darkmod/stone/cobblestones/cobblestone_vert_grey
* textures/darkmod/stone/sculpted/tiling_1d/concrete_trim01
* textures/darkmod/wood/boards/wood_rot_planks01
* textures/darkmod/wood/boards/wood_rot_planks02
* textures/darkmod/wood/panels/tiling_1d/wood_old_trim01
* textures/darkmod/wood/panels/tiling_1d/wood_rot_trim01

== See also ==

* [http://thedarkmod.com/downloads.php Download TDM]

What's new in TDM 1.01

2010-01-20T22:09:19Z

Ishtvan:

Euler Angle Convention Used in Doom3

2008-12-13T19:39:42Z

Ishtvan: /* Order of rotations */

[http://en.wikipedia.org/wiki/Euler_angles Euler Angles] are a way of specifying the orientation of a given object relative to three reference axes in the world. To orient objects, Doom3 uses the "angles" spawnarg, which takes three space-delimited values, defined as: "pitch yaw roll". We need to know more than this to precisely specify the orientation of something. We need to know which axis is which, and we need to know the order in which these operations are performed.

== Definition of axes==
Imagine you are standing in a Doom3 map. The '''z''' axis is up. A pure yaw rotates about the '''z''' axis. The '''x''' axis is forward. A pure roll rotates about the x axis. The '''y''' axis extends out to your left. A pure pitch rotates about the '''y''' axis.

== Order of rotations ==
To determine the order of multiple rotations, Doom3 uses the "yaw, pitch, roll" convention (also known as "zyx," the full rotation matrix for this convention is given in [http://en.wikipedia.org/wiki/Euler_angles this article]). Let's say you have entered a spawnarg as "pitch yaw roll." This is how Doom3 applies these values to orient an object: First, the yaw is applied about the world '''z''' axis, second, the pitch is applied about the yawed '''y''' axis, and third, the roll is applied about the yawed and pitched '''x''' axis.

== Sign Conventions ==
In mathematics, a clockwise rotation is a positive angle, and a counterclockwise rotation is a negative angle. Pitch, yaw and roll have their own conventions. The combination of the defined axes, the mathematical rotation sign convention, and the sign conventions of pitch, yaw and roll result in some sign changes when going from the pitch, yaw, roll angles to the actual angular rotation about the axis that is entered in to the rotation matrix. The conventions are described below:

Pitch is positive when pitching from forward to up. This is a counterclockwise rotation about the '''y''' (left) axis. Therefore, positive pitch means negative rotation angle. Yaw is positive when rotating from the forward to the right. This is a counterclockwise rotation about the '''z''' (up) axis. Therefore, positive yaw means negative rotation angle. Roll is positive when rotating from up to right. This is a clockwise rotation about the '''x''' (forward) axis. Therefore, positive roll means positive rotation angle.

== Example 1 ==
Suppose you start out with an airplane pointing straight ahead with level wings. You want the airplane to end up pointing all the way to your right, with the right wing pointing down at the ground. Keeping in mind that the angles are applied in the order of yaw, pitch, roll, we enter a yaw of +90 degrees, and a roll of 90 degrees. We would enter in an angles spawnarg "pitch yaw roll" of "0 90 90". If instead the roll had been applied before the yaw, these angles would have resulted in an airplane pointing straight down with its wings extending forward and back, so the order of rotations does matter.

== Example 2 ==
Again you start out with an airplane pointing straight ahead with wings level. Now, you want the airplane nose pointing to your left and up 45 degrees, and you want the airplane to be upside-down. Again, yaw is applied first, then pitch, then roll. So we know yaw must be -90, pointing the airplane left. Pitch is +45, tipping the nose up, and roll is 180, rotating the plane upside-down about its long axis. We therefore enter an angles spawnarg ("pitch yaw roll") of "45 -90 180".

== Attaching to AI Joints of Unknown Orientation ==
When attaching objects to AI joints and trying to orient the attached object relative to the joint, oftentimes you don't know how the joint is oriented relative to the world axes. You can use '''r_showskel 1''' in the console to show the joints and display a line for each axis. You still don't know which axis is which. To figure out how to orient something relative to the joint, first apply a yaw rotation by setting the attachment angles to "0 <test angle> 0", and see how that differs from angles of "0 0 0". (It is easiest to see the difference by spawning the AI with the attachment angle set to "0 0 0", changing the angle, then calling '''reloaddecls''' and spawning another AI). Now you know which way yaw rotates. Do the same for pitch, now you know which way pitch rotates, and by process of elimination you know roll. Now you know what will happen when you input angles to orient something relative to the joint. First it will rotate in the sense you identified as yaw, then in pitch, then finally in roll.

{{editing}} {{coding}} {{ai}}

Euler Angle Convention Used in Doom3

2008-09-22T00:48:37Z

Ishtvan:

[http://en.wikipedia.org/wiki/Euler_angles Euler Angles] are a way of specifying the orientation of a given object relative to three reference axes in the world. To orient objects, Doom3 uses the "angles" spawnarg, which takes three space-delimited values, defined as: "pitch yaw roll". We need to know more than this to precisely specify the orientation of something. We need to know which axis is which, and we need to know the order in which these operations are performed.

== Definition of axes==
Imagine you are standing in a Doom3 map. The '''z''' axis is up. A pure yaw rotates about the '''z''' axis. The '''x''' axis is forward. A pure roll rotates about the x axis. The '''y''' axis extends out to your left. A pure pitch rotates about the '''y''' axis.

== Order of rotations ==
It turns out that Doom3 uses the "yaw, pitch, roll" convention (also known as "zyx," the full rotation matrix for this convention is given in [http://en.wikipedia.org/wiki/Euler_angles this article]). Let's say you have entered a spawnarg as "pitch yaw roll." This is how Doom3 applies these values to orient an object: First, the yaw is applied about the world '''z''' axis, second, the pitch is applied about the yawed '''y''' axis, and third, the roll is applied about the yawed and pitched '''x''' axis.

== Sign Conventions ==
In mathematics, a clockwise rotation is a positive angle, and a counterclockwise rotation is a negative angle. Pitch, yaw and roll have their own conventions. The combination of the defined axes, the mathematical rotation sign convention, and the sign conventions of pitch, yaw and roll result in some sign changes when going from the pitch, yaw, roll angles to the actual angular rotation about the axis that is entered in to the rotation matrix. The conventions are described below:

Pitch is positive when pitching from forward to up. This is a counterclockwise rotation about the '''y''' (left) axis. Therefore, positive pitch means negative rotation angle. Yaw is positive when rotating from the forward to the right. This is a counterclockwise rotation about the '''z''' (up) axis. Therefore, positive yaw means negative rotation angle. Roll is positive when rotating from up to right. This is a clockwise rotation about the '''x''' (forward) axis. Therefore, positive roll means positive rotation angle.

== Example 1 ==
Suppose you start out with an airplane pointing straight ahead with level wings. You want the airplane to end up pointing all the way to your right, with the right wing pointing down at the ground. Keeping in mind that the angles are applied in the order of yaw, pitch, roll, we enter a yaw of +90 degrees, and a roll of 90 degrees. We would enter in an angles spawnarg "pitch yaw roll" of "0 90 90". If instead the roll had been applied before the yaw, these angles would have resulted in an airplane pointing straight down with its wings extending forward and back, so the order of rotations does matter.

== Example 2 ==
Again you start out with an airplane pointing straight ahead with wings level. Now, you want the airplane nose pointing to your left and up 45 degrees, and you want the airplane to be upside-down. Again, yaw is applied first, then pitch, then roll. So we know yaw must be -90, pointing the airplane left. Pitch is +45, tipping the nose up, and roll is 180, rotating the plane upside-down about its long axis. We therefore enter an angles spawnarg ("pitch yaw roll") of "45 -90 180".

== Attaching to AI Joints of Unknown Orientation ==
When attaching objects to AI joints and trying to orient the attached object relative to the joint, oftentimes you don't know how the joint is oriented relative to the world axes. You can use '''r_showskel 1''' in the console to show the joints and display a line for each axis. You still don't know which axis is which. To figure out how to orient something relative to the joint, first apply a yaw rotation by setting the attachment angles to "0 <test angle> 0", and see how that differs from angles of "0 0 0". (It is easiest to see the difference by spawning the AI with the attachment angle set to "0 0 0", changing the angle, then calling '''reloaddecls''' and spawning another AI). Now you know which way yaw rotates. Do the same for pitch, now you know which way pitch rotates, and by process of elimination you know roll. Now you know what will happen when you input angles to orient something relative to the joint. First it will rotate in the sense you identified as yaw, then in pitch, then finally in roll.

{{editing}} {{coding}} {{ai}}

Euler Angle Convention Used in Doom3

2008-09-20T08:46:56Z

Ishtvan: /* Attaching to AI Joints of Unknown Orientation */

[http://en.wikipedia.org/wiki/Euler_angles Euler Angles] are a way of specifying the orientation of a given object relative to three reference axes in the world. To orient objects, Doom3 uses the "angles" spawnarg, which takes three space-delimited values, defined as: "pitch yaw roll". We need to know more than this to precisely specify the orientation of something. We need to know which axis is which, and we need to know the order in which these operations are performed.

== Definition of axes==
Imagine you are standing in a Doom3 map. The '''z''' axis is up. A pure yaw rotates about the '''z''' axis. The '''x''' axis is forward. A pure roll rotates about the x axis. The '''y''' axis extends out to your left. A pure pitch rotates about the '''y''' axis.

== Order of rotations ==
It turns out that Doom3 uses the "yaw, pitch, roll" convention (also known as "zyx," the full rotation matrix for this convention is given in [http://en.wikipedia.org/wiki/Euler_angles this article]). Let's say you have entered a spawnarg as "pitch yaw roll." This is how Doom3 applies these values to orient an object: First, the yaw is applied about the world '''z''' axis, second, the pitch is applied about the yawed '''y''' axis, and third, the roll is applied about the yawed and pitched '''x''' axis.

== Sign Conventions ==
In mathematics, a clockwise rotation is a positive angle, and a counterclockwise rotation is a negative angle. Pitch, yaw and roll have their own conventions (positive pitch is rotating something from forward to the ceiling). The combination of the defined axes, the mathematical rotation sign convention, and the sign conventions of pitch, yaw and roll result in some sign changes when going from the pitch, yaw, roll angles to the actual angular rotation about the axis that is entered in to the rotation matrix. The conventions are described below:

Pitch is positive when pitching from forward to up. This is a counterclockwise rotation about the '''y''' (left) axis. Therefore, positive pitch means negative rotation angle. Yaw is positive when rotating from the forward to the right. This is a counterclockwise rotation about the '''z''' (up) axis. Therefore, positive yaw means negative rotation angle. Roll is positive when rotating from up to right. This is a clockwise rotation about the '''x''' (forward) axis. Therefore, positive roll means positive rotation angle.

== Example 1 ==
Suppose you start out with an airplane pointing straight ahead with level wings. You want the airplane to end up pointing all the way to your right, with the right wing pointing down at the ground. Keeping in mind that the angles are applied in the order of yaw, pitch, roll, we enter a yaw of +90 degrees, and a roll of 90 degrees. We would enter in an angles spawnarg "pitch yaw roll" of "0 90 90". If instead the roll had been applied before the yaw, these angles would have resulted in an airplane pointing straight down with its wings extending forward and back, so the order of rotations does matter.

== Example 2 ==
Again you start out with an airplane pointing straight ahead with wings level. Now, you want the airplane nose pointing to your left and up 45 degrees, and you want the airplane to be upside-down. Again, yaw is applied first, then pitch, then roll. So we know yaw must be -90, pointing the airplane left. Pitch is +45, tipping the nose up, and roll is 180, rotating the plane upside-down about its long axis. We therefore enter an angles spawnarg ("pitch yaw roll") of "45 -90 180".

== Attaching to AI Joints of Unknown Orientation ==
When attaching objects to AI joints and trying to orient the attached object relative to the joint, oftentimes you don't know how the joint is oriented relative to the world axes. You can use '''r_showskel 1''' in the console to show the joints and display a line for each axis. You still don't know which axis is which. To figure out how to orient something relative to the joint, first apply a yaw rotation by setting the attachment angles to "0 <test angle> 0", and see how that differs from angles of "0 0 0". (It is easiest to see the difference by spawning the AI with the attachment angle set to "0 0 0", changing the angle, then calling '''reloaddecls''' and spawning another AI). Now you know which way yaw rotates. Do the same for pitch, now you know which way pitch rotates, and by process of elimination you know roll. Now you know what will happen when you input angles to orient something relative to the joint. First it will rotate in the sense you identified as yaw, then in pitch, then finally in roll.

{{editing}} {{coding}} {{ai}}

Euler Angle Convention Used in Doom3

2008-09-20T08:45:49Z

Ishtvan: /* Attaching to AI Joints of Unknown Orientation */

[http://en.wikipedia.org/wiki/Euler_angles Euler Angles] are a way of specifying the orientation of a given object relative to three reference axes in the world. To orient objects, Doom3 uses the "angles" spawnarg, which takes three space-delimited values, defined as: "pitch yaw roll". We need to know more than this to precisely specify the orientation of something. We need to know which axis is which, and we need to know the order in which these operations are performed.

== Definition of axes==
Imagine you are standing in a Doom3 map. The '''z''' axis is up. A pure yaw rotates about the '''z''' axis. The '''x''' axis is forward. A pure roll rotates about the x axis. The '''y''' axis extends out to your left. A pure pitch rotates about the '''y''' axis.

== Order of rotations ==
It turns out that Doom3 uses the "yaw, pitch, roll" convention (also known as "zyx," the full rotation matrix for this convention is given in [http://en.wikipedia.org/wiki/Euler_angles this article]). Let's say you have entered a spawnarg as "pitch yaw roll." This is how Doom3 applies these values to orient an object: First, the yaw is applied about the world '''z''' axis, second, the pitch is applied about the yawed '''y''' axis, and third, the roll is applied about the yawed and pitched '''x''' axis.

== Sign Conventions ==
In mathematics, a clockwise rotation is a positive angle, and a counterclockwise rotation is a negative angle. Pitch, yaw and roll have their own conventions (positive pitch is rotating something from forward to the ceiling). The combination of the defined axes, the mathematical rotation sign convention, and the sign conventions of pitch, yaw and roll result in some sign changes when going from the pitch, yaw, roll angles to the actual angular rotation about the axis that is entered in to the rotation matrix. The conventions are described below:

Pitch is positive when pitching from forward to up. This is a counterclockwise rotation about the '''y''' (left) axis. Therefore, positive pitch means negative rotation angle. Yaw is positive when rotating from the forward to the right. This is a counterclockwise rotation about the '''z''' (up) axis. Therefore, positive yaw means negative rotation angle. Roll is positive when rotating from up to right. This is a clockwise rotation about the '''x''' (forward) axis. Therefore, positive roll means positive rotation angle.

== Example 1 ==
Suppose you start out with an airplane pointing straight ahead with level wings. You want the airplane to end up pointing all the way to your right, with the right wing pointing down at the ground. Keeping in mind that the angles are applied in the order of yaw, pitch, roll, we enter a yaw of +90 degrees, and a roll of 90 degrees. We would enter in an angles spawnarg "pitch yaw roll" of "0 90 90". If instead the roll had been applied before the yaw, these angles would have resulted in an airplane pointing straight down with its wings extending forward and back, so the order of rotations does matter.

== Example 2 ==
Again you start out with an airplane pointing straight ahead with wings level. Now, you want the airplane nose pointing to your left and up 45 degrees, and you want the airplane to be upside-down. Again, yaw is applied first, then pitch, then roll. So we know yaw must be -90, pointing the airplane left. Pitch is +45, tipping the nose up, and roll is 180, rotating the plane upside-down about its long axis. We therefore enter an angles spawnarg ("pitch yaw roll") of "45 -90 180".

== Attaching to AI Joints of Unknown Orientation ==
When attaching things to AI joints and trying to orient them, oftentimes you don't know how the joint is oriented. You can use '''r_showskel 1''' in the console to show the joints and display a line for each axis. You still don't know which axis is which. To figure out how to orient something relative to the joint, first apply a yaw rotation by setting the attachment angles to "0 <test angle> 0", and see how that differs from angles of "0 0 0". (It is easiest to see the difference by spawning the AI with the attachment angle set to "0 0 0", changing the angle, then calling '''reloaddecls''' and spawning another AI). Now you know which way yaw rotates. Do the same for pitch, now you know which way pitch rotates, and by process of elimination you know roll. Now you know what will happen when you input angles to orient something relative to the joint. First it will rotate in the sense you identified as yaw, then in pitch, then finally in roll.

{{editing}} {{coding}} {{ai}}

Euler Angle Convention Used in Doom3

2008-09-20T08:45:28Z

Ishtvan: /* Attaching to AI Joints of Unknown Orientation */

[http://en.wikipedia.org/wiki/Euler_angles Euler Angles] are a way of specifying the orientation of a given object relative to three reference axes in the world. To orient objects, Doom3 uses the "angles" spawnarg, which takes three space-delimited values, defined as: "pitch yaw roll". We need to know more than this to precisely specify the orientation of something. We need to know which axis is which, and we need to know the order in which these operations are performed.

== Definition of axes==
Imagine you are standing in a Doom3 map. The '''z''' axis is up. A pure yaw rotates about the '''z''' axis. The '''x''' axis is forward. A pure roll rotates about the x axis. The '''y''' axis extends out to your left. A pure pitch rotates about the '''y''' axis.

== Order of rotations ==
It turns out that Doom3 uses the "yaw, pitch, roll" convention (also known as "zyx," the full rotation matrix for this convention is given in [http://en.wikipedia.org/wiki/Euler_angles this article]). Let's say you have entered a spawnarg as "pitch yaw roll." This is how Doom3 applies these values to orient an object: First, the yaw is applied about the world '''z''' axis, second, the pitch is applied about the yawed '''y''' axis, and third, the roll is applied about the yawed and pitched '''x''' axis.

== Sign Conventions ==
In mathematics, a clockwise rotation is a positive angle, and a counterclockwise rotation is a negative angle. Pitch, yaw and roll have their own conventions (positive pitch is rotating something from forward to the ceiling). The combination of the defined axes, the mathematical rotation sign convention, and the sign conventions of pitch, yaw and roll result in some sign changes when going from the pitch, yaw, roll angles to the actual angular rotation about the axis that is entered in to the rotation matrix. The conventions are described below:

Pitch is positive when pitching from forward to up. This is a counterclockwise rotation about the '''y''' (left) axis. Therefore, positive pitch means negative rotation angle. Yaw is positive when rotating from the forward to the right. This is a counterclockwise rotation about the '''z''' (up) axis. Therefore, positive yaw means negative rotation angle. Roll is positive when rotating from up to right. This is a clockwise rotation about the '''x''' (forward) axis. Therefore, positive roll means positive rotation angle.

== Example 1 ==
Suppose you start out with an airplane pointing straight ahead with level wings. You want the airplane to end up pointing all the way to your right, with the right wing pointing down at the ground. Keeping in mind that the angles are applied in the order of yaw, pitch, roll, we enter a yaw of +90 degrees, and a roll of 90 degrees. We would enter in an angles spawnarg "pitch yaw roll" of "0 90 90". If instead the roll had been applied before the yaw, these angles would have resulted in an airplane pointing straight down with its wings extending forward and back, so the order of rotations does matter.

== Example 2 ==
Again you start out with an airplane pointing straight ahead with wings level. Now, you want the airplane nose pointing to your left and up 45 degrees, and you want the airplane to be upside-down. Again, yaw is applied first, then pitch, then roll. So we know yaw must be -90, pointing the airplane left. Pitch is +45, tipping the nose up, and roll is 180, rotating the plane upside-down about its long axis. We therefore enter an angles spawnarg ("pitch yaw roll") of "45 -90 180".

== Attaching to AI Joints of Unknown Orientation ==
When attaching things to AI joints and trying to orient them, oftentimes you don't know how the joint is oriented. You can use '''r_showskel 1''' in the console to show the joints and display a line for each axis. You still don't know which axis is which. To figure out how to orient something relative to the joint, first apply a yaw rotation by setting the attachment angles to "0 <test angle> 0", and see how that differs from angles of "0 0 0". (It is easiest to see the difference by spawning the AI with the attachment angle set to "0 0 0", changing the angle, then calling '''reloaddecls''' and spawning another AI). Now you know which way yaw rotates. Do the same for pitch, now you know which way pitch rotates, and by process of elimination you know roll. Now you know what will happen when you input angles to orient something relative to the joint. It will rotate first in the sense you identified as yaw, then in pitch, then finally in roll.

{{editing}} {{coding}} {{ai}}

Euler Angle Convention Used in Doom3

2008-09-20T08:45:01Z

Ishtvan: /* Attaching to AI Joints of Unknown Orientation */

[http://en.wikipedia.org/wiki/Euler_angles Euler Angles] are a way of specifying the orientation of a given object relative to three reference axes in the world. To orient objects, Doom3 uses the "angles" spawnarg, which takes three space-delimited values, defined as: "pitch yaw roll". We need to know more than this to precisely specify the orientation of something. We need to know which axis is which, and we need to know the order in which these operations are performed.

== Definition of axes==
Imagine you are standing in a Doom3 map. The '''z''' axis is up. A pure yaw rotates about the '''z''' axis. The '''x''' axis is forward. A pure roll rotates about the x axis. The '''y''' axis extends out to your left. A pure pitch rotates about the '''y''' axis.

== Order of rotations ==
It turns out that Doom3 uses the "yaw, pitch, roll" convention (also known as "zyx," the full rotation matrix for this convention is given in [http://en.wikipedia.org/wiki/Euler_angles this article]). Let's say you have entered a spawnarg as "pitch yaw roll." This is how Doom3 applies these values to orient an object: First, the yaw is applied about the world '''z''' axis, second, the pitch is applied about the yawed '''y''' axis, and third, the roll is applied about the yawed and pitched '''x''' axis.

== Sign Conventions ==
In mathematics, a clockwise rotation is a positive angle, and a counterclockwise rotation is a negative angle. Pitch, yaw and roll have their own conventions (positive pitch is rotating something from forward to the ceiling). The combination of the defined axes, the mathematical rotation sign convention, and the sign conventions of pitch, yaw and roll result in some sign changes when going from the pitch, yaw, roll angles to the actual angular rotation about the axis that is entered in to the rotation matrix. The conventions are described below:

Pitch is positive when pitching from forward to up. This is a counterclockwise rotation about the '''y''' (left) axis. Therefore, positive pitch means negative rotation angle. Yaw is positive when rotating from the forward to the right. This is a counterclockwise rotation about the '''z''' (up) axis. Therefore, positive yaw means negative rotation angle. Roll is positive when rotating from up to right. This is a clockwise rotation about the '''x''' (forward) axis. Therefore, positive roll means positive rotation angle.

== Example 1 ==
Suppose you start out with an airplane pointing straight ahead with level wings. You want the airplane to end up pointing all the way to your right, with the right wing pointing down at the ground. Keeping in mind that the angles are applied in the order of yaw, pitch, roll, we enter a yaw of +90 degrees, and a roll of 90 degrees. We would enter in an angles spawnarg "pitch yaw roll" of "0 90 90". If instead the roll had been applied before the yaw, these angles would have resulted in an airplane pointing straight down with its wings extending forward and back, so the order of rotations does matter.

== Example 2 ==
Again you start out with an airplane pointing straight ahead with wings level. Now, you want the airplane nose pointing to your left and up 45 degrees, and you want the airplane to be upside-down. Again, yaw is applied first, then pitch, then roll. So we know yaw must be -90, pointing the airplane left. Pitch is +45, tipping the nose up, and roll is 180, rotating the plane upside-down about its long axis. We therefore enter an angles spawnarg ("pitch yaw roll") of "45 -90 180".

== Attaching to AI Joints of Unknown Orientation ==
When attaching things to AI joints and trying to orient them, oftentimes you don't know how the joint is oriented. You can use '''r_showskel 1''' in the console to show the joints and display a line for each axis. You still don't know which axis is which. To figure out how to orient something relative to the joint, first apply a yaw rotation by setting the attachment angles to "0 <test angle> 0", and see how that differs from angles of "0 0 0". (It is easiest to see the difference by spawning the AI with the attachment angle set to "0 0 0", changing the angle, then calling '''reloaddecls''' and spawning another AI). Now you know which way yaw rotates. Do the same for pitch, now you know which way pitch rotates, and by process of elimination you know roll. Now you know what will happen when you input angles to orient something relative to the joint. It will rotate in the sense you identified as yaw, then in pitch, then finally in roll.

{{editing}} {{coding}} {{ai}}

Euler Angle Convention Used in Doom3

2008-09-20T08:44:20Z

Ishtvan: /* Attaching to AI Joints of Unknown Orientation */

[http://en.wikipedia.org/wiki/Euler_angles Euler Angles] are a way of specifying the orientation of a given object relative to three reference axes in the world. To orient objects, Doom3 uses the "angles" spawnarg, which takes three space-delimited values, defined as: "pitch yaw roll". We need to know more than this to precisely specify the orientation of something. We need to know which axis is which, and we need to know the order in which these operations are performed.

== Definition of axes==
Imagine you are standing in a Doom3 map. The '''z''' axis is up. A pure yaw rotates about the '''z''' axis. The '''x''' axis is forward. A pure roll rotates about the x axis. The '''y''' axis extends out to your left. A pure pitch rotates about the '''y''' axis.

== Order of rotations ==
It turns out that Doom3 uses the "yaw, pitch, roll" convention (also known as "zyx," the full rotation matrix for this convention is given in [http://en.wikipedia.org/wiki/Euler_angles this article]). Let's say you have entered a spawnarg as "pitch yaw roll." This is how Doom3 applies these values to orient an object: First, the yaw is applied about the world '''z''' axis, second, the pitch is applied about the yawed '''y''' axis, and third, the roll is applied about the yawed and pitched '''x''' axis.

== Sign Conventions ==
In mathematics, a clockwise rotation is a positive angle, and a counterclockwise rotation is a negative angle. Pitch, yaw and roll have their own conventions (positive pitch is rotating something from forward to the ceiling). The combination of the defined axes, the mathematical rotation sign convention, and the sign conventions of pitch, yaw and roll result in some sign changes when going from the pitch, yaw, roll angles to the actual angular rotation about the axis that is entered in to the rotation matrix. The conventions are described below:

Pitch is positive when pitching from forward to up. This is a counterclockwise rotation about the '''y''' (left) axis. Therefore, positive pitch means negative rotation angle. Yaw is positive when rotating from the forward to the right. This is a counterclockwise rotation about the '''z''' (up) axis. Therefore, positive yaw means negative rotation angle. Roll is positive when rotating from up to right. This is a clockwise rotation about the '''x''' (forward) axis. Therefore, positive roll means positive rotation angle.

== Example 1 ==
Suppose you start out with an airplane pointing straight ahead with level wings. You want the airplane to end up pointing all the way to your right, with the right wing pointing down at the ground. Keeping in mind that the angles are applied in the order of yaw, pitch, roll, we enter a yaw of +90 degrees, and a roll of 90 degrees. We would enter in an angles spawnarg "pitch yaw roll" of "0 90 90". If instead the roll had been applied before the yaw, these angles would have resulted in an airplane pointing straight down with its wings extending forward and back, so the order of rotations does matter.

== Example 2 ==
Again you start out with an airplane pointing straight ahead with wings level. Now, you want the airplane nose pointing to your left and up 45 degrees, and you want the airplane to be upside-down. Again, yaw is applied first, then pitch, then roll. So we know yaw must be -90, pointing the airplane left. Pitch is +45, tipping the nose up, and roll is 180, rotating the plane upside-down about its long axis. We therefore enter an angles spawnarg ("pitch yaw roll") of "45 -90 180".

== Attaching to AI Joints of Unknown Orientation ==
When attaching things to AI joints and trying to orient them, oftentimes you don't know how the joint is oriented. You can use '''r_showskel 1''' in the console to show the joints and display a line for each axis. You still don't know which axis is which. To figure out how to orient something relative to the joint, first apply a yaw rotation by setting the attachment angles to "0 <test angle> 0", and see how that differs from angles of "0 0 0". (It is easiest to see the difference by spawning a copy of the AI with the attachment angle of "0 0 0", changing the angle, then calling '''reloaddecls''' and spawning another AI). Now you know which way yaw rotates. Do the same for pitch, now you know which way pitch rotates, and by process of elimination you know roll. Now you know what will happen when you input angles to orient something relative to the joint. It will rotate in the sense you identified as yaw, then in pitch, then finally in roll.

{{editing}} {{coding}} {{ai}}

Euler Angle Convention Used in Doom3

2008-09-20T08:42:36Z

Ishtvan: /* Attaching to AI Joints of Unknown Orientation */

[http://en.wikipedia.org/wiki/Euler_angles Euler Angles] are a way of specifying the orientation of a given object relative to three reference axes in the world. To orient objects, Doom3 uses the "angles" spawnarg, which takes three space-delimited values, defined as: "pitch yaw roll". We need to know more than this to precisely specify the orientation of something. We need to know which axis is which, and we need to know the order in which these operations are performed.

== Definition of axes==
Imagine you are standing in a Doom3 map. The '''z''' axis is up. A pure yaw rotates about the '''z''' axis. The '''x''' axis is forward. A pure roll rotates about the x axis. The '''y''' axis extends out to your left. A pure pitch rotates about the '''y''' axis.

== Order of rotations ==
It turns out that Doom3 uses the "yaw, pitch, roll" convention (also known as "zyx," the full rotation matrix for this convention is given in [http://en.wikipedia.org/wiki/Euler_angles this article]). Let's say you have entered a spawnarg as "pitch yaw roll." This is how Doom3 applies these values to orient an object: First, the yaw is applied about the world '''z''' axis, second, the pitch is applied about the yawed '''y''' axis, and third, the roll is applied about the yawed and pitched '''x''' axis.

== Sign Conventions ==
In mathematics, a clockwise rotation is a positive angle, and a counterclockwise rotation is a negative angle. Pitch, yaw and roll have their own conventions (positive pitch is rotating something from forward to the ceiling). The combination of the defined axes, the mathematical rotation sign convention, and the sign conventions of pitch, yaw and roll result in some sign changes when going from the pitch, yaw, roll angles to the actual angular rotation about the axis that is entered in to the rotation matrix. The conventions are described below:

Pitch is positive when pitching from forward to up. This is a counterclockwise rotation about the '''y''' (left) axis. Therefore, positive pitch means negative rotation angle. Yaw is positive when rotating from the forward to the right. This is a counterclockwise rotation about the '''z''' (up) axis. Therefore, positive yaw means negative rotation angle. Roll is positive when rotating from up to right. This is a clockwise rotation about the '''x''' (forward) axis. Therefore, positive roll means positive rotation angle.

== Example 1 ==
Suppose you start out with an airplane pointing straight ahead with level wings. You want the airplane to end up pointing all the way to your right, with the right wing pointing down at the ground. Keeping in mind that the angles are applied in the order of yaw, pitch, roll, we enter a yaw of +90 degrees, and a roll of 90 degrees. We would enter in an angles spawnarg "pitch yaw roll" of "0 90 90". If instead the roll had been applied before the yaw, these angles would have resulted in an airplane pointing straight down with its wings extending forward and back, so the order of rotations does matter.

== Example 2 ==
Again you start out with an airplane pointing straight ahead with wings level. Now, you want the airplane nose pointing to your left and up 45 degrees, and you want the airplane to be upside-down. Again, yaw is applied first, then pitch, then roll. So we know yaw must be -90, pointing the airplane left. Pitch is +45, tipping the nose up, and roll is 180, rotating the plane upside-down about its long axis. We therefore enter an angles spawnarg ("pitch yaw roll") of "45 -90 180".

== Attaching to AI Joints of Unknown Orientation ==
When attaching things to AI joints and trying to orient them, oftentimes you don't know how the joint is oriented. You can use '''r_showskel 1''' in the console to show the joints and display a line for each axis. You still don't know which axis is which. To figure out how to orient something relative to the joint, first apply a yaw rotation by setting the attachment angles to "0 <test angle> 0", and see how that differs from angles of "0 0 0". Now you know what yaw does. Do the same for pitch, now you know which way pitch rotates, and by process of elimination you know roll. Now you know what will happen when you input angles to orient something relative to the joint. It will rotate in the sense you identified as yaw, then in pitch, then finally in roll.

{{editing}} {{coding}} {{ai}}

Euler Angle Convention Used in Doom3

2008-09-20T08:42:03Z

Ishtvan:

[http://en.wikipedia.org/wiki/Euler_angles Euler Angles] are a way of specifying the orientation of a given object relative to three reference axes in the world. To orient objects, Doom3 uses the "angles" spawnarg, which takes three space-delimited values, defined as: "pitch yaw roll". We need to know more than this to precisely specify the orientation of something. We need to know which axis is which, and we need to know the order in which these operations are performed.

== Definition of axes==
Imagine you are standing in a Doom3 map. The '''z''' axis is up. A pure yaw rotates about the '''z''' axis. The '''x''' axis is forward. A pure roll rotates about the x axis. The '''y''' axis extends out to your left. A pure pitch rotates about the '''y''' axis.

== Order of rotations ==
It turns out that Doom3 uses the "yaw, pitch, roll" convention (also known as "zyx," the full rotation matrix for this convention is given in [http://en.wikipedia.org/wiki/Euler_angles this article]). Let's say you have entered a spawnarg as "pitch yaw roll." This is how Doom3 applies these values to orient an object: First, the yaw is applied about the world '''z''' axis, second, the pitch is applied about the yawed '''y''' axis, and third, the roll is applied about the yawed and pitched '''x''' axis.

== Sign Conventions ==
In mathematics, a clockwise rotation is a positive angle, and a counterclockwise rotation is a negative angle. Pitch, yaw and roll have their own conventions (positive pitch is rotating something from forward to the ceiling). The combination of the defined axes, the mathematical rotation sign convention, and the sign conventions of pitch, yaw and roll result in some sign changes when going from the pitch, yaw, roll angles to the actual angular rotation about the axis that is entered in to the rotation matrix. The conventions are described below:

Pitch is positive when pitching from forward to up. This is a counterclockwise rotation about the '''y''' (left) axis. Therefore, positive pitch means negative rotation angle. Yaw is positive when rotating from the forward to the right. This is a counterclockwise rotation about the '''z''' (up) axis. Therefore, positive yaw means negative rotation angle. Roll is positive when rotating from up to right. This is a clockwise rotation about the '''x''' (forward) axis. Therefore, positive roll means positive rotation angle.

== Example 1 ==
Suppose you start out with an airplane pointing straight ahead with level wings. You want the airplane to end up pointing all the way to your right, with the right wing pointing down at the ground. Keeping in mind that the angles are applied in the order of yaw, pitch, roll, we enter a yaw of +90 degrees, and a roll of 90 degrees. We would enter in an angles spawnarg "pitch yaw roll" of "0 90 90". If instead the roll had been applied before the yaw, these angles would have resulted in an airplane pointing straight down with its wings extending forward and back, so the order of rotations does matter.

== Example 2 ==
Again you start out with an airplane pointing straight ahead with wings level. Now, you want the airplane nose pointing to your left and up 45 degrees, and you want the airplane to be upside-down. Again, yaw is applied first, then pitch, then roll. So we know yaw must be -90, pointing the airplane left. Pitch is +45, tipping the nose up, and roll is 180, rotating the plane upside-down about its long axis. We therefore enter an angles spawnarg ("pitch yaw roll") of "45 -90 180".

== Attaching to AI Joints of Unknown Orientation ==
When attaching things to AI joints and trying to orient them, oftentimes you don't know how the joint is oriented. You can use '''r_showskel 1''' in the console to show the joints and display a line for each axis. You still don't know which axis is which. To figure out how to orient something, first apply a yaw rotation by setting the attachment angles to "0 <test angle> 0", and see how that differs from angles of "0 0 0". Now you know what yaw does. Do the same for pitch, now you know which way pitch rotates, and by process of elimination you know roll. Now you know what will happen when you input angles to orient something relative to the joint. It will rotate in the sense you identified as yaw, then in pitch, then finally in roll.

{{editing}} {{coding}} {{ai}}

Euler Angle Convention Used in Doom3

2008-09-20T08:33:13Z

Ishtvan: /* Example 2 */

[http://en.wikipedia.org/wiki/Euler_angles Euler Angles] are a way of specifying the orientation of a given object relative to three reference axes in the world. To orient objects, Doom3 uses the "angles" spawnarg, which takes three space-delimited values, defined as: "pitch yaw roll". We need to know more than this to precisely specify the orientation of something. We need to know which axis is which, and we need to know the order in which these operations are performed.

== Definition of axes==
Imagine you are standing in a Doom3 map. The '''z''' axis is up. A pure yaw rotates about the '''z''' axis. The '''x''' axis is forward. A pure roll rotates about the x axis. The '''y''' axis extends out to your left. A pure pitch rotates about the '''y''' axis.

== Order of rotations ==
It turns out that Doom3 uses the "yaw, pitch, roll" convention (also known as "zyx," the full rotation matrix for this convention is given in [http://en.wikipedia.org/wiki/Euler_angles this article]). Let's say you have entered a spawnarg as "pitch yaw roll." This is how Doom3 applies these values to orient an object: First, the yaw is applied about the world '''z''' axis, second, the pitch is applied about the yawed '''y''' axis, and third, the roll is applied about the yawed and pitched '''x''' axis.

== Sign Conventions ==
In mathematics, a clockwise rotation is a positive angle, and a counterclockwise rotation is a negative angle. Pitch, yaw and roll have their own conventions (positive pitch is rotating something from forward to the ceiling). The combination of the defined axes, the mathematical rotation sign convention, and the sign conventions of pitch, yaw and roll result in some sign changes when going from the pitch, yaw, roll angles to the actual angular rotation about the axis that is entered in to the rotation matrix. The conventions are described below:

Pitch is positive when pitching from forward to up. This is a counterclockwise rotation about the '''y''' (left) axis. Therefore, positive pitch means negative rotation angle. Yaw is positive when rotating from the forward to the right. This is a counterclockwise rotation about the '''z''' (up) axis. Therefore, positive yaw means negative rotation angle. Roll is positive when rotating from up to right. This is a clockwise rotation about the '''x''' (forward) axis. Therefore, positive roll means positive rotation angle.

== Example 1 ==
Suppose you start out with an airplane pointing straight ahead with level wings. You want the airplane to end up pointing all the way to your right, with the right wing pointing down at the ground. Keeping in mind that the angles are applied in the order of yaw, pitch, roll, we enter a yaw of +90 degrees, and a roll of 90 degrees. We would enter in an angles spawnarg "pitch yaw roll" of "0 90 90". If instead the roll had been applied before the yaw, these angles would have resulted in an airplane pointing straight down with its wings extending forward and back, so the order of rotations does matter.

== Example 2 ==
Again you start out with an airplane pointing straight ahead with wings level. Now, you want the airplane nose pointing to your left and up 45 degrees, and you want the airplane to be upside-down. Again, yaw is applied first, then pitch, then roll. So we know yaw must be -90, pointing the airplane left. Pitch is +45, tipping the nose up, and roll is 180, rotating the plane upside-down about its long axis. We therefore enter an angles spawnarg ("pitch yaw roll") of "45 -90 180".

{{editing}} {{coding}} {{ai}}

Euler Angle Convention Used in Doom3

2008-09-20T08:31:36Z

Ishtvan: /* Example 1 */

[http://en.wikipedia.org/wiki/Euler_angles Euler Angles] are a way of specifying the orientation of a given object relative to three reference axes in the world. To orient objects, Doom3 uses the "angles" spawnarg, which takes three space-delimited values, defined as: "pitch yaw roll". We need to know more than this to precisely specify the orientation of something. We need to know which axis is which, and we need to know the order in which these operations are performed.

== Definition of axes==
Imagine you are standing in a Doom3 map. The '''z''' axis is up. A pure yaw rotates about the '''z''' axis. The '''x''' axis is forward. A pure roll rotates about the x axis. The '''y''' axis extends out to your left. A pure pitch rotates about the '''y''' axis.

== Order of rotations ==
It turns out that Doom3 uses the "yaw, pitch, roll" convention (also known as "zyx," the full rotation matrix for this convention is given in [http://en.wikipedia.org/wiki/Euler_angles this article]). Let's say you have entered a spawnarg as "pitch yaw roll." This is how Doom3 applies these values to orient an object: First, the yaw is applied about the world '''z''' axis, second, the pitch is applied about the yawed '''y''' axis, and third, the roll is applied about the yawed and pitched '''x''' axis.

== Sign Conventions ==
In mathematics, a clockwise rotation is a positive angle, and a counterclockwise rotation is a negative angle. Pitch, yaw and roll have their own conventions (positive pitch is rotating something from forward to the ceiling). The combination of the defined axes, the mathematical rotation sign convention, and the sign conventions of pitch, yaw and roll result in some sign changes when going from the pitch, yaw, roll angles to the actual angular rotation about the axis that is entered in to the rotation matrix. The conventions are described below:

Pitch is positive when pitching from forward to up. This is a counterclockwise rotation about the '''y''' (left) axis. Therefore, positive pitch means negative rotation angle. Yaw is positive when rotating from the forward to the right. This is a counterclockwise rotation about the '''z''' (up) axis. Therefore, positive yaw means negative rotation angle. Roll is positive when rotating from up to right. This is a clockwise rotation about the '''x''' (forward) axis. Therefore, positive roll means positive rotation angle.

== Example 1 ==
Suppose you start out with an airplane pointing straight ahead with level wings. You want the airplane to end up pointing all the way to your right, with the right wing pointing down at the ground. Keeping in mind that the angles are applied in the order of yaw, pitch, roll, we enter a yaw of +90 degrees, and a roll of 90 degrees. We would enter in an angles spawnarg "pitch yaw roll" of "0 90 90". If instead the roll had been applied before the yaw, these angles would have resulted in an airplane pointing straight down with its wings extending forward and back, so the order of rotations does matter.

== Example 2 ==
Again you start out with an airplane pointing straight ahead with wings level. Now, you want the airplane nose pointing to your left and up 45 degrees, and you want the airplane to be upside-down. Again, yaw is applied first, then pitch, then roll. So we know yaw must be -90, pointing the airplane left. Pitch is +45, tipping the nose up, and roll is 180, rotating the plane upside-down about its long axis. We therefore enter an angles spawnarg "pitch yaw roll" of "45 -90 180".

{{editing}} {{coding}} {{ai}}

Euler Angle Convention Used in Doom3

2008-09-20T08:28:31Z

Ishtvan: /* Order of rotations */

[http://en.wikipedia.org/wiki/Euler_angles Euler Angles] are a way of specifying the orientation of a given object relative to three reference axes in the world. To orient objects, Doom3 uses the "angles" spawnarg, which takes three space-delimited values, defined as: "pitch yaw roll". We need to know more than this to precisely specify the orientation of something. We need to know which axis is which, and we need to know the order in which these operations are performed.

== Definition of axes==
Imagine you are standing in a Doom3 map. The '''z''' axis is up. A pure yaw rotates about the '''z''' axis. The '''x''' axis is forward. A pure roll rotates about the x axis. The '''y''' axis extends out to your left. A pure pitch rotates about the '''y''' axis.

== Order of rotations ==
It turns out that Doom3 uses the "yaw, pitch, roll" convention (also known as "zyx," the full rotation matrix for this convention is given in [http://en.wikipedia.org/wiki/Euler_angles this article]). Let's say you have entered a spawnarg as "pitch yaw roll." This is how Doom3 applies these values to orient an object: First, the yaw is applied about the world '''z''' axis, second, the pitch is applied about the yawed '''y''' axis, and third, the roll is applied about the yawed and pitched '''x''' axis.

== Sign Conventions ==
In mathematics, a clockwise rotation is a positive angle, and a counterclockwise rotation is a negative angle. Pitch, yaw and roll have their own conventions (positive pitch is rotating something from forward to the ceiling). The combination of the defined axes, the mathematical rotation sign convention, and the sign conventions of pitch, yaw and roll result in some sign changes when going from the pitch, yaw, roll angles to the actual angular rotation about the axis that is entered in to the rotation matrix. The conventions are described below:

Pitch is positive when pitching from forward to up. This is a counterclockwise rotation about the '''y''' (left) axis. Therefore, positive pitch means negative rotation angle. Yaw is positive when rotating from the forward to the right. This is a counterclockwise rotation about the '''z''' (up) axis. Therefore, positive yaw means negative rotation angle. Roll is positive when rotating from up to right. This is a clockwise rotation about the '''x''' (forward) axis. Therefore, positive roll means positive rotation angle.

== Example 1 ==
Suppose you start out with an airplane pointing straight ahead with level wings. You want the airplane to end up pointing all the way to your right, with the right wing pointing down at the ground. Keeping in mind that the angles are applied in the order of yaw, pitch, roll, we enter a yaw of +90 degrees, and a roll of 90 degrees. We would enter in an angles spawnarg "pitch yaw roll" of "0 90 90". (NOTE: If instead the roll had been applied before the yaw, these angles would have resulted in an airplane pointing straight down with its wings extending forward and back, so the order of rotations matters).

== Example 2 ==
Again you start out with an airplane pointing straight ahead with wings level. Now, you want the airplane nose pointing to your left and up 45 degrees, and you want the airplane to be upside-down. Again, yaw is applied first, then pitch, then roll. So we know yaw must be -90, pointing the airplane left. Pitch is +45, tipping the nose up, and roll is 180, rotating the plane upside-down about its long axis. We therefore enter an angles spawnarg "pitch yaw roll" of "45 -90 180".

{{editing}} {{coding}} {{ai}}

Euler Angle Convention Used in Doom3

2008-09-20T08:27:07Z

Ishtvan: /* Example 2 */

[http://en.wikipedia.org/wiki/Euler_angles Euler Angles] are a way of specifying the orientation of a given object relative to three reference axes in the world. To orient objects, Doom3 uses the "angles" spawnarg, which takes three space-delimited values, defined as: "pitch yaw roll". We need to know more than this to precisely specify the orientation of something. We need to know which axis is which, and we need to know the order in which these operations are performed.

== Definition of axes==
Imagine you are standing in a Doom3 map. The '''z''' axis is up. A pure yaw rotates about the '''z''' axis. The '''x''' axis is forward. A pure roll rotates about the x axis. The '''y''' axis extends out to your left. A pure pitch rotates about the '''y''' axis.

== Order of rotations ==
It turns out that Doom3 uses the "zyx" or "yaw, pitch, roll" convention (The full rotation matrix for this convention is given in [http://en.wikipedia.org/wiki/Euler_angles this article]). Let's say you have entered a spawnarg as "pitch yaw roll." This is how Doom3 applies these values to orient an object: First, the yaw is applied about the world '''z''' axis, second, the pitch is applied about the yawed '''y''' axis, and third, the roll is applied about the yawed and pitched '''x''' axis.

== Sign Conventions ==
In mathematics, a clockwise rotation is a positive angle, and a counterclockwise rotation is a negative angle. Pitch, yaw and roll have their own conventions (positive pitch is rotating something from forward to the ceiling). The combination of the defined axes, the mathematical rotation sign convention, and the sign conventions of pitch, yaw and roll result in some sign changes when going from the pitch, yaw, roll angles to the actual angular rotation about the axis that is entered in to the rotation matrix. The conventions are described below:

Pitch is positive when pitching from forward to up. This is a counterclockwise rotation about the '''y''' (left) axis. Therefore, positive pitch means negative rotation angle. Yaw is positive when rotating from the forward to the right. This is a counterclockwise rotation about the '''z''' (up) axis. Therefore, positive yaw means negative rotation angle. Roll is positive when rotating from up to right. This is a clockwise rotation about the '''x''' (forward) axis. Therefore, positive roll means positive rotation angle.

== Example 1 ==
Suppose you start out with an airplane pointing straight ahead with level wings. You want the airplane to end up pointing all the way to your right, with the right wing pointing down at the ground. Keeping in mind that the angles are applied in the order of yaw, pitch, roll, we enter a yaw of +90 degrees, and a roll of 90 degrees. We would enter in an angles spawnarg "pitch yaw roll" of "0 90 90". (NOTE: If instead the roll had been applied before the yaw, these angles would have resulted in an airplane pointing straight down with its wings extending forward and back, so the order of rotations matters).

== Example 2 ==
Again you start out with an airplane pointing straight ahead with wings level. Now, you want the airplane nose pointing to your left and up 45 degrees, and you want the airplane to be upside-down. Again, yaw is applied first, then pitch, then roll. So we know yaw must be -90, pointing the airplane left. Pitch is +45, tipping the nose up, and roll is 180, rotating the plane upside-down about its long axis. We therefore enter an angles spawnarg "pitch yaw roll" of "45 -90 180".

{{editing}} {{coding}} {{ai}}

Euler Angle Convention Used in Doom3

2008-09-20T07:46:40Z

Ishtvan: New page: [http://en.wikipedia.org/wiki/Euler_angles Euler Angles] are a way of specifying the orientation of a given object relative to three reference axes in the world. To orient objects, Doom3 ...

[http://en.wikipedia.org/wiki/Euler_angles Euler Angles] are a way of specifying the orientation of a given object relative to three reference axes in the world. To orient objects, Doom3 uses the "angles" spawnarg, which takes three space-delimited values, defined as: "pitch yaw roll". We need to know more than this to precisely specify the orientation of something. We need to know which axis is which, and we need to know the order in which these operations are performed.

'''Definition of axes:''': Imagine you are standing in a Doom3 map. The '''z''' axis is up. A pure yaw rotates about the '''z''' axis. The '''x''' axis is forward. A pure roll rotates about the x axis. The '''y''' axis extends out to your left. A pure pitch rotates about the '''y''' axis.

'''Order of rotations''': It turns out that Doom3 uses the "zyx" or "yaw, pitch, roll" convention (The full rotation matrix for this convention is given in [http://en.wikipedia.org/wiki/Euler_angles this article]). Let's say you have entered a spawnarg as "pitch yaw roll." This is how Doom3 applies these values to orient an object: First, the yaw is applied about the world '''z''' axis, second, the pitch is applied about the yawed '''y''' axis, and third, the roll is applied about the yawed and pitched '''x''' axis.

'''Sign Conventions''': In mathematics, a clockwise rotation is a positive angle, and a counterclockwise rotation is a negative angle. Pitch, yaw and roll have their own conventions (positive pitch is rotating something from forward to the ceiling). The combination of the defined axes, the mathematical rotation sign convention, and the sign conventions of pitch, yaw and roll result in some sign changes when going from the pitch, yaw, roll angles to the actual angular rotation about the axis that is entered in to the rotation matrix. The conventions are described below:

Pitch is positive when pitching from forward to up. This is a counterclockwise rotation about the '''y''' (left) axis. Therefore, positive pitch means negative rotation angle. Yaw is positive when rotating from the forward to the right. This is a counterclockwise rotation about the '''z''' (up) axis. Therefore, positive yaw means negative rotation angle. Roll is positive when rotating from up to right. This is a clockwise rotation about the '''x''' (forward) axis. Therefore, positive roll means positive rotation angle.

'''Example 1''': Suppose you start out with an airplane pointing straight ahead with level wings. You want the airplane to end up pointing all the way to your right, with the right wing pointing down at the ground. Keeping in mind that the angles are applied in the order of yaw, pitch, roll, we enter a yaw of +90 degrees, and a roll of 90 degrees. We would enter in an angles spawnarg "pitch yaw roll" of "0 90 90". (NOTE: If instead the roll had been applied before the yaw, these angles would have resulted in an airplane pointing straight down with its wings extending forward and back, so the order of rotations matters).

'''Example 2''': Again you start out with an airplane pointing straight ahead with wings level. Now, you want the airplane nose pointing to your left and up 45 degrees, and you want the airplane to be upside-down. Again, yaw is applied first, then pitch, then roll. So we know yaw must be -90, pointing the airplane left. Pitch is +45, tipping the nose up, and roll is 180, rotating the plane upside-down about its long axis. We therefore enter an angles spawnarg "pitch yaw roll" of "45 -90 180".