A Stranger

Hello everyone,

I just want to say thank you for sticking with us through the biggest site update we’ve ever rolled out. Last year’s launch didn’t go as smoothly as we’d hoped and we know there have been some issues along the way, so we really appreciate your patience and feedback. It’s helped us get to a much stronger place moving forward.
Now that things have stabilised a bit, today we’re launching a bunch of new features and changes that we think you’re going to love.
Discovery: Tag Filters
The whole point of our tag system has always been discovery. You’ve been able to click into tags and explore everything connected to them, but proper filtering on category pages was missing.

That’s now changed.
You can now explore and filter by tags directly on category pages, with the system built to expand much further over time.
To start, we’ve added brand, country, and year filters to vehicle pages, along with a “Made with AI” filter on script pages.

You can now filter by Brand, Country and Year on Vehicle pages.

A small change on the surface, but a big step toward making discovery faster, cleaner, and far more useful across the platform.
Discovery: Site Wide Tag Exclusions
To give you even more control over what you see on LCPDFR.com, we’re introducing account-level, site-wide tag exclusions.
Any files matching the tags you choose to exclude will be hidden across the site — including the downloads portal, download feeds, trending and featured sections, and search results.

The tag filtering controls, now available in Account Settings. In this example, files tagged as outdated are being hidden.


The downloads category page, showing 1 active account tag filter and 34 files hidden as a result of excluding the outdated tag.

Whether you want to hide AI-generated work, certain vehicle types, specific countries, or even particular vehicle years, we hope this system helps you fully customize how you browse content on LCPDFR.com.

Note: We're aware of an issue of going to Account Settings, then navigating to Downloads Filters will not load the tag box correctly and we're working to fix it. Refreshing the page if the tag box doesn't load will workaround this for now.

Site Experience: Thanking Creators
As a thank you to our creators and contributors, we’ll be removing external advertisements for community members who are actively engaging with the community.

The exact criteria may evolve over time, as our community contributes in many different ways. Whether you're helping new members with questions, uploading mods, or simply being an active part of the site, we want to recognize and reward those contributions.

For creators who share their mods with the LCPDFR.com community, ads will be removed once you reach 1,000 verified unique downloads.

For all other members, ads will be removed once you achieve the Sergeant rank (1,000 community points). Our rank system awards points for a variety of community activity, including forum posts, gallery uploads, comments and reviews (+1), giving or receiving reputation (+1), gaining followers (+2), and more.

This change is going live today, though it may take some time after reaching the requirements for the benefit to be applied to your account. Logging in and out if you meet the criteria may help this apply sooner. We also plan to add a way for members to track their progress toward these thresholds in the future.

This is one small way we can give back to the creators and community members who help make the site what it is.

Developer: API
Our old API has started to show its age and wasn’t really built with the growth of the website in mind.

Historically, we’ve had to handle security on LCPDFR.com in some fairly unique ways. While we want to discourage automated traffic, serving an API directly from our main website domain meant we also had to keep certain protections less aggressive than we would’ve liked.

The API has been moved onto its own dedicated infrastructure, allowing us to properly monitor usage, apply separate security procedures, and relax some of the harsher caching behaviour that existed previously.

We’ve also adopted the more standard approach of enforcing API keys across the new API. This allows us to better track usage, apply limits where necessary, and manage access more effectively. API keys are issued in line with our new API Guidelines, which outline acceptable usage and restrictions around commercial use.

There are currently two key types available:
Version Check Keys — designed for embedding into your own plugins, primarily for update and version checking.
Full API Keys — provide broader access to the API, including mass file listings, extended file metadata (such as tags), .NET assembly data, and more.
Full API keys require approval. We may contact you with questions about your intended usage. Both full and limited API keys require an active LCPDFR.com account that has been active for at least one week.

You can request API keys in your Account Settings.

You can see usage limits, documentation and regenerate your key from Account Settings.


With the new downloads listing API, you can list up to 10,000 files at once. Full documentation available in Account Settings with an issued key.

Overall, this new API infrastructure gives us a far more scalable and maintainable foundation moving forward. Separating the API from the main website allows us to improve security, reliability, and performance without impacting the experience of regular community members on LCPDFR.com.

We’ll be deprecating the old API in stages.
Effective today, the old version check API endpoint (checkForUpdates) will no longer be available for newly submitted files. All remaining endpoints, apart from checkForUpdates, will be turned off on 1 June.
We understand that deprecating checkForUpdates may cause issues for some plugins. We plan to phase this out later this year in stages and with planned brownouts and will share more details in the API forum closer to the time.
We’re not stopping there, either.

While these updates are a big step forward for discovery, customization, and the overall site experience, we already know where we want to focus next, on search.

The truth is, we’ve largely outgrown the search system our current software provides. It was never really built for our mod heavy platform with this much content, this many tags, and the kind of discovery features we now want to support properly.

Because of that, search is probably going to involve a lot more custom work from us moving forward. Better relevance, smarter filtering with the new options announced above, and a generally cleaner experience are all things we want to improve over time.

As always, we do appreciate your feedback. We try to guide LCPDFR.com based on what the community wants, alongside the areas where we feel we can improve and do better ourselves.

We’re looking forward to seeing everyone use these new features, and we’re excited to keep improving the platform alongside the community that makes it what it is.

Cyan.

Please find attached the latest SDK for RPH (for game build 3717). It contains the fixed GameControl enum. An excellent comparison for the enum can be found here.


RPH_SDK_3717.zip

Add this to your LSPDFR.ini located in GTAV/LSPDFR: Ambient.DisablePlayerHolsteringActions = true
That disables the new LSPD:FR holster animation. 

Change the plugin timeout threshold from 10000 to 60000 in the RagePluginHook.ini file and change Main.PreloadAllModel in GTAV/LSPDFR -> LSPDFR.ini to false.

LSPDFR & RAGE Plugin Hook Enhanced and Upcoming Site Upgrades
We're excited to share the latest updates on projects bringing LSPDFR and RAGE Plugin Hook to GTA 5 Enhanced Edition alongside refreshing our entire website - with new features, a new design and a more fluid experience.


LSPDFR & RAGE Plugin Hook Enhanced
With the recent release of Grand Theft Auto V Enhanced Edition @LMS has been working on porting RAGE Plugin Hook. While still in its early development stages, RPH is now successfully running on the Enhanced Edition with most of the basic features working, including running small plugins and DX12 rendering. In addition, our biggest LSPDFR update ever is currently in closed-beta testing and we hope to have more news on it soon.

Below are some screenshots of these previously console-only vehicles being spawned through RPH in the Enhanced Edition.
 

 
 
RPH running on the Enhanced Edition.


RPH on Apple Silicon
As part of the port to the Enhanced version and DX12 support, we have streamlined some core systems, now allowing RPH and LSPDFR to run on Apple Silicon. We're still addressing performance issues and visibility concerns before considering a potential future patch.


 
LSPDFR and RAGE Plugin Hook running on a MacBook M4.


Website Platform Update and Invision Community 5
We're in the early stages of migrating from Invision Community 4 to 5, which will transform our entire platform.
This update combines rewrites of Invision Community core features with rewrites of our own software to provide users with a faster and cleaner experience. Community members will enjoy a fresh design and responsive theme that follows your OS dark mode decision. On top of this, substantial effort across the board has been made to fix performance issues.
 
Most of the changes to our new platform are behind the scenes, but the most visible improvement you'll see, apart from the general design change, is the new editor. This new editor comes with many improvements and is easy to use. It also introduces some new features, like Content Boxes, that will make structuring mod download pages a little bit better.

We hope to provide further updates over the coming weeks and months as we prepare this for release.

 
 
In progress development of our new platform using mock data.
 
 
 
The new editor, showcasing the Content Boxes feature.
 

Of course.
Edit the backup.xml or the DefaultRegions or whatever .xml's for UltimateBackup and simply add the cars.

It would certainly boost sales once again for PC. if it works & staff wants to do it, we're all onboard!

Install the latest version of ScripthookVdotnet:

https://github.com/scripthookvdotnet/scripthookvdotnet-nightly/releases/tag/v3.6.0-nightly.114

It was either removed by the author or the staff team.
 
Not much you can do about it except maybe ask the author. 

Hello community,
 
I noticed more and more requests on how to fix the liveries on the newly introduced police vehicles. I wrote the FAQ on it and thought maybe it would be nice in the forums as well.
If it's not appreciated, I fully understand. 🙂

Now, let's get to it.
 
╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼
 
You may have noticed that replace vehicles for the latest police DLC vehicles look inverted, incorrect, total blackout or simply off.
With Patchday mp2023_02 and Patch2023_01 new police vehicles have been introduced to the game. Those vehicles have not only new sirenID and LightID’s, but also a different carvariations.meta.
 
Due to this difference, exchanging them with replacement vehicles can cause them to appear black or have messed up liveries.
The fix for this is rather simple. You can change the sirenID to their default values later on.
 
1. Locate the carvariations.meta for the new police vehicle.
For the police vehicles in Patch2023_01 you can find it in mp2023_02. (Do not replace vehicles in mp2023_02, only edit the carvariations.meta!)
For the police vehicles in Patch2024_01 you can find them in mp2024_01. (Do not replace vehicles in mp2024_01, only edit the carvariations.meta!)
 
2. Make sure Edit Mode is enabled in OpenIV. Right click the carvariations.meta in the given path and press Edit:
 
mods/update/x64/dlcpacks/DLC PACK OF THE VEHICLE/dlc.rpf/common/data
 

 
 
3. Highlight the police vehicle you want to edit. The entire section for a vehicle is referred to as a “slot”. This is what a slot looks like:
The end of the slot is usually identified by the  "“SirenSetting value=”1” ”

4. Once you have highlighted the slot, simply replace it with a vanilla template of a police vehicle by pasting it.
You can get those templates from other cars, or like in this case, from Albo1125’s MODDING DLC. 
 
Once you have replaced the text, press “SAVE” and you’re done.
 

 
 
I hope this helps those who replace the new DLC police vehicles.
Otherwise, enjoy the show. 
 
Thank you and good luck!
 

Hello community,
 
I noticed more and more requests on how to fix the liveries on the newly introduced police vehicles. I wrote the FAQ on it and thought maybe it would be nice in the forums as well.
If it's not appreciated, I fully understand. 🙂

Now, let's get to it.
 
╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼╼
 
You may have noticed that replace vehicles for the latest police DLC vehicles look inverted, incorrect, total blackout or simply off.
With Patchday mp2023_02 and Patch2023_01 new police vehicles have been introduced to the game. Those vehicles have not only new sirenID and LightID’s, but also a different carvariations.meta.
 
Due to this difference, exchanging them with replacement vehicles can cause them to appear black or have messed up liveries.
The fix for this is rather simple. You can change the sirenID to their default values later on.
 
1. Locate the carvariations.meta for the new police vehicle.
For the police vehicles in Patch2023_01 you can find it in mp2023_02. (Do not replace vehicles in mp2023_02, only edit the carvariations.meta!)
For the police vehicles in Patch2024_01 you can find them in mp2024_01. (Do not replace vehicles in mp2024_01, only edit the carvariations.meta!)
 
2. Make sure Edit Mode is enabled in OpenIV. Right click the carvariations.meta in the given path and press Edit:
 
mods/update/x64/dlcpacks/DLC PACK OF THE VEHICLE/dlc.rpf/common/data
 

 
 
3. Highlight the police vehicle you want to edit. The entire section for a vehicle is referred to as a “slot”. This is what a slot looks like:
The end of the slot is usually identified by the  "“SirenSetting value=”1” ”

4. Once you have highlighted the slot, simply replace it with a vanilla template of a police vehicle by pasting it.
You can get those templates from other cars, or like in this case, from Albo1125’s MODDING DLC. 
 
Once you have replaced the text, press “SAVE” and you’re done.
 

 
 
I hope this helps those who replace the new DLC police vehicles.
Otherwise, enjoy the show. 
 
Thank you and good luck!
 

Install the latest version of ScripthookVdotnet:

https://github.com/scripthookvdotnet/scripthookvdotnet-nightly/releases/tag/v3.6.0-nightly.114

We need a PC version of the game first. 

Could be a vehicles.meta issue.
 
1. Locate and open the vehicles.meta in:      mods/update/update.rpf/common/data/levels/gta5 -> Right click -> Edit.
2. Search for the ambulance slot.
3. Scroll down to its <FLAGS> section.
4. Make sure it has this:

FLAG_EXTRAS_ALL
 

Delete startup.rphs in your GTAV folder. 

Do you have StopThePed?

If so, please disable the RealisticWeaponSystem ingame with "G" or in the StopThePed.ini.

Rename it to mods. You have your mods folder disabled. That is why nothing is loading.

They are numerics, they stand for keys. 

https://docs.microsoft.com/en-us/dotnet/api/system.windows.forms.keys?redirectedfrom=MSDN&view=netframework-4.8

Extract them as a .png (sort by size) and use f.ex Paint to scale them to a lower resolution. 

To 
 
To add to this and @Mrsuperx13's incredibly informative response; the SlimDX issue is a system-specific error.
Meaning that yes; it's an exception caused in RPH by your system.
 
The Antivirus scheme + the reinstallation of DX and system specific drivers has always seemed to work best.
It's not RPH, LSPD:FR or your mods. It's your system. And that is why it's so hard to diagnose. 
Everyone's system is different.
 
Therefor, please retry the steps in the RPH FAQ like mentioned above. 
As said all the way back in 2020:

To 
 
To add to this and @Mrsuperx13's incredibly informative response; the SlimDX issue is a system-specific error.
Meaning that yes; it's an exception caused in RPH by your system.
 
The Antivirus scheme + the reinstallation of DX and system specific drivers has always seemed to work best.
It's not RPH, LSPD:FR or your mods. It's your system. And that is why it's so hard to diagnose. 
Everyone's system is different.
 
Therefor, please retry the steps in the RPH FAQ like mentioned above. 
As said all the way back in 2020:

If you installed mod files in the mods folder, like has been recommended for years now, this is literally impossible.
1. (I know it was tongue in cheek but) Rage stands for Rockstar.Advanced.Game.Engine ("plugin hook" is pretty self explanatory) the game engine that Rockstar created and that runs GTA.
2. It is no one in the community's fault that Rockstar are completely anti-modding and have constantly tried to shutdown mod creators and mod access at every opportunity they can. 
3. In that regard it makes sense why GTA V is worse than GTA IV - Rockstar have gotten more advanced and more anti-mod.
4. Everything we have in terms of modding Rockstar games is because amazing talented people have found smart workarounds to all the roadblocks Rockstar have put in place. 
 
This community is filled with amazing people who have dedicated so much time and effort for free to help ungrateful people like you time and time again.
Do you know why any of those troubleshooting steps are known? Because people like A Stranger (Head of the RPH discord and creator of the RPH faq(which has every known possible solution to the SlimDX error for example)), and many others, have spent years of their lives, thousands of hours of their free time, dedicated to helping people and finding solutions to the problems that come along with modding a game that does not want to be modded. 
 
I'm sure it's frustrating to try and solve such an annoying issue when you just wanna play the game. But don't take it out on the people who are the ones that are literally trying to help and have laid the groundwork for every troubleshooting step you have tried so far for this issue and every other known issue. 
 
In conclusion double check the RPH FAQ double check every step as everything known about that error is documented there.
 
P.s. when dealing with problems it's always good to be specific - For GTA V it's called LSDPFR not LCPDFR

This is simply not true. 
SHV and ELS are 100% stable. The only time they may cause crashes is through user error or windows interfering with them. 
Furthermore if you had an issue with ELS... That would reflect on ELS not on SHV.

And added the exception? Re-installing does nothing if you didn't perform the primary function for re-installing.
 
Sounds like an issue with an ELS xml and not ScriptHookV. Again, mine works perfectly fine. Never had an issue to this day.
 
I consulted with someone on this and they stated that for most cases involved "System.IO.IOException" in the crash message, first thing worth trying is anti-virus exceptions.

But I digress, simply try my solution and give us the results of the test.

That is incorrect. LSPDFR and SHV are stable as I am able to install them right now and they work just fine.
 
I appreciate you ignoring my advice when I went out of the way to assist you and get your game working.
 
Then why make a post about this? If I was in your shoes, I would be taking my advice and trying what is offered to me. I want your game to work just as much as you do.