FtDLulz

That's something that happens that I haven't managed to track down yet. Don't worry about it, it seems harmless.

If the vehicle is longer than an average car, the character will essentially teleport to get to the search location. This is because I can't detect the vehicle's size in my scripts, making it hard to compensate for larger-than-normal vehicles.

Right now, I have it so it checks the vehicle to see if the vehicle is a police vehicle, which is a Rage Plugin Hook function. It may not detect those.

Thanks for the heads-up, I've been really busy lately and I'm not really keeping up with GTA V / RPH updates. I don't really have time to test it, so if you have any problems, just post here and I'll be sure to get to it as soon as I can.

You have version 0.20 of the RPH. Update, please.

Ah, that would be because it gets a position behind the ped, but since your character pushes the ped out of the way, the position is actually in front. Then your character turns and faces the position, but the problem is the ped is no longer there. I'll probably try freezing the ped's position until the search is finished, so there's no chance of the ped being pushed out of the way. Thanks for the report and a video!

It's right between the SearchKeyboard and SearchController settings. Make sure you have the latest version of Vehicle Search.

It's already implemented.

Is the modifier key set to 'None' and have you tried the default controls?

Did you check if it's actually loading?

I can't seem to find the cause of those messages, probably something to do with the default value being read wrong. It shouldn't affect anything. The DrugItems are pretty much the same as the regular items, since Vehicle Search doesn't communicate with Police Radio just yet.

You're running RPH v0.20, while the newest Ped Search requires v0.21 or v0.22. Here's a version of Ped Search compatible with RPH v0.20, though I would just recommend upgrading RPH to v0.22 as long as it doesn't break your other plugins. PedSearch v1.1.0 (RPH v0.20.641.4077).zip

It's the correct log. By latest do you mean RPH v0.22? If you could delete your RAGEPluginHook.log, start up the game and try using Ped Search again, then post your newly-generated log here, that'd be much appreciated.

I'm not completely sure, but I think it's meters. Those foot pursuits usually carry you a long distance -- you could try ramping up the removal radius (not above the add radius, of course) if you have RetrivalMethod=0.

If you send me your full RAGEPluginHook.log, it'd be appreciated. In a day or two I hope to release a version compiled with RPH v0.22, as the current one is compiled against v0.21, and even though it should work, it seems some people are having problems.

The VehiclePersistence and PedPersistence booleans are basically toggles for that part of the plugin. If one is false, that means the logic to keep that entity persistent is never ran. If you have both VehiclePersistence and VehiclesUnoccupiedOnly set to true, it will only make unoccupied vehicles persistent. The manual flagging of vehicles sounds interesting, if I ever get some free time I'll be sure to implement that. Unfortunately, I don't think I can override LSPDFR's logic like that.

Be sure you have the latest RPH and Vehicle Search.

That's odd, as it's trying to find the method of animation from an old Rage Hook. Double check and make sure you updated Vehicle Search to 2.0.4. I'll try and play around with it once I get some free time.

The latest version should work with RPH v0.22.

Could you send me your RAGEPluginHook.log file?

This. This is an example of a perfect bug report. Unfortunately, the latest version of Ped Search requires v0.22 of the RPH, and you have v0.20. You can download a version that is compatible with RPH v0.20 here: PedSearch v1.1.0 (RPH v0.20.641.4077).zip

For Firefox, I believe you can go to your downloads, right click the download, and unblock it that way. For Chrome, once you download it and Chrome blocks it, go to your downloads (chrome://downloads in the url bar) and click Recover Malicious File. Accept and it'll recover the file.

Sure -- I wasn't aware it didn't work already with v0.22.