EDIT:  I have been doing research and have come to the conclusion that the strings I listed are simply filenames assigned by OpenIV to the different sirens.

Could Albo or some other coder kindly have a go at using the GET_SOUND_ID native function to identify the siren natives in-game? I am getting desperate to get the other sirens working as I really despise having only the LSPD sirens working. From my research, I believe they will be something similar to VEHICLES_HORNS_SIREN_FBI_1 or SIRENS_FBI_1.

 

From research I also believe these siren strings may be found in the file "sounds.dat54.rel" located in x64\audio\audio_rel\config because GTA IV's siren strings were located in a very similar file. However, the names of sounds in there are encrypted with hashes and I have no idea how you would decrypt them. The missing siren strings more than likely start with VEHICLES_HORNS... or SIRENS_...

 

Overall conclusion is that the only way to get these strings is to decrypt the sounds.dat54.rel file or use native sounds functions as mentioned above.

Edited September 2, 20187 yr by TheHC09
Correcting

An update to ELS in general is required honestly, considering the problem with the AI traffic management (suspect AI will lock its steering and drive slowly off, usually into a wall, when you are in pursuit).

Edited May 11, 20187 yr by Pipeline

2 minutes ago, Pipeline said:

An update to ELS in general is required honestly, considering the problem with the AI traffic management (suspect AI will lock its steering and drive slowly off, usually into a wall, when you are in pursuit).

That's to do with the ELS TrafficControl setting and technically is supposed to happen, but could do with tidying up. Turning it off in the ini will stop that problem happening. But agreed, there are other issues that need fixing, most notably to do with the AI, such as the AI never changing siren tones or using airhorn and the AI flash patterns glitching out.

 

I don't understand where LtCaine has gone, apparently he hasn't been heard from in ages. I am grateful for his work but its becoming a bit of a joke now that he hasn't done anything for a year and a half.

Just now, TheHC09 said:

That's to do with the ELS TrafficControl setting and technically is supposed to happen, but could do with tidying up. Turning it off in the ini will stop that problem happening. But agreed, there are other issues that need fixing, most notably to do with the AI, such as the AI never changing siren tones or using airhorn and the AI flash patterns glitching out.

 

I don't understand where LtCaine has gone, apparently he hasn't been heard from in ages. I am grateful for his work but its becoming a bit of a joke now that he hasn't done anything for a year and a half.

Lt. Caine is barely ever heard of, honestly. You get used to it. He releases something and then all goes quiet. Also, I'm aware turning traffic control off in the ini "fixes" the problem, but only in the sense that it goes away and you lose the traffic control features. Which I happen to like very much, barring the bug.

I'm tagging the ELS team in this to make them aware. @GravelRoadCop @Lt.Caine @Lt.Caine2 @Albo1125 @Bxbugs123 @Prophet @PoliceWag

I'm not sure if the account "Lt.Caine2" is legitimate, just to let you know.

Well not a big deal either way.

1 hour ago, Pipeline said:

An update to ELS in general is required honestly,

Exactly, having all these strings is pointless since ELS can't use'em.

 

 

@Lt.Caine has disappeared off the radar since the release of ELS V. I haven't been able to get a hold of him since then. I've heard that he kept active with an online GTA V community ( highspeed gaming) that bxbugs123 was part of, but I don't know if he still maintains his activity with them. 

 

However I do understand that in order to update the ELS V for these new siren hash tags to work is by having @LMS to update his core codes that makes ELS V work as it is. He would need to add the new siren hash tags into his framework and Lt.Caine would have to import/inject the updated framework into ELS V. I could be wrong but this was something Lt.Caine had mentioned to me at one point. 

 

One day he will resurface again and make an update to ELS V, but the question is when. Heck, i don't even know if he's still alive or not. 

I suppose you'll have to resurrect him if that truly is the case... can't go back on "One day he will resurface again and make an update to ELS V"! 😛

 

(Only joking of course... and I certainly hope it isn't actually the case. We would all be very sad if such a talented member of our community was indeed gone.)

I've just tested these strings using some of my own code to avoid any checks that ELS may have built in (although I don't think it has - it wouldn't need an update to be able to utilise any newly known valid sound strings).

 

These strings do not work with the PLAY_SOUND_FROM_ENTITY native and thus cannot be used with ELS. This can further be demonstrated by the fact that all the currently known strings that do work with the native (VEHICLES_HORNS_SIREN_1 etc) do not have a matching filename in OpenIV.

 

I don't know how OpenIV have assigned filenames to these particular siren tones, but it seems like they are definitely not assigned based on the names that the natives themselves use. Whether or not there's a correlation I'm not sure (there seems to be some form of correlation for a select few of the currently known native names and their corresponding OpenIV file names). Further research into the strings the native uses is needed before these alternative tones can be used.

Edited May 12, 20187 yr by Albo1125

ELS should be open source. There could be a system like SoundOff Signal's Blueprint and other cool features if active members could contribute.

8 hours ago, Albo1125 said:

I've just tested these strings using some of my own code to avoid any checks that ELS may have built in (although I don't think it has - it wouldn't need an update to be able to utilise any newly known valid sound strings).

 

These strings do not work with the PLAY_SOUND_FROM_ENTITY native and thus cannot be used with ELS. This can further be demonstrated by the fact that all the currently known strings that do work with the native (VEHICLES_HORNS_SIREN_1 etc) do not have a matching filename in OpenIV.

 

I don't know how OpenIV have assigned filenames to these particular siren tones, but it seems like they are definitely not assigned based on the names that the natives themselves use. Whether or not there's a correlation I'm not sure (there seems to be some form of correlation for a select few of the currently known native names and their corresponding OpenIV file names). Further research into the strings the native uses is needed before these alternative tones can be used.

Try something like "VEHICLES_HORNS_SIREN_04_QUICK" or "SIRENS_SIREN_04_QUICK"

Bump @Albo1125 Have you attempted using "GET_SOUND_ID" in order to identify the siren strings? For example spawn Non-ELS ambulance that uses the ambulance siren and then try to identify its string? I'm not familiar with scripts/natives so sorry if this wouldn't work.

Just wanted to bump this thread and say that currently, ELS has an issue. where the siren will go completely mute after about six minutes, this always happens whenever I have a wanted level for that long, and again, it's only for ELS vehicles, non-els vehicles work just fine. I know it's not likely to happen, but I really hope this mod gets updated someday. 

Bump again @Albo1125 @Pipeline @GravelRoadCop @Giordano

I have been doing research and have come to the conclusion that the strings I listed are simply filenames assigned by OpenIV to the different sirens.

Could Albo or some other coder kindly have a go at using the GET_SOUND_ID native function to identify the siren natives in-game? I am getting desperate to get the other sirens working as I really despise having only the LSPD sirens working. From my research, I believe they will be something similar to VEHICLES_HORNS_SIREN_FBI_1 or VEHICLES_SIRENS_FBI_1. Cheers all.

 

Update: From research I also believe these siren strings may be found in the file "sounds.dat54.rel" located in x64\audio\audio_rel\config because GTA IV's siren strings were located in a very similar file. However, the names of sounds in there are encrypted with hashes and I have no idea how you would decrypt them. The missing siren strings more than likely start with VEHICLES_HORNS... or SIRENS_...

Overall conclusion is that the only way to get these strings is to decrypt the sounds.dat54.rel file or use native sounds functions as mentioned above.

Edited September 2, 20187 yr by TheHC09
Adding update

I personally am not a coder but I hope something can come of this. Thanks for your research.

See update in my post above

@Pipeline @Albo1125 @GravelRoadCop @Giordano I've found the majority of the ELS siren strings and they're working! See post: https://www.lcpdfr.com/forums/topic/86408-i-have-found-the-els-siren-strings-100-working/