[Bug] Streamed GFX files are no longer loaded on FiveM for GTAV Enhanced

[Sulane-commits]

Summary

What happened?

Since a recent FiveM for GTAV Enhanced update, custom .gfx files placed inside a resource's stream folder no longer appear to be loaded by the client.

The resource containing the files starts correctly on the server and is shown as started.

However, when another resource tries to request the streamed Scaleform movie, it never finishes loading.

For example, we are using the generic_texture_renderer_gfx resource containing:

• generic_texture_renderer.gfx
• generic_texture_renderer_2.gfx

The resource is correctly started before the scripts that use it, but both Scaleforms fail to load.

We receive errors similar to:

[cp_ranked] ERROR: Scaleform "generic_texture_renderer" was not loaded — is generic_texture_renderer_gfx started?

[cp_ranked] ERROR: Scaleform "generic_texture_renderer_2" was not loaded — is generic_texture_renderer_gfx started?

The resource is started, so the issue appears to be that the .gfx files are no longer being streamed, registered, or made available to the client.

Expected behavior

Custom .gfx files located inside the resource's stream folder should be downloaded and loaded by the client.

Calling:

RequestScaleformMovie('generic_texture_renderer')

should eventually result in:

HasScaleformMovieLoaded(handle) == true

Actual behavior

The resource starts without any server-side error, but the streamed Scaleform movie never loads.

HasScaleformMovieLoaded remains false and all interfaces using these custom .gfx files stop working.

Steps to reproduce

1. Create or install a resource containing a custom .gfx file inside its stream folder.
2. Start the resource in server.cfg.
3. Start another resource that requests the custom Scaleform with RequestScaleformMovie.
4. Join the server using FiveM for GTAV Enhanced.
5. Wait for the Scaleform to load.
6. Observe that the Scaleform never loads, even though the resource is started.

Resource structure

generic_texture_renderer_gfx/
├── fxmanifest.lua
└── stream/
    ├── generic_texture_renderer.gfx
    └── generic_texture_renderer_2.gfx

Additional information

• Platform: FiveM for GTAV Enhanced
• The GFX resource is started before the dependent resource.
• Restarting the GFX resource does not resolve the issue.
• Restarting the dependent resource does not resolve the issue.
• The .gfx files are present inside the resource's stream folder.
• The scripts worked previously with the same resource structure.
• The problem affects every script relying on these custom Scaleform files.
• Clearing the client cache does not resolve the issue.
• No missing-resource error is displayed on the server.

Environment

• FXServer artifact: latest
• Game edition: GTAV Enhanced
• Reproducible with a minimal test resource: Yes

[Whomsky]

Can confirm, this completely broke ScaleformUI

[manups4e]

ScaleformUI is a known problem #165
I suspect the problem here could be related but in a different way as it maybe still relies into the internal C++ API being called directly from inside the scaleform crashing its loading and therefore the script itself... i didn't make generic_texture_renderer_gfx but i suspect it uses the ImageLoaderMC class internally to call the C++ internal API to load the textures in it and then to load them in its movieclips via callbacks between the game and the scaleform.
Which i think might be the reason of the non-loading scaleforms...
I have other custom scaleforms perfectly working which don't use internal API calls.. and others that do use them and are still working so mine is just an hypotesis

[Whomsky]

Had ScaleformUI (menus specifically) working up until this update 😆

[manups4e]

Oh 🤔

[Gogsi]

Taken from #376 this is another Scaleform that experienced a regression in b111
MINIMAP_LOADER.zip

[manups4e]

This is a different one... As it's handled via minimap overlays natives and not directly via classic scaleform methods.. But definitely could be related