> For the complete documentation index, see [llms.txt](https://sl-scritps.gitbook.io/sl-scripts-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sl-scritps.gitbook.io/sl-scripts-documentation/products/sl-perspective-camera.md).

# SL Perspective Camera

## SL Perspective Camera

**Code:** Current Package\
**Resource:** `sl_perspective_camera`\
**Version:** Current Release\
**Category:** Camera Utility / Immersion Tool / Visual RP\
**Status:** Stable

**Structured tools for serious roleplay servers.**

***

### Overview

SL Perspective Camera is an immersive camera utility for FiveM roleplay servers.

It allows players, staff or creators to use alternative camera perspectives for roleplay, screenshots, cinematic moments, visual testing or more immersive scene presentation.

The resource is designed to improve how players see and frame the world without turning the camera into a complicated editor or full production tool.

***

### What is this script for?

SL Perspective Camera gives servers a simple way to add controlled camera perspective tools.

It is useful for:

* Immersive roleplay views
* Cinematic angles
* Character-focused scenes
* Event presentation
* Staff screenshots
* Media-style scenes
* Creator testing
* Better visual storytelling
* Roleplay scenes that need a different point of view
* Server content creation

The main goal is:

```txt
Activate perspective camera → adjust view → use the scene naturally → return to normal camera
```

***

### Roleplay Experience

SL Perspective Camera is designed around a simple idea:

```txt
The player changes perspective.
The scene feels more cinematic or immersive.
The player can experience the moment from a better angle.
```

This can help roleplay feel more intentional, especially during events, conversations, screenshots, media scenes or cinematic setups.

The tool should support the roleplay moment without distracting from it.

***

### Player IC Usage

For players, SL Perspective Camera can be used to support immersive scenes or visual roleplay.

Common player IC uses:

* Framing a character moment
* Taking a more immersive view during social RP
* Creating cinematic screenshots
* Supporting media or photography RP
* Seeing a scene from a better angle
* Creating visual memories from RP moments

Normal player flow:

```txt
Open perspective camera → adjust view → use the moment → exit camera mode
```

Example IC lines:

```txt
“Let me get a better angle.”
“This view looks perfect.”
“Hold that pose for a second.”
“I want to capture this moment.”
```

Players should use the camera to support the scene, not to gain unfair information or interrupt serious RP.

***

### Player / IC Flow

#### 1. The player opens the camera tool

Depending on configuration, the player may open the perspective camera with a command, keybind or allowed interaction.

Common command examples:

```txt
/perspective
/perspectivecam
```

Check your configuration for the exact command.

***

#### 2. Camera mode activates

Once active, the player gets access to the configured perspective camera behavior.

Expected result:

```txt
The camera changes to the selected perspective.
```

The exact view depends on the server configuration.

***

#### 3. The player adjusts or uses the view

Depending on configuration, the player may be able to:

* Change camera angle
* Adjust distance
* Adjust height
* Use a fixed perspective
* Use a cinematic perspective
* Reset the camera
* Exit camera mode

The goal is to keep the camera useful and simple.

***

#### 4. The player continues the scene

The camera perspective can be used during:

```txt
social RP
screenshots
events
media moments
character scenes
vehicle showcases
cinematic presentation
```

***

#### 5. The player exits camera mode

When finished, the player exits the perspective camera.

Expected result:

```txt
Camera returns to normal.
Player controls return to normal.
Roleplay continues.
```

***

### Creator / Media IC Usage

For photographers, media characters or content creators, SL Perspective Camera can help create better visual scenes.

Common IC uses:

* Frame a subject from a cinematic angle
* Capture event moments
* Prepare character screenshots
* Support news/media scenes
* Capture vehicles or businesses
* Create clean visual content for the server

Example IC flow:

```txt
Choose subject → activate camera → adjust perspective → capture scene → exit camera
```

Example IC lines:

```txt
“Stay there, the angle is good.”
“I’m going to take the shot from here.”
“This perspective shows the whole scene.”
```

This makes the resource useful for servers that care about community media, screenshots and visual storytelling.

***

### Admin / Owner IC Usage

For admins, owners and staff, SL Perspective Camera can be used as a visual support tool.

Common admin/owner IC uses:

* Capture official event screenshots
* Prepare promotional images
* Support staff-hosted scenes
* Create cinematic angles for announcements
* Test how a scene looks from player perspective
* Support media jobs or trusted creators
* Document server updates
* Capture business openings or public events

Example admin/event flow:

```txt
Prepare scene → position players/props → activate perspective camera → capture angles → exit/reset camera
```

Example event scenario:

```txt
Staff prepares a public city event.
A trusted creator uses Perspective Camera to capture cleaner angles.
The screenshots are later used for Discord announcements or event recaps.
```

For server owners, the tool helps make the server look more polished in public content.

***

### Admin / Owner Technical Flow

Admins and owners should configure access, controls and camera limits before enabling the tool publicly.

Common admin actions may include:

* Configure command names
* Configure keybinds
* Configure permissions
* Configure camera modes
* Configure distance limits
* Configure movement limits
* Configure reset behavior
* Configure UI hints
* Configure safe exit behavior
* Restrict access if needed
* Test with normal players and staff

Recommended admin checks:

```txt
1. Confirm the resource starts correctly.
2. Open the perspective camera with the configured command.
3. Test camera activation.
4. Test camera controls.
5. Test reset/exit behavior.
6. Confirm gameplay controls return normally.
7. Test permission restrictions.
8. Test in interiors and exterior areas.
9. Check F8 and server console for errors.
```

***

### Example IC Scenarios

#### Character moment

A player uses a better angle for a character screenshot.

```txt
“This is a good shot of the character.”
```

#### Vehicle showcase

A player frames a vehicle from a lower or cinematic angle.

```txt
“Park it there, I’ll get the front angle.”
```

#### Business promotion

A business owner captures a clean image of the location.

```txt
“We need a good photo for the opening.”
```

#### Staff event

Staff uses the camera to capture event moments.

```txt
“Take one wide shot of the crowd.”
```

#### Media RP

A media player uses the perspective to frame coverage.

```txt
“This angle shows the whole scene behind the reporter.”
```

***

### What this resource is not

SL Perspective Camera is not intended to be a full video editor, full photo mode, livestream system or cinematic recorder by itself.

It is focused on:

```txt
camera perspective
immersive views
simple cinematic angles
visual roleplay support
safe camera reset
controlled usage
```

For advanced photography, servers may also use SL Photo Mode.\
For reporter/news scenes, servers may also use SL Auto News Camera.

***

### Main Features

* Perspective camera utility
* Immersive camera views
* Cinematic angle support
* Player and staff use cases
* Useful for screenshots and roleplay scenes
* Command or keybind access depending on configuration
* Configurable permissions
* Configurable camera behavior
* Configurable limits
* Safe exit/reset behavior
* Useful for creator and media workflows
* Lightweight camera-focused design
* Clean SL Scripts style

***

### Dependencies

#### Required

```txt
FiveM server
```

#### Recommended / Optional

```txt
ox_lib
QBCore
Qbox
ESX
Standalone mode
```

The exact dependency setup depends on server configuration.

SL Perspective Camera usually does not require inventory, target or database systems unless your installed version or custom configuration adds them.

***

### Installation Notes

1. Place the resource folder inside your server resources folder.

Example:

```txt
resources/[sl_scripts]/sl_perspective_camera
```

2. Make sure the folder name is:

```txt
sl_perspective_camera
```

3. Configure:

```txt
config.lua
custom.lua
locales/
```

4. Add the resource to your `server.cfg`.

Example:

```cfg
ensure ox_lib

ensure sl_perspective_camera
```

If your build does not require `ox_lib`, configure fallback behavior in `config.lua`.

***

### How to Use

#### Basic Player Flow

1. The player opens the perspective camera.
2. Camera mode activates.
3. The player adjusts or uses the configured perspective.
4. The player captures screenshots or uses the angle for RP if needed.
5. The player exits the camera.
6. Normal gameplay camera returns.

#### Basic Admin Flow

1. Admin configures access and controls.
2. Admin tests camera modes.
3. Admin tests reset and exit behavior.
4. Admin checks permissions.
5. Admin enables the tool for trusted users or configured groups.

#### IC Summary

```txt
Player activates camera perspective → scene is framed better → player exits and continues RP
```

#### OOC / Technical Summary

```txt
Command/keybind opens tool → camera mode activates → player adjusts view → reset/exit restores normal camera
```

***

### Controls

Exact controls may depend on configuration.

Common perspective camera controls may include:

```txt
W / A / S / D = move or adjust camera depending on mode
Mouse = look around
Scroll = zoom or adjust camera distance
Q / E = adjust height or rotation depending on mode
SHIFT = faster movement if enabled
CTRL = slower movement if enabled
H = hide/show helper UI if configured
R = reset camera if configured
BACKSPACE / ESC = exit camera mode
```

Check `config.lua` and in-game hints for the exact control layout.

Recommended:

```txt
Keep controls simple.
Show clear hints while camera mode is active.
Always provide a safe exit key.
```

***

### Commands

Command names may depend on configuration.

Common command examples:

```txt
/perspective
/perspectivecam
/sl_perspective
/sl_perspective_camera
```

Possible admin/reset command examples:

```txt
/perspective_reset
/sl_perspective_admin
```

Check `config.lua` for the exact command names used by your installed version.

Commands are useful for opening the tool, testing camera behavior or resetting camera state if needed.

***

### Permissions

Permission setup depends on server configuration.

Common permission levels may include:

```txt
view
use
media
admin
owner
```

Recommended access logic:

```txt
Players = basic camera use if allowed
Media/creators = camera use for screenshots and RP content
Staff = event and documentation use
Admins = full access and reset tools
Owners = full access
```

Permissions may use:

* Ace permissions
* Framework groups
* Jobs
* Job grades
* Config admin list
* Custom permission bridge

Recommended:

```txt
Restrict advanced camera freedom if your server wants stricter RP control.
```

***

### Usage Guidelines

#### Good uses

```txt
character screenshots
vehicle screenshots
business promotion
event documentation
cinematic RP scenes
media RP
server announcements
creator content
```

#### Avoid

```txt
using the camera to spy through walls
using camera mode during combat
interrupting serious RP
blocking scenes while taking screenshots
gaining unfair information from camera angles
staying in camera mode longer than needed
```

Servers should define rules based on how strict their roleplay environment is.

***

### Configuration

Open:

```txt
config.lua
```

Common settings may include:

```txt
Product information
Locale
Debug mode
Startup logs
Command settings
Keybind settings
Permission settings
Camera modes
Camera speed
Camera distance
Camera limits
Zoom settings
Control settings
UI hint settings
Exit/reset behavior
Admin settings
```

Recommended for production:

```lua
Config.Debug = false
```

Use debug mode only while testing or troubleshooting.

***

### Custom Integrations

Open:

```txt
custom.lua
```

Use this file for server-specific functions such as:

* Custom notifications
* Custom permission checks
* Custom framework integration
* Custom job restrictions
* Custom admin checks
* Custom logging
* Custom camera restrictions

If your server uses standard permission systems, you may only need to configure access.

***

### Startup Logs

When the resource starts correctly, you may see logs similar to:

```txt
[sl_perspective_camera][INFO] Server ready: SL Perspective Camera
[sl_perspective_camera][INFO] Client ready: SL Perspective Camera | Use /perspective
```

If startup logs are disabled, check `config.lua`.

***

### Best Practices

#### Keep it lightweight

SL Perspective Camera should be fast to open, easy to exit and simple to understand.

Recommended:

```txt
Use it for quick angles and visual support.
Do not overcomplicate the controls.
```

***

#### Use clear permission rules

If the camera can move freely, restrict it to trusted users or keep camera limits strict.

Recommended:

```txt
Public use = limited perspective modes
Media/creator use = expanded camera modes
Admin use = full testing/reset tools
```

***

#### Test in different places

Camera behavior can feel different depending on the location.

Test in:

```txt
interiors
exteriors
vehicles
crowded event areas
business interiors
narrow spaces
wide open areas
```

***

### Troubleshooting

#### Perspective camera does not open

Check:

```txt
- The resource is started.
- You are using the correct command.
- Commands are enabled in config.lua.
- You have permission to use the camera.
- F8 console has no errors.
- Server console has no errors.
```

***

#### Camera does not move

Check:

```txt
- Camera mode activated correctly.
- Controls are configured.
- Another camera resource is not active.
- Another NUI is not blocking controls.
- Player state allows camera usage.
- F8 console has no camera/control errors.
```

***

#### Camera feels too fast or too slow

Check:

```txt
- Camera speed settings.
- Slow/fast modifier settings.
- Zoom settings.
- Control sensitivity.
```

Adjust values gradually and test in game.

***

#### Player gets stuck after exiting camera mode

Check:

```txt
- Exit/reset behavior is enabled.
- ESC/BACKSPACE exit control is configured.
- Camera reset function is working.
- Player controls are restored after exit.
- Another resource is not taking camera control.
```

Try the configured reset command if available.

***

#### Camera clips into walls or objects

Check:

```txt
- Camera distance limit.
- Collision settings if available.
- Interior layout.
- Maximum zoom/distance.
- Camera mode selected.
```

Recommended:

```txt
Use shorter camera distance in interiors.
Use stricter limits for public players.
```

***

#### Normal players can access restricted camera tools

Check:

```txt
- Permission settings.
- Ace permissions.
- Framework group detection.
- Job/grade restrictions.
- custom.lua permission bridge.
- Config admin list.
```

Recommended:

```txt
Restrict advanced camera modes to staff, media jobs or trusted creators.
```

***

#### Screenshots or recordings do not save

SL Perspective Camera helps frame the scene, but the final capture may depend on the player’s screenshot or recording tool.

Check:

```txt
- FiveM screenshot settings.
- Steam screenshot settings.
- Windows capture settings.
- Recording software settings.
- Disk space and save folder.
```

***

### Version Notes

#### Current Release

* Perspective camera workflow for immersive views and visual RP.
* Supports player, media, creator and staff use cases depending on configuration.
* Focused on clean camera behavior, safe exit and practical roleplay presentation.

***

### Support

When asking for support, include:

```txt
Product: SL Perspective Camera
Resource name: sl_perspective_camera
Version:
Framework:
Issue:
Steps to reproduce:
Command used:
Permission setup:
Camera mode:
Server console error:
Client F8 error:
Screenshot/video:
```

Example:

```txt
Product: SL Perspective Camera
Resource name: sl_perspective_camera
Version: Current Release
Framework: Qbox
Issue: Camera opens but does not reset after exiting
Steps to reproduce: Use /perspective, move camera, press ESC
Command used: /perspective
Permission setup: media/staff only
Camera mode: default
Server console error: none
Client F8 error: attached
Screenshot/video: attached
```

***

### Final Notes

SL Perspective Camera works best as a lightweight immersive camera utility.

For best results, configure clear permissions, simple controls and safe camera limits so the tool supports roleplay without creating unfair camera advantages.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://sl-scritps.gitbook.io/sl-scripts-documentation/products/sl-perspective-camera.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
