@Jayden585

Hi. A possible conflict could be the <PropsName> defined in peds.ymt no longer corresponding with the new edited data in the ped's own .ymt.

@MetaGTA

Hi.

I am one of the few idiots, hehe, who have actually invested a not insignificant portion of time, into manipulating single clips via CodeWalker's .ycd export options.

This has given me an opportunity to edit the default rootbone position offsets of different seated animations, to add custom ptfx and audio to anims, and to copy one or several .clip entries from .ycd A to ycd B, helping me create my own custom .ycds.

However...as slick so succinctly put it, that is really all there is to it, at least at this point.

Yes, a new script could change that, but unfortunately, nobody with the required set of skills is currently working on such a script.

For what it is worth though, most of the flags, or rather Tags and Properties, with attributes, do not seem to directly control the animations themselves, but rather, as you said yourself, various types of "events".

I have resolved quite a few of .ycd hashes, and concluded that everything(probably) is in lowercase, and that all the aforementioned events mostly are related to inverse kinematics,prop creation, audio and ptfx.

So if, and that's a big if, such a script would become available, we would already be well on our way towards a more comprehensive level of animation modding.

Have a nice day.

@a63nt-5m1th

It's as simple as it can possibly be. You just search for the fragment you need in the RPF explorer. Then you choose Export XML, edit what you want to edit, and then you choose Import XML.

The RPF explorer inside of CodeWalker is LIGHTNING fast, and among many other advantages, it gives you the option of instantly sorting your search results. CodeWalker also has binary search and World search options and much much more.

I hope you are going to have just the amount of fun you are hoping for.

lol

Modifiver

@a63nt-5m1th @PermissionToLand

Hi.

You can export the fragment to .xml using Codewalker, and then edit the shaders in the xml.

@InfiniteQuestion

It's positive to see more people researching this area of GTA V modding.

Here is a some additional information.

You guys have to remember how interconnected/interdependent everything is.

To REALLY control ambient vehicle densities, both parked and driving, requires comprehensive configuration of both gameconfig.xml, zonebind.ymt, scenarios.meta, settings.xml(Documents), popcycle.dat, vehicles.meta, pedpersonality.ymt and popgroups.ymt.

And even ALL the individual path .ynds, plus ALL the individual Navmesh .ynvs. if you want to adjust all this on a "per street/neighbourhood" level.

Beginning with changing values in the gameconfig is a really good start though, and I wish you nothing but good luck going forward.

Have a nice day and happy modding.

Modifiver.

@epoqx @a63nt-5m1th

Short and sweet version.

A lot of assembly required.

The most detailed way to edit the light coming from a prop is to edit the prop itself. Each street light prop model has its own Light section in its .ydr/.yft.

First you export the file to xml from CodeWalker and then you keep editing until you are content with the result.

This will no doubt require a substantial amount of trial and error, as well as having to initially deal with a somewhat steep learning curve.

Alternatively, the above can be achieved with 3ds/zmodeler.

So yes, you will no doubt feel like this :

And then this :

But every time you pull yourself together, and move away from the burning wreckage :

You learn a little more, get a little better, and eventually you will reach you goal.

Also, considering the way the melee system is set up, this type of brute forcing it via coding, would never naturally fit into the game.

The melee system (Action folder) is a surprisingly deep and extremely interdependent system, containing 100s of settings and conditions, spread throughout more than 10 files.

In the overhaul of the game that I am working on, I am also rebuilding melee combat from the ground up, meaning changing everything from ycd editing the speed, blending and duration of animations to bringing back proper shovinh, both armed and unarmed.

So in short. Melee in V needs to be changed natively via file edits, not a script.

Brilliant work, man.

I am not sure that I follow though. Will the final iteration have both custom vehicle and ped popgroups or only vehicle groups?

To me ped variety is essential to my overhaul since I use a ton of rare peds in a number of custom scenario types and ambient wandering entries.

Once again, thank you for your hard work. It is greatly appreciated.

First off, congrats on the release and for the initiative as a whole.

What I would suggest is adding full support of custom popgroups/popcycles entries. Including both vehicles and pedestrians.

My current project in the works contains numerous custom groups in both files and I would be very grateful for a more efficient way to streamline part of my workload that way.

Have a nice day.

Hi.

@epoqx @a63nt-5m1th

Adding on to what is already going on in here.

The most reliable way to force a vehicle to spawn, outside of writing a script, is simply to use Codewalker to create a new custom cluster of highprio spawns in your chosen location. It can be a single vehicle model or it can be a set with a pool of x number of vehicles(vanilla,dlc,custom,anything). You can also freely choose between having the vehicle spawn empty, spawn with a driver and/or passengers, and when/if you want the vehicle to drive away from its fixed spawn coords and become part of the normal traffic flow.

When you test this to the point of overkill it looks like this :

and...

Modifiver is coming in 2020