Lennyy

You’re welcome!

Do you have pedprops limit adjuster installed? Your topic has been moved to GTA V Support, this is not LSPDFR related. Please post in the correct location in the future.

Start GTA V, wait until you spawned as M, T or F. Alt tab out of the game and start RPH. Load LSPDFR as normal. Afterwards attach your RagePluginHook.log file please.

Are you using natural vision?

Generally not a bad idea if you can remember what you installed lately. I’d just remove the mods folder altogether and start a new one. No.

Your topic has been moved to GTA V Support, this is not LSPDFR related. Please post in the correct location in the future.

Apologies. I haven't been notified of your reply here. While I still can't exactly say that causes those blips, you have a few other flaws in your log. First, I'd update GTA V by deleting PlayGTAV.exe and verifying your game files, then update LSPDFR/RPH. The crash in this log is related to a blip as well. Please navigate to your GTAV/lspdfr/lspdfr.ini and set Main.DisableGameBlipHiding = true. Update these plugins: Callout Launcher Interior Callouts MizCallouts MTFO: Move The F*** Over PIS: Persistent Identity System Police Menu Move Realistic Traffic AI from GTAV\Plugins\LSPDFR to GTAV\Plugins\ As for the red blips, do they only show up when you load LSPDFR and go on duty?

LSPDFR-specific plugins (such as the ones mentioned by you) will never show up in RPH's plugins tab as they are loaded via LSPDFR itself.

Your topic has been moved to GTA V Support, this is not LSPDFR related. Please post in the correct location in the future.

You’re welcome!

Your crash is related to Policing Redefined; you seem to have swapped keybinds in its .ini file, however, the letter ù doesn't exist in that context. You can find available keybinds here.

Do you have a link to a video showcasing this? Or did you simply find that screenshot on the internet somewhere? This topic has been moved to the appropriate forum. Please post in the correct location in the future.

I tried with your XML lines and can confirm it's a flaw of Ultimate Backup. What you could do is use the First Responder Medic option, change the ped outfits and the car. They had one driver and one passenger for me. I'm not sure if you need your Fire Chief to actually fight the fire on scene, but maybe you can also add the role="fire" to the XML scheme.

Maybe it's a general flaw with UB and that specific unit. I'll see what happens for me. Can you paste the section of your XML that appears to be faulty?

Your topic has been moved to GTA V Support, this is not LSPDFR related. Please post in the correct location in the future.

Your topic has been moved to GTA V Support, this is not LSPDFR related. Please post in the correct location in the future.

The only way to frequently spawn SAHP patrols is to use the "state patrol" option and customise them the way you like. Doing what you are trying with zones isn't going to be of any success, I'm afraid.

You called for First Responder (Fire) with the zone "LosSantosCity". Can you please double-check the XML lines for that specific unit? By default, the First Responder backup spawns with "FBI2".

Can you go in game and request that backup unit. Afterwards attach your RPH.log file please. You either set the uits up incorrectly or you are requesting the wrong backup option. Your topic has been moved to LSPDFR 0.4 Support. Please post in the correct location in the future.

Try downloading this version of IPT.Common: https://github.com/Immersive-Plugins-Team/IPT.Common/releases/download/1.5/IPT.Common-1.5.0.5.zip Drag and drop the .dll into your main GTA V folder, click yes if prompted to replace.

Your topic has been moved to GTA V Support, this is not LSPDFR related. Please post in the correct location in the future.

Can you also attach your latest RagePluginHook.log and a screenshot of the "issue" you are facing (i.e. your map)?

Your topic has been moved to GTA V Support, this is not LSPDFR related. Please post in the correct location in the future.

SirenSettings limit adjuster ist seit dem letzten Update (3788) nicht funktionsfähig.