Asset version mismatch prevents default Qbox resources from starting on GTA V Enhanced

[casalis8407-cloud]

Summary

Several default Qbox resources fail to start on FiveM for GTA V Enhanced because FXServer reports asset version mismatch errors for multiple streamed .ytd files.

The affected resources include qbx_customs, qbx_hud, and qbx_properties. The resources only start after the incompatible .ytd files are removed from their stream folders, which is only a temporary workaround and may break their intended visual functionality.

Issue type

Server

Repro rate

Always

Server build version

FXServer-early-access b94 win32

OS

No response

CPU

No response

GPU

No response

RAM

No response

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

Windows

OS version / distribution

Windows Server 2022 Standard Evaluation, build 20348

CPU

AMD Ryzen 9 7950X 16-Core Processor

RAM

8 GB

Using txAdmin?

Yes

Hosting provider

Other GSP

Machine type

VPS

/perf endpoint output

http://localhost:40120/perf

DDoS protection

Unknown

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Install a fresh Qbox server using the standard txAdmin recipe on Windows Server 2022.

2. Start the server with the default Qbox resources enabled, including qbx_customs, qbx_hud, and qbx_properties.

3. Observe the FXServer console during startup. The affected resources fail to start because FXServer reports "Asset version mismatch" errors for several streamed .ytd files.

Expected Behavior

All default Qbox resources should start successfully on FiveM for GTA V Enhanced without requiring any streamed asset files to be removed.

The included .ytd files should be compatible with the current game and FXServer environment.

Actual Behavior

Several default Qbox resources fail to start because FXServer reports asset version mismatch errors.

Examples:

qbx_customs:
Asset version mismatch for "stream/vehicle_paint_ramps.ytd"

qbx_hud:
Asset version mismatch for "stream/circlemap.ytd"
Asset version mismatch for "stream/minimap.ytd"
Asset version mismatch for "stream/squaremap.ytd"

qbx_properties:
Asset version mismatch for "stream/auto_shop_board.ytd"
Asset version mismatch for "stream/auto_shop_board_img.ytd"

The resources only start after the affected .ytd files are moved outside the resource folders and the server cache is cleared.

Evidence

Relevant console errors:

Failed to start resource qbx_customs.
Error: Asset version mismatch for "stream/vehicle_paint_ramps.ytd"

Failed to start resource qbx_hud.
Error: Asset version mismatch for "stream/circlemap.ytd"

Failed to start resource qbx_hud.
Error: Asset version mismatch for "stream/minimap.ytd"

Failed to start resource qbx_hud.
Error: Asset version mismatch for "stream/squaremap.ytd"

Failed to start resource qbx_properties.
Error: Asset version mismatch for "stream/auto_shop_board.ytd"

Failed to start resource qbx_properties.
Error: Asset version mismatch for "stream/auto_shop_board_img.ytd"

After moving the affected files and clearing the cache, the resources started successfully.

Additional Context

Server environment:

Platform: Windows
OS: Windows Server 2022 Standard Evaluation, build 20348
CPU: AMD Ryzen 9 7950X 16-Core Processor
RAM: 8 GB
Server manager: txAdmin
Framework: Qbox / QBX
ox_lib version: 3.39.0
Reproduction rate: Always

ox_lib starts successfully, and dependent resources such as qbx_core and ox_target also start. The failures occur while FXServer is loading the streamed .ytd assets.

Temporary workaround:
The incompatible .ytd files were moved outside the resources directory, the server cache was cleared, and FXServer was restarted.

This allows the resources to start, but the removed files may be required for their intended visual functionality, so this is not considered a permanent fix.

[ihyajb]

you need to convert the assets using alchemist. gen8 assets are not compatible with the gen9 version of gta. https://docs.fivem.net/docs/alchemist/

[casalis8407-cloud]

Okay, buddy, I'll check it right now.

[Gogsi]

A fix for this bug has been implemented and is available in the latest patch b95. Please try again and let us know if the issue persists. Thanks for your help!