# First Person Perspective Fixes **Published:** October 08 2023 by [FronkenZeepa](https://app.gitbook.com/u/pj9Ccv6IrMVhmNUW9HVbn6CYZ2B2 "mention")\ **Last documented update:** February 18 2024 by [mana vortex](https://app.gitbook.com/u/NfZBoxGegfUqB33J9HXuCs6PVaC3 "mention") 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. * [WolvenKit](https://wiki.redmodding.org/wolvenkit/readme) * [Adding new items](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators/modding-guides/items-equipment/adding-new-items) * [File Formats](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators/files-and-what-they-do/file-formats) * [Exporting and importing meshes](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators/3d-modelling/exporting-and-importing-meshes) {% hint style="warning" %} To implement anything in this guide, you will need [a Wolvenkit project](https://app.gitbook.com/s/-MP_ozZVx2gRZUPXkd4r/wolvenkit-app/usage/wolvenkit-projects) 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 [analyze other mods!](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators/modding-guides/analysing-other-mods) {% endhint %} ### Index * [Your sleeves render behind your arms](#problem-1-your-sleeves-render-behind-your-arms) * [Head/Face/Glasses/Mask/Helmet visible and obstructing vision](#problem-2-head-face-glasses-mask-helmet-visible-and-obstructing-vision.) * [You only need to hide a certain part of the clothing, like the collar/fur/stitching](#problem-3-you-only-need-to-hide-a-certain-part-of-the-clothing-like-the-collar-fur-stitching.) {% hint style="warning" %} **If you are modifying someone else's mod**: If you are changing someone else's mod, the easiest thing is to [name your Wolvenkit project](https://app.gitbook.com/s/-MP_ozZVx2gRZUPXkd4r/wolvenkit-app/usage/wolvenkit-projects#project-naming-and-mod-load-order) 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 [Mod Browser](https://app.gitbook.com/s/-MP_ozZVx2gRZUPXkd4r/wolvenkit-app/editor/asset-browser#mod-browser) and [searching](https://app.gitbook.com/s/-MP_ozZVx2gRZUPXkd4r/wolvenkit-app/usage/wolvenkit-search-finding-files) for `archive:name_of_file` For more information on this, read [here](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/recolours-and-refits/r-and-r-your-own-wolvenkit-project#a-full-repack). {% endhint %} {% hint style="success" %} If you're creating a fix for someone else's asset, why not drop them the final files - or a link to this guide? {% endhint %} ## Problem #1: Your sleeves render *behind* your arms

(This can also present itself as rendering behind the body when you look down, for shirts, pants, shoes, etc.)

This is probably the most common problem I've seen, and is also thankfully the easiest to fix. ### Solution 1. Open up the [mesh entity](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators-theory/files-and-what-they-do/file-formats/entity-.ent-files#mesh-component-entity-simple-entity) (`.ent`) file for the item you need to fix:

There are no appearances in a mesh entity file!

2. Expand the `components` array, then find any `component`s with `Mesh` in their types, and check if they require fixing. In my example project, it's both the jacket and the sleeves.

You might have to hunt around to find the right component, depending on how many there are.

3. Scroll down and find the array `renderingPlaneAnimationParam`*,* which will most likely be grayed out.

4. Click on it. In the right pane, change `None` to renderPlane.

Make sure to follow the same capitalization, otherwise it won't work!

{% hint style="info" %} Instead of `renderPlane`, you can also use `renderPlaneLeftArm` and `renderPlaneRightArm` individually. {% endhint %} 5. Repeat this process for any other component, as needed 6. When finished, save the file (either Ctrl + S or the Save button top left). 7. 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)

Still better than wearing a *real* helmet.

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 [#problem-3-partial-hiding-justdraculathings](#problem-3-partial-hiding-justdraculathings "mention") ### Solution 1. 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. {% hint style="info" %} If you don't have a yaml because you're changing an in-game item for some reason, you need to start at [#fixing-the-root-entity](#fixing-the-root-entity "mention"). If you [convert it to a dynamic appearance](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/adding-new-items/archivexl-dynamic-variants#the-root_entity), you can stick to these parts in the rest of the guide. {% endhint %} 2. Open the file in any text editor (recommended: [**Notepad++**](https://notepad-plus-plus.org/downloads/)) 3. Helpful documentation on .yaml files resides [here](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators/modding-guides/items-equipment/adding-new-items/archive-xl-item-structure-explained#the-control-file-yourmodname.yaml). Hopefully it looks something like this:

This is my example .yaml file with only *one* entry. Yours might have more.

4. Check if there is something called `$instances`. If yes, the mod is using [archivexl-dynamic-variants](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/items-equipment/adding-new-items/archivexl-dynamic-variants "mention") and you are done here — go to [#dynamic-variants-hiding-fpp](#dynamic-variants-hiding-fpp "mention") 5. Find the line `appearanceSuffixes`*. IIf it is missing or empty,* **do not add it** – use [#dynamic-variants-hiding-fpp](#dynamic-variants-hiding-fpp "mention") instead. 6. If you have `itemsFactoryAppearanceSuffix.Camera` in your appearanceSuffixes array, you are dealing with [#legacy-variants-hiding-fpp](#legacy-variants-hiding-fpp "mention").

Hopefully, you won't find this in there. If you do: be careful, this mod is an antiquity! :D

### Legacy variants: hiding FPP {% hint style="info" %} For dynamic appearances (if the yaml has a key called `$instances`), go to [#dynamic-variants-hiding-fpp](#dynamic-variants-hiding-fpp "mention") {% endhint %} 1. Switch back to Wolvenkit. 2. Open the [root entity (.ent)](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators-theory/files-and-what-they-do/file-formats/entity-.ent-files#root-entity) file (it should have an array called `appearances`)

You now have two ways of hiding the item in first person: #### Hiding FPP via tag {% hint style="warning" %} This will not work with [archivexl-dynamic-variants](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/items-equipment/adding-new-items/archivexl-dynamic-variants "mention")! {% endhint %} 1. Find the array `tags` at the end of the list. 2. In the panel on the right, click "add new item" (the yellow +) until you have an empt text field. 3. In the text field, enter `EmptyAppearance:FPP` #### Hiding FPP via appearance definition 1. Find and expand the `appearances` array. 2. For each entry in there, you need to complete the following steps (the example project has only one entry). 1. Select each entry 2. Duplicate it via right-click menu 3. For the old entry: Change its `name` to end in `&TPP` (third person perspective) 4. For the new entry: 1. Change the `name` to end in `&FPP` (first person camera) 2. Change the depotPath to `base\characters\appearances\player\items\empty_appearance.app` 3. change the `appearanceName` to `default`

### Dynamic variants: Hiding FPP {% hint style="info" %} For legacy appearances (if the yaml does not have a key called `$instances`), go to [#legacy-variants-hiding-fpp](#legacy-variants-hiding-fpp "mention") {% endhint %} 1. Switch back to Wolvenkit. 2. Pick **one of the two** options below (we recommend[#hiding-fpp-in-the-.app](#hiding-fpp-in-the-.app "mention")) 3. Complete the section under [#checking-the-root-entity](#checking-the-root-entity "mention") #### Hiding FPP in the .app 1. Open the [.app file](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators-theory/files-and-what-they-do/file-formats/appearance-.app-files) in Wolvenkit 2. Open the `appearances` array 3. Select each appearance and add `&camera=tpp` to the name.

#### Hiding FPP in the mesh\_entity 1. Open the [https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators-theory/files-and-what-they-do/file-formats/entity-.ent-files#mesh-component-entity-simple-entity](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators-theory/files-and-what-they-do/file-formats/entity-.ent-files#mesh-component-entity-simple-entity "mention") in Wolvenkit 2. Open the `components` array 3. Select each component with `Mesh` in its type and add `&camera=tpp` to the name

{% hint style="info" %} Alternatively, you can duplicate the component and have two for different meshes. This will be covered in [#problem-3-partial-hiding-justdraculathings](#problem-3-partial-hiding-justdraculathings "mention") {% endhint %} #### Checking the root entity {% hint style="info" %} If your `yaml` file had an `$instances` block, the item is already dynamic and you can skip this step. {% endhint %} 1. Find and open the [root entity](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators-theory/files-and-what-they-do/file-formats/entity-.ent-files#root-entity). If you have no idea which one it is, you can open the .csv and find the file paths in there. 2. Inside the file, make sure that you have a **`DynamicAppearance`** entry in your tags array (for a full guide with screenshot, see [archivexl-dynamic-variants](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/items-equipment/adding-new-items/archivexl-dynamic-variants "mention") -> [#the-root\_entity](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/adding-new-items/archivexl-dynamic-variants#the-root_entity "mention")) 3. 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)

I probably could have chosen a better example, but I'm sure you can see the big clump of fur on the right.

Fixing this is very similar to Problem #2, just with a few extra steps. ### Solution 1. Create an additional FPP appearance by following the steps in [#hiding-fpp-via-appearance-definition](#hiding-fpp-via-appearance-definition "mention"). **Skip 2.4.3 and 2.4.4**. 2. The `depotPath` should point at the same .app file as the \&TPP appearance. 3. Change the value for appearanceName. For example, add \_fpp

4. Open your .app file and expand the `appearances` array. {% hint style="info" %} You need to repeat the following steps for every appearance in the .app. {% endhint %} 5. Select an appearance and duplicate it 6. 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 1. Open up the appearance's `partsValue` array 2. Open the .ent file that is linked inside 3. In the .ent file, open the `components` array and check any component with Mesh in its name:\\

4. Open the linked .mesh file in Wolvenkit 5. Select `Mesh Preview`

6. In the right-hand panel, you will see a list of checkboxes. {% hint style="info" %} If there is only one submesh, you need to edit it in Blender to split off or delete the offending parts - complete the section [#creating-a-second-.mesh](#creating-a-second-.mesh "mention") before proceeding. I'll wait. {% endhint %} 7. Toggle them off until the part that is in your face turns invisible. In my example, submesh 01 hides the upper collar. 8. Remember the number (01 in the example below)

9. Proceed to the section for [*Chunk Masks*](#chunk-masks)*.* ### Chunk Masks {% hint style="info" %} You can learn more about chunk masks under [https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators-theory/files-and-what-they-do/file-formats/3d-objects-.mesh-files](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators-theory/files-and-what-they-do/file-formats/3d-objects-.mesh-files "mention") -> [submeshes-materials-and-chunks](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/files-and-what-they-do/file-formats/3d-objects-.mesh-files/submeshes-materials-and-chunks "mention"). This is not necessary for the purpose of this guide. {% endhint %} 1. Switch back to the appearance (.app) file 2. Expand your first person appearance. 3. Expand the `partsOverrides` array. If it's empty, click on the array itself, then in the right pane, click create item in array. 4. Select `componentsOverrides` by clicking on it. 5. In the right panel, click on the yellow + to create a new item in array. 6. Open up the mesh entity (.ent) file and expand the `components` array. 7. Find the component that needs its parts hidden and copy the name. In my example, the component is `examplejacket1_fur`*.*

8. Back to the appearance (.app) file. Paste the component's name from the mesh entity into the *`componentName`* field.

9. Click on `chunkMask` and uncheck the submeshes that you want to hide. (You found out which ones that were in [#finding-the-right-submesh](#finding-the-right-submesh "mention") - In my example it was submesh 01)

10. **Optional**: If you need to hide more parts or affect more components/meshes, rinse and repeat. 11. Save the appearance (.app) file and install the mod to test. If all went well, there should no longer be parts clipping into view.

Results may vary depending on the item, but this is much better, no?

### Creating a second mesh {% hint style="info" %} 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 [#editing-the-.mesh](#editing-the-.mesh "mention") {% endhint %} 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. 1. Duplicate the `.mesh` file that's clipping in first person. For my example, I'm using the jacket mesh 2. Duplicate the meshentity `.ent` file that belongs to the `.mesh` file. 3. 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...) 4. ```

``` 5. In the `.app` file, open your first person appearance. 6. Add a `partsOverride` by following the steps under [#chunk-masks](#chunk-masks "mention") (skip step 9) 7. Change the depotPath to your new \_fpp meshentity file. 8. ```

``` 9. Save and close the .app – it is now pointing at your new \_fpp meshentity. 10. In the \_fpp meshentity file, open the components array 11. Select the component with Mesh in its name, open it and change the depotPath for the mesh to your new \_fpp mesh file. 12. ```

``` 13. 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 [Blender 3.6](https://www.blender.org/download/) and the [wolvenkit-blender-io-suite](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/modding-tools/wolvenkit-blender-io-suite "mention"). 1. Optional, but recommended: If you don't have the [wolvenkit-blender-io-suite](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/modding-tools/wolvenkit-blender-io-suite "mention") installed, do that now. 2. In Wolvenkit, find the [Export Tool](https://app.gitbook.com/s/-MP_ozZVx2gRZUPXkd4r/wolvenkit-app/usage/import-export) 3. Export your \_fpp .mesh file. * If the export throws an error, uncheck the Export Materials option in the settings panel (you don't need it) 4. You now have a `.glb` file in your project's `raw` folder. You can find it like this: 1. Switch the Project Explorer to the `source` or `raw` tab 2. Right-click on your exported file 3. Select the option to show it in Windows Explorer Now, hit up the [3d-editing-submeshes](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/3d-modelling/3d-editing-submeshes "mention") page and edit your mesh. When you are done, use the [Wolvenkit Import Tool](https://app.gitbook.com/s/-MP_ozZVx2gRZUPXkd4r/wolvenkit-app/tools/tools-import-export#import-tool) to import back the .glb file.

{% hint style="info" %} If you stuck to the guide, you shouldn't run into any errors. If you do, check the [troubleshooting-your-mesh-edits](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/3d-modelling/troubleshooting-your-mesh-edits "mention") page, or reach out to us on [Discord](https://discord.gg/redmodding) in `#mod-dev-chat.` {% endhint %} 5. [Install and launch](https://app.gitbook.com/s/-MP_ozZVx2gRZUPXkd4r/wolvenkit-app/menu/toolbar#install-and-launch) the project 6. ??? 7. Profit ## Technical detes > for a mesh to disappear in FPP we must set the component's `visibilityAnimationParam = n"invisible_in_fpp"` --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/items-equipment/first-person-perspective-fixes.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.