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.

Siren Mastury with ELS cars

Featured Replies

I installed all ELS cars correctly. I have installed a second set of els cars since the first ones did not work. Not sure if it was me installing them incorrect but then I noticed none of the els cars support the siren mastery? I see streamers use siren mastery with installed ELS cars so what am I missing? It works for the default gta v cars no problem.

Here are two attached pictures showing what I mean. FBI2 tahoe shows default car working with siren mastery. FBI1 shows siren mastery not working.

 

let me know what I did not change inorder to use ELS cars with siren mastery thanks!

Capture.PNG2.PNG

Capture.PNG

Edited by Officer Omega

  • Author

I moved it from the pack_default folder into the ELS main folder and now it shows up. However the lights of the car does not show. I can hear the sound of the els mod but cannot see the lights when I activate the sirens.

 

let me explain this carefully as this is confusing even for myself. When I place the car xml into the ELS folder it works. Except the lights when the siren is activated. When I place the xml files in the pack_default folder inside the ELS folder it no longer works at all. It just goes to the default lspdfr sirens like pressing J 3 times or pressing G to activate sirens. The els ini file detects it inside the pack default folder but not if it is in the ELS main folder which is very confusing.

 

Here is ELS log file with the xml files inside pack_default. If I place the xml files in the ELS main folder the ELS log says cannot find els xml files because it looks for it inside the pack_default folder.

==================================================
        LUXART SYSTEMS PROCESS LOG (V-ASI)       
==================================================
MOD ELS.asi
NAM Emergency Lighting System V
VER [ 1.05 ]
--------------------------------------------------
 
<AHOOK> Attempting to initialize AdvancedHookV by LMS.
 (OK) AdvancedHookV.dll file found and successfully initialized.
<FILEG> Collecting information from ELS.ini.
 (OK) Main configuration data successfully collected.
<VCONT> Attempting to open VCF container at: [ .//ELS//pack_default ].
 (OK) VCF container found, scanning for files.
<FILEV> Found file: [ fbi.xml ].
<FILEV> Verifying vehicle model name [ fbi ].
 (OK) Is valid vehicle model, assigned VMID [ 0 ].
      Parsing file. *A crash before all clear indicates faulty VCF.*
      VCF Description: police2
      VCF Author: Luxart
   (OK) Collected data from: 'ADMIN'.
   (OK) Collected data from: 'INTERFACE'.
   (OK) Collected data from: 'EOVERRIDE'.
   (OK) Collected data from: 'MISC'.
   (OK) Collected data from: 'CRUISE'.
   (OK) Collected data from: 'ACORONAS'.
   (OK) Collected data from: 'SOUNDS'.
   (OK) Collected data from: 'WRNL'.
   (OK) Collected data from: 'PRML'.
   (OK) Collected data from: 'SECL'.
   (OK) ALL CLEAR -- Configuration file processed.
<FILEV> Found file: [ POLICE.xml ].
<FILEV> Verifying vehicle model name [ POLICE ].
 (OK) Is valid vehicle model, assigned VMID [ 1 ].
      Parsing file. *A crash before all clear indicates faulty VCF.*
      VCF Description: Sample VCF
      VCF Author: Luxart
   (OK) Collected data from: 'ADMIN'.
   (OK) Collected data from: 'INTERFACE'.
   (OK) Collected data from: 'EOVERRIDE'.
   (OK) Collected data from: 'MISC'.
   (OK) Collected data from: 'CRUISE'.
   (OK) Collected data from: 'ACORONAS'.
   (OK) Collected data from: 'SOUNDS'.
   (OK) Collected data from: 'WRNL'.
   (OK) Collected data from: 'PRML'.
   (OK) Collected data from: 'SECL'.
   (OK) ALL CLEAR -- Configuration file processed.
<FILEV> Found file: [ police2.xml ].
<FILEV> Verifying vehicle model name [ police2 ].
 (OK) Is valid vehicle model, assigned VMID [ 2 ].
      Parsing file. *A crash before all clear indicates faulty VCF.*
      VCF Description: 15Charger_Whelen Liberty
      VCF Author: Luxart/J.J Dawkins
   (OK) Collected data from: 'ADMIN'.
   (OK) Collected data from: 'INTERFACE'.
   (OK) Collected data from: 'EOVERRIDE'.
   (OK) Collected data from: 'MISC'.
   (OK) Collected data from: 'CRUISE'.
   (OK) Collected data from: 'ACORONAS'.
   (OK) Collected data from: 'SOUNDS'.
   (OK) Collected data from: 'WRNL'.
   (OK) Collected data from: 'PRML'.
   (OK) Collected data from: 'SECL'.
   (OK) ALL CLEAR -- Configuration file processed.
<FILEV> Found file: [ police3.xml ].
<FILEV> Verifying vehicle model name [ police3 ].
 (OK) Is valid vehicle model, assigned VMID [ 3 ].
      Parsing file. *A crash before all clear indicates faulty VCF.*
      VCF Description: 16Taurus__Whelen Liberty
      VCF Author: Luxart/J.J Dawkins
   (OK) Collected data from: 'ADMIN'.
   (OK) Collected data from: 'INTERFACE'.
   (OK) Collected data from: 'EOVERRIDE'.
   (OK) Collected data from: 'MISC'.
   (OK) Collected data from: 'CRUISE'.
   (OK) Collected data from: 'ACORONAS'.
   (OK) Collected data from: 'SOUNDS'.
   (OK) Collected data from: 'WRNL'.
   (OK) Collected data from: 'PRML'.
   (OK) Collected data from: 'SECL'.
   (OK) ALL CLEAR -- Configuration file processed.
<FILEV> Vehicle information retrieved. Loaded [ 4 ] ELS-enabled model(s).
 

Capture.PNG3.PNG

Capture.PNG4.PNG

Capture.PNG5.PNG

Edited by Officer Omega

  • Author

so I watched a video saying the els cars that I put in the vcf folder are not activating because they are acting as extras rather than ingame gta v cars. I just need to find out how to fix that

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

Recently Browsing 0

  • No registered users viewing this page.

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.