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.
The latest updated version of RAGE Plugin Hook, required to play LSPDFR, can be found inside the LSPDFR download. It is not currently available on the RAGE Plugin Hook website.

Vehicles in excess of default GTA model names cannot pull over AI.

Featured Replies

So,

 

I understand how to create an additional agency, and the xml files associated with agencies, outfits etc.

 

Through troubleshooting I've found that any vehicles in excess of the default GTA police vehicles cannot pull any vehicles over - for example:

 

CAN Pull Over AI:

 

Police

Police2

Police3

Sheriff

Sheriff2

 

CANNOT pull over AI (these are not the exact cars, just to give you an idea that anything that isn't a default model name cannot pull over cars)

Police5

Sheriff3

lssheriff

lssheriff2

 

When attempting to pull someone over with an additional car the car simply keeps driving and doesn't stop. The siren doesn't even blip automatically like it does with a normal vehicle.

 

How is LSPDFR deciding what cars are eligible to initiate a traffic stop? I've copied from the default vehicles in my vehicles meta and just changed name/audio name hashes. Not sure why these additional card in excess of the defaults cant pull over anybody.

 

Vehicles.meta file added for context

vehicles.zip

Edited by Singleton

2 hours ago, Singleton said:

So,

 

I understand how to create an additional agency, and the xml files associated with agencies, outfits etc.

 

Through troubleshooting I've found that any vehicles in excess of the default GTA police vehicles cannot pull any vehicles over - for example:

 

CAN Pull Over AI:

 

Police

Police2

Police3

Sheriff

Sheriff2

 

CANNOT pull over AI (these are not the exact cars, just to give you an idea that anything that isn't a default model name cannot pull over cars)

Police5

Sheriff3

lssheriff

lssheriff2

 

When attempting to pull someone over with an additional car the car simply keeps driving and doesn't stop. The siren doesn't even blip automatically like it does with a normal vehicle.

 

How is LSPDFR deciding what cars are eligible to initiate a traffic stop? I've copied from the default vehicles in my vehicles meta and just changed name/audio name hashes. Not sure why these additional card in excess of the defaults cant pull over anybody.

 

Vehicles.meta file added for context

vehicles.zip 75.19 kB · 1 download

 

Im going to take a gander that the additional cars are all ELS vehicles, using provided xml's?

 

If so, the issue is likely a setting that you need to change in those .xml's

 

If they are non-els addon vehicles, I would check the vehicles.meta to ensure they are flagged as emergency vehicles.

  • Author
18 hours ago, zach016 said:

 

A link to the specific post that describes how to fix the issue I was referencing.

Yep familiar with that but don't think that's the case.

 

It's not all vehicles I have issues with, just anything over the default police/sheriff vehicles or those with complete custom names. If it was an ELS issue then presumably all of the cars would be messed up. Nevertheless I did give it a shot and still presenting the same issue. I also isolated by disabling all of my mods, so I think that leaves only two options being either an LSPDFR issue, or a vehicle issue. I'm beginning to think this might be an issue that LSPDFR has to fix...maybe.

39 minutes ago, Singleton said:

Yep familiar with that but don't think that's the case.

 

It's not all vehicles I have issues with, just anything over the default police/sheriff vehicles or those with complete custom names. If it was an ELS issue then presumably all of the cars would be messed up. Nevertheless I did give it a shot and still presenting the same issue. I also isolated by disabling all of my mods, so I think that leaves only two options being either an LSPDFR issue, or a vehicle issue. I'm beginning to think this might be an issue that LSPDFR has to fix...maybe.

 

I would think it's a vehicle issue, more specifically I would suspect an issue in the vehicles.meta. (I've used plenty of custom vehicles with 0.4, with completely custom names, both ELS and non-ELS, so while it doesn't eliminate LSPDFR as a possible cause, it certainly isn't designed in such a way that they cannot work.)

 

My current guess, as mentioned in the previous post, is that the custom vehicles are missing a flag denoting them as law enforcement vehicles. Check the vehicles.meta entries for the bolded flag below.

 

Quote

<flags>FLAG_NO_BOOT FLAG_LAW_ENFORCEMENT FLAG_NO_RESPRAY FLAG_DONT_SPAWN_IN_CARGEN FLAG_EXTRAS_STRONG FLAG_IGNORE_ON_SIDE_CHECK FLAG_AVERAGE_CAR FLAG_HEADLIGHTS_USE_ACTUAL_BONE_POS FLAG_DONT_TIMESLICE_WHEELS</flags>

 

 

Edited by zach016

  • Author
2 minutes ago, zach016 said:

 

I would think it's a vehicle issue, more specifically I would suspect an issue in the vehicles.meta. (I've used plenty of custom vehicles with 0.4, with completely custom names, both ELS and non-ELS, so while it doesn't eliminate LSPDFR as a possible cause, it certainly isn't designed in such a way that they cannot work.)

 

My current guess, as mentioned in the previous post, is that the custom vehicles are missing a flag denoting them as law enforcement vehicles. Check the vehicles.meta entries for the bolded flag below.

 

 

 

Indeed thats what I was leaning towards but I've scoured the vehicles.meta file and I couldn't find anything that jumped out to be correct. I've copied a line from a vehicle I have named "lssheriff" within my meta file (which cannot initiate traffic stops).

 

 <flags>FLAG_HAS_LIVERY FLAG_EXTRAS_REQUIRE FLAG_EXTRAS_STRONG FLAG_LAW_ENFORCEMENT FLAG_EMERGENCY_SERVICE FLAG_NO_RESPRAY FLAG_DONT_SPAWN_IN_CARGEN FLAG_REPORT_CRIME_IF_STANDING_ON FLAG_HAS_INTERIOR_EXTRAS</flags>

1 minute ago, Singleton said:

Indeed thats what I was leaning towards but I've scoured the vehicles.meta file and I couldn't find anything that jumped out to be correct. I've copied a line from a vehicle I have named "lssheriff" within my meta file (which cannot initiate traffic stops).

 

 <flags>FLAG_HAS_LIVERY FLAG_EXTRAS_REQUIRE FLAG_EXTRAS_STRONG FLAG_LAW_ENFORCEMENT FLAG_EMERGENCY_SERVICE FLAG_NO_RESPRAY FLAG_DONT_SPAWN_IN_CARGEN FLAG_REPORT_CRIME_IF_STANDING_ON FLAG_HAS_INTERIOR_EXTRAS</flags>

 

I popped open the vehicles.meta you provided, and checked lssheriff.

 

One thing that stood out to me, was the audiohash line.

Quote

<audioNameHash />

 

While this works fine for the default vehicles, with custom vehicles they end up with no sound whatsoever. Could be a part of the issue.

 

Should look something like:

Quote

<audioNameHash>POLICE</audioNameHash>

 

 

 

 

That issue aside, I presume you created the relevant entries in carvariations.meta as well?

  • Author
Just now, zach016 said:

 

I popped open the vehicles.meta you provided, and checked lssheriff.

 

One thing that stood out to me, was the audiohash line. 

 

While this works fine for the default vehicles, with custom vehicles they end up with no sound whatsoever. Could be a part of the issue.

 

Should look something like:

 

 

 

 

That issue aside, I presume you created the relevant entries in carvariations.meta as well?

Yeah that meta file at the time of posting had the borked audio line, has since been corrected but still cannot initiate traffic stops. Now that you say it I didn't create entries in carvariations that might have something to do with it - correct me if I'm wrong - the carvars file only effects the lighting of the vehicle, no?

6 minutes ago, Singleton said:

Yeah that meta file at the time of posting had the borked audio line, has since been corrected but still cannot initiate traffic stops. Now that you say it I didn't create entries in carvariations that might have something to do with it - correct me if I'm wrong - the carvars file only effects the lighting of the vehicle, no?

 

 

Basic Lighting, Non-ELS emergency lighting, as well as liveries. Don't think ELS vehicles need an entry (spent the last few weeks working with vanilla styled non-ELS vehicles due to texture loss issues, can't recall the way I set the ELS ones up), however non-ELS vehicles certainly do.

Edited by zach016

  • Author
27 minutes ago, zach016 said:

 

 

Basic Lighting, Non-ELS emergency lighting, as well as liveries. Don't think ELS vehicles need an entry (spent the last few weeks working with vanilla styled non-ELS vehicles due to texture loss issues, can't recall the way I set the ELS ones up), however non-ELS vehicles certainly do.

yeah guess I'm screwed. Gonna go back to vanilla I suppose and see if I can replicate 😞

 

This is a support topic.
Only reply here to offer help or assistance to Singleton. Off-topic or "me too" replies will be removed.

Need support yourself? Make a new topic instead.

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.