Hi y'all,

This is going to be a decently lengthy post, so bear with me please.

I like to use vehicles from the two regions I've worked as an LEO/Firefighter in for my game. After a little while, I get bored of one region and switch everything over to the other region. Seeing as one region is in Colorado, which uses red and blue for ALL emergency vehicles, and one is in the South, which uses blue/white for LE, and red/white for fire/ems, it's kind of a pain to switch all those files over. Not only do I have to switch the vehicles (agencies don't use the same fleet) and change out the textures, but I also have to edit the carcols.ymt and the carvar sirensettings to have blue coronas or red coronas for the respective vehicles, etc.

I want to make two separate dlcpacks, which contain the respective files for each region. That way, just by changing the "dlclist.xml," I can pretty much seamlessly transition from one region to the other.

I used the existing dlcpacks and this tutorial to try and make a pack, and I was ALMOST able to successfully load all vehicles! Unfortunately, the replacement vehicles (police, police2, sheriff2, etc) all worked perfectly fine, however, all add-on vehicles (K9, Sheriff3, Police5, etc) did not act as emergency vehicles as they're supposed to. The vehicles would spawn, had audio, and would drive... but the horn was a civilian horn, and the lights and siren were not operational. I double checked the carvariations.meta included in the dlcpack to make sure the required lines were there, and they were... I checked the vehicles.meta and they were listed as emergency vehicles (<vehicleClass>VC_EMERGENCY</vehicleClass>, and plenty of flags that are common for the police vehicles in game).

So I have no idea what I'm missing, and why it would load the vehicles, but not allow the add-ons to act as emergency vehicles.

Please help me figure this out! It's a terrible feeling being so close but so far away! Lol

Thanks a lot!

Edit: Here are the content.xml and setup2.xml I used in the dlcpack. I'm hoping it's just a simple error here somehow.

content.xml

setup2.xml

31 minutes ago, FirstDue Digital said:

snip

Your problem is most likely vehicles.meta

You need to use a police car for the audio hash such as:

<audioNameHash>police2</audioNameHash>

and then in flags make sure you have:

 <flags>FLAG_LAW_ENFORCEMENT FLAG_EMERGENCY_SERVICE</flags>

...in addition to any other flags.

3 minutes ago, Kilyin said:

Your problem is most likely vehicles.meta

You need to use a police car for the audio hash such as:

<audioNameHash>police2</audioNameHash>

and then in flags make sure you have:

 <flags>FLAG_LAW_ENFORCEMENT FLAG_EMERGENCY_SERVICE</flags>

...in addition to any other flags.

I use sheriff2 as the audioNameHash for all of the add-ons, and I have those flags on each vehicle as well.

9 minutes ago, FirstDue Digital said:

I use sheriff2 as the audioNameHash for all of the add-ons, and I have those flags on each vehicle as well.

dunno then other than your setup2.xml looks like it might be missing a line.

Maybe try this:

Spoiler

<?xml version="1.0" encoding="UTF-8"?>
<SSetupData>
  <deviceName>dlc_larimer</deviceName>
  <datFile>content.xml</datFile>
  <timeStamp>28/08/2016 00:00:00</timeStamp>
  <nameHash>larimer</nameHash>
  <contentChangeSetGroups>
    <Item>
      <NameHash>GROUP_STARTUP</NameHash>
      <ContentChangeSets>
        <Item>LARIMER_AUTOGEN</Item>
      </ContentChangeSets>
    </Item>
  </contentChangeSetGroups>
  <type>EXTRACONTENT_COMPAT_PACK</type>
  <order value="999" />  
</SSetupData>

 

What line appears to be missing?

4 minutes ago, FirstDue Digital said:

What line appears to be missing?

the nameHash line.

I'll give that a shot.

 

Also, I forgot to mention earlier, but I also tried to change the wheels on one of the add-on vehicles using a trainer, and instead of the actual names for the wheels, all the choices were named "wheelchoice##." The replacement vehicles still showed proper names. I don't have that issue when the add-on vehicles aren't in the custom dlcpack (when I put them in mpchristmas2).

 

 

Nope, that's not it. Something else must be the root.

Edited September 28, 20169 yr by FirstDue Digital

im in same boat did u figure it out