Phaxol

The plugin should automatically detect if you are using a controller or not, no need to turn it on or off I will probably change it in the next update, thanks for the suggestion 🙂 If you could get me a log of when the issue happens I can look into it, is there anything you think might be triggering it?

Newest version should be compatible with STP intox levels now, it was based on traffic policer alone before This can be a common crash. I'm starting to think it is because my plugin pauses the game and then another plugin tries to spawn something but the spawning fails, causing the game to crash. I will look into taking out the pause and seeing if it stops the crash

The independent controller system along with a couple other bug fixes should be done sometime this weekend, while the STP issue will take a little longer. Sorry, I have gotten quite busy again with school work and finals are in 2 weeks so development has slowed again

I'm going to be investigating this bug in the next release, I believe it's caused by STP setting drug/alcohol levels independently of Traffic Policer, should be a simple enough fix using the STP API Its definitely on my list of planned features; I will probably have one more bug fixing update for this version before I add more to the computer's functionality. I am hoping after the next update to add evidence integration, tablet mode, as well as being able to see prior arrests/citations for peds

Yeah the dismissal bug has plagued the plugin for a very long time, just to show you how much I have tried to stop this issue from happening: As for the other crash, I do usually use try/catch or ped checks but a crash in that function is very rare because the thread closes very quickly and the reference to the ped only needs to stay alive long enough for it to finish, I will add better error handling to it in the future

Sorry but if it were that easy the issue would have been fixed by now, here is my logic before every line of dismissal in the dismiss ped code: There are 5 different checks to make sure the ped is not arrested, getting arrested, stopped by STP, or being interacted with by my plugin before being dismissed. This puts me in a tight spot because if I remove the functionality, peds will just stand there indefinitely after you are done interacting if the user is not using STP or the default LSPDFR stop to dismiss them. There are a couple ideas I am toying around with, such as making STP a requirement and only letting the Interaction+ menu open on traffic stops and if the ped is stopped by STP, rewriting the dismissal function and hoping for the best, or making a "Dismiss Ped" option in the menu for each ped, which would still mean having to code the same dismissal function in case the player leaves the area without dismissing the ped. As of right now, I'm not really sure which path to take but will probably just completely rewrite the function in the future Most likely the ped object became null and caused a crash, which can happen randomly while playing. My plugin cannot access the ped object anymore because it has been made null through some unknown mechanism which causes a full crash, there's really no fix but to restart the game; just a complication that arises from heavily modifying the game and having many moving parts working on the same object

Interaction+ is not meant as and probably never will be a replacement for the default LSPDFR stop function or STP stop function, it is recommended to use my plugin in conjunction with either of those to have better control over the peds. However, if you are issuing a ticket to a driver on a traffic stop that is still in their vehicle, they will wait until you return to your vehicle to drive away. If the ped is outside of the vehicle and you are only using the Interaction+ menu to control them, they should return to their car after the preset time in the .ini file (default 30 seconds)

Yeah, in America it is an automatic arrest for driving under the influence, so there is no citation option. You can edit the Charges and Citations XML files to better suit your needs :) Try running both the game and RagePluginHook as administrator, should fix this issue :)

I will have to look into blocking controller input while the menu is open, thanks for the suggestions 🙂

Yeah, I'm starting to think Bejoljo's plugins just don't respond to the blocking of input, which if they don't then there's nothing I can do about it. I will need to test more to confirm. 2.2.4 should have the same issue, I have not touched this function in the newest update so it should be exactly the same code.

Very weird, I did not touch any of the code pertaining to this and I am still able to create arrest reports for arrested peds: Have you tried not asking for the ID after they are arrested? That may reset their computer entry and the logic to make the arrest reports available might be reset. Try either using the automatic entry on traffic stops or do it before the ped is arrested for now, I will look into a fix

I might rework how the plugin finds when to make the traffic stop menu available, although its weird that happens because the traffic stop menu shouldn't open if the ped is out of the car and arrested. I will have to look into it a little more, might be a weird interaction with the new way LSPDFR does traffic stops

This can be done, you must simply ask the ped for their ID in the Interaction+ menu then their ID will appear in the computer system. Going to look into STP integration soon

That error looks to me like LSPDFR caused this crash. This part: is caused because the main plugin crashed, meaning my plugin cannot continue to run and throws an error

I have fixed the computer entry deletion for vehicles (sure of it this time), upped the radius for traffic stop detection by 0.5, and fixed the issue when the computer would shut down when a pedheadshot could not be generated. Anyone on that wants to test to make sure these are fixed before the update goes live PM me, need people to test it out

Hmm, I'm starting to think this happens when the game just can't generate a headshot for the ped, and my code doesn't handle it well. Going to add a fail-safe timer that if triggered will give a notification without a ped headshot instead of causing the plugin to freeze 1. Hmm I cannot reproduce this issue, I successfully wrote and issued 3 citations to different vehicle. Does this issue affect all vehicles? 2. This has been known for a while, I will try to boost the detection radius in the next release to fix the issue 3. Probably caused by the transport taking over the ped and eventually making them null, I could maybe do something about the menu locking up but in the long run its safer to do all computer work before calling transport There should already be a 10 second fail-safe in these functions where the ped is teleported to the next needed position and the test continues. Its recommended to do the test in a wide area with enough room for the ped to move; you should be able to walk anywhere and have the ped move to you when you press the interact key again

Is it arrested peds you see dissappearing quickly or just peds you have ID'd? Have you tried upping the default time in the .ini file? And that other one is a known bug that's been around forever. Once I have time to talk to Bejoljo I might just remove the part of the code that I think is causing that weird interaction. I can never get it to consistently reproduce itself in my game, it seems almost random if it happens or not. I will have to look into the vehicles not deleting more, I thought I had fixed the issue but I guess not. As for the stolen vehicle registration name, unfortunately this seems to be a bug with the LSPDFR API as I use the provided function "GetVehicleOwnerName" to return the registration status. Either LSPDFR is setting the name incorrectly, or what ever spawned that random car stealing event did.

You must first ask for the ped's ID through the Interaction+ menu, I'm going to talk to Bejoljo and see if he would be interested in making the two plugins work together

Damn I was kinda worried that would happen, I made a change to get rid of some unnecessary log errors but it seems it prevented the time refresh for arrested peds, making them get deleted faster. Looks like there will be another small update coming, I guess I should have tested that before release lol

You don't have Traffic Policer installed correctly, it is needed for the plugin to run. Without it the game will always crash when approaching on traffic stops/observing suspects. I do not use the vanilla interaction menu so I will have to test out how they interact, I recommend using StopThePed as I know the two plugins work fine together. I'm pretty sure this issue is due to the ped headshot cache being filled up. The game only allows for 34 ped headshots to be registered, meaning if you use functions that use ped headshots (creating arrest reports, record checks, citations, etc) more than 34 times, the fiber my thread is on will be stuck in an infinite loop waiting for the headshot to be registered but it never is, so the plugin stops working. Luckily there is a function for unregistering headshots when I am done with them so it should be an easy fix. Just to confirm, this issue only happens after a while of gameplay, correct?

Controller accessibility is on my list of things to do for the next update, just recently got a gamepad to test

Trust me, its high on the list 😎 more than likely will be in next update unless i release a smaller bug fix update first

Do you have DarkMyre's API installed in your main GTA V folder? It is required for SearchWarrant to work. https://www.ausgamer.net/files/file/24-darkapi/

The newest log file is in GTAV main directory titled "RagePluginHook.log", all past log files are in GTAV\Logs as said above

Was this a full out crash or just an LSPDFR plugin crash? I notice right before the end of the log there was an error in computer entry deletion, but it was handled to prevent a plugin crash. I am fixing this issue in the next update as well, already have plans on a work around Do you have Traffic Policer installed?