[Bug] Failed to open file 'cfx_resource_ox_lib:/imports/* #42
Replies: 9 comments 4 replies
|
Same happens on the client side as well but weirdly some parts of it works some dont..
|
|
For me also, UPVOTE this discussion |
|
Same issue here. Also appears both client and server side. And for some reason most of scripts that are dependent on ox_lib seems to work, but some of them seems to be broken. |
|
guys same her wtf its happening @overextended |
|
These errors are just visual. FiveM Legacy didn't showed failed file reads. osx is trying to read the same files in Legacy and this is specifically is not breaking any behavior inside it. |
|
I'm facing the same error as well in FiveM Enhanced, It is actually causing certain ox_lib dependent scripts to fail like, illenium_appearance and even qbx_core Eventhough resources are started, the behaviour of the specified scripts are not working as expected, but the same is working properly in Fivem Legacy. I think any ox_lib dependent scripts might act strange on FiveM Enhanced, unless or until this issue is rectified |
|
#207 same issue which it's related to vfs bug/ issue |
|
Thanks, will be fixed in the next build. |
|
A fix for this bug has been implemented and is available in Hotfix 6. Please try again and let us know if the issue persists. Thanks for your help! |
Uh oh!
There was an error while loading. Please reload this page.
Summary
After switching to FiveM Enhanced (server build 3570), every resource using ox_lib imports logs errors like:
Failed to open file 'cfx_resource_ox_lib:/imports/require/server.lua'
Failed to open file 'cfx_resource_ox_lib:/imports/locale/server.lua'
Failed to open file 'cfx_resource_ox_lib:/imports/versionCheck/server.lua'
The errors occur for every resource using ox_lib (qbx_core, ox_inventory, ox_target, ox_doorlock, qbx_management, etc.).
Interestingly, ox_lib itself starts successfully before these errors appear.
This only happens on FiveM Enhanced. The same server and resources work correctly on the regular FiveM build.
The resources continue starting, but the server console is flooded with "Failed to open file" messages.
Expected behavior:
Files referenced through the cfx_resource_ox_lib virtual resource path should resolve correctly without logging "Failed to open file".
Issue type
Server
Repro rate
Always
Server build version
3570
OS
Windows 11
CPU
AMD Ryzen 7 5800x
GPU
RTX 3070
RAM
32GB DDR4
Storage type
None
Connection type
None
ISP and bandwidth
No response
DxDiag
No response
Network graph
No response
Platform
None
OS version / distribution
Windows Server 2022
CPU
AMD EPYC 9374F
RAM
20GB DDR4 EEC
Using txAdmin?
Yes
Hosting provider
Other GSP
Machine type
None
/perf endpoint output
No response
DDoS protection
NO
ulimit -n value (Linux only)
No response
Docker Compose file (Docker only)
No response
Steps to Reproduce
Expected Behavior
Resources should be able to load files from the virtual resource path
cfx_resource_ox_lib:/imports/*without errors.No "Failed to open file" messages should be logged when starting ox_lib or resources depending on it.
Actual Behavior
When starting the server on FiveM Enhanced (server build 3570), every resource that depends on ox_lib logs multiple errors such as:
Failed to open file 'cfx_resource_ox_lib:/imports/require/server.lua'
Failed to open file 'cfx_resource_ox_lib:/imports/locale/server.lua'
Failed to open file 'cfx_resource_ox_lib:/imports/versionCheck/server.lua'
The issue affects all ox_lib dependent resources (e.g. qbx_core, ox_inventory, ox_target, ox_doorlock, qbx_management, etc.).
ox_lib itself starts successfully, but the server console is flooded with these errors. This does not occur on the regular FiveM build.
Evidence
No response
Additional Context
Failed to open file 'cfx_resource_ox_lib:/imports/require/server.lua'
Failed to open file 'cfx_resource_ox_lib:/imports/locale/server.lua'
Failed to open file 'cfx_resource_ox_lib:/imports/versionCheck/server.lua'
This occurs for qbx_core, ox_inventory, ox_target, ox_doorlock and other ox_lib dependent resources.
The same resources work correctly on the regular FiveM build and only show this behavior on FiveM Enhanced.
All reactions