F8 console errors on FiveM start up

– First sign something wasn’t working right –
Over the last couple days I noticed that some ‘press e interact’ points like legacyfuel and esx_drugs when interacted with would disable a bunch of keys. I cannot access weapon wheel or get into vehicles afterwards but can climb objects, move, and access menus. I get no script errors in the F8 console. I disabled all scripts I’ve been working on recently and still the issue persisted.

– F8 console errors on FiveM start up –
I then ran fivem with the F8 console from the beginning before I connected to my server and got these errors.



I deleted caches.xml, citizen folder, and then tried again but still get the errors. I’m also not sure if its related to my issue but I’m stumped as all scripts were working up until recently.

My server is called ‘City of Tresh’

Any help would be greatly appreciated.

Hello, this is a friendly reminder because this is your first time creating a topic (or it has been a while since your last topic) in this category.

Please note that most of the support is provided by the FiveM community on a voluntary basis. We ask you to be patient; there is no guarantee we have a solution to your problem(s). To avoid unnecessary/duplicate topics, please browse the forums before creating a topic.

To improve your chances of your issue(s) being solved, please provide as much information as possible about the issue(s) you are having. Also —whenever possible— please use the template given to you when creating a topic.

Thanks for keeping these forums tidy!
:mascot:

This topic has been moved to the appropriate category.

I've moved your post because I don't see any issues in the screenshots you've posted; I too get the error in the first screenshot, and haven't had any issues, and the output from the second and third screenshots are expected.

Moving to your issue of disabling keys, I suggest you identify a specific resource that is causing you issues (as you have already done), then check he loops inside said resources (since the DisableControlAction() native for example, needs to be called per frame). Either way, I would bet this is a server issue, not a client one.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.