@Yodah01 said in Vwe Error:

[21-03-2018 20:16:59] [5648] ERROR -> Unable to find XML DOCUMENT with path "common\data\dlclist.xml" in archive "C:\Program Files\Rockstar Games\Grand Theft Auto V\mods\update\update.rpf"

I reckon that^ is where you should look first.

Either your 'dlclist.xml' is missing from:

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

(use OpenIV, go to that location & make sure 'dlclist.xml' exists)

OR

The .oiv installer cannot find it for some reason (not sure why?)

If you don't have a 'dlclist.xml' you can try generating one using Add-On DLCList Generator [.NET] & then installing it (using OpenIV) to:

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

then retry installing the .oiv

Tip (.oiv Manual Install): If you install 7zip you can right-click an '.oiv' file > '7zip' > 'Extract to "Nameofmodhere\ "' which will extract the .oiv to a folder of the mod name.
In that folder will usually be a 'content' folder & an 'assembly.xml'. The 'assembly.xml' tells the installer what to edit (add lines to 'dlclist.xml' etc (if required)) & where to install the files from the extracted 'content' folder into the game.
You can use this to install just about any .oiv manually. Just go into the 'content' folder, take the files & place them (using OpenIV) in the location stated in the 'archive path' line's in 'assembly.xml'

Example (of the 'archive path' lines format):

<archive path="x64c.rpf" createIfNotExist="True" type="RPF7">
  <archive path="levels\gta5\props\vegetation\v_ext_veg.rpf" createIfNotExist="False" type="RPF7">

so for the example above the file 'v_ext_veg.rpf' goes in:

x64c.rpf\levels\gta5\props\vegetation\ ** here **

@player32
Yeah, what I had in my installed gameconfig before starting the tutorial was the same as that too.

In that part of the tutorial as long as your gameconfig looks like this (which is identical to the first code block you posted above but NOT the second).

COPY THIS CODE BELOW & USE IT IN THAT PART OF THE TUT:

<Item>
  <Build>any</Build>
  <Platforms>x64</Platforms>
  <Config type="CGameConfig">
    <Threads>
      <Item key="Update">
        <Priority>PRIO_TIME_CRITICAL</Priority>
      </Item>
      <Item key="ControlMgrUpdateThread">
        <Priority>PRIO_HIGHEST</Priority>
      </Item>
      <Item key="AsyncShapeTestMgr">
        <Priority>PRIO_HIGHEST</Priority>
      </Item>
      <Item key="RageDvdReader">
        <Priority>PRIO_TIME_CRITICAL</Priority>
      </Item>
      <Item key="RecordingThreadDefault">
        <Priority>PRIO_ABOVE_NORMAL</Priority>
      </Item>
      <Item key="ReplayQuantizeThread">
        <Priority>PRIO_BELOW_NORMAL</Priority>
      </Item>
      <Item key="RecordingThreadGameAndObject">
        <Priority>PRIO_ABOVE_NORMAL</Priority>
      </Item>
      <Item key="RageAudioEngineThread">
        <Priority>PRIO_NORMAL</Priority>
      </Item>
      <Item key="RageHddReader">
        <Priority>PRIO_TIME_CRITICAL</Priority>
      </Item>
      <Item key="RmptfxUpdateThread">
        <Priority>PRIO_HIGHEST</Priority>
      </Item>
      <Item key="RecordingThreadPed">
        <Priority>PRIO_ABOVE_NORMAL</Priority>
      </Item>
      <Item key="PathServer">
        <Priority>PRIO_LOWEST</Priority>
      </Item>
      <Item key="RecordingThreadVehicle">
        <Priority>PRIO_ABOVE_NORMAL</Priority>
      </Item>
      <Item key="ResourcePlacementThread">
        <Priority>PRIO_LOWEST</Priority>
      </Item>
      <Item key="RageAudioMixThread">
        <Priority>PRIO_TIME_CRITICAL</Priority>
      </Item>
      <Item key="SaveBlockDataThread">
        <Priority>PRIO_NORMAL</Priority>
      </Item>
      <Item key="RageDvdStreamer">
        <Priority>PRIO_BELOW_NORMAL</Priority>
      </Item>
      <Item key="RageHddStreamer">
        <Priority>PRIO_LOWEST</Priority>
      </Item>
      <Item key="Render">
        <Priority>PRIO_ABOVE_NORMAL</Priority>
      </Item>
      <Item key="NorthAudioUpdate">
        <Priority>PRIO_NORMAL</Priority>
      </Item>
      <Item key="RageNetSend">
        <Priority>PRIO_BELOW_NORMAL</Priority>
      </Item>
      <Item key="RageNetRecv">
        <Priority>PRIO_BELOW_NORMAL</Priority>
      </Item>
      <Item key="RageVoiceChatWorker">
        <Priority>PRIO_BELOW_NORMAL</Priority>
      </Item>
      <Item key="ReplayFileManager">
        <Priority>PRIO_LOWEST</Priority>
      </Item>
    </Threads>
  </Config>
</Item> 

& you can rule that part out as causing any problems
In that part of the tutorial I didn't copy & paste the information I just checked the priorities were the same in my gameconfig. If your gameconfig is the same (as what I have posted above) in that part already then just skip part 9.).

@player32
You must have made a mistake. I just followed the 'GAMECONFIG RE-Sized tutorial.rtf' instructions, edited & replaced my 'gameconfig.xml' & my game loads up fine.

Try downloading this gameconfig.xml to get your game working again.

You can always try the GTA Re-sized edits on that gameconfig safe in the knowledge that you have a backup. If you are struggling getting it to work post back here & I'll help you out

Pro Tip: Use Notepad++ to edit files as it has many useful features that will make the job a lot easier for you. Everything from a red vertical line being drawn from the start of a block of data to the end so you know exactly what you have to replace/edit/delete etc (open up your 'gameconfig.xml' with Notepad++ & click on any '<Item>' line & you will see what I mean) to plugins like XMLTools that will check your syntax automatically for you

@adinhoa
I think what you are looking for is 'vehiclemodelsets.meta'.

\mods\update\update.rpf\common\data\ai\vehiclemodelsets.meta

Search inside the file for 'modded' (there are lots) & you'll see something like this:

<Item type="CAmbientModelSet">
  <Name>DUBSTA2_MODDED</Name>
  <Models>
    <Item>
      <Name>Dubsta2</Name>
      <Variations type="CAmbientVehicleModelVariations">
        <BodyColour1 value="120" />
        <BodyColour2 value="120" />
        <BodyColour3 value="120" />
        <BodyColour4 value="120" />
        <WindowTint value="-1" />
        <ColourCombination value="-1" />
        <Livery value="-1" />
        <ModKit value="0" />
        <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="0" />
          </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="7" />
          </Item>
          <Item>
            <ModType>VMT_SUSPENSION</ModType>
            <ModIndex value="3" />
          </Item>
          <Item>
            <ModType>VMT_BONNET</ModType>
            <ModIndex value="1" />
          </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>
    <Item>
      <Name>Dubsta2</Name>
      <Variations type="CAmbientVehicleModelVariations">
        <BodyColour1 value="158" />
        <BodyColour2 value="89" />
        <BodyColour3 value="89" />
        <BodyColour4 value="158" />
        <WindowTint value="-1" />
        <ColourCombination value="-1" />
        <Livery value="-1" />
        <ModKit value="0" />
        <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="0" />
          </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="7" />
          </Item>
          <Item>
            <ModType>VMT_SUSPENSION</ModType>
            <ModIndex value="3" />
          </Item>
          <Item>
            <ModType>VMT_BONNET</ModType>
            <ModIndex value="1" />
          </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>

I haven't experimented with this myself so I don't know the finer points of exactly how it works but it should be pretty easy to play with & find out. Always make a backup.

Also be aware:
@PNWParksFan said in VehicleModelSets being weird:

There is a limit of 256 entries in vehiclemodelsets.meta. It sounds like you're over that limit, which will cause it to pick the wrong entry sometimes.

@Bloxx112
Nice one Glad you got it fixed

@Bloxx112
Either:

A ) - The cars that are not appearing are not installed correctly.

B ) - You are over the dlc limit. You can test this by removing some entries from dlclist.xml

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

OpenIV can be used to access game files (extract files & edit with Notepad++ or alternatively edit them where they are by right-clicking the file in OpenIV & selecting 'Edit...'). Note: Make backups before editing ANY files! Always!

Remove the add-on cars that are working leaving only the cars that fail to spawn (say 2 of them). If you load up the game & the cars now spawn that's a strong indication that you were hitting/over the dlc limit.

DLC Limit (possible fixes):
You could try various gameconfig.xml's to see if you can find one that works in increasing the dlc limit for you for your version of the game. The success of this will depend on how many add-ons you have. If you are way over the limit (depends on version of game but ~50>60 add-ons in total (inc game dlc's) or there abouts) a new gameconfig won't make much difference.

If you can't fix it with a new gameconfig & aren't willing to remove any of your add-ons then your only option is to combine your add-ons by creating your own add-on pack. Basic info on add-on packs in a reply by me to a similar question a few days ago here also.

@GeorgianLORD

Editing:

<light_amb_occ_mult_veh>

will change how dark the Ambient Occlusion (AO, what your red arrow is pointing at above^) is under vehicles. Higher values are darker, lower lighter. That is the only thing that setting will change about the graphics. Everything else will look the same.
Note: There may also be '<light_amb_occ_mult_veh>' settings for certain areas in 'timecycle_mods_1/2/3/4.xml' (also in timecycle folder) that you will have to edit to get rid of AO under vehicles completely. Depends on how the files have been modded previously, do a search in the files for 'light_amb_occ_mult_veh' & change the values accordingly. You are safe to change every '<light_amb_occ_mult_veh>' value found to whatever you want ('0.000' (zero) to turn vehicle AO off completely)

Cool, no probs Best of luck.

@ushercooloff
Think about it like this. You go over the dlc limit & that breaks something that causes the game to act funny & not be able to read most of your add-ons. Your add-ons are still there & still installed correctly it's just the game can't see them as there are too many for it to handle.
It's not that you can only have so many cars & if you go over that limit you don't get the extra cars it's that if you go over that limit it breaks the game & anything can happen

This looks like a good tutorial. The basic principle of creating an add-on pack is to take the data from inside multiple files & combine the data into just one file of that type. Knowing the basic formatting/syntax of the files ('handling.meta', vehicles.meta', 'carcols.meta', 'carvariations.meta' etc) will help you from making a mistake here. If you are comfy working with replace cars you have probably done enough data shifting (correctly copying & pasting blocks of data from one file to another) to have enough skill to master it. The main issues will be the tedious repetitiveness of it & the risk of making a silly mistake.
I would start by taking a working add-on mod with multiple vehicles (that have working upgrades so the folder ('vehiclemods' usually), archive structure ('vehicles.rpf' usually) & 'content.xml' entries (see below for more on 'content.xml') are there for upgrades to be used so you don't have to create them yourself), use it as the base for your add-on pack & work from there. The more complex & multi-file containing an add-on you choose to base your add-on pack on the better, as it means that more of the structure work will have been done for you & all you will be doing is adding files or adding data into pre-existing files.
Note: Leave the add-on folder name & 'dlclist.xml' entry alone at the moment. They can be changed later, no need to risk breaking something before you start.

content.xml - This tells the game where things inside the add-on are. Pick one & have a look inside it. They are pretty much all very similar. If you start with an already working multi-car add-on there's no real need to edit 'content.xml'. Just put the cars & the files you add into the pre-existing files/folder/archives (ie cars go where the original cars are (usually 'vehicles.rpf'), file data goes INSIDE the correct files (handling data into the pre-existing 'handling.meta' file, vehicle data to 'vehicles.meta' etc)).

Use Notepad++ as your editor of choice. It has a lot of useful features (red verticle line showing where a block of data starts & ends. Click on any '<Item type=' or '</Item>' in any 'handling.meta' & you will see what I mean) & plugins (XMLTools plugin to check syntax etc)

It really is that easy, all you have to do is combine the data of multiple separate add-on files into one add-on & it's singular files. Watch for silly mistakes & prepare for it to be boring but also very satisfying when you are complete.

Tip: Start by turning a single car add-on into a correctly working 2 car add-on pack

@ushercooloff
Remove all but one of your modded add-ons (choose a car that is failing to spawn at the moment, so you can test if it does now) from 'dlclist.xml' (make a backup of dlclist.xml first if you like).
Load game, see if car spawns.
If it does then you know that it is installed correctly & you are most likely looking at having hit the dlc limit
Start adding back other add-ons in groups of 5 or something (or add them all back & remove 5, however you want to do it. Prioritise etc. Whatever suits you)
Each time you add/take 5 new lines to dlclist.xml, load the game & check to see if cars spawn

From what I remember, I think it is important to test that a wide group of cars all spawn correctly as I seem to remember that when I added/removed lines from the dlclist.xml it caused different cars to fail to spawn (it's not always the same car as I recall so test a few).

Say the game has a limit of 50 add-ons & Rockstar use 2 updating the game without increasing the hardcoded limit etc then you will have 2 add-ons less to be able to use. If you are at the hardcoded limit already when you update your game you need to remove 2 add-ons for it to work correctly again. Sorry, new patch is a bit of a ********** that way from what I have heard

You can always combine add-ons & remove the limit so not all is lost