[Bug] CreateRuntimeTextureFromImage file not found #149
normal88
started this conversation in
[BUG] FiveM for GTAV Enhanced
Replies: 2 comments 5 replies
|
Thanks, we are looking into this. |
0 replies
|
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! |
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment


Uh oh!
There was an error while loading. Please reload this page.
Summary
The native CreateRuntimeTextureFromImage fails to load a PNG file that physically exists in the resource and is correctly declared in fxmanifest.lua. The exact same resource, file structure, and script work correctly on FiveM Legacy, but fail consistently on Enhanced.
Error : Script error in Native CreateRuntimeTextureFromImage: "The file "Utils/Markers/teleportation.png" was not found."
Issue type
Client
Repro rate
Always
Server build version
FXServer-early-access b94 win32
OS
Windows 11 25H2
CPU
AMD Ryzen 5 8400F
GPU
NIVIDA RTX 4060
RAM
32GB DDR5
Storage type
SSD NVMe
Connection type
Ethernet
ISP and bandwidth
100 Mbps
DxDiag
No response
Network graph
No response
Platform
None
OS version / distribution
No response
CPU
No response
RAM
No response
Using txAdmin?
None
Hosting provider
None
Machine type
None
/perf endpoint output
No response
DDoS protection
No response
ulimit -n value (Linux only)
No response
Docker Compose file (Docker only)
No response
Steps to Reproduce
1.Create a resource with an image file at images/IMG.png.
2.Declare the file in fxmanifest.lua under files (e.g. files { 'images/IMG.png.' }).
3.Call CreateRuntimeTextureFromImage client-side referencing that path.
4.On Legacy: works correctly, texture loads.
5.On Enhanced: native throws "file not found" even though the file exists on disk and is declared identically.
Expected Behavior
CreateRuntimeTextureFromImage should resolve the declared file path the same way on Enhanced as it does on Legacy, since the resource structure, manifest declaration, and file itself are unchanged between the two.
Actual Behavior
The native fails to find the file and throws a script error, even though:
Evidence
No response
Additional Context
All reactions