> For the complete documentation index, see [llms.txt](https://zynoxdev.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zynoxdev.gitbook.io/docs/zynox-resources/zx_loading_screen.md).

# ZX - Loading Screen

Zynox Studio Documents > ZYNOX RESOURCES

## 🎬 ZX - Loading Screen

Premier AAA game HUD loading screen — dynamic 7-season particle engine, 4-corner frameless HUD, 3-in-1 background engine, and interactive audio player.

A state-of-the-art loading experience designed to give your FiveM server a high-end first impression. Built with frameless floating glassmorphism, authentic real-time analog clock & calendar, dynamic seasonal particles, FiveM player name handover, and 60+ FPS zero-latency performance.

```lua
author 'Zynox Development'
```

```lua
dependencies { 'standalone' }
```

![Version](https://img.shields.io/badge/version-1.0.0-0088ff.svg) ![Compatibility](https://img.shields.io/badge/FiveM-Standalone%20%7C%20Qbox%20%7C%20QBCore%20%7C%20ESX-00a2ff.svg) ![Resmon](https://img.shields.io/badge/Resmon-0.00ms-0066ff.svg) ![Author](https://img.shields.io/badge/Author-Zynox%20Development-0055ff.svg)

***

### 📑 Resource Pages

* [📥 Installation & Setup](/docs/zynox-resources/zx_loading_screen/installation.md)
* [⚙️ Configuration Guide](/docs/zynox-resources/zx_loading_screen/configuration.md)
* [🎨 Customization & Media](/docs/zynox-resources/zx_loading_screen/customization.md)
* [❓ Troubleshooting & FAQ](/docs/zynox-resources/zx_loading_screen/troubleshooting.md)

***

### Overview

* **Modern minimalist HUD** — Frameless floating interface featuring a round analog ticking clock, live pulse indicator, real-time date calendar, and neon segmented loading bar.
* **Dynamic 7-Season particle engine** — Automatically adapts seasonal particle physics and color schemes according to the player's real-world calendar date (Christmas snow, Halloween embers, Valentine hearts, Summer fireflies, New Year confetti, Spring blossom, and Cyberpunk cyan).
* **Authentic player greeting** — Connects directly to FiveM's deferral handover system to welcome players by their actual Steam or FiveM username.
* **3-in-1 Background media engine** — Easily switch between Ken Burns photo slideshows, local looping MP4 videos, or fullscreen YouTube live embeds directly in `config.js`.
* **Interactive music player** — Complete with dancing neon VU meter frequency visualizers, click-to-seek progress timeline, volume slider, and keyboard shortcuts (`[SPACE]`, `[M]`, `[↑/↓]`, `[←/→]`).
* **100% Standalone & 0.00ms CPU** — Pure hardware-accelerated NUI CEF rendering with zero framework dependencies.

***

### 🛠️ Technical Specifications

| Property            | Details                                              |
| ------------------- | ---------------------------------------------------- |
| **Framework**       | Standalone (Qbox, QBCore, ESX, vRP, Custom)          |
| **Idle Resmon**     | **0.00ms** (Pure NUI execution during connect phase) |
| **Audio Engine**    | HTML5 Web Audio API + VU Meter Canvas Visualizer     |
| **Particle Engine** | Pure Canvas 2D Physics Particle System               |
| **Media Support**   | Local MP4, YouTube Embeds, 4K WebP / PNG / JPG       |
| **Configuration**   | Vanilla JavaScript Object (`html/config.js`)         |

***

-# © 2026 Zynox Development • [Official Store](https://zynoxdev.tebex.store/) • [Discord](https://discord.gg/2yuPTmsqjX)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://zynoxdev.gitbook.io/docs/zynox-resources/zx_loading_screen.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.