point_devshot_camera
 Class hierarchy
|
|---|
| CPointDevShotCamera |
point_devshot_camera.cpp
|
point_devshot_camera is a point entity available in all 
Source games. It is used by the -makedevshots system, which automatically takes screenshots at the position of every devshot camera in the level.
In code, it is represented by theCPointDevShotCameraclass, defined in thepoint_devshot_camera.cppfile.
Important:This is a preserved entity in 
.
- On a new round entities with this classname will intentionally not reset. You can use
logic_autoto emulate resetting it. - Killing it removes it forever, as it is not respawned on a new round.
- It cannot be spawned with a
point_template. - Parenting this with non preserved entities may have undesirable effects.
Basic Usage
Place a point_devshot_camera entity in your map and give it a name, the name of the area it looks at is a good name. If you want you can make sure the angle and location are good by using spectate ingame and using getpos in the console to find your co-ordinates and angle. Adjust the FOV to match what you're using ingame if you wish and that's all the entity itself needs.
Next, open up your compile options and either in the input bar at the bottom of the normal mode add -makedevshots or in the $game_exe section of the expert mode add the same thing. Make sure you remove options such as -dev so that your screenshots don't have the console in them!
Once you have compiled your map the mod will load up and just let it be, it will load the map and take the screenshots automatically. The screenshots will be saved to <mod>/screenshots/<mapname>/<cameraname> as .tga files.
An example of what can be achieved with these from Team Fortress 2(Video broken.)
Bug:In Team Fortress 2 the first camera placed (with the lowest ID) may take a screenshot of the starting chalkboard. It is advised to create a fake first camera to prevent the actual first's images being of nothing but the chalkboard. [todo tested in?]Devshot cameras can be loaded from a text file in the maps folder with the same name as the map, but with the extension *.txt, using standard keyvalue syntax. It's the same data as the entity keyvalues in hammer.
MapCameras
{
TestCamera1
{
origin "256 256 256"
angles "-15 50 0"
FOV 90
}
TestCamera2
{
origin "-256 -256 -256"
angles "90 0 0"
FOV 90
}
}
|
Keyvalues
- Name
(targetname)<string> - The name that other entities refer to this entity by, via Inputs/Outputs or other keyvalues (e.g.
parentnameortarget).
Also displayed in Hammer's 2D views and Entity Report.See also: Generic Keyvalues, Inputs and Outputs available to all entities
- Camera Name
(cameraname)<string> - Used as the name of the directory to store screenshots from this camera. Must be unique within the level.
Warning:Failing to set a name will lead to the screenshot process failing at runtime- Camera FOV
(FOV)<integer> - FOV of this camera.
- Pitch Yaw Roll (Y Z X)
(angles)<angle> - This entity's orientation in the world. Pitch is rotation around the Y axis, yaw is the rotation around the Z axis, roll is the rotation around the X axis.
Inputs
TakeScreenshot(only in
)- Teleport and take a screenshot from this camera (Softlocks the player. Restart the map)
