@lu7582482
Here's the basics on editing police vehicle spawns

dispatch.meta:

To change the dispatch/police vehicles that spawn & pursue you when you have a wanted level, you edit the vehicle's listed in the '<VehicleSets>' section of 'dispatch.meta':

...\Grand Theft Auto V\mods\update\update.rpf\common\data\dispatch.meta

The various '<VehicleSets>' sections will look something like this:

<VehicleSets> Example (POLICE_CAR):

	<VehicleSets>
		<Vehicle>
			<Name>POLICE_CAR</Name>
			<ConditionalVehicleSets>
				<Item>
					<ZoneType>VEHICLE_RESPONSE_ARMY_BASE</ZoneType>
					<VehicleModels>
						<Vehicle>crusader</Vehicle>
						<Vehicle>mesa3</Vehicle>
						<Vehicle>barracks</Vehicle>
					</VehicleModels>
					<PedModels>
						<Ped>S_M_M_Marine_01</Ped>
						<Ped>S_M_Y_Marine_01</Ped>
						<Ped>S_M_Y_Marine_03</Ped>
					</PedModels>
				</Item>
				<Item>
					<ZoneType>VEHICLE_RESPONSE_COUNTRYSIDE</ZoneType>
					<VehicleModels>
						<Vehicle>SHERIFF</Vehicle>
						<Vehicle>SHERIFF</Vehicle>
						<Vehicle>SHERIFF</Vehicle>
						<Vehicle>SHERIFF2</Vehicle>	
					</VehicleModels>
					<PedModels>
						<Ped>S_M_Y_Sheriff_01</Ped>
					</PedModels>
				</Item>
				<Item>
					<VehicleModels>
						<Vehicle>police3</Vehicle>
						<Vehicle>police2</Vehicle>
						<Vehicle>police</Vehicle>
						<Vehicle>policet</Vehicle>
					</VehicleModels>
					<PedModels>
						<Ped>S_M_Y_Cop_01</Ped> 
					</PedModels>
				</Item>		
			</ConditionalVehicleSets>
		</Vehicle>

<ZoneType>:

• 'VEHICLE_RESPONSE_ARMY_BASE' - Controls what dispatch vehicles spawn at Zancudo Military Base
• 'VEHICLE_RESPONSE_COUNTRYSIDE' - Controls what dispatch vehicles spawn when you are in the Countryside.
• No '<ZoneType>' line (3rd one down usually) - Controls what dispatch vehicles spawn when you are in the main City.

<VehicleModels>:
The '<VehicleModels>' sections control what vehicles will spawn & at what ratio to
one another they are likely to spawn.

Example:

					<ZoneType>VEHICLE_RESPONSE_COUNTRYSIDE</ZoneType>
					<VehicleModels>
						<Vehicle>SHERIFF</Vehicle>
						<Vehicle>SHERIFF</Vehicle>
						<Vehicle>SHERIFF</Vehicle>
						<Vehicle>SHERIFF2</Vehicle>	
					</VehicleModels>

'SHERIFF' is 3x more likely to spawn compared to 'SHERIFF2'

<WantedResponses>:
You can control what VehicleSets spawn at what wanted level in the '<WantedResponses>' section of the same file ('<WantedLevel1>' > '<WantedLevel5>' etc).

Example (WantedResponses > WantedLevel1):

	<WantedResponses>
		<WantedLevel1>
			<DispatchServices>
				<Item>
					<DispatchType>DT_PoliceAutomobile</DispatchType>
					<NumPedsToSpawn value="8"/>
					<DispatchVehicleSets>
						<Dispatch>POLICE_CAR_WOMEN</Dispatch>
						<Dispatch>POLICE_CAR</Dispatch>
					</DispatchVehicleSets>
				</Item>
				<Item>
					<DispatchType>DT_PoliceBoat</DispatchType>
					<NumPedsToSpawn value="3"/>
					<DispatchVehicleSets>
						<Dispatch>POLICE_BOAT</Dispatch>
					</DispatchVehicleSets>
				</Item>
			</DispatchServices>
		</WantedLevel1>

The names in the '<DispatchVehicleSets>' sections ('POLICE_CAR' etc) correspond to the names in the '<VehicleSets>' section encountered earlier.

vehiclemodelsets.meta:

To edit the dispatch/police vehicles that you see driving in traffic (but not chasing anyone), & some parked outside police stations & such, you edit 'vehiclemodelsets.meta':

...\Grand Theft Auto V\mods\update\update.rpf\common\data\ai\vehiclemodelsets.meta

Can't remember exactly what does what, but search 'vehiclemodelsets.meta' for 'police' & you'll find them all & can then edit &/or add more police vehicles to those '<Item type="CAmbientModelSet">' sections & see what it changes in-game etc & find your preference.

@Itzhak880
Had you used a downloaded 100% save file previous to noticing this issue? If so, might be that once you complete the game (or use someone elses save file) loading screens get locked in or something (I've never completed the game (on PC anyway) & a new save/mission progress has always worked to shuffle the load screens for me). Maybe, try starting a completely new game, right from the prologue & see if anything changes?

If that doesn't work (or you could even try this first if you wanted):

Create new 'pc_settings.bin' & 'cfg.dat' files:

• Search your C: (OS Install) drive for 'pc_settings.bin' & 'cfg.dat' (they should both be in the same Rockstar/Socialclub etc related folder together (ie don't delete any files of those names if you find them alone, on their own or in a folder unrelated to GTA V ).
• Make a backup of them & then delete/move them
• New ones will be created next time you start the game.
• Any bloat/corruption that may have appeared in those files (if it indeed has) should then be cleared.
• It shouldn't affect your game in any other way.

@LEXLYC

Quickest 'mods' folder diagnosis (in your situation):

• Create a new empty folder called something like 'mods - [REMOVED]' (name it whatever you want, anything will do) next to your 'mods' folder
• Move '.rpf' files/folder structures (one by one, loading the game after each removal) across from your 'mods' folder to the new 'mods - [REMOVED]' etc one.

Note: folder structures ('dlcpacks' etc) will need to diagnosed one '.rpf' at a time if an issue is discovered within it/them etc, but you can move the whole folder structure to begin with to either, quickly identify an issue within it, or rule it out completely etc.

• Using that^ process, you should be able to identify which '.rpf/s' are causing any issues
• Once you narrow it down & identify a problem '.rpf', back it up & then use the same process to identify any problem files within it (or rebuild it anew (file by file etc) using a fresh vanilla file)

Extra:
Given that you are crashing on startup, & that's quicker to identify if the issue still exists than letting the game fully load & then manually quiting etc, it's quickest for you to work from a broken 'mods' folder & remove files/folder structures from it one at a time to identify the issue.
Normally, a diagnostic 'mods' folder rebuild goes the other way (rename original 'mods' folder, create a new one next to it, move files across one by one from old to new 'mods' folder etc), but the way I outlined above, & for the reason I've given (loading time), will be quickest (slightly) for you in your situation. Feel free to do it either way tho, whatever you're most comfortable with.

50/50 Method/Binary 'mods' folder Rebuild:
Using a 50/50 approach, ie moving half of the files/folders (in any one folder) in or out of your 'mods' folder at a time will net the quickest returns, & allow you to usually identify a culprit's general location within 6 to 7 loads of the game (for each folder tested):

50/50 Method - Proof of Concept (starting sample 100 files in folder):

No. of Loads of Game        No. of Files     
         0                       100
         1                       50
         2                       25
         3                       12.5 (lets call it 12)
         4                       6
         5                       3
         6                       1.5
         7                       <1 (i.e below 1, folder/archive identified)

• You are moving files (rather than copying & pasting them/creating duplicates etc) from one 'mods' folder to another (the renamed/newly created one), so only one copy of the files exists at any given time. Dead easy to identify what you have tested/removed already & not get confused that way.
• Just be sure not to delete anything & always back up any file before you attempt to edit it. That way, if you want to go back to where you started, you just move all the files (in the their correct locations ofc) back into your original 'mods' folder & you are good/identical to what you had before.

extratitleupdatedata.meta:

Just so you know, you never, ever, ever have to edit 'extratitleupdatedata.meta'. If you download any add-on & it tells you to add data to 'extratitleupdatedata.meta', just completely ignore it & skip that part. It's completely unnecessary & 100% useless for mod author created dlcs.

Background Info (extratitleupdatedata.meta):
Editing 'extratitleupdatedata.meta' is something that some early car modders mistakenly thought they needed to do & a lot of newer modders continue to make the same mistake (having learned the (incorrect) process from early car modders/tutorials etc). The file can only be used by Rockstar, basically to allow them to update individual files within a '.rpf' without forcing the user to download the full '.rpf' again, so only ever of any use for official Rockstar dlcs & totally pointless for any mod author created add-on/dlc.

TLDR (extratitleupdatedata.meta):
Always skip editing 'extratitleupdatedata.meta', it does nothing for modded add-ons & is just a complete waste of time

@Itzhak880

'loadingscreen_startup.ytd' will always display first no matter what:

...\Grand Theft Auto V\mods\update\update.rpf\x64\data\cdimages\scaleform_frontend.rpf\loadingscreen_startup.ytd

As to the other ones in:

...\Grand Theft Auto V\mods\update\update.rpf\x64\data\cdimages\scaleform_platform_pc.rpf

If you use a different save or progress the story mode a bit & save, different ones will display. You'll see them all eventually if you do that

@JohnFromGWN
I do have 'update2.rpf' in my 'OpenIV.log' (must be your atypical environment or something)

Oh yeah, that's gold standard, nice one @Squirrelz

@JohnFromGWN
By the by, I've tested the new patch on 2 different machines now, my own & also a friends (so, updating an already modded game & then installing my mods to a previously completely unmodded game, & I got none of the aforementioned issues running mods. 1.0.2699 looks pretty stable to me, I can't find any obvious issues with it (I only have my own maps (just adding props) & no MLOs installed).

I did have a few CTD's (no error), but only while I was testing the limits & deliberately doing things that were likely to crash the game (like leaving my old 'update.rpf' installed, or installing half my modded files (so stuff was missing) etc), but no infinite loading or dlc limit to be found (tested ~65 modded add-ons active at the same time, mostly vehicles, they all loaded fine).

@JohnFromGWN said in Gta 5 crashes when more than 2 mods are installed:

Keep it simple until game is stable

That's the order of the day. I can't diagnose any of the aforementioned issues first-hand & gain any info that way anyway (was hoping I would get at least one of the issues to pop up, but it was not to be).

@JohnFromGWN
Yeah, that was my thought, no prompt from OpenIV to update 'update2.rpf' might allow it to sneak past people unnoticed & unpatched & potentially cause an issue etc.

@JohnFromGWN said in Gta 5 crashes when more than 2 mods are installed:

However is it necessary

It's not essential, but I wanted a focus put on 'update2.rpf' as it has been mentioned a lot, related to potential solutions to certain issues, at least for some users. Just wanted it in people's view, hopefully someone plays about with it & get's me some valid info back, maybe we get lucky etc).

@JohnFromGWN said in Gta 5 crashes when more than 2 mods are installed:

how common are these issues?

It's hard to tell. The thing that initially made this update/patch standout to me as potentially unique in some way tho, & what peaked my interest (I usually bug out at patch time, lets face it, it ain't fun for anyone ) is that I've had a few very capable mod authors & experienced modders contact me about it. I know them well enough to know their capability (going back years in some cases) & they have the skillset to fix any ordinary update/patch issues/'mods' folder diagnosis etc no problem. Just seemed a little statistically unusual & worthy of further investigation etc (albeit subjective, skilled modder friends etc don't usually contact me after a patch, that is totally unprecedented etc).

Could well be that the update process was just a little flaky initially & caused problems that are now resolved by most. Have to wait for people to get back to me on that/too early to tell anything conclusively at this point.

Going from the only information I have at my disposal atm (however unreliable), people seem to have one or more of these issues:

• Crashes (tells us nothing really, without further specific user info/could easily be non-patch related etc)
• Infinite loading (slightly more interesting that just crashing, but as above, further info required/can't rule out standard non-patch related issue etc)
• No add-on dlcs loading (possibly related to below/just that some users haven't tested reducing the number of dlcs & found a threshold yet (if one exists for them etc), also could be non-patch related, can't rule it out).
• Add-on dlcs are limited to only being able to add a few (appears to be 2 dlc limit atm) & custom gameconfig's don't fix it (somewhat unusual/uncommon issue worthy of investigation, given custom gameconfig does not fix etc).

Still need it confirmed whether it's any dlc, or just vehicle ones the apparent restriction applies to & whether people perhaps have different limits or are always 2x dlc etc. That's what I'm investigating here, that very tiny limit (2 dlc etc) that has been imposed on @MrKristupas & some others that the new custom gameconfig's appear not to fix.

@meerty
Perhaps you might try loading just a vanilla 'dlclist.xml' & see if your game loads that? If it does, then add back in custom dlc one at a time to see whether a limit exists. Basically, try & confirm for me whether your issue is the same as the op's (MrKristupas) & that you are limited to loading just 2 (or similar number of) add-on vehicle dlcs?
If you don't have a very low dlc limit imposed, you're better off creating your own thread to deal with your specific issue (or at the very least find threads that specifically reference your exact issue). It just gets too confusing & messy diagnosing separate issues within the same thread & if yours is in fact a 'no mods work whatsoever' issue, there are a miriad of things that could cause that, it really needs it's own dedicated thread.
A solution for your issue can likely be found, but it's normal for patch introduced issues/normal issues occuring at the same time as a patch to take a lot longer to resolve. It's total , but you'll just have to wait around until the GTA V modding community has a better idea of what is going on & what this patch has potentially done etc.

The best thing you can do when you create that thread is provide a very detailed account of:

• the mods you have installed (inc. add-ons, scripts (in scripts folder), scripts & such in main GTA V root folder ('.asi/.dll' usually etc)
• the tests you have conducted (like testing a vanilla gameconfig & confirming whether your game works with that or not etc)
• Anything else you have tried & the results you got from it etc

It's better that you provide more info than is needed, than not enough info. So, don't spare the keyboard. Be as thorough as you possibly can.

General Info/Areas of Interest Concerning Patch 1.0.2699 for Anyone with Any Issues:

Packfile Limit Adjuster:

The patch breaking Packfile Limit Adjuster adds another variable into the mix this time also (especially given how popular & often vital it is & that the new one isn't thoroughly tested etc). Best way I could see to begin diagnosing without that as a variable, would be for people to get their games to a state where Packfile Limit Adjuster is no longer required to be installed & thus, remove it from their 'Grand Theft Auto V' root folder while conducting initial tests. Then, once initial game stability/testing etc has been completed/potential issues there found & resolved etc, it can be reintroduced, if required, & any Packfile Limit Adjuster specific issues (if indeed any exist) diagnosed on their own etc.

gameconfig.xml:

F7YO 'Backup' Gameconfig
Something to be aware of. The F7YO backup file (in the 'Backup' folder within his 30th July (9 days ago) upload) is not a backup of the vanilla 1.0.2699 'gameconfig.xml', but an earlier game version. Those reverting, & using that file to do so (after having issues etc), may inadvertently be introducing a new variable into their diagnostic results.

SyncedScenesMP:
This new pool arrived with the new patch & is a variable I can't account for. It's never appeared in any previous vanilla 'gameconfig.xml':

                        <Item>
                            <PoolName>SyncedScenesMP</PoolName>
                            <PoolSize value="64"/>
                        </Item>

Unlikely that it's the root of any issues, as it appears to be multiplayer related, but can't rule it out completely. Some reports of people finding success reverting to F7YO's previous 'Gta Config v28 for v 1.0.2612' gameconfig could potentially account for 'SyncedScenesMP' not being there in that older gameconfig version, perhaps (ie probably nothing, but worth ruling out none the less).

Ignoring 'SyncedScenesMP', the other values that have changed are:

F7YO gameconfig (values changed in F7YO 1.0.2699 compared to F7YO 1.0.2612):

<PoolSizes>:
DwdStore
ScriptStore
HandlingData

<ConfigPopulation>:
<PedMemoryMultiplier
<VehicleMemoryMultiplier

<ConfigModelInfo>:
<MaxExtraPedModelInfos
<MaxExtraVehicleModelInfos

<PlayerBroadcastData>:
(single '<NumInstances' value changed)

<ConfigScriptStackSizes>:
MULTIPLAYER_MISSION
FMMC_LAUNCHER
MULTIPLAYER_FREEMODE
MISSION

F7YO's download contains 42 separate 'gameconfig.xml' files for 1.0.2699 (so I'm not listing all exact value changes. I just quickly compared the 'Stock Traffic (Means Gta base)' ones from their respective 'For More Mods' folders).

update2.rpf:

Just a file of note, something to keep an eye on as it has been mentioned a lot by people having various issues over the last week or so (mostly in regard to fixing dlc limit/mods not working issues, but occasionally others too). Just because of that, & the ease with which one could diagnose issues relating to 'update2.rpf', it's worth ruling out in whatever way one can conceive:

ie:

• Make sure if it's in your 'mods' folder that it's up to date (ie use the 1.0.2699.0 vanilla one, not older etc, rebuild it if you have to etc)
• Verify game integrity (even if you have reinstalled since having issues)
• Remove it from your 'mods' folder (if you have it there normally etc) as a test
• Anything else you think of etc

Disclaimer:
I don't think we are anywhere near a solution to potential patch issues. The ones that do actually exist & can in time be separated from standard/normal 'mods' folder issues I mean. Too much of it is still guesswork. I would need a lot more accurate info to get anywhere near making any assumptions about what might be causing any apparent issues.
All I have done here really, is scour the internet with a focus on quantity & continuity of posted results & draw up some potential avenues of research. The continuity of data has been high, I'll give it that, especially as regards 'update2.rpf', so no harm in ruling it out at least, given it should be reasonably quick to do.

@JohnFromGWN said in Gta 5 crashes when more than 2 mods are installed:

graduate to GTA6

Just as a little aside, I thought, "Ooh, I wonder how long it will be until I could potentially mod GTA VI to a standard I would find acceptable?" (ie full file edit access in OpenIV etc). Gonna be ~2030 (say GTA VI releases 2025, & then potentially ~5yrs for OpenIV team to give us full access etc). That's a way longer timescale than I had in my head! lol. Ok , RDR2 modding it is then.

@gti92
You probably want to add your extra taxis to the 'VEH_TAXI' section in 'popgroups.ymt' as well. Maybe the 'VEH_TRANSPORT' one too, but I would probably test just the 'VEH_TAXI' section on it's own first.

...\Grand Theft Auto V\mods\update\update.rpf\x64\levels\gta5\popgroups.ymt

VEH_TAXI:

    <Item>
      <Name>VEH_TAXI</Name>
      <models>
        <Item>
          <Name>taxi</Name>
          <Variations type="NULL"/>
        </Item>
      </models>
      <flags>POPGROUP_SCENARIO POPGROUP_AMBIENT</flags>
    </Item>

VEH_TRANSPORT:

    <Item>
      <Name>VEH_TRANSPORT</Name>
      <models>
        <Item>
          <Name>bus</Name>
          <Variations type="NULL"/>
        </Item>
        <Item>
          <Name>taxi</Name>
          <Variations type="NULL"/>
        </Item>
      </models>
      <flags>POPGROUP_SCENARIO POPGROUP_AMBIENT</flags>
    </Item>

As long as it actually works (it should, I've just never tested it etc), I think 'popgroups.ymt' will get you the most pronounced results, should have mentioned that first tbh, but feel free to experiment with 'popgroups.ymt' &/or 'vehiclemodelsets.meta' & see what one or combination gets you the best results

@gti92
Find 'vehiclemodelsets.meta' here:

...\Grand Theft Auto V\mods\update\update.rpf\common\data\ai\vehiclemodelsets.meta

& add new vehicles to the 'taxi' 'CAmbientModelSet' within it:

Default 'vehiclemodelsets.meta' 'taxi' 'CAmbientModelSet':

    <Item type="CAmbientModelSet">
      <Name>taxi</Name>
      <Models>
        <Item>
          <Name>taxi</Name>
          <Variations type="NULL" />
          <Probability value="1.000000" />
        </Item>
      </Models>
    </Item>

Example (new taxi vehicles added):

    <Item type="CAmbientModelSet">
      <Name>taxi</Name>
      <Models>
        <Item>
          <Name>taxi</Name>
          <Variations type="NULL" />
          <Probability value="1.000000" />
        </Item>
        <Item>
          <Name>taxi2</Name> <!-- 2nd taxi added -->
          <Variations type="NULL" />
          <Probability value="1.000000" />
        </Item>
        <Item>
          <Name>taxi3</Name> <!-- 3rd taxi added -->
          <Variations type="NULL" />
          <Probability value="1.000000" />
        </Item>
        <Item>
          <Name>taxi4</Name> <!-- 4th taxi added -->
          <Variations type="NULL" />
          <Probability value="1.000000" />
        </Item>
      </Models>
    </Item>

The game will then choose one at random when the 'taxi' 'CAmbientModelSet' is called/spawned.

Note:

• You can add any vehicle/vehicle name. They don't have to be called taxi1/2/3/4 etc. Any name will work.
• I'm not confident the '<Probability value' works as you might think, by allowing you to control the probability of one vehicle spawning over the others (can't remember if it works ). Feel free to try it, if you need it etc, but if it doesn't make a difference you can always duplicate entries & control the car to car spawn ratio that way.

ie, for example, enter 'taxi2' etc twice:

        <Item>
          <Name>taxi2</Name>
          <Variations type="NULL" />
          <Probability value="1.000000" />
        </Item>
        <Item>
          <Name>taxi2</Name>
          <Variations type="NULL" />
          <Probability value="1.000000" />
        </Item>

& it will have twice the chance of spawning compared to any other single entry vehicle/s in that 'taxi' 'CAmbientModelSet' section.

@JohnFromGWN
Definitely a lot of diagnostic chaff floating about atm. My favourite is the 'edit 'version.txt' one' lol

@meerty @MrKristupas

Unconfirmed reports of this (below) fixing some people's games:

• There's no overt confirmation (from someone who's skill I know & trust anyway) that this will defo work, just rumblings around the internet/a few people mentioning it (or variations of this process) in various forums/comments pages etc. Easy enough to test/rule out tho, so I figured worth mentioning.

Before diving into any diagnostic information gathering (as per previous posts etc), try this (if not ruled out already):

• Delete 'update2.rpf' from 'mods' folder (back it up if modded/edited)
• Copy the 1.0.2699 vanilla 'update2.rpf' over into your 'mods' folder (depending on the state of your game, perhaps a fresh clean 'mods' folder worth trying here. See 'Fresh 'mods' folder:' below on that)
• Test load the game with the 1.0.2699 vanilla gameconfig installed & then experiment with the 1.0.2699 custom gameconfigs available atm for further launches of the game (start with F7YO's one, but depending on results, try others too).
• If you find stability somewhere in that^, proceed to add mods/dlcs/add-ons etc one at a time & see how the game reacts.

Note:

• The important part is the creation of a new (& ideally integrity verified) 1.0.2699 vanilla 'update2.rpf' in your 'mods' folder.
• Also, test load the game a few times after each change, just to make sure your results are consistent & you didn't just get lucky/unlucky with a random successful load of the game/random one off crash etc.

Fresh 'mods' folder:

Following that^ kind of approach, who here has rebuilt their 'mods' folder afresh using the vanilla files supplied with 1.0.2699? Especially, 'update.rpf' & 'update2.rpf', but possibly other '.rpf's s well? (ie nothing ported over from your old (pre-1.0.2699) 'mods' folder. Everything recreated anew etc).

Again, easy enough to test: (a quick initial test anyway, & as long as you have enough hdd space ofc)

Basic Steps:

• Rename your 'mods' folder temporarily
• Create a new one in it's place
• Copy fresh vanilla 1.0.2699 files into newly created 'mods' folder (in the correct location ofc, probably only need 'update.rpf' & 'update2.rpf' for an initial test. Do them separately if you want to be thorough)
• Test load game with the 1.0.2699 vanilla gameconfig & then custom gameconfig/s etc
• If it loads up & appears stable, start to activate your mods in a meaningful & careful manner (ie one mod at a time) & see how the game holds up as you progress etc.

Note:
Make backups at every step (like every single step, backing up the whole '.rpf' is often easiest (hdd space allowing)), then if you encounter a crash/infinite load screen/other issues etc, revert files back to what worked & test again. If you get confusing results, or an issue persists through reverting your changes by 1 step etc, revert back a couple of steps (or more, if needed) instead, & test again. Basically, be thorough & only progress once you're 100% confident your current game is free of issues.

@MrKristupas
Getting a lot of reports of behaviour like that, things suddenly breaking halfway through testing something else, even reinstalls that don't work/are instantly broken etc. Seems like something is causing the game to be mega unstable. Could very well be that it's all the same issue, just everyone's results vary slightly depending on their exact setup or the damage caused is a bit random or some such. Only time will tell.
No worries, enjoy the rest of your vacation