Hey, so a lot
of VRChat tutorials are really bad. Today we're going to be going over
attaching accessories and clothing to avatars. A lot of old tutorials have you do this
in literally the worst possible way. So I felt like making a modern tutorial that takes into account
the newer methods would be very helpful. We're going to start in the VR
chat creator companion. This is the new way the VRC distributes
it’s SDKs and it's also just fairly useful. If you don't like this, keep in mind
you only have to use it to create the project. If you're used to just opening
your Unity hub and launching the project
there, you can still do that. And that's what I most often do, but
I just create it in the creator companion. The other thing
that's really helpful about this is if you go down to settings
and packages, you can add community repositories. So VRC Fury is what
we're going to be using today for the Nondestructive workflow. I highly, highly recommend
going to their GitHub, copying the link that they give you clicking and repository,
pasting it in here and here. And hit add. Of course it doesn't work for me
because I've already added it. All right. And once you've done that, you can just go
to projects, create a new one. Avatars. Give it a name, create it, and then we can just hit. Plus on this VRC Fury, Gesture
Manager is also probably recommended one. Then once that's done,
just hit open project. All right. Now that we're in our unity project,
I would just go ahead and import all of the things that we want to use,
including the base and accessories we'd like to attach. If you're doing this on
an existing project and you installed VRC, Fury or Thry’s tools via
alternate means listed on their github*, you can verify that they're installed
by going up to tools. You can see that we have the VRC Fury menu
and we have Thry’s menu. So both of those are working. I'm gonna go ahead and open up the included scene
that comes the Nardoragon package, and it already has a pre-setup avatar
ready for me to go. Most Avatar bases
come with some sort of set up like this. You just need to find wherever it is. Sometimes it's a prefab
that you drag into an existing scene. Sometimes
it's a scene that's already set up. And I also
downloaded this free hoodie off of Gumroad. There's a link in the description. It also comes already set up with a VRC Fury script, set up
ready to go to be attached to an avatar. When you have a prefab like this that's already set up with VRC. Furey The only thing required in order
to install it to your avatar is to place it
underneath the avatar root, which is whichever component contains your avatar descriptor. And there you go. You are done. It is ready to go. It is ready to upload, if I uploaded it- this
that would be automatically merged, etc. and nothing else needs to be touched in
90% of cases in order for this to work. The one thing that I do caution you about
is when you have pre set up VRC fury assets, do not turn it off, leave it in whatever state it is. And that's just going to give you the
least likely chance of anything breaking. If you're annoyed by however it looks
when it is attached to your avatar and you would like to not see it. You can go over here in the hierarchy and you can turn off the visibility
by clicking the little eyeball icon. So that's really easy. But what if we have a prefab
which is not set up with the VRC fury? These tech pants come with a prefab,
which is already set up with a material and some physbones and stuff,
but no VRC fury component. So we got to set that up ourself. First: Let's just go ahead and take this
and put it underneath the root of our avatar. Let’s add
a VRC fury component. Two things are absolutely necessary
in order for this to work properly
with any Avatar base. The first is an armature link, and in the armature link
we need to put our root bone, which is usually for things
like pants and jackets, a hip bone. But in a case of something
that only goes on the arm, the root bone may be like upper arm
or some other bone, in which case you'd have to select
the corresponding bone on the avatar. Whenever you have long menus like this,
you can just type in the first letter and scroll
through all the options if you need to. But for this, it's just the hip bone. If you get some debug info down here
that lets you know that
you know it's detected the scales and it's adding a few as children,
everything is working correctly. These bones are added as children
because they are bones that do not exist on the base armature
and they are just the ones that are used for physbones,
for the little straps. The other thing we do is
we add a BlendShape Link, and so this actually makes sure
that the blend shapes on your clothing, match that on the base. We're going to put in the name of the skinned mesh
object on the avatar. This is most often “Body”,
but whatever part of your avatar that is, well, the body
with all of the customization blendshapes that's what you put down here
into the BlendShape Link we also need to add whatever skin mesh
we're linking. And for that, that is the tech pants. So we are going to drag in Tech Pants. And if we get debug info down here
saying that Linked blend shapes are leg size, blah blah, blah, blah blah, it's
all working properly just like that. This asset's ready to go. You can create a toggle
however you prefer, which with whatever method you prefer,
as long as you're not turning off the component
that contains the VRC Fury script, just make sure that you turn on and off
the mesh as opposed to that. I'm going to show you how to do it
with VRC Fury. It's straightforward and simple. You just go down here add a toggle. Sometimes the names in vrc fury
are a little confusing. If you ever don't know what something is
and there's a little question mark by it, you can click it and it gives you a short
description of what this is. So for this menu path, if I wanted just a
toggle named pants, I just type in pants. If I want pants to be underneath
a menu called clothing,
I just type in clothing slash pants. And then if I were to create
another toggle somewhere else and use this same prefix,
it would show up in the same menu. I'm also going to go to options here, and I'm going to say
that this toggle is saved between worlds. Click Add Action and we're going to say
we're doing an object toggle drag in our skinned mesh and then this is ready to go if you want this to be defaulted on, then you can default on
and you will want to leave this on. If you instead don't want to default
on, you want a default off. I would go in here
and I would disable the skinned mesh and then leave Default on, off. Now, in order to test this without
leaving the Unity editor, we can go. We can click on our root of our avatar. Click on Tools, VRCFury,
build an editor test copy. This may take a second
and you also may get this pop up. I have not had any issues
with just letting VRC Fury auto fix this. In most cases it just works. But if it does cause issues,
you can just skip this step. I'm going to click Auto Fix. Okay. Now with our test avatar built,
I'm going to disable the original. This just means
that it won't be simulated. And in order to test
that everything is working, we want to use
whichever emulator of your choice. If you're using GestureManager
as installed via creator companion or if you're using Lyuma,
however you want to do it. I'm just going to enter play mode
since I'm using GestureManager and we can see that
we have our handsome Nardoragon and our clothing menu exists
which contains the pants toggle, which if I turn on right there and our
physbones all work we can also, for example in the Nardoragon
go to customizations, and if we turn on the female toggle
the pants, follow the blend shape, change of the base for the hoodie,
it adds its own menu. We can turn it on the turn on the hood up. All these included
animations all seem to work. Last thing I want to touch on before I close this off for VRC
Fury is nondestructive. What this means
is that since we're not directly making any changes to the FX layer or the menu or parameters
that are set up in your avatar descriptor and everything is built on upload
using the V or C Fury script, these can be easily removed
and added at any point in time. So I wanted to upload
a version of this avatar without the hoodie Prefab included. All I need do for that is to drag it
out of the avatar package. It's also nice
because it's easy to debug issues if, for example, I've had issues with this
hoodie in the past where face tracking wouldn't work on the Nardoragon
when the hoodie was included, I was only able to figure that out
because I was very easily able to pull the hoodie prefab out of the avatar,
build it and find that it worked. This is not the case with things like Avatar 3.0 Manager,
which is a destructive workflow. It directly edits the FX layer and makes permanent changes to them. Another thing to note though,
is that however, since this is nondestructive
and we're not directly editing things until we upload,
when you look at your performance ranking, it will not always be accurate
to what will actually be uploaded. For example,
the bone count here says 197 Bones. This includes all of the bones that will be merged. See, if I look at the test copy, it only has 189 bones because those bones
are actually being merged. That's just something to keep in mind
is that sometimes what you see here in the VRC SDK
window is not totally accurate. All right. I hope that was helpful. If you managed to get something useful out of this,
consider appeasing the YouTube algorithms so that others can also find this video
or sharing it around. In the next episode, I would like to start
covering some blender stuff very specifically relating to VRC. And yeah,
I plan to make a series of these tutorials that will cover everything
from optimization to doing custom kit
bashes and other sort of things. And yeah, thanks for watching.
