Published: October 08 2023 by
Last documented update: February 18 2024 by
In this guide, I will do my best to address the most common first person issues I've seen, and how to fix them.
Prerequisite and other relevant Guides
This guide assumes that you have an already working in-game item, and at least a basic understanding of WolvenKit.
To implement anything in this guide, you will need with the mod's files. You already have that if you're fixing your own mod (hopefully). If not, check out this guide on how to
Index
If you are modifying someone else's mod:
If you are changing someone else's mod, the easiest thing is to the same as the mod's .archive file and add all the files from the original mod. You can do that by switching to the and for archive:name_of_file
If you're creating a fix for someone else's asset, why not drop them the final files - or a link to this guide?
Problem #1: Your sleeves render behind your arms
This is probably the most common problem I've seen, and is also thankfully the easiest to fix.
Solution
Open up the (.ent) file for the item you need to fix:
Expand the components array, then find any components with Mesh in their types, and check if they require fixing. In my example project, it's both the jacket and the sleeves.
Instead of renderPlane, you can also use renderPlaneLeftArm and renderPlaneRightArm individually.
Repeat this process for any other component, as needed
When finished, save the file (either Ctrl + S or the Save button top left).
Install and test the mod in-game. If you did it correctly, your sleeves should now render properly.
Problem #2: It's in your face (#justStormtrooperThings)
To fix this problem, you need to hide your item in first person perspective.
This part of the guide will show you how to turn the entire item invisible. If you don't want that, check
Solution
This fix starts in the .yaml file (which should live under your Wolvenkit project's resources folder in the subfolder r6/tweaks, perhaps in a subfolder).
If you are editing someone else's mod, you need to copy their .yaml to your project. If you don't know which file that is, check their Nexus mod files, as it will be part of the original .zip file.
If you don't have a yaml because you're changing an in-game item for some reason, you need to start at . If you , you can stick to these parts in the rest of the guide.
Open the file in any text editor (recommended: )
Helpful documentation on .yaml files resides . Hopefully it looks something like this:
Check if there is something called $instances
Legacy variants: hiding FPP
For dynamic appearances (if the yaml has a key called $instances), go to
Switch back to Wolvenkit.
Open the file (it should have an array called appearances)
You now have two ways of hiding the item in first person:
Hiding FPP via tag
This will not work with !
Find the array tags at the end of the list.
In the panel on the right, click "add new item" (the yellow +) until you have an empt text field.
In the text field, enter EmptyAppearance:FPP
Hiding FPP via appearance definition
Find and expand the appearances array.
For each entry in there, you need to complete the following steps (the example project has only one entry).
Select each entry
Dynamic variants: Hiding FPP
For legacy appearances (if the yaml does not have a key called $instances), go to
Switch back to Wolvenkit.
Pick one of the two options below (we recommend)
Complete the section under
Hiding FPP in the .app
Open the in Wolvenkit
Open the appearances array
Select each appearance and add &camera=tpp to the name.
Hiding FPP in the mesh_entity
Open the in Wolvenkit
Open the components array
Select each component with Mesh in its type and add &camera=tpp to the name
Alternatively, you can duplicate the component and have two for different meshes. This will be covered in
Checking the root entity
If your yaml file had an $instances block, the item is already dynamic and you can skip this step.
Find and open the . If you have no idea which one it is, you can open the .csv and find the file paths in there.
Inside the file, make sure that you have a DynamicAppearance entry in your tags array (for a full guide with screenshot, see -> )
If you don't, add it. Congratulations, you're good to go!
Testing
Save and close the file. Repeat the whole process for any other items that need to be obliterated in first person. Install and test. If all went well, no more obstructed vision!
Problem #3: Partial hiding (#justDraculaThings)
Fixing this is very similar to Problem #2, just with a few extra steps.
Solution
Create an additional FPP appearance by following the steps in . Skip 2.4.3 and 2.4.4.
The depotPath should point at the same .app file as the &TPP appearance.
Change the value for appearanceName. For example, add _fpp
Open your .app file and expand the appearances array.
You need to repeat the following steps for every appearance in the .app.
Select an appearance and duplicate it
Change its name to correspond to the appearanceName that you used in your root entity (Step 3)
At this point, it can be done in a few ways, depending on some factors:
Finding the right submesh
Open up the appearance's partsValue array
Open the .ent file that is linked inside
In the .ent file, open the components array and check any component with Mesh in its name:\
In the right-hand panel, you will see a list of checkboxes.
If there is only one submesh, you need to edit it in Blender to split off or delete the offending parts - complete the section before proceeding. I'll wait.
Toggle them off until the part that is in your face turns invisible. In my example, submesh 01 hides the upper collar.
Remember the number (01 in the example below)
Proceed to the section for .
Chunk Masks
You can learn more about chunk masks under -> . This is not necessary for the purpose of this guide.
Switch back to the appearance (.app) file
Expand your first person appearance.
Expand the partsOverrides array. If it's empty, click on the array itself, then in the right pane, click create item in array.
Optional: If you need to hide more parts or affect more components/meshes, rinse and repeat.
Save the appearance (.app) file and install the mod to test. If all went well, there should no longer be parts clipping into view.
Creating a second mesh
The clean way to do this is to split the original mesh into submeshes, which you can then hide via chunkmasks. If you want to do that, skip straight to
To show a different item (one with the clipping bits removed) in first person perspective, we need to create a second .mesh file and a corresponding meshentity .ent that we can display. This guide will show you how.
Duplicate the .mesh file that's clipping in first person. For my example, I'm using the jacket mesh
Duplicate the meshentity .ent file that belongs to the .mesh file.
In the .app file, open your first person appearance.
Add a partsOverride by following the steps under (skip step 9)
Change the depotPath to your new _fpp meshentity file.
Save and close the .app – it is now pointing at your new _fpp meshentity.
In the _fpp meshentity file, open the components array
Select the component with Mesh in its name, open it and change the depotPath for the mesh to your new _fpp mesh file.
Save and close the .ent - it is now pointing at your _fpp mesh.
Editing the .mesh
For the next step, we need to export our .mesh file and edit it. You can use any 3d editing program, but this guide will use and the .
Optional, but recommended: If you don't have the installed, do that now.
In Wolvenkit, find the
Export your _fpp .mesh file.
Now, hit up the page and edit your mesh.
When you are done, use the to import back the .glb file.
If you stuck to the guide, you shouldn't run into any errors. If you do, check the page, or reach out to us on in #mod-dev-chat.
the project
???
Profit
Technical detes
for a mesh to disappear in FPP we must set the component's visibilityAnimationParam = n"invisible_in_fpp"
You might have to hunt around to find the right component, depending on how many there are.
Scroll down and find the array renderingPlaneAnimationParam, which will most likely be grayed out.
Click on it. In the right pane, change None to renderPlane.
Make sure to follow the same capitalization, otherwise it won't work!
. If yes, the mod is using
and you are done here — go to
Find the line appearanceSuffixes. IIf it is missing or empty,do not add it – use Dynamic variants: Hiding FPP instead.
If you have itemsFactoryAppearanceSuffix.Camera in your appearanceSuffixes array, you are dealing with Legacy variants: hiding FPP.
Hopefully, you won't find this in there. If you do: be careful, this mod is an antiquity! :D
Duplicate it via right-click menu
For the old entry: Change its name to end in &TPP (third person perspective)
For the new entry:
Change the name to end in &FPP (first person camera)
Change the depotPath to base\characters\appearances\player\items\empty_appearance.app
change the appearanceName to default
Should look like this now.
You might have to hunt around to find the right component, depending on how many there are.
Open the linked .mesh file in Wolvenkit
Select Mesh Preview
Select componentsOverrides by clicking on it.
In the right panel, click on the yellow + to create a new item in array.
Open up the mesh entity (.ent) file and expand the components array.
Find the component that needs its parts hidden and copy the name. In my example, the component is examplejacket1_fur.
Back to the appearance (.app) file. Paste the component's name from the mesh entity into the componentName field.
Click on chunkMask and uncheck the submeshes that you want to hide. (You found out which ones that were in Finding the right submesh - In my example it was submesh 01)
Change their names to end in _fpp to indicate that this is a mesh for the
first person perspective
(or do whatever you want, but this guide assumes...)
If the export throws an error, uncheck the Export Materials option in the settings panel (you don't need it)
You now have a .glb file in your project's raw folder. You can find it like this:
Switch the Project Explorer to the source or raw tab
