Best posts made by a63nt-5m1th

@Reacon
Like this?

ORIGINAL:

---

REDUCED BRIGHTNESS:

I did this by editing the textures in the '.ytd' directly. Obviously this approach only works if you can access the textures & ideally they are not shared with other vehicles/used elsewhere in the game. Apart from that it's a pretty good solution. I haven't found a way of doing it by just using data files (carcols etc).

The basic '.dds' process is:

• Open the '.ytd' in OpenIV

• Export ('Export Selected' (Bottom left)) 'jet_windowsjet_windows_a' & 'jet_windows_a' ('Save as type: DDS File (*.dds)')

• Open them with Photoshop (or some other picture editing software that can (ideally) handle .dds. (.png will work too if not. See 'Note 2:' below))

• For Photoshop you want something like 'Intel® Texture Works Plugin for Photoshop' installed to be able to import/export '.dds' textures correctly

• Reduce the 'Levels' of the images down to ~3>5% of their original (that's what I did in the comparison above but you'll have to experiment to get this just right for the visuals of your game).
  Note: If the software you are using doesn't have a 'Levels' setting then simply reducing the brightness/playing with contrast/darkening the image somehow etc will have a very similar effect.

• In Photoshop it is:

• • 'Image' Tab > 'Adjustments' > 'Levels'
• • or 'Ctrl+L' is the shortcut

You then move the brighter arrow (right one) in the 'Output Levels' section left (or type in the bottom right number box (0>100)) to reduce the overall levels & make the image darker.

• Save the textures (if saving as '.dds' make sure 'Intel® Texture Works (.DDS....' is selected in Photoshop's 'Save'/'Save as...' dialogue).

After that, save the '.dds' textures in the Intel® Texture Works save dialogue as:

• • Texture Type: 'Color + Alpha'
• • Compression: 'BC3 8bpp (Linear)' (also known as 'DXT5')
• • Mip Maps: 'Auto Generate'

Once you have successfully saved/exported the '.dds', go to the OpenIV Texture editor & 'Replace' (Top Right) the original textures & 'Save' (Bottom Right) the '.ytd'.
Check it out in-game

Note 2:
Working with .dds textures is something that pops up in modding games a LOT so it is good to give yourself a working setup for it (if you don't already have one/Photoshop etc) but OpenIV can also export to '.png' by changing the 'Save as type' drop down after selecting 'Export Selected'. You'll find plenty of software that can open & edit a '.png' so it may be a good way to go if you have trouble with '.dds'/don't have Photoshop etc.

@House-Rushton said in Eliminating Omnilight Prop Tags:

Illuminating** Omnilite

Is that the name of them? Did you find them?
I would be very interested in knowing where you got them & exactly what they are called?

Edit: Ah, I think I see what you've done, Title edit? If you edit your original post you can change the title directly

@GEEK
Your pic isn't showing as it resides inside your google account which I cannot access but if I had to guess I reckon what you are looking at is a texture conflict.
If that is the case it means you have two different dashboard textures of the same name in your game. The game doesn't know which one to display & freaks out. You need to find the one you don't want & delete it or replace it with the one you do so they are both identical.

Extra: In 'vehicle.meta' , there is a setting for the dashboard:

        <dashboardType>VDT_NAMEHERE</dashboardType> 

It may help in diagnosing the issue to change it to something else.

Also, you might want to look at the texture relationships ('<txdRelationships>') section for Car A & B in their 'vehicles.meta'. The part that looks like this:

  <txdRelationships>
    <Item>
      <parent>vehshare</parent>
      <child>vehshare_truck</child>
    </Item>
    <Item>
      <parent>vehshare</parent>
      <child>vehicles_comet_interior</child>
    </Item>
    <Item>
      <parent>vehshare</parent>
      <child>vehicles_btype_interior</child>
    </Item>
    <Item>
      <parent>vehshare_truck</parent>
      <child>vehshare_worn</child>
    </Item>
    <Item>
      <parent>vehshare_truck</parent>
      <child>vehshare_army</child>
    </Item>
    <Item>
      <parent>vehshare</parent>
      <child>vehicles_blista2_interior</child>
    </Item>
    <Item>
      <parent>vehshare</parent>
      <child>vehicles_futo_interior</child>
    </Item>  

See if it points you in the right direction? ie If they are using the futo interior textures (for example) go & have a look at it's textures & 'futo.ytd's & make sure all files of the same name contain EXACTLY the same textures/see if the Futo dash works? etc

@_Divine_
Yeah, it's the underslashes in your username causing that.
Usernames with underslashes break functionality on the forums for sure but I also sent a test notification to " @_Divine_ " from a mod comment box so you can see if you get it?
Would be pure if you were missing replies to mod comments too.

@zyankenta
Glad it worked

@Divine
Just so you know there is nothing wrong with VStancer. I only mention it as it highlighted the issue for me on a few cars. The wheels were slightly off axis in the cars to begin with & would jump even further off axis (right wheels further in) if VStancer was enabled.
I opted to use VStancer over the unfinished/incorrectly setup cars as I could notice the wheels were slightly off axis even when VStancer was uninstalled so there was no way I was keeping those vehicles in my collection looking like that once I noticed it.
Nothing can be done about it in VStancer as it is the car model that is broken. The only way to fix it, as mentioned, is in ZModeler unfortunately.

Extra: Do you have issues getting notifications of someone tagging your username? @Divine < Seems to always remove both the underscores from it?
@_Divine_ < Had to add a backslash to it directly after the '@' to get it to turn blue. Like this:

@\_Divine_

If you do find you are missing notifications that^ is probably the reason. You can contact the site for a slight username change if needs be. 'Dark0ne' (<that's a 'zero') is who you need to contact for that

@Andrew-Cooper
The simple answer is Yes, a Laptop is a PC & Yes, you will be able to use it to mod GTA V.

Just make sure any Laptop you buy is within GTA V minimum specs:

Recommended System Requirements:

• OS: Windows 8.1 64 Bit, Windows 8 64 Bit, Windows 7 64 Bit Service Pack 1.
• Processor: Intel Core i5 3470 @ 3.2GHZ (4 CPUs) / AMD X8 FX-8350 @ 4GHZ (8 CPUs)
• Memory: 8GB.
• Video Card: NVIDIA GTX 660 2GB / AMD HD7870 2GB.
• Sound Card: 100% DirectX 10 compatible.
• HDD Space: 65GB.

@zyankenta
Let me know if it works. Also, where exactly is that house? I know I've seen it, just can't find it right now

@_Divine_
Afaik that's an issue with the model itself. You would need to get the author to fix it or use Zmodeler to fix it yourself (if the model is unlocked & allows you to do so).
Are you using VStancer, yeah?
You can always replace that broken car with one that works & still have the rest of your modpack cars so it's hopefully not a total loss

@zyankenta
If it's what I think it is, I hated that fog too.

Try setting:

	<Fog value="0.000000"/>

to zero in the named weathers in the '<WeatherTypes>' section of 'weather.xml':

...\mods\update\update.rpf\common\data\levels\gta5\weather.xml

You'll have to do it for each of the weathers in the part of the file that looks like this:

  </WeatherGpuFx>
  <WeatherTypes>
	<Item>
	<Name>EXTRASUNNY</Name>
	<Sun value="1.0"/>
	<Cloud value="0.150000"/>
	<WindMin value="0.0"/>
	<WindMax value="0.0"/>
	<Rain value="0.000000"/>
	<Wetness value="0.000000"/>
	<Snow value="0.000000"/>
	<SnowMist value="0.000000"/>
	<Fog value="0.000000"/>
    <RippleBumpiness value="0.370000"/>
    <RippleMinBumpiness value="0.250000"/>
    <RippleMaxBumpiness value="0.500000"/>
    <RippleBumpinessWindScale value="0.500000"/>
    <RippleScale value="0.340000"/>
    <RippleSpeed value="20.000000"/>
    <RippleVelocityTransfer value="0.450000"/>
    <OceanBumpiness value="0.150000"/>
    <DeepOceanScale value="0.72000"/>
    <OceanNoiseMinAmplitude value="5.00000"/>
    <OceanWaveAmplitude value="0.860000"/>
    <ShoreWaveAmplitude value="1.800000"/>
    <OceanWaveWindScale value="0.700000"/>
    <ShoreWaveWindScale value="0.700000"/>
    <OceanWaveMinAmplitude value="0.000000"/>
    <ShoreWaveMinAmplitude value="0.200000"/>
    <OceanWaveMaxAmplitude value="0.50000"/>
    <ShoreWaveMaxAmplitude value="1.5000000"/>
    <OceanFoamIntensity value="0.070000"/>
    <OceanFoamScale value="0.050000"/>
    <RippleDisturb value="0.050000"/>
    <Lightning value="false"/>
	<Sandstorm value="false"/>
	<DropSettingName>-</DropSettingName>
	<MistSettingName>-</MistSettingName>
	<GroundSettingName>-</GroundSettingName>
    <TimeCycleFilename>COMMON:/DATA/TIMECYCLE/W_EXTRASUNNY.XML</TimeCycleFilename>
	<CloudSettingsName>CONTRAILSclouds</CloudSettingsName>
  </Item>
  <Item>
	<Name>CLEAR</Name>
    <Sun value="0.8"/>
    <Cloud value="1.000000"/>
	<WindMin value="0.0"/>
	<WindMax value="0.1"/>
	<Rain value="0.000000"/>
	<Wetness value="0.000000"/>
	<Snow value="0.000000"/>
    <SnowMist value="0.000000"/>
	<Fog value="0.000000"/>
    <RippleBumpiness value="0.420000"/>
    <RippleMinBumpiness value="0.250000"/>
    <RippleMaxBumpiness value="0.500000"/>
...

@ABERRATION
Note: Make appropriate backups before trying any of this:

You could Ctrl+F3 'search everywhere' (game & mods folder) in OpenIV & then search for 'vehshare.ytd' & replace everything you find with your one 'vehshare.ytd' of choice.

Just backup all the .rpf archives that contain 'vehshare.ytd' & then it will be very simple to return to what you had before if anything goes wrong/doesn't do anything etc.

It's just that if you replace ALL of the 'vehshare.ytd' in your game (as per above instructions) the game HAS to be taking the textures from at least one of the 'vehshare.ytd's you have replaced.
If it doesn't work after that then my only conclusion would be that either it HAS made the change to the textures but it is hard to notice ingame or alternatively you somehow live in a alternate Universe to me where the laws of cause & effect no longer apply
The game has to take the textures from somewhere so after that maybe try removing/deleting all of the 'vehshare.ytd's from your game & loading up the game after each deletion to see if you notice a crash/changes ingame etc.
You could also make the change a lot more noticable by replacing textures in a 'vehshare.ytd' (make backups of what is important first) with bright pink/graffiti textures etc (anything, just something hard to miss) & see if you notice it then? I say this as years back I had a similar problem where textures in the vehshare.ytd looked vastly different to the vanilla one but once displayed ingame looked VERY similar which caused me to question whether I had done it right?! I had, I just couldn't really see the change easily.
Anyway, try out a few things & let me know how you get on

@Xxkillask8rxX
Here are a few ideas:

• Try downloading through a free vpn/proxy like Zenmate plugin for browsers (Firefox/Chrome etc).

• Temporarily disable Firewall/anti-virus

• Make sure your 'hosts' file (C:\Windows\System32\drivers\etc\hosts) is NOT blocking the ip

Your default 'hosts' file should look like this:

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.
#	127.0.0.1       localhost
#	::1             localhost

Make sure there are NOT a heap of ip addresses & hostnames after that. It will look somewhat like this if there is:

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.
#	127.0.0.1       localhost
#	::1             localhost

0.0.0.0 localhost
0.0.0.0 0-29.com
0.0.0.0 0-2u.com
0.0.0.0 0-days.net
0.0.0.0 0-free-porn-0.com
0.0.0.0 000info.com
0.0.0.0 000webhost.com
0.0.0.0 001.adsenser.cn
0.0.0.0 001.hitgraph.jp
0.0.0.0 002.hitgraph.jp
0.0.0.0 007arcadegames.com
0.0.0.0 007guard.com
0.0.0.0 007software.com
0.0.0.0 008i.com
0.0.0.0 008k.com

In yours it may be '127.0.0.1' instead of '0.0.0.0' at the start of the lines. It's all the same. It's a loopback address which means your computer will refuse to connect to any hostname that is written after the '0.0.0.0' or '127.0.0.1' part of the line.

It may also be that the download site is blocking your ip. You should be able to get around this by using Zenmate or any proxy/vpn etc who's ip address is not on the download sites blocklist.

@JustHelpMeFixMyMods
I can confirm (with my game at least) that missing out the closing statement (the last '</Item>') in a vehicles section in carvariations results in this error on startup:

Nice easy way for you to test if the game is loading a particular carvariations

I got a crash on startup if I made the Faction's carvariation settings look like this:

            <Value value="100" />
          </Item>
        </Probabilities>
      </plateProbabilities>
      <lightSettings value="74" />
      <sirenSettings value="0" />
    </Item>
    <Item>
      <modelName>faction</modelName>
      <colors>
        <Item>
          <indices content="char_array">
            0
            0
            0
            0
          </indices>
          <liveries>
            <Item value="false" />
            <Item value="false" />
            <Item value="false" />
            <Item value="false" />
            <Item value="false" />
            <Item value="false" />
            <Item value="false" />
            <Item value="false" />
          </liveries>
        </Item>
      </colors>
      <kits>
        <Item>0_default_modkit</Item>
      </kits>
      <windowsWithExposedEdges />
      <plateProbabilities>
        <Probabilities>
          <Item>
            <Name>Standard White</Name>
            <Value value="100" />
          </Item>
        </Probabilities>
      </plateProbabilities>
      <lightSettings value="2" />
      <sirenSettings value="0" />

    <Item>
      <modelName>faction2</modelName>
      <colors>
        <Item>
          <indices content="char_array">
            73
            73
            92
            88 

Note: Last '</Item>' after 'Faction' '<sirenSettings value="0" />' removed.

You might test dropping it into here:

...\mods\update\update.rpf\dlc_patch\mplowrider\common\data\carvariations.meta

if you don't get a crash with it in 'dlcpacks' to start with

@JustHelpMeFixMyMods
Just wanted to mention the 'dlc_patch' folder in 'update.rpf':

...\mods\update\update.rpf\dlc_patch

Any files that are in the named subfolders will override any of the same that are in 'dlcpacks'.

Have a look in here:

...\mods\update\update.rpf\dlc_patch\mplowrider\common\data

& make sure there is no carvariations. There is a carcols in there by default but there shouldn't be any carvariations (by default) or if there is one try editing that instead (if it contains any Faction settings).

@sswiftor
Is it not here?:

GTA ROOT FOLDER\x64\audio\sfx\WEAPONS_PLAYER.rpf\lmg_combat.awc

^Sounds like it anyway. There is also a 'ptl_50cal.awc' file in there too although to me that doesn't sound like .50 cal turret.
Note: Be aware most weapon sounds are shared between multiple weapons. Changing one will change the others too.

If not, my second guess would be here (somewhere, but I couldn't hear it):

GTA ROOT FOLDER\x64\audio\sfx\RESIDENT.rpf\weapons.awc

@JustHelpMeFixMyMods
I can confirm my Faction works. ie Suspension, Engine Upgrade, etc all work. So there must be something wrong with your files somewhere (carcols or carvariations most likely. Maybe vehicles.meta).
My data looks like this:

'carvariations.meta' (mplowrider):

    <Item>
      <modelName>faction</modelName>
      <colors>
        <Item>
          <indices content="char_array">
            0
            0
            0
            0
          </indices>
          <liveries>
            <Item value="false" />
            <Item value="false" />
            <Item value="false" />
            <Item value="false" />
            <Item value="false" />
            <Item value="false" />
            <Item value="false" />
            <Item value="false" />
          </liveries>
        </Item>
      </colors>
      <kits>
        <Item>0_default_modkit</Item>
      </kits>
      <windowsWithExposedEdges />
      <plateProbabilities>
        <Probabilities>
          <Item>
            <Name>Standard White</Name>
            <Value value="100" />
          </Item>
        </Probabilities>
      </plateProbabilities>
      <lightSettings value="2" />
      <sirenSettings value="0" />
    </Item>

'0_default_modkit' - 'carcols.ymt' (update.rpf):

    <Item>
      <kitName>0_default_modkit</kitName>
      <id value="0"/>
      <kitType>MKT_STANDARD</kitType>
      <visibleMods/>
      <linkMods/>
      <statMods>
        <Item>
          <identifier/>
          <modifier value="25"/>
          <audioApply value="1.00000000"/>
          <weight value="20"/>
          <type>VMT_ENGINE</type>
        </Item>
        <Item>
          <identifier/>
          <modifier value="50"/>
          <audioApply value="1.00000000"/>
          <weight value="20"/>
          <type>VMT_ENGINE</type>
        </Item>
        <Item>
          <identifier/>
          <modifier value="75"/>
          <audioApply value="1.00000000"/>
          <weight value="20"/>
          <type>VMT_ENGINE</type>
        </Item>
        <Item>
          <identifier/>
          <modifier value="100"/>
          <audioApply value="1.00000000"/>
          <weight value="20"/>
          <type>VMT_ENGINE</type>
        </Item>
        <Item>
          <identifier/>
          <modifier value="25"/>
          <audioApply value="1.00000000"/>
          <weight value="5"/>
          <type>VMT_BRAKES</type>
        </Item>
        <Item>
          <identifier/>
          <modifier value="50"/>
          <audioApply value="1.00000000"/>
          <weight value="5"/>
          <type>VMT_BRAKES</type>
        </Item>
        <Item>
          <identifier/>
          <modifier value="100"/>
          <audioApply value="1.00000000"/>
          <weight value="5"/>
          <type>VMT_BRAKES</type>
        </Item>
        <Item>
          <identifier/>
          <modifier value="25"/>
          <audioApply value="1.00000000"/>
          <weight value="5"/>
          <type>VMT_GEARBOX</type>
        </Item>
        <Item>
          <identifier/>
          <modifier value="50"/>
          <audioApply value="1.00000000"/>
          <weight value="5"/>
          <type>VMT_GEARBOX</type>
        </Item>
        <Item>
          <identifier/>
          <modifier value="100"/>
          <audioApply value="1.00000000"/>
          <weight value="5"/>
          <type>VMT_GEARBOX</type>
        </Item>
        <Item>
          <identifier/>
          <modifier value="20"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_ARMOUR</type>
        </Item>
        <Item>
          <identifier/>
          <modifier value="40"/>
          <audioApply value="1.00000000"/>
          <weight value="10"/>
          <type>VMT_ARMOUR</type>
        </Item>
        <Item>
          <identifier/>
          <modifier value="60"/>
          <audioApply value="1.00000000"/>
          <weight value="20"/>
          <type>VMT_ARMOUR</type>
        </Item>
        <Item>
          <identifier/>
          <modifier value="80"/>
          <audioApply value="1.00000000"/>
          <weight value="30"/>
          <type>VMT_ARMOUR</type>
        </Item>
        <Item>
          <identifier/>
          <modifier value="100"/>
          <audioApply value="1.00000000"/>
          <weight value="40"/>
          <type>VMT_ARMOUR</type>
        </Item>
        <Item>
          <identifier>HORN_TRUCK</identifier>
          <modifier value="1766676233"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>HORN_COP</identifier>
          <modifier value="2904189469"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>HORN_CLOWN</identifier>
          <modifier value="2543206147"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>HORN_MUSICAL_1</identifier>
          <modifier value="1732399718"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>HORN_MUSICAL_2</identifier>
          <modifier value="2046162893"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>HORN_MUSICAL_3</identifier>
          <modifier value="2194999691"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>HORN_MUSICAL_4</identifier>
          <modifier value="2508304100"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>HORN_MUSICAL_5</identifier>
          <modifier value="3707223535"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>HORN_SAD_TROMBONE</identifier>
          <modifier value="632950117"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier/>
          <modifier value="5"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_SUSPENSION</type>
        </Item>
        <Item>
          <identifier/>
          <modifier value="10"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_SUSPENSION</type>
        </Item>
        <Item>
          <identifier/>
          <modifier value="15"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_SUSPENSION</type>
        </Item>
        <Item>
          <identifier/>
          <modifier value="20"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_SUSPENSION</type>
        </Item>
        <Item>
          <identifier>MUSICAL_HORN_BUSINESS_1</identifier>
          <modifier value="3628534289"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>MUSICAL_HORN_BUSINESS_2</identifier>
          <modifier value="3892554122"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>MUSICAL_HORN_BUSINESS_3</identifier>
          <modifier value="4112892878"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>MUSICAL_HORN_BUSINESS_4</identifier>
          <modifier value="116877169"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>MUSICAL_HORN_BUSINESS_5</identifier>
          <modifier value="2684983719"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>MUSICAL_HORN_BUSINESS_6</identifier>
          <modifier value="2982690084"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>MUSICAL_HORN_BUSINESS_7</identifier>
          <modifier value="3203290992"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>DLC_BUSI2_C_MAJOR_NOTES_C0</identifier>
          <modifier value="771284519"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>DLC_BUSI2_C_MAJOR_NOTES_D0</identifier>
          <modifier value="2586621229"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>DLC_BUSI2_C_MAJOR_NOTES_E0</identifier>
          <modifier value="283386134"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>DLC_BUSI2_C_MAJOR_NOTES_F0</identifier>
          <modifier value="3884502400"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>DLC_BUSI2_C_MAJOR_NOTES_G0</identifier>
          <modifier value="265723083"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>DLC_BUSI2_C_MAJOR_NOTES_A0</identifier>
          <modifier value="1746883687"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>DLC_BUSI2_C_MAJOR_NOTES_B0</identifier>
          <modifier value="1919870950"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>DLC_BUSI2_C_MAJOR_NOTES_C1</identifier>
          <modifier value="1085277077"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>HIPSTER_HORN_1</identifier>
          <modifier value="444549672"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>HIPSTER_HORN_2</identifier>
          <modifier value="1603064898"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>HIPSTER_HORN_3</identifier>
          <modifier value="240366033"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>HIPSTER_HORN_4</identifier>
          <modifier value="960137118"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>INDEP_HORN_1</identifier>
          <modifier value="3572144790"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>INDEP_HORN_2</identifier>
          <modifier value="3801396714"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>INDEP_HORN_3</identifier>
          <modifier value="2843657151"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>INDEP_HORN_4</identifier>
          <modifier value="3341811489"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>LUXE_HORN_1</identifier>
          <modifier value="3199657341"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>LUXE_HORN_2</identifier>
          <modifier value="2900378064"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>LUXE_HORN_3</identifier>
          <modifier value="3956195248"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>LUXORY_HORN_1</identifier>
          <modifier value="676333254"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>LUXURY_HORN_2</identifier>
          <modifier value="2099578296"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>LUXURY_HORN_3</identifier>
          <modifier value="1373384483"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>ORGAN_HORN_LOOP_01</identifier>
          <modifier value="2916775806"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>ORGAN_HORN_LOOP_01_PREVIEW</identifier>
          <modifier value="3714706952"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>ORGAN_HORN_LOOP_02</identifier>
          <modifier value="2611860261"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>ORGAN_HORN_LOOP_02_PREVIEW</identifier>
          <modifier value="3206770359"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>LOWRIDER_HORN_1</identifier>
          <modifier value="310529291"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>LOWRIDER_HORN_1_PREVIEW</identifier>
          <modifier value="2965568987"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>LOWRIDER_HORN_2</identifier>
          <modifier value="55291550"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>LOWRIDER_HORN_2_PREVIEW</identifier>
          <modifier value="965054819"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>XM15_HORN_01</identifier>
          <modifier value="55862314"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>XM15_HORN_01_PREVIEW</identifier>
          <modifier value="2156743178"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>XM15_HORN_02</identifier>
          <modifier value="400002352"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>XM15_HORN_02_PREVIEW</identifier>
          <modifier value="897484282"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>XM15_HORN_03</identifier>
          <modifier value="560832604"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
        <Item>
          <identifier>XM15_HORN_03_PREVIEW</identifier>
          <modifier value="314232747"/>
          <audioApply value="1.00000000"/>
          <weight value="0"/>
          <type>VMT_HORN</type>
        </Item>
      </statMods>
      <slotNames/>
      <liveryNames/>
      <livery2Names/>
    </Item>

Maybe compare them to your files & see if anything pops out at you

Be real vigilant when comparing two sets of data. I use Diffchecker to remove any chance of human error. It will highlight differences between two blocks of text & the online version (no install) is free & easy to use.
Have you also tested to see if any other '0_default_modkit' vehicles work correctly? If it was more than just the Faction affected then it might suggest broken '0_default_modkit' settings in carcols.

@JustHelpMeFixMyMods said in Willard Faction (regular) doesn't work with any modkit.:

I went into mplowrider and changed the colors of the faction, and when I spawn it, it still starts with just grey and black which was not one of the options I gave it which means that the game is looking at another carvariations file for information on the faction.

It doesn't necessarily mean the game is using another file. It may be that the Faction is just locked to those colours no matter the carvariation settings. Try messing with some other of the Faction settings in carvariations & see if you can get any kind of reaction out of the game. Even a crash will confirm it is using that file so you're safe to try anything really.

@JustHelpMeFixMyMods
'mplowrider' & 'wov' are the only 2 locations I know of.

By default it doesn't contain any Faction settings but just in case you didn't realise it existed there is a 'carvariations.ymt' here:

..\mods\update\update.rpf\x64\data\carvariations.ymt

& here:

...\mods\x64a.rpf\data\carvariations.ymt

One way to find the issue or even possibly rule out 'carvariations' would be to use Ctrl+F3 in OpenIV & search for 'carvariations'.
Once the search completes select the 'Extract results' drop-down box & select 'Extract all files' & choose somewhere to put them.
Open the folder where you extracted them all & search inside all of the files for 'faction' & see what you find (Agent Ransack can search all of the files very quickly at the same time if needs be )
The major downside with this is if you do find some extra Faction settings somewhere you will have no idea where abouts in the game it actually is (you'll see when you extract & have a look in the folder).
Tip: Compare the filesize in Windows Explorer to the one in the OpenIV Search Results to help you narrow down where the file is in the game if you find any nefarious Faction settings

@Korboisbeast
As a guess, first thing I would try is a modded gameconfig.xml. Choose one that matches the game version (1.0.1365.1 etc) you are on

If that doesn't work, could you give me a bit more info on what process you have used to install car mods?
Are you using the game folder or a 'mods' folder?
Add-on or Replace vehicle?
If add-on, have you added the vehicle's line to 'dlclist.xml'?
If add-on, where are any modded vehicle add-on 'dlc.rpf' placed? (ie folder structure)
& anything else you think may be relevant. The more detailed you are, the more likely people will be to repond to your post with an idea/explanation/instructions etc

@adinhoa
Yeah, I'll create a full 'vehiclemodelsets.meta' tutorial once I figure out all the different parts of the file & exactly what they do

@Guyconfident
Have you added this line:

		<Item>dlcpacks:\EMF\</Item>

to your 'dlclist.xml' here:

...\mods\update\update.rpf\common\data\dlclist.xml

Your 'dlclist.xml' should look somewhat like this afterwards

		<item>dlcpacks:\LA_ROADS\</item>
		<Item>dlcpacks:\addoncars\</Item>
		<Item>dlcpacks:\baba0rum\</Item>
		<Item>dlcpacks:\EMF\</Item>
	</Paths>
</SMandatoryPacksData>

^That is the correct format (ie line placed above the '</Paths>' & '</SMandatoryPacksData>' lines)

After that it's just a matter of putting the replace vehicle's '.ytd' & '.yft' into this folder:

...\mods\update\x64\dlcpacks\EMF\dlc.rpf\x64\vehicles.rpf

so it looks like this:

& then any tuning parts they have into this one:

...\mods\update\x64\dlcpacks\EMF\dlc.rpf\x64\vehicle_mods.rpf

Note: You place just the individual vehicle modifications ('blade_hood_1.yft' etc for example) into the 'vehicle_mods.rpf'. Do NOT put the vehicles '_mods.rpf' (say 'blade_mods.rpf') archive into there. If done correctly you will end up with lots of different vehicle's modifications all in the same folder like this:

The only other thing to look out for is you can't delete the 'vehshare.ytd' in:

...\mods\update\x64\dlcpacks\EMF\dlc.rpf\x64\vehshare.rpf

or the game will crash.

Note: You can save yourself some hassle & ensure that all of the textures in 'vehshare.ytd' display correctly in-game if you make sure all of the 'vehshare.ytd's that you have installed (throughout your entire 'mods' folder. Not just the 'EMF' folder structure) are the same file with the exact same textures in them.
If you have modded 'vehshare.ytd' in the past then all you would do is grab a copy of it & place it here:

...\mods\update\x64\dlcpacks\EMF\dlc.rpf\x64\vehshare.rpf\vehshare.ytd

overwriting the one that comes with the EMF mod.

You can then use Ctrl+F3 in OpenIV to search for 'vehshare.ytd' & make sure they are ALL the same file. If not, overwrite & replace them all with your modded 'vehshare.ytd' of choice.
Be careful as certain mods require their own 'vehshare.ytd' that is different to your prefered modded one. In that case you would want to import any different textures into your modded one (careful not to overwrite any (of the same name) you want to keep) so that it has all of the textures you need for everything. You then replace all the 'vehshare.ytd's in your 'mods' folder structure with your new super 'has everything you need in it' 'vehshare.ytd'.
If you don't do this, it won't break your game, you just run the risk that some things (alloy wheels are a good example) may show up missing their textures/weird colours etc.

@ethannn_
In OpenIV try right-clicking 'carcols.ymt & selecting 'Export to META/XML (.xml)', choose where to extract the file (you should end up with a 'carcols.ymt.xml' file) & then open it with Notepad etc to edit it. If all went well it should be in plain text (ie decrypted) & easy to edit with any text editor.
To import it back into OpenIV just take the 'carcols.ymt.xml' (Note: without changing the file extension. Leave it as '.ymt.xml') & drag & drop it back to it's original location. OpenIV will then convert it automatically to '.ymt'.
Do this each time you export/import the file or you will get the random symbol encrypted mess thing.
Note: OpenIV can open 'carcols.ymt' in plain text all of the time by double-clicking on it etc. You can also edit it directly from within OpenIV by right-clicking & then selecting 'Edit' (Ctrl+Enter). This will open the file in OpenIV & allow you to edit & then save (bottom right). Just be careful with this as you can't easily revert changes (Ctrl+Z etc) as you can with a text editor so watch out for typos etc & make sure you keep a backup of it before each edit.

@adinhoa

Getting there Also managed to get it to spawn with different wheels & just a carbon roof & louvres too (none of the other modifications).
This is just editing the cars in the 'LS_CUSTOMS_MODDED_SP' '<Item type="CAmbientModelSet">' section in 'vehiclemodelsets.meta' (most predictable spawn point I could find). I'm not actually sure which one of the Dominators this orange one is (3rd one I suspect. The one with '<ModKit value="1" />' set but I'm not sure I'll figure that out at a later date)
My 'LS_CUSTOMS_MODDED_SP' AmbientModelSet section looks like this:

    <Item type="CAmbientModelSet">
      <Name>LS_CUSTOMS_MODDED_SP</Name>
      <Models>
        <Item>
          <Name>DOMINATOR</Name>
          <Variations type="CAmbientVehicleModelVariations">
            <BodyColour1 value="71" />
            <BodyColour2 value="62" />
            <BodyColour3 value="18" />
            <BodyColour4 value="20" />
            <WindowTint value="4" />
            <ColourCombination value="-1" />
            <Livery value="-1" />
            <ModKit value="0" />
            <Mods>
              <Item>
                <ModType>VMT_BUMPER_F</ModType>
                <ModIndex value="2" />
              </Item>
              <Item>
                <ModType>VMT_BUMPER_R</ModType>
                <ModIndex value="2" />
              </Item>
              <Item>
                <ModType>VMT_WING_L</ModType>
                <ModIndex value="-1" />
              </Item>
              <Item>
                <ModType>VMT_WING_R</ModType>
                <ModIndex value="-1" />
              </Item>
              <Item>
                <ModType>VMT_EXHAUST</ModType>
                <ModIndex value="2" />
              </Item>
              <Item>
                <ModType>VMT_WHEELS</ModType>
                <ModIndex value="12" />
              </Item>
              <Item>
                <ModType>VMT_SUSPENSION</ModType>
                <ModIndex value="3" />
              </Item>
              <Item>
                <ModType>VMT_BONNET</ModType>
                <ModIndex value="2" />
              </Item>
              <Item>
                <ModType>VMT_SPOILER</ModType>
                <ModIndex value="2" />
              </Item>
              <Item>
                <ModType>VMT_SKIRT</ModType>
                <ModIndex value="2" />
              </Item>
              <Item>
                <ModType>VMT_GRILL</ModType>
                <ModIndex value="2" />
              </Item>
              <Item>
                <ModType>VMT_CHASSIS</ModType>
                <ModIndex value="2" />
              </Item>
              <Item>
                <ModType>VMT_ROOF</ModType>
                <ModIndex value="2" />
              </Item>
            </Mods>
            <Extra1>CantUse</Extra1>
            <Extra2>CantUse</Extra2>
            <Extra3>CantUse</Extra3>
            <Extra4>CantUse</Extra4>
            <Extra5>CantUse</Extra5>
            <Extra6>CantUse</Extra6>
            <Extra7>CantUse</Extra7>
            <Extra8>CantUse</Extra8>
            <Extra9>CantUse</Extra9>
            <Extra10>CantUse</Extra10>
          </Variations>
          <Probability value="1.000000" />
        </Item>
        <Item>
          <Name>DOMINATOR</Name>
          <Variations type="CAmbientVehicleModelVariations">
            <BodyColour1 value="41" />
            <BodyColour2 value="62" />
            <BodyColour3 value="18" />
            <BodyColour4 value="20" />
            <WindowTint value="4" />
            <ColourCombination value="-1" />
            <Livery value="-1" />
            <ModKit value="0" />
            <Mods>
              <Item>
                <ModType>VMT_BUMPER_F</ModType>
                <ModIndex value="0" />
              </Item>
              <Item>
                <ModType>VMT_BUMPER_R</ModType>
                <ModIndex value="0" />
              </Item>
              <Item>
                <ModType>VMT_WING_L</ModType>
                <ModIndex value="-1" />
              </Item>
              <Item>
                <ModType>VMT_WING_R</ModType>
                <ModIndex value="-1" />
              </Item>
              <Item>
                <ModType>VMT_EXHAUST</ModType>
                <ModIndex value="0" />
              </Item>
              <Item>
                <ModType>VMT_WHEELS</ModType>
                <ModIndex value="10" />
              </Item>
              <Item>
                <ModType>VMT_SUSPENSION</ModType>
                <ModIndex value="3" />
              </Item>
              <Item>
                <ModType>VMT_BONNET</ModType>
                <ModIndex value="0" />
              </Item>
              <Item>
                <ModType>VMT_SPOILER</ModType>
                <ModIndex value="0" />
              </Item>
              <Item>
                <ModType>VMT_SKIRT</ModType>
                <ModIndex value="0" />
              </Item>
              <Item>
                <ModType>VMT_GRILL</ModType>
                <ModIndex value="0" />
              </Item>
              <Item>
                <ModType>VMT_CHASSIS</ModType>
                <ModIndex value="0" />
              </Item>
              <Item>
                <ModType>VMT_ROOF</ModType>
                <ModIndex value="0" />
              </Item>
            </Mods>
            <Extra1>CantUse</Extra1>
            <Extra2>CantUse</Extra2>
            <Extra3>CantUse</Extra3>
            <Extra4>CantUse</Extra4>
            <Extra5>CantUse</Extra5>
            <Extra6>CantUse</Extra6>
            <Extra7>CantUse</Extra7>
            <Extra8>CantUse</Extra8>
            <Extra9>CantUse</Extra9>
            <Extra10>CantUse</Extra10>
          </Variations>
          <Probability value="1.000000" />
        </Item>
        <Item>
          <Name>DOMINATOR</Name>
          <Variations type="CAmbientVehicleModelVariations">
            <BodyColour1 value="75" />
            <BodyColour2 value="62" />
            <BodyColour3 value="18" />
            <BodyColour4 value="20" />
            <WindowTint value="4" />
            <ColourCombination value="-1" />
            <Livery value="-1" />
            <ModKit value="1" />
            <Mods>
              <Item>
                <ModType>VMT_BUMPER_F</ModType>
                <ModIndex value="1" />
              </Item>
              <Item>
                <ModType>VMT_BUMPER_R</ModType>
                <ModIndex value="1" />
              </Item>
              <Item>
                <ModType>VMT_WING_L</ModType>
                <ModIndex value="-1" />
              </Item>
              <Item>
                <ModType>VMT_WING_R</ModType>
                <ModIndex value="-1" />
              </Item>
              <Item>
                <ModType>VMT_EXHAUST</ModType>
                <ModIndex value="1" />
              </Item>
              <Item>
                <ModType>VMT_WHEELS</ModType>
                <ModIndex value="13" />
              </Item>
              <Item>
                <ModType>VMT_SUSPENSION</ModType>
                <ModIndex value="3" />
              </Item>
              <Item>
                <ModType>VMT_BONNET</ModType>
                <ModIndex value="0" />
              </Item>
              <Item>
                <ModType>VMT_SPOILER</ModType>
                <ModIndex value="1" />
              </Item>
              <Item>
                <ModType>VMT_SKIRT</ModType>
                <ModIndex value="1" />
              </Item>
              <Item>
                <ModType>VMT_GRILL</ModType>
                <ModIndex value="1" />
              </Item>
              <Item>
                <ModType>VMT_CHASSIS</ModType>
                <ModIndex value="1" />
              </Item>
              <Item>
                <ModType>VMT_ROOF</ModType>
                <ModIndex value="1" />
              </Item>
            </Mods>
            <Extra1>CantUse</Extra1>
            <Extra2>CantUse</Extra2>
            <Extra3>CantUse</Extra3>
            <Extra4>CantUse</Extra4>
            <Extra5>CantUse</Extra5>
            <Extra6>CantUse</Extra6>
            <Extra7>CantUse</Extra7>
            <Extra8>CantUse</Extra8>
            <Extra9>CantUse</Extra9>
            <Extra10>CantUse</Extra10>
          </Variations>
          <Probability value="1.000000" />
        </Item>
      </Models>
    </Item>

which gave me the orange one above fully modded, a dark blue one with different alloys & only a carbon roof & louvres & a dark purple-ish one with different alloys again that looked standard with no mods.

You can see there are also options for extras in there too:

            <Extra1>CantUse</Extra1>
            <Extra2>Either</Extra2>
            <Extra3>CantUse</Extra3>
            <Extra4>CantUse</Extra4>
            <Extra5>CantUse</Extra5>
            <Extra6>CantUse</Extra6>
            <Extra7>CantUse</Extra7>
            <Extra8>CantUse</Extra8>
            <Extra9>CantUse</Extra9>
            <Extra10>CantUse</Extra10>

with the option of 'CantUse' or 'Either' (<that's all I've seen so far & I don't know exactly what they do yet?). Gonna take a while to test everything but I reckon there at least a half decent chance of getting vehicles to spawn (some vehicles at least) with exactly what modifications & extras one wants

@adinhoa
I reckon it should be possible to get cars to spawn in traffic with upgrades. The game does it with certain modded vehicles already. I don't know the finer points of how it works (like can you set specific upgrades or is it a little random? etc) but I reckon 'vehiclemodelsets.meta' has a lot to do with it.
I did a little experiment with 'vehiclemodelsets.meta' last night but I couldn't find any of the cars I edited spawning in traffic so it may be difficult to test the result until I can predict the spawning. I definitely want to know how it works so will be continuing to research & test ideas (although it may be a slow process).
I'll be sure to let you know if I figure anything out though (I'll probably create a tutorial if I suss it out)

@Adr3r
Yeah, that's what I would say. Could have been a conflict between multiple mods too. Some things just don't play nice together. Glad you got it working though
Just take your time when installing mods, check the game still works as you install each one & always, ALWAYS make sure you have a current up-to-date backup of the files/.rpf archives you edit/mod so that recovery is always just one step away. Best of luck

@Adr3r
No probs
I would empty your 'mods' folder completely & check that the game works on it's own before proceeding to install any gameconfigs or add-ons.
Once you've done that, copy over 'update.rpf' to the 'mods\update' folder & install a gameconfig to here:

\mods\update\update.rpf\common\data\gameconfig.xml

If you are on 1.0.1365.1 I would choose one of the first two in that gameconfig list (F7YO's or [YCA] SCRAT's). If you're on an older version of the game try this one (it's what I have installed & it's very stable. I'm on 1.0.1180.2).
Then load the game & check everything is working as it should. It's very unlikely a gameconfig broke your game. I've found the most popular & frequently updated ones to be very stable so I reckon something else must have gone wrong. Sometimes .rpf archives or the files they contain can just corrupt from you simply just editing them. That's why it is so important to have good backup strategy. If you have the hard drive space I advocate backing up the entire .rpf as this means the least amount of work if something goes wrong.
Once you have a custom gameconfig installed & your game is confirmed to still work move on & install this Dodge Coronet Super Bee add-on to your 'mods' folder. It has an .oiv installer which will install the car & add the '<Item>dlcpacks:\bee</Item>' line to your 'dlclist.xml' for you, which will keep the whole process very simple & easy. No need for you to do anything else other than load up the game after & test spawning the car using the name 'bee'.
See how you get on with that & get back to us here if you have any trouble