Security Camera - Revision history

Datiswous: /* Examining a Test Map */

2026-03-10T16:57:31Z

Examining a Test Map

← Older revision		Revision as of 16:57, 10 March 2026
Line 248:		Line 248:


	==Examining a Test Map==		== Examining a Test Map ==

	You can obtain a test map with sample cameras in it here: [https://ftp.thedarkmod.com/tutorials/RemoteCamera/camerawiki2.pk4 camerawiki2.pk4]. Similar setups can be found as prefabs in AI/Machines.		You can obtain a test map with sample cameras in it here: [https://ftp.thedarkmod.com/tutorials/RemoteCamera/camerawiki2.pk4 camerawiki2.pk4]. Similar setups can be found as prefabs in AI/Machines.
Line 256:		Line 256:
	[[Image:Cw1.jpg\|256px\|thumb\|right\|cam1]]		[[Image:Cw1.jpg\|256px\|thumb\|right\|cam1]]

	~~'''~~A rotating camera that sweeps back and forth~~'''~~		=== A rotating camera that sweeps back and forth ===

	This camera (''cam1'') starts its rotation at 135 degrees (assuming +X is 0 degrees), and sweeps clockwise until it reaches 45 degrees. It pauses for a moment, then return-sweeps back to 135 degrees. It has a spotlight.		This camera (''cam1'') starts its rotation at 135 degrees (assuming +X is 0 degrees), and sweeps clockwise until it reaches 45 degrees. It pauses for a moment, then return-sweeps back to 135 degrees. It has a spotlight.
Line 273:		Line 273:
	[[Image:Cw2.jpg\|256px\|thumb\|right\|cam1's display]]		[[Image:Cw2.jpg\|256px\|thumb\|right\|cam1's display]]
	{{clear}}		{{clear}}
	~~'''~~A stationary camera that doesn't move~~'''~~		=== A stationary camera that doesn't move ===

	[[Image:Cw3.jpg\|320px\|thumb\|right\|cam2 and its display]]		[[Image:Cw3.jpg\|320px\|thumb\|right\|cam2 and its display]]
Line 287:		Line 287:


	~~'''~~A screen showing the view from another entity (a target_null)~~'''~~		=== A screen showing the view from another entity (a target_null) ===

	[[Image:Cw6.jpg\|320px\|thumb\|right\|a small screen showing what a target_null is seeing]]		[[Image:Cw6.jpg\|320px\|thumb\|right\|a small screen showing what a target_null is seeing]]

Dragofer at 11:08, 19 April 2025

2025-04-19T11:08:38Z

Show changes

Dragofer at 08:50, 29 January 2022

2022-01-29T08:50:18Z

← Older revision		Revision as of 08:50, 29 January 2022
Line 105:		Line 105:
	==Examining a Test Map==		==Examining a Test Map==

	You can obtain a test map with sample cameras in it here: [~~http~~://ftp.thedarkmod.com/tutorials/RemoteCamera/camerawiki.pk4 camerawiki.pk4].		You can obtain a test map with sample cameras in it here: [https://ftp.thedarkmod.com/tutorials/RemoteCamera/camerawiki.pk4 camerawiki.pk4].

	Open the map ''camerawiki.map'' in Dark Radiant. In this map, we have examples of the different cameras.		Open the map ''camerawiki.map'' in Dark Radiant. In this map, we have examples of the different cameras.

Dragofer at 09:10, 17 February 2021

2021-02-17T09:10:23Z

← Older revision		Revision as of 09:10, 17 February 2021
Line 1:		Line 1:
	==Security Camera==		==Security Camera==

	<span style="color: red">This is the article documenting the security camera of TDM 2.09 and older. ~~See~~ [[Security Camera]] ~~for a more recent version~~.</span>		<span style="color: red">This is the article documenting the security camera of TDM 2.09 and older. As of 2.10, the article [[Security Camera (2.10+)]] will be accurate.</span>

	The security camera (aka remote camera) has been a part of TDM for years, but has been rarely, if ever, used. Recent problems came to light when trying to use it, so I (grayman) decided to flesh it out for 2.06. That done, some issues supporting a more Thief-like camera model were discovered too late in the 2.06 release cycle to safely accommodate required changes in the camera, so work will continue into 2.07.		The security camera (aka remote camera) has been a part of TDM for years, but has been rarely, if ever, used. Recent problems came to light when trying to use it, so I (grayman) decided to flesh it out for 2.06. That done, some issues supporting a more Thief-like camera model were discovered too late in the 2.06 release cycle to safely accommodate required changes in the camera, so work will continue into 2.07.

Dragofer at 09:09, 17 February 2021

2021-02-17T09:09:13Z

Show changes

Dragofer at 10:29, 15 February 2021

2021-02-15T10:29:44Z

← Older revision		Revision as of 10:29, 15 February 2021
Line 186:		Line 186:
	===Multiple Display Screens / Reflective Water / Skybox===		===Multiple Display Screens / Reflective Water / Skybox===

	If you plan to use more than one camera with display screens in your mission, or if the camera display will appear in the same player POV as the sky or reflective water surfaces, you'll need to ~~copy~~ the ~~material shader ''~~textures/~~darkmod~~/camera~~'' (in materials~~/~~tdm_security_camera.mtr) to a map-specific *.mtr file, rename it to something like ''camera1'', and give it a unique ''map'' keyword. Place this file in your mission's ''materials''~~ folder.		If you plan to use more than one camera with display screens in your mission, or if the camera display will appear in the same player POV as the sky or reflective water surfaces, you'll need to use unique camera materials for each screen. You can find 9 additional camera materials in the textures/common/camera/ folder. If you should need even more, you can simply clone one of the materials and change the name after the ''map'' keyword.

	~~For example, if~~ you ~~have two cameras in your mission~~, you ~~would assign~~ one of ~~these shaders to~~ the ~~display for the first camera,~~ and the ~~other shader to the display for the second:~~

	~~<pre>~~
	~~camera1~~
	{
	~~qer_editorimage textures/editor/cameragui.tga~~
	~~noshadows~~
	{
	~~red Parm0~~
	~~green Parm1~~
	~~blue Parm2~~
	~~remoteRenderMap 232 232 // width / height of render image, ie resolution of screen~~
	~~scale -1, -1~~
	~~translate -1, -1~~
	~~map "camera1"~~
	}
	}

	~~camera2~~
	{
	~~qer_editorimage textures/editor/cameragui.tga~~
	~~noshadows~~
	{
	~~red Parm0~~
	~~green Parm1~~
	~~blue Parm2~~
	~~remoteRenderMap 232 232 // width / height of render image, ie resolution of screen~~
	~~scale -1, -1~~
	~~translate -1, -1~~
	~~map "camera2"~~
	}
	}
	~~</pre>~~

	~~Note~~ the ''map ~~"camera1"~~'' ~~and ''map "camera2"'' lines. These unique names allow the renderer to correctly display both camera displays in the same mission~~.

Dragofer: Reworded how to setup a display screen.

2021-02-15T10:12:40Z

Reworded how to setup a display screen.

← Older revision		Revision as of 10:12, 15 February 2021
Line 176:		Line 176:
	==Sending to a Display Screen==		==Sending to a Display Screen==

	You can ~~let the security camera send~~ a ~~view, either its own or another entity~~'s ~~view, to a display screen. The display screen~~ is ~~simply~~ a func_static patch that uses the shader ''textures/darkmod/camera''. ~~Size the~~ patch ~~appropriately~~.		You can create a display screen: all that's needed is a func_static patch that uses the shader ''textures/darkmod/camera''. It's recommended to put another patch behind it, since this func_static will get hidden if it's switched off. The screen then needs to be given a spawnarg "cameraTarget" that names either a security camera or a different entity, typically a target_null. The screen will display what that entity sees.

	~~Both~~ the screen ~~and~~ the security camera entity ~~may use~~ the ~~cameraTarget spawnarg~~:		Using a security camera has the advantage that you can easily turn the display screen on or off simply by triggering the security camera. If you're using the view from another entity type, switching the screen on/off requires taking advantage of a security camera's coding with the following setup:
	* "cameraTarget" ~~- On~~ the ~~display screen~~ entity~~: the name of the camera~~ whose view ~~will be painted on this display.~~		* display_screen with a "cameraTarget" spawnarg pointing to the entity whose view you want
	* "cameraTarget" ~~- On~~ the ~~security~~ camera ~~entity (optional): specify~~ a ~~different entity~~ that ~~should supply~~ the ~~view, i~~.~~e. in order to get a better vantage point. Usually this is a target_null entity~~.		* a security camera with a "cameraTarget" spawnarg pointing to the same entity as above. It doesn't matter where this camera is.
			* a button that targets the security camera. Triggering the security camera will toggle the screen display.

Dragofer at 17:56, 14 February 2021

2021-02-14T17:56:13Z

← Older revision		Revision as of 17:56, 14 February 2021
Line 145:		Line 145:

	The security camera supports the following global script functions:		The security camera supports the following global script functions:
	* getSecurityCameraState() - Returns the security camera's state. 1 = unalerted, 2 = ~~suspicious~~, 3 = fully alerted, 4 = inactive (power off), 5 = destroyed, 0 = not a security camera.		* getSecurityCameraState() - Returns the security camera's state. 1 = unalerted, 2 = partially alerted, 3 = fully alerted, 4 = inactive (power off), 5 = destroyed, 0 = not a security camera.
	* getShaderParm(7) - Returns the current value of shaderParm7 on the camera model. 0 = unalerted, 1 = about to resume sweep after a partial alert, 2 = partially alerted, 3 = fully alerted.		* getShaderParm(7) - Returns the current value of shaderParm7 on the camera model. 0 = unalerted, 1 = about to resume sweep after a partial alert, 2 = partially alerted, 3 = fully alerted.
	* activate() and trigger() - These activate or deactivate the camera fully, representing switching power on or off.		* activate() and trigger() - These activate or deactivate the camera fully, representing switching power on or off.

Dragofer at 10:40, 14 February 2021

2021-02-14T10:40:33Z

← Older revision		Revision as of 10:40, 14 February 2021
Line 106:		Line 106:

	* "broken" - Use this model when the camera is destroyed.		* "broken" - Use this model when the camera is destroyed.
	* "clipmodel" - Assign a simplified collision mesh to this camera. Should be under 32 tris, have no convex angles and use textures/common/collision.		* "clipmodel" - Assign a simplified collision mesh to this camera. Should be under 32 tris, have only convex angles and use textures/common/collision.
	* "viewOffset" - A vector that defines the offset of the camera's 'eye' from the camera's origin.		* "viewOffset" - A vector that defines the offset of the camera's 'eye' from the camera's origin.
	* "lightOffset" - A vector that defines the spotlight offset from the camera's origin.		* "lightOffset" - A vector that defines the spotlight offset from the camera's origin.

Dragofer at 10:12, 14 February 2021

2021-02-14T10:12:24Z

← Older revision		Revision as of 10:12, 14 February 2021
Line 105:		Line 105:
	These spawnargs are important if you change the camera model:		These spawnargs are important if you change the camera model:

			* "broken" - Use this model when the camera is destroyed.
	* "clipmodel" - Assign a simplified collision mesh to this camera. Should be under 32 tris, have no convex angles and use textures/common/collision.		* "clipmodel" - Assign a simplified collision mesh to this camera. Should be under 32 tris, have no convex angles and use textures/common/collision.
	* "viewOffset" - A vector that defines the offset of the camera's 'eye' from the camera's origin.		* "viewOffset" - A vector that defines the offset of the camera's 'eye' from the camera's origin.