Lennyy

Thanks Cyan for the updates 👍

IT thankfully started working again for some reason

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.

Does this work better: http://www.dev-c.com/files/ScriptHookV_3788.0_1013.34.zip
 

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

Please post the RagePluginHook.log which can be found in the main folder.

Vincentsgm had this in development but haven't heard anything about it in a year or two.

it worked! thanks!

AI Fuel is causing a crash.
Update:
Attempted crime callouts
Compulite
JM callouts remastered
MegaphoneUI
QwanedCallouts
Remove:
Arrest Manager
Assorted callouts
Police smart radio

Vincentsgm had this in development but haven't heard anything about it in a year or two.

Vincentsgm had this in development but haven't heard anything about it in a year or two.

Vincentsgm had this in development but haven't heard anything about it in a year or two.

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.

Stop the ped seemed to have caused this issue, I've switched over to policing redefined.

No worries!

Hi! Maybe this helps you: 


To my knowledge this is still up to date.

 
 

Thanks for taking the time and effort to supply the forums with a guide like this! I've moved it to a more fitting subforum :).

Creating custom sirens for GTA 5 can be tedious, but with the right workflow, you can get perfectly looping, loud, and high-quality tones in-game. This guide covers everything from sourcing the audio to editing loops, maximizing volume, importing via OpenIV, and making it work for FiveM.

Prerequisites & Golden Rules

Tools Required:
Audacity (for audio editing)
OpenIV (for GTA 5 archive modding)
ArchiveFix (only required if you are porting this to FiveM)

Golden Rule: Always create backups of your game files and strictly use the mods folder in OpenIV. Make sure Edit Mode is clicked ON in OpenIV before starting.
Organization: Create a dedicated project folder on your PC. Keep your original downloaded videos/audio separated from your edited files and final game-ready exports.


Phase 1: Sourcing the Perfect Audio

The foundation of a great siren is a clean source file.

Find Clean Audio: Search YouTube (or other sources) for clips of the siren you want. Look for videos with the absolute minimum amount of background noise.
Avoid the Doppler Effect: Find a clip where the emergency vehicle is stationary or moving very slowly. The Doppler effect alters both the pitch and speed of the sound as the vehicle passes, which is incredibly difficult to fix later.
Download: Use an audio downloader website (like NoTube) to rip the audio from the video.


Phase 2: Audacity - Creating the Perfect Loop
This is the most meticulous part of the process. You want the siren to loop seamlessly without any clicking or popping.
Isolate the Tone: Right click on your downloaded sound and open with Audacity, go to Mix>Resample>Mix Stereo Down to Mono. Find the cleanest single cycle of the siren.
Trim the Fat: Click and drag to highlight the section you want to keep. Copy, click on an empty area down and paste it there and delete the old one by selecting and pressing Backspace.
The Zero-Crossing Method (Fixing Pops): If the start and end of your audio clip don't align perfectly, you will hear a "pop" every time it loops.
Zoom all the way into the audio track usingCtrl + Mouse Wheel until you can see the individual dots on the waveform line.
Let Audacity do the hard work for you: Highlight your clip and press Z on your keyboard (or go to Select > At Zero Crossings). This snaps your selection edges perfectly to the horizontal center line (zero amplitude).
Test the Loop: Use Shift + Space to play the selection in a continuous loop.
Save Your Project: Go to File > Save Project > Save Project. The hardest part is done, lock in this progress before altering the volume.


Phase 3: Audacity - The "Flat Volume" Method

To ensure your siren sounds consistently loud and powerful in-game without volume fluctuations, flatten its dynamic range.
1. Compression and Limiting Highlight your audio, then navigate to Effect > Volume and Compression > Compressor
Threshold: -20 dB to -25 dB
Make Up Target: 0 dB
Knee Width: 0 dB
Ratio: 10.1
Lookahead: 1.0 ms
Attack/Release: 0.1 ms
2. Forced Amplification (Optional) If it still needs more punch, force it right to the edge of clipping:
Go to Effect > Volume and Compression > Amplify...
Check the box for "Allow clipping" and increase the New Peak Amplitude by a few dB.
3. Export the File: When you are done, go to File > Export Audio... * Format: WAV (Microsoft)
Encoding: Signed 16-bit PCM 32000hz
Name the file exactly as the siren you intend to replace (look into the box at the end of this guide to see the siren names).


Phase 4: OpenIV - Injecting the Audio (vehicles.awc)

Now you need to get your new .wav file into the game's audio archive.
Locate the File: In OpenIV, navigate to mods/x64/audio/sfx/RESIDENT.rpf.
Export to openFormats: Scroll down to find vehicles.awc. Right-click on it and select Export to openFormats (.oac). Choose a location on your desktop.
Replace the Audio: Go to your desktop. You will now see a file named vehicles.oac and a folder paired with it named vehicles. Open that vehicles folder. Find the original siren .wav file, delete it, and drag in your new custom .wav file (ensure it has the exact same name as the one you deleted).
Import Back to OpenIV: Go back to OpenIV. Either Right-click in empty space and select Import openFormats, or simply drag and drop the vehicles.oac file directly into the OpenIV window. It will automatically recompile the .awc file with your new siren inside.
Tip: Keep your loops short! GTA 5 has a strict file size limit for the vehicles.awc archive. If you exceed it, your game will crash or audio will mute. If you need to save space, download "dead air" (silent) audio files to replace obscure, unused vehicle sounds in the archive.


Phase 5: FiveM Specific Step (ArchiveFix)
If you are only playing Single Player LCPDFR, skip this step.
FiveM requires custom .rpf files to be encrypted properly, otherwise the server will crash or reject the files.
After you have successfully imported your .oac back into OpenIV, close OpenIV.
Locate the physical RESIDENT.rpf file on your computer (the one you just modified inside your mods/x64/audio/sfx/ folder).
Drag and drop the entire RESIDENT.rpf file directly onto your ArchiveFix.exe application.
A command prompt window will briefly pop up to confirm it has been encrypted/fixed. Your file is now ready to be streamed to your FiveM server.


[TheHC09] ELS Siren Strings Reference
After extensive research, I have finally found the siren strings for ELS, and all but two siren tones are now working in-game!
They seem to correspond to the OpenIV assigned names, but they have the beginning part of the string added. These were all found by me personally through research and experimenting, so you're welcome (also would appreciate this being a pinned topic for others to find). From what I gather, the string is basically referring to the location of the siren file in the game's archive ('RESIDENT' being the RESIDENT.rpf and 'VEHICLES' being vehicles.awc, followed by the siren name).

LSPD Main Police Siren:

"VEHICLES_HORNS_SIREN_1" - Police Primary (Note: "RESIDENT_VEHICLES_SIREN_PA20A_WAIL" doesn't work for some reason)

"VEHICLES_HORNS_SIREN_2" - Police Secondary (Note: "RESIDENT_VEHICLES_SIREN_2" doesn't work for some reason)

Firetruck Siren:

"RESIDENT_VEHICLES_SIREN_FIRETRUCK_WAIL_01" - Firetruck Primary
"RESIDENT_VEHICLES_SIREN_FIRETRUCK_QUICK_01" - Firetruck Secondary
Police Bike Siren:
"RESIDENT_VEHICLES_SIREN_WAIL_03" - Police Bike Primary

"RESIDENT_VEHICLES_SIREN_QUICK_03" - Police Bike Secondary

FIB Siren:

"RESIDENT_VEHICLES_SIREN_WAIL_02" - FIB Primary

"RESIDENT_VEHICLES_SIREN_QUICK_02" - FIB Secondary

Ambulance Siren:

"RESIDENT_VEHICLES_SIREN_WAIL_01" - Ambulance Primary

"RESIDENT_VEHICLES_SIREN_QUICK_01" - Ambulance Secondary

Siren Warning/Priority Tones:

"VEHICLES_HORNS_POLICE_WARNING" - Police Warning (Note: "RESIDENT_VEHICLES_POLICE_WARNING" doesn't work)

"VEHICLES_HORNS_AMBULANCE_WARNING" - Ambulance Warning (Note: "RESIDENT_VEHICLES_AMBULANCE_WARNING" doesn't work)

Siren Horns:

"SIRENS_AIRHORN" - Airhorn (Note: "RESIDENT_VEHICLES_AIRHORN_EQD" doesn't work)

"VEHICLES_HORNS_FIRETRUCK_WARNING" - Firetruck Horn (Note: "RESIDENT_VEHICLES_FIRE_TRUCK_HORN" doesn't work)
[TastyFlavour] Update: Sheriff (Granger) Sirens Fix
While the standard Granger strings (RESIDENT_VEHICLES_SIREN_WAIL_04 and QUICK_04) do not work for some reason, I have found the Granger Sirens that DO work correctly with ELS:
Granger Wail: sirens_slow_dir4
Granger Yelp: fast_9oghrv1

[Nazdravi412] Siren file names
Airhorn
AIRHORN_EQD - Generic Bullhorn
 
Police Bike
SIREN_WAIL_03 - PoliceB Main
SIREN_QUICK_03 - PoliceB Secondary
 
FIB
SIREN_WAIL_02 - FIB Primary
SIREN_QUICK_02 - FIB Secondary
 
Police
SIREN_PA20A_WAIL - Police Primary
SIREN_2 - Police Secondary
POLICE_WARNING     - Police Warning

Sheriff Granger
SIREN_WAIL_03 - Sheriff Granger Primary
SIREN_QUICK_03 - Sheriff Granger Secondary
  
Ambulance
SIREN_WAIL_01 - Ambulance Primary
SIREN_QUICK_01 - Ambulance Secondary
AMBULANCE_WARNING - Ambulance Warning

Fire Trucks
FIRE_TRUCK_HORN - Fire Horn
SIREN_FIRETRUCK_WAIL_01 - Fire Primary
SIREN_FIRETRUCK_QUICK_01 - Fire Secondary

I am having the same issue with the V menu. Could it be that the author simply hardcoded that button and forgot to remove it?

Worked for me: 

Could you possibly attach a screenshot of your issue? I'm having trouble imagining whats being wrong with your game.

I haven't really got an idea what the issue outlined in your RPH log may mean, but why don't you try to uninstall and reinstall the entire plugin with all its files? Also worth uninstalling and reinstalling the speech engine for your language as outlined in Opus's tutorial video on YouTube.

This is being outlined in the ELS user guide as seen below:

 

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

No problem! I never heard of that plugin but glad you found out which one caused your „issue“.

Thank you, it really helped.

Your custom regions file is faulty. "An item with the same key has already been added" means you have a zone twice in two different regions/units. A zone is something like "AIRP" for Los Santos International Airport or "ROCKF" for Rockford Hills.