Best posts made by a63nt-5m1th

@Spaarda
'<fMass value=' in 'handling.meta'. This value of mass doesn't affect handling in ANY way. The value is ONLY used in calculations to do with collisions/crashes/one vehicle pushing another/vehicle hitting object etc.
I couldn't find a way to decrease the mass of stop signs etc (which would have been the perfect solution with the most control) so have settled on increasing the mass of all vehicles by a factor of ten (see example below).

Example:

    <Item type="CHandlingData">
      <handlingName>ADDER</handlingName>
      <fMass value="18000.000000" /> x10. default is '1800'.

This allows me to smash through small signs without much (if any) loss of speed. Ideally I'd like the streetlights to be solid (like vanilla) rather than being able to drive through them as I can now but I haven't found a way to reduce object/prop mass.

GTAV Handling Editors or Notepad++'s find & replace functionality will help ease the burden of changing all values manually

@lasper
I'm not sure but here's a few ideas anyway:

Maybe try defaulting 'vehicleaitasks.ymt' to vanilla?

Specifically these parts:

<Item type="CTaskVehicleGoToHelicopter__Tunables">
<Name>ctaskvehiclegotohelicopter</Name>
<slowDistance value="150.0" />
<maxCruiseSpeed value="250.0" />
<maxPitchRoll value="1.0" />
<maxThrottle value="1.0" />
<leanKp value="0.1" />
<leanKi value="0.0" />
<leanKd value="0.05" />
<yawKp value="1.0" />
<yawKi value="0.0" />
<yawKd value="0.05" />
<throttleKp value="1.0" />
<throttleKi value="0.0" />
<throttleKd value="0.1" />
<whiskerForwardTestDistance value="50.0" />
<whiskerForwardSpeedScale value="3.0" />
<whiskerLateralTestDistance value="20.0" />
<whiskerVerticalTestDistance value="25.0" />
<whiskerTestAngle value="30.0" />
<avoidHeadingChangeSpeed value="180.0" />
<avoidHeadingJump value="30.0" />
<avoidPitchChangeSpeed value="90.0" />
<avoidPitchJump value="90.0" />
<avoidLockDuration value="1.0" />
<hash_collision_4970624124 value="0.25" />
<hash_collision_1056893569 value="1.0" />
<hash_collision_3844241672 value="2.0" />
<hash_collision_15394816095 value="10.0" />
<hash_collision_7215765668 value="-0.75" />
<numHeightmapFutureSamples value="10" />
<futureHeightmapSampleTime value="1.0" />
<DistanceXYToUseHeightMapAvoidance value="500.0" />
<TimesliceMinDistToTarget value="15.0" />
<TimesliceTimeAfterAvoidanceMs value="5000" />
</Item>

&

<Item type="CTaskVehicleGoToPlane__Tunables">
<Name>ctaskvehiclegotoplane</Name>
<numFutureSamples value="8" />
<futureSampleTime value="0.5" />
<maxDesiredAngleYawDegrees value="15.0" />
<maxDesiredAnglePitchDegrees value="30.0" />
<maxDesiredAngleRollDegrees value="60.0" />
<angleToTargetDegreesToNotUseMinRadius value="45.0" />
<minMinDistanceForRollComputation value="20.0" />
<maxMinDistanceForRollComputation value="100.0" />
<maxYaw value="1.0" />
<maxPitch value="1.0" />
<maxRoll value="1.0" />
<maxThrottle value="2.0" />
<yawKp value="1.0" />
<yawKi value="0.0" />
<yawKd value="0.05" />
<pitchKp value="0.1" />
<pitchKi value="0.0" />
<pitchKd value="0.05" />
<rollKp value="0.1" />
<rollKi value="0.0" />
<rollKd value="0.05" />
<throttleKp value="1.0" />
<throttleKi value="0.0" />
<throttleKd value="0.1" />
</Item>

Note: Those are the settings I have & they work (no suicide/crashing etc) but they may not be the same as vanilla. Compare what you have to my values (or a default copy of the file) & see if anything pops out

Extra: Obviously if you have edited the 'handling.meta' values for planes etc then that might be causing it also. Planes too fast/can't turn enough etc. Might be worth defaulting them also just to see. Make backups etc.
Also temporarily remove any/all scripts that may be causing it. Rename 'scripts' folder etc just to remove them as a variable.
Let us know how you get on

@MrVibrating
afaik there's no separate parameter to isolate locked wheel/skidding grip/friction from the rest of the ABS ON/OFF braking calculations. You could do it with a script but I've never seen any specific parameters like that in the game files.
I'm confident you will be able to get the result you require though as I think it is just a matter of looking at the problem from a different perspective.
As it stands I've made a few presumptions as to what you may want to achieve/why differences in ABS ON/OFF braking distance might be an issue for you etc. Hopefully I'm on the money but if not give me a better idea of the end result you want to achieve I'll have a more precise response for you .

I take it you are switching ABS ON/OFF using the 'strModelFlags' in the vehicles 'handling.meta' yeah?

My results:

• 1 = ABS_STD - Small brake marks at end of skid
• 2 = ABS_OPTION - Long dark brake marks
• 4 = ABS_ALT_STD - Dotted brake marks (like real life ABS)
• 8 = ABS_ALT_OPTION - Long dark brake marks (similar/same as '2')

For me at least 1, 2 & 8 brake about the same. 2 & 8 may even stop quicker (quick test) but I don't like the heavy dark brake marks much.
I take it you want the one that looks like real life? ie 'ABS_ALT_STD' ('4') dotted brake marks?
Generally you would select 'ABS_ALT_STD' ('4') in the vehicles 'strModelFlags' line in 'handling.meta' & then compensate for the reduction in braking ability by increasing:

      <fBrakeForce value="increase_value_here" />

If you are in the situation where you have 2 vehicles the same/similar using the same 'handling.meta' settings & you want one to have standard braking & the other to have ABS (dotted line etc & increased stopping ability, like real life) one way to solve that would be to create a separate & different handling profile & then point the ABS vehicle version's 'vehicles.meta' '<handlingId>' to the new ABS handling profile.

Example (Standard):

'vehicles.meta':

    <Item>
      <modelName>vigero</modelName>
      <txdName>vigero</txdName>
      <handlingId>VIGERO</handlingId>
      <gameName>VIGERO</gameName>

'handling.meta':

    <Item type="CHandlingData">
      <handlingName>VIGERO</handlingName>
...
      <fBrakeForce value="2.500000" />
...
      <strModelFlags>440010</strModelFlags>

Example (ABS ON):

'vehicles.meta':

    <Item>
      <modelName>vigero</modelName>
      <txdName>vigero</txdName>
      <handlingId>VIGEROABS</handlingId>
      <gameName>VIGERO</gameName>

'handling.meta':

    <Item type="CHandlingData">
      <handlingName>VIGEROABS</handlingName>
...
      <fBrakeForce value="3.250000" />
...
      <strModelFlags>440040</strModelFlags>

Note: In the example above I've increased the '<fBrakeForce value=' by 30%. You'll obviously have to experiment to find the correct value for your liking

Let us know how you get on or if you have any more info to add etc

@Rogans
At the moment NVR only adds one of these files (branchbend_windsettings.xml) & in fact it is identical to the vanilla version of the files so changes nothing about the wind influence.

However, there are two '<wind_speed_mult>' lines (one for the main city (URBAN) , one for the countryside/towns etc (GLOBAL) in each of the w_****.xml timecycle files.
Try setting them to this:

      <wind_speed_mult> 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000 0.0000</wind_speed_mult>

& see if that either stops the wind influence or at least reduces it to acceptable levels

Default is '1.0000'. NVR's vary between '0.3000' (xmas) & '4.5000' (foggy/stormy).

Note: '<wind_speed_mult>' can also be set in 'timecycle_mods_1>4.xml' so you may have to clean up in those files also to remove/reduce wind influence in all areas of the game. Use Codewalker to see the areas timecycle modifiers affect ('[<<]' > 'Selection' > 'Time Cycle Modifiers'). Hope it helps

@Master10185
I use Muted Speech and Pain

In the 'MutedSpeechAndPain.ini' you can switch ON/OFF speech & pain sounds for player characters & pedestrians independent of one another.
If you just want the player speech muted & the other sounds normal make it look like this:

---------------------------------------Values are set/updated directly----------------------------------------------------
Values can be changed during gameplay.
--------------------------------------------------------------------------------------------------------------------------
[Player_Sounds]
pain_sounds=1  
speech_sounds=0

[Pedestrian_Sounds]
pain_sounds=1
speech_sounds=1

'1' means you can hear the sounds. '0' means muted.

@ReNNie @MaximumMatt

I tested 2x backslash:

		<Item>dlcpacks:\ninjah2\</Item>

2x frontslash:

		<Item>dlcpacks:/ninjah2/</Item>

& even 1x backslash/1x frontslash:

		<Item>dlcpacks:\ninjah2/</Item>

& it is all the same. My dlc's load & spawn correctly no matter the combination as long as there are two of them in the right place so I guess we can remove that as a variable.

@MaximumMatt
Make sure your 'dlclist.xml' is in this format at the bottom:

		<item>dlcpacks:\velociraptor\</item>
		<Item>dlcpacks:\topkickhd\</Item>
	</Paths>
</SMandatoryPacksData>

ie:

	</Paths>
</SMandatoryPacksData>

are the last two lines. Nothing below them.
In fact, post your entire 'dlclist.xml' here so we can have a look at it & see if anything jumps out. Maybe post the Karin Rebel/Raptor data files also (handling/vehicles/carvariations/carcols.meta) if this happened immediately after those changes or you can get your dlc's to spawn by removing the Karin Rebel edits (make backups & replace mod folder '.rpf's that contain Karin Rebel data with vanilla ones to check quickly etc).
Use the code block method or upload to Pastebin

@BrixyJebach
patchday3ng I think. Yep, here:

...\mods\update\x64\dlcpacks\patchday3ng\dlc.rpf\x64\levels\gta5\vehicles.rpf\futo.yft

Tip:

Ctrl+F3 in OpenIV to search for things by name. Try searching for 'futo.yft' & it will show you all of the 'futo.yft' locations in your game/mods folder. You then replace whichever one you find in the highest patchday.

@silentexecute
You have a parsing/syntax error in your 'content.xml' at line 78/79

There should only be one of these:

	  </filesToEnable>
	  </filesToEnable>

Delete one of the lines to fix

I can confirm the car spawns for me (using ENT) after applying this fix

@zyankenta
My GTA V install is over 200GB, overclocked GTX 1080, overclocked hex core Xeon x5660 @4.3Ghz, EVO 850, 4K DSR High/Very High settings & runs silky smooth +60fps all the time (the game is highly optimised by me right enough).
GTA V is like most of the big open world games. Bad/weird shit happens sometimes for no good god damn reason. That's modding.
My guess would be Redux is your most likely culprit. People who have to resort to stealing shit (Redux creator) are never the most skilled.
Glad you got it working Just build on what you have now, one mod at a time & put the game through it's paces after each install to look for bugs etc

@ArmaniAdnr
Try Texture Toolkit bud
It does crash, a lot, but if you stick with it you can usually get what you need done. As you just need to extract the texture I don't think you'll have any problems. It's usually when you are using it to import/add textures & save them in a file that it crashes.

@Stinger321 said in Player dies on rain or water:

any suggestion on how to fix it?

It ain't going to be simple. I've only ever been asked about this once before over a year ago. Given that it would have been a different version of Redux & you & the other guy (can't remember who) are about the only people in the world that it seems to have happened to I reason it must be some sort of weird conflict somewhere.
I made a backup of my 'mods' folder & installed Redux but there were no problems for me so I have no way to diagnose .
Note: I never installed Reshade or ENB & although I doubt they would cause this it might be an idea to remove them & see if it does anything? You never know.
I would also remove all/any scripts you have installed & test that too (move 'scripts' folder somewhere else etc) & try running GTAV without any other software running in the background (especially any monitoring/capture software).
I've scoured Google etc for info but can't find anything relating to dying in the rain/water unfortunately .

Method 01:
I'd say your best bet is delete your 'mods' folder & start again. Install Redux first, check if happening & if not proceed to install other mods one by one checking the game after each new install. If it happens with just Redux installed proceed to Method 02:/Ideas: below.
Note: Make a backup of your 'mods' folder at each stage as you progress (SSD's are very helpful here ) so you can revert easily should the game break at any point

Method 02:
Alternatively, while you still have Redux installed or if it happens with a fresh Redux/'mods' folder you could:

• Grab a copy of 7Zip & install it
• Right-click on the 'GTA5_REDUX_V1.5_FULL.oiv' & select '7Zip' > 'Extract to "GTA5_REDUX_V1.5_FULL" '
• The files contained in 'GTA5_REDUX_V1.5_FULL.oiv' will then be extracted to the 'GTA5_REDUX_V1.5_FULL' folder in the same location as the '.oiv'
• The extracted 'content' folder contains the files that Redux installed & the 'assembly.xml' will tell you where the Redux files are installed in the game.

Note: As a general rule do not follow the folder structure in the 'content' folder when installing/looking for files this way. Always follow the paths outlined in the 'assembly.xml'

From here it's a process of looking through the 'assembly.xml' to find where the files that Redux installed are in your game & defaulting each file to vanilla one at a time. Loading the game & checking after each default to see if the problem disappears/changes.
You are probably safe to ignore the '.ytd' files for now (although I have seen textures crash a game. Maybe default 'water.ytd' & 'graphics.ytd' if you like) & concentrate on defaulting the '.xml'/'.meta'/'.dat'/'.ymt' files you find.
Warning: There are quite a few data files. About 100 in all so it will take a little time.
If that doesn't fix anything maybe default the sound (.awc) & texture ('.ytd') files also.

You can probably see now why I went with 'delete your mods folder & start again' as my primary choice of procedure. It's probably a lot less work/simpler.

Ideas:
As you can hide under things/be in car & survive the death rain it sounds to me like it may have something to do with actually getting wet (ie the wet look fx etc). It might be an idea to have a look though the site & try mods/scripts that change what happens when the player/peds get wet. Say, like this one.
Also, say you make yourself invulnerable (trainer settings etc). Are you able to survive?
If you can find a way to survive, it will be invaluable info in solving the issue. Test out everything you can conceive of:

• Does it happen in all areas of the game? Ocean? Swimming Pool? etc
• Does it happen at all times? Day & Night?
• Does anyone (any peds/any characters) ever survive it?
• Does it instantly kill or remove health & then kill?
• Do any of these values (in 'w_rain.xml' etc) stop it happening? :

		<no_weather_fx> 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000</no_weather_fx>
		<no_rain> 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000</no_rain>
		<no_rain_ripples> 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000 1.0000</no_rain_ripples>

Note: You change them to '1.0000' to stop the effect & also test them individually as it may be informative . Not what I would call a fix. Just a possible workaround/info gathering.

• Does wetness from water hydrants/fire truck hose kill?

• Does water inside buildings kill? Fountains/pools etc if you can find any.

• Do you die if you are wearing your scuba gear (in game lol)?
  

• Does it happen if you get out of the Submarine underwater or only when you resurface etc?

Try & think of anything you can do with water/wetness & test it out in game. See if you can find anything that changes the outcome
Best of luck

@9Lincoln20

Have you tried Holy Water?

Maybe it's a demon , but my money is on some corruption somewhere. Let me know how you get on with the Error Checking & System Scan/Reinstall OpenIV
If that doesn't change anything then we'll call that Preacher lol or maybe try something else like deleting the entire mods/x64/audio folder (making backup first if contain files important), restart PC (do full power off/drain of power completely) & see if files appear again & if not then try loading the game to see if sounds back to default?
If that works then copy game folder /x64/audio over to mods folder, restart computer, load up game & check sounds etc. There will be a workaround somewhere, we just need to find it

@Reclusive-Eagle
Good investigating. I like it

@9Lincoln20
Can you confirm that when you try to replace or delete 'weapons.awc' OpenIV gives you an error etc or that you are presuming there is an issue as the in-game sounds sound the same even though you have successfully replaced 'weapons.awc'?

'Weapons.awc' Confirmed Unable To Edit/Delete (OpenIV Error etc):

If all other '.awc' are working correctly, it's most likely that 'weapons.awc' is corrupt.
Backup any '.awc' files you have edited & want to keep & then replace/remake entire 'RESIDENT.RPF' from backup & then re-install anything that is missing.
Sorry, it's not much help if you don't have a thorough backup regime. Implement one if you don't already have one.
A less severe solution might be to just rebuild 'RESIDENT.RPF' manually somewhere in OpenIV (ie create new 'RESIDENT.RPF' in a folder in the root of GTA install (for example) & then move all '.awc' from the old one to Windows Explorer folder & then into the new 'RESIDENT.RPF'). You never know, could get rid of your GTA gremlins.
Best of luck

'Weapons.awc' Presumed Not Working As In-Game Gun Sounds Do Not Change:

The sounds for the player's weapons are here:

...\mods\x64\audio\sfx\WEAPONS_PLAYER.rpf

If you are only changing the 'weapons.awc' here:

...\mods\x64\audio\sfx\RESIDENT.rpf\weapons.awc

then you are only changing the sounds for the ai, not the gun's that the player uses.

Replace the 'snp_heavy.awc', 'snp_rifle.awc', 'spl_grenade_player.awc' etc files in 'WEAPONS_PLAYER.rpf' with the ones from Gun Sounds Overhall to fix if this is the case.

@Reclusive-Eagle
I'm no expert (like Razed etc) but if I have the info I'll share it

Extra:
Streetlight intensity can also be edited using ENB's 'SpotIntensity' values (in the 'LIGHTARTIFICIAL' section, (if it exists in ENB settings)).
Note: ENB's 'spotintensity' values also alter car headlight intensity (& probably some other lighting) at the same time, which is not always desirable.
Extra bright/dim headlights can be compensated for by editing '<light_vehicle_intenity_scale>' (<R* typo, not mine) in any of the weathers 'w_namehere.xml' files. The advantage being that you can see immediate changes in-game using the ENB approach.

@Stau_puffed93

Yeah, you want to incease the 'fSuspensionForce' value in 'handling.meta':

Example:

      <fSuspensionForce value="2.200000" />

Compensate for harder suspension with the 'fSuspensionCompDamp' &/or 'fSuspensionReboundDamp' if the vehicle jumps up to much when going over bumps/pavements etc.

Given your problem I would also check:

      <fSuspensionBiasFront value="0.420000" />

make sure it is somewhere near '0.5'. (ie no '1.0' or '0.0')

These values below limit the travel of the suspension:

      <fSuspensionUpperLimit value="0.120000" /> *how far wheels up into car
      <fSuspensionLowerLimit value="-0.110000" /> *how far wheels hang below car

They can be used to limit suspension travel if the car bottoms out (wheels up into car body) or the wheels hang too low below the car when jumping etc. Values are usually around '0.1' or '-0.1' respectively.
Best of luck. Hope it helps

@Reclusive-Eagle
'Urban' is the main City area.
'Global' is all other areas (Countryside, Zancudo, small towns etc).

They are two distinct & seperate areas. Global doesn't affect Urban City in any way & vice versa.

@ReNNie
Not sure this is what you are looking for exactly but there is a 'FREEWAY' 'CAmbientModelSet' in 'vehiclemodelsets.meta' that may have some functionality that may be of use to you. Perhaps. It looks like this:

    <Item type="CAmbientModelSet">
      <Name>FREEWAY</Name>
      <Models>
        <Item>
          <Name>BURRITO</Name>
          <Variations type="NULL" />
          <Probability value="1.000000" />
        </Item>
        <Item>
          <Name>burrito3</Name>
          <Variations type="NULL" />
          <Probability value="1.000000" />
        </Item>
        <Item>
          <Name>PONY</Name>
          <Variations type="NULL" />
          <Probability value="1.000000" />
        </Item>
        <Item>
          <Name>speedo</Name>
          <Variations type="NULL" />
          <Probability value="1.000000" />
        </Item>
        <Item>
          <Name>BOBCATXL</Name>
          <Variations type="NULL" />
          <Probability value="1.000000" />
        </Item>
        <Item>
          <Name>BISON</Name>
          <Variations type="NULL" />
          <Probability value="1.000000" />
        </Item>
        <Item>
          <Name>Bison3</Name>
          <Variations type="NULL" />
          <Probability value="1.000000" />
        </Item>
        <Item>
          <Name>SADLER</Name>
          <Variations type="NULL" />
          <Probability value="1.000000" />
        </Item>
      </Models>
    </Item>

Not sure exactly where they spawn on/around the freeway etc but they look very much like service/utility vehicles for the most part so swapping them out for your service pack vehicles might just get you close to the probability you are looking for without too much hassle. I'm presuming they spawn quite regularly but not too many or we would have noticed duplicates (having eight different, effectively random vehicles to choose from per spawn point undoubtedly helps remove chance of duplicates & may solve any 'too many instances at any given time' issue straight out of the box ).
Not sure about the:

          <Probability value="1.000000" />

Haven't tested that value (& I've only ever seen it = 1.000000 so may just be an ON/OFF (1/0), although that would seem like a pointless waste of space R* if that were the case). Could be the probability of spawn frequency within that ''CAmbientModelSet'. Might be worth testing at some point if you go down this route
Just thought I'd share anyway as 'vehiclemodelsets.meta' can sometimes offer an alternate approach to certain specific spawn requirements. All the best

@Morgesan

I'm really not sure but I reckon here:

...\x64\audio\sfx\SCRIPT.rpf\michael_4_fireworks.awc

might be a good place to start

A quick edit to the files will answer pretty quickly whether or not they are the ones you seek. Best of luck

@kaaashi020
No promises, but if you upload your problem '.xml' map & send me the link I'll take a look at it

@xxx78
No probs

@princegaz

In 'dispatchtuning.ymt' here:

...\mods\update\update.rpf\x64\data\tune\dispatchtuning.ymt (edit this one if exists)

or here:

...\mods\x64a.rpf\data\tune\dispatchtuning.ymt (edit this one if previous does NOT exist)

there is a section like this:

		<Item type="CDispatchHelperSearchInAutomobile__Tunables">
			<Name>CDispatchHelperSearchInAutomobile</Name>
			<Constraints>
				<Item>
					<MinTimeSinceLastSpotted value="0.000000" />
					<MaxTimeSinceLastSpotted value="60.000000" />
					<MaxRadiusForMinTimeSinceLastSpotted value="100.000000" />
					<MaxRadiusForMaxTimeSinceLastSpotted value="15.000000" />
					<MaxHeight value="0.000000" />
					<MaxAngle value="3.140000" />
					<UseLastSeenPosition value="true" />
					<UseByDefault value="true" />
					<UseEnclosedSearchRegions value="true" />
				</Item>
			</Constraints>
			<MaxDistanceFromRoadNode value="40.000000" />
			<CruiseSpeed value="20.000000" />
		</Item>

Edit these (below) parameters to reduce the size of the search radius:

					<MaxRadiusForMinTimeSinceLastSpotted value="100.000000" /> (max radius, just after being spotted)
					<MaxRadiusForMaxTimeSinceLastSpotted value="15.000000" /> (max radius after 60 secs (<from '<MaxTimeSinceLastSpotted value="60.000000" />') of not being spotted)

Let me know how you get on

@eshenk
Nice one that's what I like to hear. Glad I could help bud

@eshenk
Aye, it seems Texture Toolkit just makes it's own rules a lot of the time .
The only other thing I do is I work from within the TT install folder. I found it a bit more reliable that way rather than files saved on different hard drives etc (may well just have just been pure luck it worked a bit better that way though).

@MaxLuk
Thanks