Camera

This property is the CFrame of the Camera and definies its position and orientation in the 3D world.

Some transformations, such as the rotation of the head when using VR devices are not reflected in this property. For this reason, developers should use Camera:GetRenderCFrame() to obtain the 'true' CFrame of the camera.

How to set the camera's CFrame

You can move the camera by setting the CFrame property. However, the default camera scripts also set the CFrame property. When manually setting the CFrame property, it may be overwritten by the [camera scripts][1] which update every frame. There are two options to address this:

1. Set the camera Camera.CameraType to 'Scriptable'. When the camera is 'Scriptable' the default scripts will not update the CFrame. This method is simplest and recommended in most cases

2. Replace the default camera scripts with an alternative that doesn't interfere with the developer's desired implementation. This is only recommended when developers do not need any default camera's functionality

How the Camera CFrame works

Like all CFrame data, the camera CFrame represents a position and an orientation.

The most intuitive way to position and orientate the Camera is by using the new CFrame constructor with the pos and lookAt parameters, for example:

local pos = Vector3.new(0, 10, 0)
local lookAt = Vector3.new(10, 0, 0)
local cameraCFrame = CFrame.new(pos, lookAt)
workspace.CurrentCamera.CFrame = cameraCFrame

In the above example the Camera is positioned at Vector3.new(0, 10, 0) and oriented to be looking towards Vector3.new(10, 0, 0).

Animating the Camera CFrame

Although the camera can be placed in the manner demonstrated above, you may want to animate the Camera to smoothly move from one CFrame to another. For this, there are a number of options:

1. Creating a Tween using TweenService that animates the CFrame property of the camera. See the code sample below for an example of this
2. Setting the camera CFrame every frame with RunService:BindToRenderStep() and the lerp CFrame method

When using the default camera scripts, the CameraSubject property has two roles:

• Defining the object the Camera is to follow, in the case of the 'Follow', 'Attach', 'Track', 'Watch' and 'Custom' CameraTypes
• For all CameraTypes but 'Scriptable', the object whose position the Camera's Camera.Focus will be set to

CameraSubject accepts a variety of Instances. The default camera scripts respond differently to different CameraSubject types:

• Humanoid: By default the CameraSubject is set to the LocalPlayer's Humanoid. The camera scripts will follow the Humanoid factoring in the Humanoid's current state and Humanoid.CameraOffset
• BasePart: The camera scripts will follow the position of any BasePart, with a vertical offset in the case of VehicleSeats

You can configure the Camera to follow a Model by setting the CameraSubject to the model's Model.PrimaryPart.

The CameraSubject cannot be set to nil. If it is, it will revert to its previous value.

To restore the CameraSubject to its default value, set it to the LocalPlayer's Humanoid like so:

local Players = game:GetService("Players")

local localPlayer = Players.LocalPlayer

local function resetCameraSubject()
	if workspace.CurrentCamera and localPlayer.Character then
		local humanoid = localPlayer.Character:FindFirstChildOfClass("Humanoid")
		if humanoid then
			workspace.CurrentCamera.CameraSubject = humanoid
		end
	end
end

The default Roblox camera scripts have several built in behaviors. Setting the CameraType of a player's Camera will toggle between these behaviors. Note some CameraType's require a valid Camera.CameraSubject to work correctly.

• Fixed: Camera is stationary
• Follow: Camera moves with the Camera.CameraSubject and rotates to keep the subject in the center of view
• Attach: Camera moves with the Camera.CameraSubject at a fixed offset and will rotate as the subject rotates
• Track: Camera moves with the Camera.CameraSubject but does not rotate automatically
• Watch: Camera is stationary but will rotate to keep the Camera.CameraSubject in the center of view
• Custom: Default
• Scriptable: No default behavior. Used by developers to script custom behavior

The above only applies when you use the default Roblox [camera scripts][1]. If you write your own camera scripts, you can choose to listen to CameraType and implement your own behaviors or ignore the property entirely.

Manually controlling the Camera

In some cases you may wish to manually control the Camera (for example during a cut-scene). The best way to do this is by setting the CameraType to 'Scriptable'. The default camera scripts will not move or update the Camera on its own if CameraType is set to 'Scriptable'. This means you can freely modify the Camera using its properties and functions. For more information on positioning and orientating the Camera manually see the Camera.CFrame page.

If you want complete control over the camera at all times, you may replace the default camera scripts with your own.

Sets how many degrees in the diagonal direction (from one corner of the viewport to its opposite corner) the camera can view.

See FieldOfView for a more general explanation of FOV.

Field of view, often shortened to FOV, is the extent of the observable game world that can be seen on screen at a given moment. The FieldOfView property is clamped between 1 and 120 degrees and defaults at 70. Very low or very high fields of view are not recommended as they can be disorientating to players.

The FieldOfView property sets how many degrees in the vertical direction (y-axis) the camera can view. Uniform scaling is enforced meaning the vertical and horizontal field of view are always related by the aspect ratio of the screen. This means the FieldOfView property also determines the horizontal field of view.

See the images below for an example of how different FieldOfView settings can impact the extent of the perceptive game world. At a FOV of 70, a considerable portion of the game world is visible:

However when the FOV is reduced to 30, although the Camera's Camera.CFrame has not changed, a much smaller portion of the game world is rendered:

Suggested uses for FieldOfView

Changing FOV can produce a variety of effects, such as:

• Reducing FOV to give the impression of magnification (for example when using binoculars)
• Increasing FOV when the player is 'sprinting' to give the impression of a lack of control

The Camera's FOV must be updated to reflect ViewportSize changes. The value of the FieldOfViewMode property determines which FOV value will be kept constant.

For example, when the value of FieldOfViewMode is set to FieldOfViewMode.Vertical, the horizontal FOV is updated when the viewport is resized, while the vertical FOV is kept constant. On the other hand, if the value is set to FieldOfViewMode.Diagonal, both horizontal and vertical FOV might be changed to keep the diagonal FOV constant.

The Camera Focus is a CFrame that determines the area in 3D space the graphics engine will prioritize.

Certain graphical operations Roblox performs, such as updating lighting, can take a lot of time or computational effort to complete. Focus tells Roblox the area in 3D space to prioritize when performing such operations. For example dynamic lighting from objects such as PointLights may not render at distances far from the Focus.

The default Roblox camera scripts automatically set the Focus to follow the Camera.CameraSubject (usually a Humanoid). However, Focus will not be automatically updated in the following cases:

• When the Camera.CameraType is set to 'Scriptable'
• When the default camera scripts are not being used

In these cases, you should update Focus every frame, using RunService:BindToRenderStep() function at the 'Camera' RenderPriority.

Focus has no bearing on the positioning or orientation of the Camera (see Camera.CFrame for this).

Un-linking the camera from a VR user's head motions can cause motion sickness. This property should only be set to false after extensive testing.

Toggles whether the Camera will automatically track the head motion of a player using a VR device.

When HeadLocked is true, the engine will combine the Camera Camera.CFrame with the CFrame of the user's head to render the position and orientation of the Camera correctly. The camera will be rendered at the following CFrame:

local UserInputService = game:GetService("UserInputService")
local headCFrame = UserInputService:GetUserCFrame(Enum.UserCFrame.Head)
renderCFrame = workspace.CurrentCamera.CFrame * headCFrame

Disabling HeadLocked

You are recommended not to disable HeadLocked for the following reasons:

• Players may experience motion sickness if an equivalent head tracking solution is not added
• The Roblox engine performs latency optimizations when HeadLocked is true

However in some circumstances you may wish to develop your own head tracking systems. For example, you may want custom camera transformations that restrict or augment the CFrame of the head.

See also:

• UserInputService's UserInputService:GetUserCFrame() function, which can be used to obtain the CFrame of the head
• UserInputService's UserInputService:RecenterUserHeadCFrame() which is used to recenter the head to the current position and orientation of the VR device
• The Camera:GetRenderCFrame() function which returns the Camera Camera.CFrame combined with the CFrame of the user's head

HeadScale is the scale of the user's head when using VR.

The unit scale of Roblox, from the user's perspective in VR, is defined as follows:

unitScale = HeadScale (in studs) / Feet ^ 2

This means the larger the HeadScale value, the smaller the world will look from the user's perspective when using VR devices.

When not using VR, this property has no effect.

This property should not be confused with Humanoid HeadScale, which is a NumberValue parented to a Humanoid to control its scaling.

See also:

The following are also useful when developing for VR:

• Camera.HeadLocked
• Camera:GetRenderCFrame()

The MaxAxisFieldOfView property sets how many degrees along the longest viewport axis the camera can view.

When the longest axis is the vertical axis, this property will behave similar to the FieldOfView property. This is generally the case when a device is in a portrait orientation. In a landscape orientation the longest axis will be the horizontal axis. In this case, the property describes the horizontal FOV of the Camera.

See FieldOfView for a more general explanation of FOV.

The NearPlaneZ property describes how far away the Camera's near clipping plane is in studs. The near clipping plane is a geometric plane that sits in-front of the Camera's Camera.CFrame. Anything between this plane and the camera will not render. This creates a cutaway view when viewing objects at very short distances. See the images below for a visual example of this:

The value of NearPlaneZ varies across different platforms, but is currently always between -0.1 and -0.5.

• Most windows systems, all Xbox systems and most iOS systems support the more precise value of -0.1
• Currently Mac and Android systems only support a NearPlaneZ of -0.5, although this may change in the future

ViewportSize describes the dimensions, in pixels, of the client's viewport.

• This property ignores the GUI inset applied by the top bar, meaning the center of the screen can be found at precisely at 50% of the ViewportSize in both directions
• You can find the position of a Vector3 in the world on the viewport using Camera:WorldToViewportPoint()

This function is broken and should not be used This function returns the current 'pan' speed of the Camera.

The 'pan' speed of the Camera describes the speed at which the Camera is rotating around its Camera.Focus around the Y axis.

See also:

• Camera:GetTiltSpeed() for the speed at which the Camera is rotating around its Camera.Focus on the Camera's X axis
• Camera:PanUnits() to 'pan' the camera
• Camera:TiltUnits() to 'tilt' the camera

This function returns an array of BaseParts that are obscuring the lines of sight between Camera's Camera.CFrame and the castPoints.

GetPartsObscuringTarget is used by the 'Invisicam' in in the default camera scripts to hide parts between the Camera's Camera.CFrame and Camera.Focus.

Any Instances included in the ignoreList array will, along with their descendants, be ignored.

See below for a visual example of this function. The Camera is represented by the grey camera model and the cast points are represented by the colored dots. The Parts highlighted in red are the ones that would be returned.

The castPoints parameter is given as an array of Vector3s, for example:

local castPoints = {Vector3.new(0, 10, 0), Vector3.new(0, 15, 0)}
local ignoreList = {}
workspace.CurrentCamera:GetPartsObscuringTarget(castPoints, ignoreList)

The array of BaseParts returned is in an arbitrary order, and no additional raycast data is provided (for example hit position, hit material and surface normal). If this information is required, you should a Workspace raycast function such as Workspace.FindPartOnRayWithIgnoreList.

If Terrain obscures a cast point, BaseParts obscuring the cast point between the obscuring Terrain and the cast point will not be returned.

Note, this function benefits from internal optimisations that make it more performant than casting a ray for each cast point individually.

This function returns the actual CFrame of the Camera as it is rendered. This includes any roll applied using Camera:SetRoll() and the impact of VR.

VR head transformations, along with roll applied using Camera:SetRoll() is not applied to the Camera.CFrame property. For this reason, it is best practice to use Camera:GetRenderCFrame() to obtain the 'true' CFrame of the Camera.

For example, when using VR the Camera is actually rendered at the following CFrame:

local UserInputService = game:GetService("UserInputService")

local headCFrame = UserInputService:GetUserCFrame(Enum.UserCFrame.Head)
renderCFrame = workspace.CurrentCamera.CFrame * headCFrame

The Camera's render CFrame will only be changed to account for the head when the Camera.HeadLocked property is true.

This function returns, in radians, the current roll applied to the Camera using Camera:SetRoll(). Roll is defined as rotation around the Camera's Z-axis.

This function only returns roll applied using the Camera:SetRoll() function. Roll manually applied to the Camera's Camera.CFrame is not accounted for. To obtain the actual roll of the Camera, including roll manually applied, you can use the following snippet:

local function getActualRoll()
	local camera = workspace.CurrentCamera

	local trueUp = Vector3.new(0, 1, 0)
	local cameraUp = camera:GetRenderCFrame().upVector

	return math.acos(trueUp:Dot(cameraUp))
end

This function is broken and should not be used.

This function returns the current 'tilt' speed of the Camera.

The 'tilt' speed of the Camera describes the speed at which the Camera is rotating around its Camera.Focus around the Camera's X axis.

See also:

Camera:GetPanSpeed() for the speed the Camera is rotating around the Camera.Focus around the Y axis Camera:PanUnits() to 'pan' the camera Camera:TiltUnits() to 'tilt' the camera

This function creates a unit Ray from a 2D position on the screen (defined in pixels). This position accounts for the GUI inset. The Ray originates from the Vector3 equivalent of the 2D position in the world at the given depth (in studs) away from the Camera.

As this function accounts for the GUI inset, the offset applied to GUI elements (such as from the top bar) is accounted for. This means the screen position specified will start in the top left corner below the top bar. For an otherwise identical function that does not account for the GUI offset, use Camera:ViewportPointToRay().

As the Ray created is a unit ray it is only one stud long. To create a longer ray, you can do the following:

local camera = workspace.CurrentCamera
local length = 500
local unitRay = camera:ScreenPointToRay(100, 100)
local ray = Ray.new(unitRay.Origin, unitRay.Direction * length)

This function sets the CameraPanMode to be used by the Camera on mobile devices.

When the *'EdgeBump' CameraPanMode is used, swipe to pan is disabled and the edge bump camera controls are enabled.

SetCameraPan mode has no effect on PC / Mac users.

This function is outdated and no longer considered best practice.

This function sets the current roll, in radians, of the Camera. The roll is applied after the Camera.CFrame and represents the rotation around the Camera's Z-axis.

For example, the following would invert the Camera:

workspace.CurrentCamera:SetRoll(math.pi) -- math.pi radians = 180 degrees

SetRoll has no effect on any roll applied using the Camera.CFrame property. Roll applied using SetRoll is not reflected in the Camera.CFrame property but is reflected in in the CFrame returned byCamera:GetRenderCFrame().

This function can only be used when the Camera.CameraType is set to 'Scriptable', regardless of whether the default camera scripts are being used. If it is used with any other Camera.CameraType a warning is given in the output.

Any roll applied using this function will be lost when the Camera.CameraType is changed from 'Scriptable'.

To obtain the roll set using this function use Camera:GetRoll().

As this function is outdated, you are advised to instead apply roll to the Camera using the Camera.CFrame property. For example:

local currentCFrame = workspace.CurrentCamera.CFrame
local rollCFrame = CFrame.Angles(0, 0, roll)
workspace.CurrentCamera.CFrame = currentCFrame * rollCFrame

This function creates a unit Ray from a 2D position on the viewport (defined in pixels). This position does not account for the GUI inset. The Ray originates from the Vector3 equivalent of the 2D position in the world at the given depth (in studs) away from the Camera.

As this function does not account for the GUI inset, the viewport position given is not equivalent to the screen position used by GUI elements. If you are not using ScreenGui.IgnoreGuiInset and need an otherwise identical function that accounts for the GUI offset, use Camera:ScreenPointToRay().

This function can be used in conjunction with the Camera.ViewportSize property to create a ray from the centre of the screen, for example:

local camera = workspace.CurrentCamera
local viewportPoint = camera.ViewportSize / 2
local unitRay = camera:ViewportPointToRay(viewportPoint.X, viewportPoint.Y, 0)

As the Ray created is a unit ray it is only one stud long. To create a longer ray, you can do the following:

local camera = workspace.CurrentCamera
local length = 500
local unitRay = camera:ScreenPointToRay(100, 100)
local ray = Ray.new(unitRay.Origin, unitRay.Direction * length)

This function returns the screen location and depth of a Vector3 worldPoint and whether this point is visible on the screen or not.

This function takes in account the current GUI inset (such as the space occupied by the top bar). This means the 2D position returned is in the same term as GUI positions and can be used to place GUI elements. For an otherwise identical function that ignores the GUI inset, see Camera:WorldToViewportPoint().

For example:

local camera = workspace.CurrentCamera
local worldPoint = Vector3.new(0, 10, 0)
local vector, onScreen = camera:WorldToScreenPoint(worldPoint)

local screenPoint = Vector2.new(vector.X, vector.Y)
local depth = vector.Z

Note this function does not perform any raycasting, meaning the visible bool will be true regardless if the worldPoint is obscured by BaseParts or Terrain.

This function returns the screen location and depth of a Vector3 worldPoint and whether this point is visible on the screen or not.

This function does not take in account the current GUI inset (such as the space occupied by the top bar). This means the 2D position returned is taken from the top left corner of the viewport. This means, unless you are using ScreenGui.IgnoreGuiInset this position is not appropriate for placing GUI elements.

For an otherwise identical function that accounts for the GUI inset, see Camera:WorldToScreenPoint().

For example:

local camera = workspace.CurrentCamera
local worldPoint = Vector3.new(0, 10, 0)
local vector, inViewport = camera:WorldToViewportPoint(worldPoint)

local viewportPoint = Vector2.new(vector.X, vector.Y)
local depth = vector.Z

Note this function does not perform any raycasting, meaning the visible bool will be true regardless if the worldPoint is obscured by BaseParts or Terrain.

Broken: This event is broken and should not be used.

This event fires when the local user's Camera switches in and out of first person mode.

This event no longer functions and cannot be used by developers due to its security context.

You can instead check the distance between the Camera's Camera.CFrame and Camera.Focus to determine if the local user is in first person mode. For example:

local camera = workspace.CurrentCamera
local distance = (camera.CFrame.p - camera.Focus.p).magnitude
local isFirstPerson = distance <= 0.5

This event fires when the Camera has finished interpolating using the Camera:Interpolate() function.

This event will not fire if a tween is interrupted due to Camera:Interpolate() being called again.

You are advised to use TweenService to animate the Camera instead, as it is more reliable and provides more options for easing styles.