Skip to content
View in the app

A better way to browse. Learn more.

LCPDFR.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

lektralek

Members
  • Joined

  • Last visited

Reputation Activity

  1. Like
    lektralek got a reaction from aidey1234 in NaturalVision Evolved Crashing LSPDFR   
    Hey all, I installed the older enb 0.275 files replacing the existing enb files from NVE which stopped my game crashing on boot. 
    The normal way of starting lspdfr through launching rage works for me. 
    I found those 2 files (you only need d3d11.dll and d3dcompiler_46e.dll) from this old enb upload here: 
    GTA 5 ENB Series v0.275 with Realistic Graphics Config Mod - GTAinside.com
    I'm on the latest everything including october 2020 NVE release, latest lspdfr and latest rage, and everything seems okay after the older enb is used. 
    I also increased my plugin timeout threshold to 60,000 in rage settings, not sure if this helped. 
     
    Credit to Joey Beckstead in this thread for finding the fix
  2. Like
    lektralek got a reaction from BlueLine Vibes in NaturalVision Evolved Crashing LSPDFR   
    Hey all, I installed the older enb 0.275 files replacing the existing enb files from NVE which stopped my game crashing on boot. 
    The normal way of starting lspdfr through launching rage works for me. 
    I found those 2 files (you only need d3d11.dll and d3dcompiler_46e.dll) from this old enb upload here: 
    GTA 5 ENB Series v0.275 with Realistic Graphics Config Mod - GTAinside.com
    I'm on the latest everything including october 2020 NVE release, latest lspdfr and latest rage, and everything seems okay after the older enb is used. 
    I also increased my plugin timeout threshold to 60,000 in rage settings, not sure if this helped. 
     
    Credit to Joey Beckstead in this thread for finding the fix
  3. Like
    So you downloaded a fancy 2015 Tahoe and installed it in the police3 slot, only to find that it rolls more than your eyes when your boss is talking to you.  Does your Silverado not drive like a truck should? or maybe your '15 Charger doesn't feel right.    There are a lot of options to choose from when deciding which handlingid you want to use for your car.  I've compiled a list of what I use for handling lines, and thus far, all have worked just fine.  For some of them, such as the Silverado and Expedition, someone else might of found a better handling, and if that's the case, please comment below letting me know what you're using and I'll give it a shot. 
     
    Some people like to edit the handling.meta.  This is not a requirement, the handlingid is all you need to touch if you just want the basics.  Handling.meta is there for those who know a bit about modding and want to refine the handling lines to feel realistic.
     
    For those that might be confused on what the handlingid is, it's one of the top lines in the vehicles.meta.
     
    Here's an example:
     
    <handlingId>police3</handlingId>  
    All of these will be for police vehicles, I will not be covering modded civilian cars.  Also note that this topic really only applies to those who have modded their police fleet.
     
     
    Crown Vic
     
    police  
     
    Dodge Charger
     
    If 09-10 version, police2  If 2013+ version, buffalo2  
     
    Ford Taurus, Chevrolet Caprice and Chevrolet Impala 
     
    police3 (this is meant for smaller vehicles, such as the Impala) premier (this is an alternative for smaller vehicles, such as the Impala.  Use this if you don't like the way police3 feels)  fugitive (this is meant for bigger/heavier cars, such as the Taurus) felon (this is an alternative for bigger/heavier cars in case you don't like Fugitive)  
     
    Ford Explorer 
     
    gresley  
     
    Chevrolet Tahoe 
     
    baller baller2  
    Ford Expedition
     
    fbi2  
    Chevrolet Silverado
     
    sandking  
    Dodge Durango
     
    baller  
    Dodge Challenger
     
    gauntlet  
    Ford Mustang
     
    dominator  
    Ford Fusion
     
    tailgater (There is most likely a very better choice out there, I'm just not sure which would work)  
    BMW motorcycle
     
    policeb  
    Ford F-150
     
    sandking  
    Ford F-350
     
    sadler  sandking - may work for this as well, not confirmed  
    Chevrolet Corvette
     
    coquette  
    Chevrolet Avalanche
     
    sandking  
    Chevrolet Camaro
     
    gauntlet  
    Nissan GTR
     
    elegy  
    Land Rover
     
    baller  
    Hearse
     
    romero  
    Dodge Polara
     
    glendale
  4. Like
    lektralek reacted to Lukez3218 in Custom sirens do not work   
    So, when you extract the sound files from the vehicles.awc file using OpenIV, it creates a bunch of .wav files (known sound format, that way we can edit them, .awc is just an archive of sounds) and these files are internally labeled by the game with different names such as POLICE_WARNING for the priority siren or AIRHORN_EQD for the air horn, though because .awc is a archive format proprietary to Rockstar Games, the developers of OpenIV had to come up with their own algorithm to extract it, and so they didn't have access to the internal labels for the files, but only to the corresponding hexadecimal labels. Now they've managed to find out more of these internal labels and thus the files that you extract from the vehicles.awc won't be labeled with their hexadecimal number anymore, but with the actual name used internally by the game. Or at least this is the explanation I came up with using my computer knowledge 🙂
    All of this to say, sirens that you download are still labeled using the hex numbers, so you have to rename them to whatever their internal label is, for example the main wail siren that used to be 0x0D329446.wav, is now SIREN_PA20A_WAIL.wav. Hope it makes more sense.
     
    EDIT: I figured you were probably more interested in a more clear explanation on how to install the sirens lol
    Just take the custom siren you want to install, it should have 4 or 5 files three of which are named SIREN_2.wav, AMBULANCE_WARNING.wav and POLICE_WARNING.wav. The others are most likely 0x0D329446.wav and 0x0EA58C7C.wav. Due to the reasons I explained above, you now have to rename these two respectively to SIREN_PA20A_WAIL.wav and AIRHORN_EQD.wav before copying them into the vehicles folder after you extracted the vehicles.awc file using OpenIV.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.