Cyan

Yeah...McAfee dislikes literally any program. It has to be one of the worst anti-viruses out there.

Which mod is not working?

NVE should work fine, it should come with a compatibility patch for LSPDFR

As @Lennyy said, GTA V works with LSPDFR in Parallels - it's actually my main development setup on my M4 Max MacBook Pro. There's some extra setup in the LSPDFR FAQ.

I would expect LCPDFR/GTA IV to also work in Parallels, but I've not tested it.

We probably would not promote paid mods or have any sort of partnership program.

Not only does it go against our principals, it opens us up to legal trouble as most paid mods are making money off of the intellectual property of other parties (primary concern being Rockstar themselves, but even companies like Ford or Axon could be more likely to pursue legal action once money is involved).

Real Pursuit AI v1.3 crashes with an unhandled access violation when scanning for active pursuits. The crash occurs when the pursuit scanner attempts to query an invalid or freed entity handle.
Crash Details
Exception Type: EXCEPTION_ACCESS_VIOLATION (0xc0000005)
Exception Address: 0x0000000000000000 (null pointer)
Stack Trace:
RealPursuit.Systems.PursuitScanner.ScanForNewPursuit(Int32 now)
-> GTA.Entity.TryGetMemoryAddress(IntPtr& address)
-> GTA.Entity.get_EntityType()
[CRASH: Attempting to read from address 0x0000000000000000]

Full Call Chain:

Real Pursuit AI Hook:OnGameCrashManaged()
→ SHVDN.NativeMemory.GetEntityAddress(Int32 handle)
→ GTA.Entity.TryGetMemoryAddress(IntPtr& address)
→ GTA.Entity.get_EntityType()
→ RealPursuit.Systems.PursuitScanner.ScanForNewPursuit(Int32 now)
→ RealPursuit.Systems.PursuitScanner.Update(Int32 now)
→ RealPursuit.Core.RealPursuitMain.OnTick()

Root Cause Analysis
Invalid Entity Handle: The pursuit scanner is iterating through entity handles and encounters one that either:
Has been deleted from memory but the handle is still referenced
Was never properly initialized
Points to freed/deallocated memory
Missing Null Check: The ScanForNewPursuit() method doesn't validate the entity handle before calling get_EntityType(), resulting in a memory access violation.
Trigger Conditions:
Occurs during story mode loading/gameplay
Likely triggered when spawning/despawning entities during dynamic pursuit scanning
May occur when multiple entities are being created/destroyed rapidly
System Context at Crash
Game Version: GTA V v1.0.1013.34 (Enhanced Edition)
Windows: Windows 10 Home Single Language (10.0.26200.0)
Active Plugins: LSPD First Response, Policing Redefined, Real Pursuit AI v1.3
Crash Time: 2026-04-14 20:06:06 PM

Reproduction
The crash occurs during story mode gameplay when Real Pursuit AI's pursuit scanner attempts to evaluate entity handles that have been invalidated or deleted.

When you are new to modding, very often.
If you are more advanced, less until never.
Of course it depends how much you change or install.

This is a short list that I'll be trying to keep up to date of issues we are seeing, and how you can resolve them. It's still a work in progress and we'll be adding new information as we go.
I'll seperate each category of issue in a spoiler, and you can click the spoiler to show the issues and fixes in that category.
 
Launching LSPDFR and going on duty
RAGEPluginHook / LSPDFR causes GTA to crash to desktop

LSPDFR takes too long to load and I get a black screen, or RAGEPluginHook stops it from loading (terminated because it caused the game to freeze)

LSPDFR crashes when I load with an 'STATUS_INVALID_PARAMETER_1: Invalid entry point. (Code: 87)' or EasyHook error in my log file (older versions)

LSPDFR crashes when I load/reload with a 'System.IndexOutOfRangeException' in my log file (older versions)

LSPDFR crashes when I go on duty

I can't go on duty with 'ForceDuty' console command and it's the first time I'm playing LSPDFR 0.4

 LSPDFR crashes on start with an SystemAccessViolation in the log and my OS language is set to Turkish (older versions)
 
LSPDFR crashes on start and my log file mentions something to do with a System.ValueTuple

LSPDFR's Pause Menu doesn't work -- only the 'Stats' menu is shown

Character System
 
My police officers don't have badges or holsters/LSPDFR only has one police outfit
 
LSPDFR Sync
 
LSPDFR Character doesn't show on the website

I can't connect to the LSPDFR Sync service

I can sync my character, but activity does not show
 
 
Controls
Problems when using a PS4 Controller
 
 
Other Plugins and Mods
Crashes whilst using LSPDFR/RPH in conjunction to Scripthook V .NET (Event Viewer shows a c00000fd Error)

An LSPDFR update has been released and now my plugins don't work
 
Other Issues
 
The game world starts to disappear when I go on duty or load LSPDFR

Due to an issue detecting the Visual Studio 2015 Redistributable, RPH does not start on arm64 systems/VMs (e.g. Macs with VMware/Parallels)

The RPH console is blank (F4 menu does not display), and I have a 4xxx or 5xxx series NVIDIA card

Status Updates
LSPDFR for Enhanced
We're very excited to announce that LSPDFR Enhanced, after months of development and testing, is now entering the next phase of the development process and is now available to our Insiders. We are deeply grateful to everyone in our staff team and closed testing community for their feedback and support that have brought us to this point.
 
The current build is largely stable, though a handful of bugs remain and we are not yet feature complete with Legacy. Development is advancing quickly, and each new revision brings us closer to a fully polished release.
 
Several community members have asked whether the Legacy edition will continue to receive attention. Both RAGEPluginHook and LSPDFR have been engineered to accommodate the Legacy and Enhanced branches side‑by‑side. With most of the heavy lifting complete, our goal is to roll out updates to both editions in parallel.
 
As soon as we’ve smoothed out the last few wrinkles and made sure everything runs flawlessly, we can’t wait to roll out LSPDFR Enhanced to everyone.
 
The new LCPDFR.com
Work on the redesigned LCPDFR.com is progressing steadily. The site and its companion, RDR2Mods.com, run on the same underlying codebase.
An early version of the community upgrade is already live on RDR2Mods.com, allowing us to gather real‑world feedback, refine new concepts, and further stabilize the platform before bringing the enhancements to LCPDFR.com.
 
 
We thank you all for your patience and continued enthusiasm, and hope to share even more with you soon.

Weird edge-case .zip file which has the path separator incorrect. Should be fixed now - our security service now deals with either case.

It's on the roadmap to bring back.

It's update season! We've released a compatibility update for LSPDFR 0.49 (Build 8564) which adds support for the new version of GTA V (v3028.0).

This build also includes some minor fixes for LSPDFR:
 
Fix possible crash in ProcessFleeingStart
Fix potential null reference when spamming keys and opening the backup menu in certain situations
 

Although this build has been tested before being made available to you, there's always the chance there's issues - please report any issues or bugs with LSPDFR on the new game version, if you find any, on the support forums.  If you do think you've found an issue, please make sure you're on the latest patch, RPH and LSPDFR version and you've tested the issue is not your mods folder needing an update (e.g. your game runs normally without RPH/FR).
 
As always, the new version of the RAGE Plugin Hook which is required for LSPDFR to work on the new GTA V update is included with the new LSPDFR download.  The RAGE Plugin Hook website has not yet been updated, so you should not download the RAGE Plugin Hook from there but instead use the included version with LSPDFR.
 
Please ensure that you now update your game to the latest version of GTA V before playing this new version of LSPDFR 0.4.9, which you can find on the main LSPDFR page.

The problem is with how your OS is configured. If it's your own PC and you set it up yourself there should be no reason for it to be locked. Did you install a cracked windows?

They are organized and sorted with the file name by time and date.
Because you are bored we should change the way the logs are stored? Even though there is already a good system? 😀

i've already made a forum about this in the past, and my question was partially answered, but sometimes i just like looking at my old logs whenever i'm bored. I know that the newest log always generates right below my ragepluginhook app in my GTA V folder, but it would be kind of nice for my logs to be more organized in my log folder.

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

Now

ELS doesn’t work on enhanced.

Generative AI is being used more and more in mod creation, and we believe transparency around its use is important. While AI offers exciting new possibilities, we understand that not everyone wants to engage with AI-made content. We hope that clear disclosure helps everyone make an informed choice before downloading a mod, and makes it easy to filter out AI-made content.

Starting today, we’re rolling out a new AI disclosure system. It allows authors to disclose the extent of their AI usage, and to be specific about which parts of a mod were AI-made or AI-assisted.
The following AI disclosure options are available:

Description
Tick this if your description was generated or rewritten/refined using AI.
We would also like to note: if you use AI to help write your description in any way, please make sure you verify all claims about your mod. We’re seeing an increase in AI-written descriptions that mention features the mod doesn’t actually include, so this is now enforced under our File Guidelines.
Images
Tick this if any images on your mod page were generated or edited/refined using AI.
Mod & Mod Content
Minor: AI helped with small refinements to the mod or its content (for example: using a chatbot/agent for assistance, or generating assets used in the mod).
Moderate: AI contributed more than 50% of the mod’s content (code, images, data, etc.).
Significant: AI created most or all of the mod (for example: full generation). Tick this as well if you wouldn’t have been able to make the mod without AI.

Some light use doesn’t need disclosure — for example, basic autocomplete or bouncing ideas off an AI.

Disclosures will appear below the file description. If you've ticked Mod & Mod Content, you will be asked for a 'Reason'. You should enter more information (why and how AI is being used) in here.
If you select Mod & Mod Content at Moderate or Significant, your file will also be tagged with the “ai” tag. This makes it easier for the community to filter AI-involved mods if they want to, and makes AI usage clear at a glance.

This is now required for new submissions, and we ask that creators also start updating their submissions if they have an AI disclosure to make. We'd like to request that all disclosures are made by the end of February.

We are hoping we do not have to enforce this too broadly, and creators will come forward and be honest about their work. There are ways of detecting AI work in images, description and content and our moderation team will kindly remind you to make a disclosure if they receive a report of AI work that looks valid. If our staff feel that the AI disclosure is inaccurate or incomplete, files may be hidden until we believe they are in compliance. Making inaccurate AI disclosures may also lead to negative reputation by our automated approval systems.

This is a first step toward balancing the new possibilities AI brings with individual preferences and a changing modding landscape.
Thanks for helping us keep things clear and transparent for everyone.

And to support that same goal of clarity and choice, we’ll be sharing more soon about global filtering options for mod discovery. Separately, we’ll also have some news to share shortly regarding the new LCPDFR.com website API.

Generative AI is being used more and more in mod creation, and we believe transparency around its use is important. While AI offers exciting new possibilities, we understand that not everyone wants to engage with AI-made content. We hope that clear disclosure helps everyone make an informed choice before downloading a mod, and makes it easy to filter out AI-made content.

Starting today, we’re rolling out a new AI disclosure system. It allows authors to disclose the extent of their AI usage, and to be specific about which parts of a mod were AI-made or AI-assisted.
The following AI disclosure options are available:

Description
Tick this if your description was generated or rewritten/refined using AI.
We would also like to note: if you use AI to help write your description in any way, please make sure you verify all claims about your mod. We’re seeing an increase in AI-written descriptions that mention features the mod doesn’t actually include, so this is now enforced under our File Guidelines.
Images
Tick this if any images on your mod page were generated or edited/refined using AI.
Mod & Mod Content
Minor: AI helped with small refinements to the mod or its content (for example: using a chatbot/agent for assistance, or generating assets used in the mod).
Moderate: AI contributed more than 50% of the mod’s content (code, images, data, etc.).
Significant: AI created most or all of the mod (for example: full generation). Tick this as well if you wouldn’t have been able to make the mod without AI.

Some light use doesn’t need disclosure — for example, basic autocomplete or bouncing ideas off an AI.

Disclosures will appear below the file description. If you've ticked Mod & Mod Content, you will be asked for a 'Reason'. You should enter more information (why and how AI is being used) in here.
If you select Mod & Mod Content at Moderate or Significant, your file will also be tagged with the “ai” tag. This makes it easier for the community to filter AI-involved mods if they want to, and makes AI usage clear at a glance.

This is now required for new submissions, and we ask that creators also start updating their submissions if they have an AI disclosure to make. We'd like to request that all disclosures are made by the end of February.

We are hoping we do not have to enforce this too broadly, and creators will come forward and be honest about their work. There are ways of detecting AI work in images, description and content and our moderation team will kindly remind you to make a disclosure if they receive a report of AI work that looks valid. If our staff feel that the AI disclosure is inaccurate or incomplete, files may be hidden until we believe they are in compliance. Making inaccurate AI disclosures may also lead to negative reputation by our automated approval systems.

This is a first step toward balancing the new possibilities AI brings with individual preferences and a changing modding landscape.
Thanks for helping us keep things clear and transparent for everyone.

And to support that same goal of clarity and choice, we’ll be sharing more soon about global filtering options for mod discovery. Separately, we’ll also have some news to share shortly regarding the new LCPDFR.com website API.

Generative AI is being used more and more in mod creation, and we believe transparency around its use is important. While AI offers exciting new possibilities, we understand that not everyone wants to engage with AI-made content. We hope that clear disclosure helps everyone make an informed choice before downloading a mod, and makes it easy to filter out AI-made content.

Starting today, we’re rolling out a new AI disclosure system. It allows authors to disclose the extent of their AI usage, and to be specific about which parts of a mod were AI-made or AI-assisted.
The following AI disclosure options are available:

Description
Tick this if your description was generated or rewritten/refined using AI.
We would also like to note: if you use AI to help write your description in any way, please make sure you verify all claims about your mod. We’re seeing an increase in AI-written descriptions that mention features the mod doesn’t actually include, so this is now enforced under our File Guidelines.
Images
Tick this if any images on your mod page were generated or edited/refined using AI.
Mod & Mod Content
Minor: AI helped with small refinements to the mod or its content (for example: using a chatbot/agent for assistance, or generating assets used in the mod).
Moderate: AI contributed more than 50% of the mod’s content (code, images, data, etc.).
Significant: AI created most or all of the mod (for example: full generation). Tick this as well if you wouldn’t have been able to make the mod without AI.

Some light use doesn’t need disclosure — for example, basic autocomplete or bouncing ideas off an AI.

Disclosures will appear below the file description. If you've ticked Mod & Mod Content, you will be asked for a 'Reason'. You should enter more information (why and how AI is being used) in here.
If you select Mod & Mod Content at Moderate or Significant, your file will also be tagged with the “ai” tag. This makes it easier for the community to filter AI-involved mods if they want to, and makes AI usage clear at a glance.

This is now required for new submissions, and we ask that creators also start updating their submissions if they have an AI disclosure to make. We'd like to request that all disclosures are made by the end of February.

We are hoping we do not have to enforce this too broadly, and creators will come forward and be honest about their work. There are ways of detecting AI work in images, description and content and our moderation team will kindly remind you to make a disclosure if they receive a report of AI work that looks valid. If our staff feel that the AI disclosure is inaccurate or incomplete, files may be hidden until we believe they are in compliance. Making inaccurate AI disclosures may also lead to negative reputation by our automated approval systems.

This is a first step toward balancing the new possibilities AI brings with individual preferences and a changing modding landscape.
Thanks for helping us keep things clear and transparent for everyone.

And to support that same goal of clarity and choice, we’ll be sharing more soon about global filtering options for mod discovery. Separately, we’ll also have some news to share shortly regarding the new LCPDFR.com website API.

Did you make sure to move all the Rage files over? Just moving the .exe isn't going to make it work!
 

This topic has been moved to the appropriate forum. Please post in the correct location in the future.

The plugin timeout threshold has nothing to do with letting the game engine prepare on load. RPH will terminate plugins that cause the game to freeze for longer than the timeout threshold. The only reason increasing it is recommended is because, due to how complex LSPDFR is, slower systems will fail to fully load LSPDFR in the default 10,000ms. LSPDFR is likely the only RPH plugin in existence that requires this to be changed, or at least one of very very few.

Generative AI is being used more and more in mod creation, and we believe transparency around its use is important. While AI offers exciting new possibilities, we understand that not everyone wants to engage with AI-made content. We hope that clear disclosure helps everyone make an informed choice before downloading a mod, and makes it easy to filter out AI-made content.

Starting today, we’re rolling out a new AI disclosure system. It allows authors to disclose the extent of their AI usage, and to be specific about which parts of a mod were AI-made or AI-assisted.
The following AI disclosure options are available:

Description
Tick this if your description was generated or rewritten/refined using AI.
We would also like to note: if you use AI to help write your description in any way, please make sure you verify all claims about your mod. We’re seeing an increase in AI-written descriptions that mention features the mod doesn’t actually include, so this is now enforced under our File Guidelines.
Images
Tick this if any images on your mod page were generated or edited/refined using AI.
Mod & Mod Content
Minor: AI helped with small refinements to the mod or its content (for example: using a chatbot/agent for assistance, or generating assets used in the mod).
Moderate: AI contributed more than 50% of the mod’s content (code, images, data, etc.).
Significant: AI created most or all of the mod (for example: full generation). Tick this as well if you wouldn’t have been able to make the mod without AI.

Some light use doesn’t need disclosure — for example, basic autocomplete or bouncing ideas off an AI.

Disclosures will appear below the file description. If you've ticked Mod & Mod Content, you will be asked for a 'Reason'. You should enter more information (why and how AI is being used) in here.
If you select Mod & Mod Content at Moderate or Significant, your file will also be tagged with the “ai” tag. This makes it easier for the community to filter AI-involved mods if they want to, and makes AI usage clear at a glance.

This is now required for new submissions, and we ask that creators also start updating their submissions if they have an AI disclosure to make. We'd like to request that all disclosures are made by the end of February.

We are hoping we do not have to enforce this too broadly, and creators will come forward and be honest about their work. There are ways of detecting AI work in images, description and content and our moderation team will kindly remind you to make a disclosure if they receive a report of AI work that looks valid. If our staff feel that the AI disclosure is inaccurate or incomplete, files may be hidden until we believe they are in compliance. Making inaccurate AI disclosures may also lead to negative reputation by our automated approval systems.

This is a first step toward balancing the new possibilities AI brings with individual preferences and a changing modding landscape.
Thanks for helping us keep things clear and transparent for everyone.

And to support that same goal of clarity and choice, we’ll be sharing more soon about global filtering options for mod discovery. Separately, we’ll also have some news to share shortly regarding the new LCPDFR.com website API.

So, I want to ask this: Is it possible to set the Plugin Timeout Threshold in RPH settings beyond 60,000? I've tried different methods in the .ini file settings, but I can't exceed the default maximum level of RPH. Actually, I think if we could give the game engine a preparation time of 90 or 120 seconds instead of 60 seconds, RPH plugins would run smoothly and without problems.