Charlie686

Of course I understand - but we're talking about development here, and the fact of the matter is that no code is being executed. Maybe you'd like to test removing your other plugins & trying again. You're the only one to report this issue; I've never been able to replicate it, nor my testers, nor has it been reported by anyone else. If you aren't willing to sign up to the platform - for whatever reasons you have to right to have - then I cannot look into this issue further. Take care! 🙂

If that's the case, it is unlikely your issue is caused by 686 Callouts. It was doing nothing at the time of the crash (having loaded several seconds prior), as evidenced in the below section of your log. That's not to say you might have a conflict with an existing modification - but this is something we can look into further! [1/23/2023 11:03:45 AM.245] LSPD First Response: [686 Callouts] All done, have a fantastic patrol! Given this modification is released entirely for free, off the back of my spare time, I hope people can understand the value in making things a little more convenient for me by contacting me through Discord. I can see you have joined the support server, and I'd be appreciative if you opened a ticket in the #686-tickets channel, thank you. 😄

I acknowledge your explanation and thank you for that; the log contains critical information on the relation of 686 Callouts' loading process to your game through informational logging, which is incredibly important. Your log does have an issue in regards to 686 Callouts, one which will be patched in the next build. But - this should not be causing any issues or the one you described. That issue can be fixed by simply restarting GTAV & reloading up LSPDFR, so please give that a try. The only thing that changed in the latest update is when some logging occurs, so it's incredibly unusual that you are experiencing this issue with this build, but not the previous. As such, I'd advise you to join my Discord here where we'll be able to look into this more effectively, given this is complicated in nature. In gratitude, I'll provide you with the next beta build for 686 Callouts which features a new callout. Thank you, Charlie686

Thank you for reaching out - but I'm not sure how you expect me to look into this without your log file.

A great modification - Lenny has gone the extra mile to make this the most reliable, intuitive & realistic trunk system. Specifically, including a closing trunk animation is a notable difference, absent from plugins like Stop The Ped. It was a real treat to be apart of the development process.

You should attach your RagePluginHook log (found in your main directory) in order for the developer to look into this issue. Equally, I've seen a few crashes from users using an outdated RAGENativeUI. Make sure yours is updated. @Officer Jared - it might be worth introducing a check to prevent such crashes, which might get your plugin accidentally being labelled as 'at fault' 🙂