The title says it all.

 

I just download a fresh new install of GTA V and pumped a bunch of mods in there, one of them being ELS. After Installing some vehicles, I put the VCF's in the Pack_Default folder in the ELS folder. I join the game expecting to see the beautiful lights, but all I get is the default siren (I replaced it with the Fed Sig 2000 LAPD Siren) and the lights not working. No beeps when pressing J, no Lock nor any Lights, except for the Tail and the Front Lights. I looked at the ELS Log and it displays some sort of error.

 

==================================================
        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: [ POLICE.xml ].
<FILEV> Verifying vehicle model name [ POLICE ].
    (OK) Is valid vehicle model, assigned VMID [ 0 ].
         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> Vehicle information retrieved. Loaded [ 1 ] ELS-enabled model(s).

 

What have I tried to fix this Issue?

 

-I reinstalled ELS, and added the VCF's back to the same folder.

-I uninstalled ASI Manager, Closed OpenIV, Reinstalled ASI Manager and rebooted my PC.

-I installed the latest version of ScriptHookV/-ScriptHookDotNet

-I rebooted my PC.

 

Am I desperate for a solution?

 

Yes.

 

I really have NO clue on what is going on with the ELS, it has always worked properly before, and now it suddenly acts up.

 

EDIT: I FOUND OUT I WAS TOO DUMB TO NOT PUT IT INSIDE THE FOLDER BUT OUTSIDE OF THE FOLDER (THE FIRST LAYER OF THE ELS FOLDER)..

 

Howdy.

Edited January 23, 20224 yr by SwitchedDreams
I found the solution.

On 1/23/2022 at 9:35 PM, SwitchedDreams said:

The title says it all.

 

I just download a fresh new install of GTA V and pumped a bunch of mods in there, one of them being ELS. After Installing some vehicles, I put the VCF's in the Pack_Default folder in the ELS folder. I join the game expecting to see the beautiful lights, but all I get is the default siren (I replaced it with the Fed Sig 2000 LAPD Siren) and the lights not working. No beeps when pressing J, no Lock nor any Lights, except for the Tail and the Front Lights. I looked at the ELS Log and it displays some sort of error.

 

==================================================
        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: [ POLICE.xml ].
<FILEV> Verifying vehicle model name [ POLICE ].
    (OK) Is valid vehicle model, assigned VMID [ 0 ].
         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> Vehicle information retrieved. Loaded [ 1 ] ELS-enabled model(s).

 

What have I tried to fix this Issue?

 

-I reinstalled ELS, and added the VCF's back to the same folder.

-I uninstalled ASI Manager, Closed OpenIV, Reinstalled ASI Manager and rebooted my PC.

-I installed the latest version of ScriptHookV/-ScriptHookDotNet

-I rebooted my PC.

 

Am I desperate for a solution?

 

Yes.

 

I really have NO clue on what is going on with the ELS, it has always worked properly before, and now it suddenly acts up.

 

EDIT: I FOUND OUT I WAS TOO DUMB TO NOT PUT IT INSIDE THE FOLDER BUT OUTSIDE OF THE FOLDER (THE FIRST LAYER OF THE ELS FOLDER)..

 

Howdy.

Does it work fine if you use a different vehicle with a different xml file?

I figured out I was too dumb to put it in a wrong section of the folder.

1 hour ago, SwitchedDreams said:

I figured out I was too dumb to put it in a wrong section of the folder.

These thing happens and arw mind blowing especially when you know what to do but still make the mistake.  😅

I fixed that and now another problem pops up. LSPDFR Crashes when I go on duty, I'll make a new post.