# AMM: Custom Props

## Summary <a href="#summary" id="summary"></a>

**Published:** April 2023 by **@manavortex**\
**Last documented update:** Feb 18 2025 by **@manavortex**

This guide will teach you how to create AMM props in two variants:

* the old way by using a [mesh entity](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/entity-.ent-files#mesh-component-entity-simple-entity) with a [.mesh](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/3d-objects-.mesh-files) file with only one appearance
* customizable by chaining a [`root entity`](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/entity-.ent-files#root-entity), an [`.app`](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/appearance-.app-files), and a [`.mesh`](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/3d-objects-.mesh-files) file with multiple appearances

Its focus is on the **file structure** and the **relations between the files**.

{% hint style="danger" %}
For another guide regarding custom props, check [textured-items-and-cyberpunk-materials](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/textures-and-luts/textured-items-and-cyberpunk-materials "mention") – it will focus on the possibilities you have with different materials, while this guide focuses on the process and the structure.
{% endhint %}

### Wait, this isn't what I want!

* To register existing props or items with WorldBuilder, check [adding-custom-resources-props](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/world-editing/object-spawner/features-and-guides/adding-custom-resources-props "mention")
* If you want to play around with materials and an existing prop, check [textured-items-and-cyberpunk-materials](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/textures-and-luts/textured-items-and-cyberpunk-materials "mention")
* If you want to enable collisions, see [enable-embedded-collisions](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/world-editing/miscellaneous/enable-embedded-collisions "mention")
* If you want to make meshes out of 2d textures, see [your-image-as-custom-mesh](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/3d-modelling/your-image-as-custom-mesh "mention")
* … or use the wiki's AI-assisted search function, or simply poke around
* If you want to use a custom model (Or other resource type) with World Builder, see [Adding custom resources](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/world-editing/object-spawner/features-and-guides/adding-custom-resources-props)

### Video Guide

For the tutorial's full written version, just keep reading. Please keep in mind that video guides will become outdated faster than wikis!

{% embed url="<https://youtu.be/3nwxM254HTI>" %}

## Where to find models

Many websites host free stuff; you can find the largest archives below. Browse [this list](https://www.3printr.com/3dmodels/categories/free-models) for a more comprehensive collection, or use the following queries in your search engine of choice:

```
thing_I_want free 3d model
thing_I_want free fbx file
```

For game design or rendering, usually textured:

* [Sketchfab](https://sketchfab.com)
* [TurboSquid](https://www.turbosquid.com/) (there's a drop-down menu on the left-hand side where you can select to search for free models!)
* [CGTrader](https://cgtrader.com)
* [Renderosity](https://www.renderosity.com/freestuff)
* [Daz3D](https://www.daz3d.com/free-3d-models)
* [ArtStation](https://www.artstation.com/marketplace/game-dev?section=free\&page=4)
* [RenderHub](https://www.renderhub.com/free-3d-models)

For 3d printing, usually not textured:

* [thingyverse](https://www.thingiverse.com/)
* [MyMiniFactory](https://www.myminifactory.com/)
* [Pinshape](https://pinshape.com/)

## **Requirements:**

* Cyberpunk 2077 game version
* [WolvenKit](https://github.com/WolvenKit/WolvenKit-nightly-releases/releases) >= 8.12 for 2.1, 8.8.1 for 1.6.1 (DLSS)
* [Appearance Menu Mod](https://www.nexusmods.com/cyberpunk2077/mods/790) (>= version 2.1, anything earlier won't have customizable appearances)
* Optional, but recommended if you want to create multiple props: [Notepad++](https://notepad-plus-plus.org/downloads/)

**Level of difficulty:** You know how to read.

## Setting up the project

This section will tell you how to get the files, then give you an [explanation](#explanation-what-did-you-just-download) of what they do and finally show you a [diagram](#diagram) on how they hang together.

{% hint style="success" %}
At any part during the process, you can [install the mod](https://app.gitbook.com/s/-MP_ozZVx2gRZUPXkd4r/wolvenkit-app/menu/toolbar#install-and-launch) and launch the game to spawn the props with AMM. In the decor tab, search for

`Tutorial item`\
`Tutorial item (customizable)`
{% endhint %}

1. Create a [project in Wolvenkit](https://app.gitbook.com/s/-MP_ozZVx2gRZUPXkd4r/wolvenkit-app/usage/wolvenkit-projects) and give it a name. This will later be the name of your archive file.
2. Download the AMM prop template from [Nexus](https://www.nexusmods.com/cyberpunk2077/mods/8011). Download **the complete source folder**, as it will have the files as depicted below.
3. Prepare your Wolvenkit project by [merging the source folder](#user-content-fn-1)[^1] you downloaded with the one from your project. By the end of it, you should have the following files:

{% hint style="warning" %}
If you want to move or rename anything, please do it as specified in [moving-and-renaming-in-existing-projects](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/items-equipment/moving-and-renaming-in-existing-projects "mention"). Doing anything else will **break the mod**.
{% endhint %}

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-9e3320bf8f85ac5370d67b284d3cfec42a59771d%2Famm_props_structure.png?alt=media" alt=""><figcaption><p>For an overview of how these files hang together, theck the <a data-mention href="#diagram">#diagram</a> section of this guide.</p></figcaption></figure>

4. Optional, but recommended: Start the game and spawn the props, as in the green hint box at [the beginning of this section](#setting-up-the-project).
5. Optional, but very recommended: Read through the next section to understand what's going on here.
6. If you're the more hands-on kind of learner, skip to [#using-other-meshes](#using-other-meshes "mention") or [#creating-another-prop](#creating-another-prop "mention") to fuck around and find out.

{% hint style="info" %}
The first part of the structure is up to you, although for the sake of the tutorial you might want to stick to it. There's a section later on [how to change your paths](#the-final-touches).

The second part (under "resources") is where AMM will look for custom props. You can't change it other than creating subfolders under "Custom Props".
{% endhint %}

### Explanation: what did you just download?

{% hint style="success" %}
This section gives an explanation of the included files, explaining the difference in file structure between props with vs without variants.

If you don't want to know this, you can skip ahead to [#using-other-meshes](#using-other-meshes "mention") or [#creating-another-prop](#creating-another-prop "mention") to get crackin', or check the [diagram](#diagram) to see how the files connect.
{% endhint %}

#### LUA file

This file registers your prop with AMM. File content looks like this:

```lua
return {
  -- put your name. Unless that's what you're called, not judging.
  modder = "your_name_here",
  
  -- you're supposed to put your _OWN_ thing here
  unique_identifier = "amm_custom_props_tutorial",

  props = {
    {
      name = "Tutorial item (customizable)",
      path = "tutorial\\amm_props\\template\\template.ent",
      category = "Misc",
      distanceFromGround = 1,
      appearances = {
          "template_item_textured",
          "template_item_multilayered",
      }
    }, 
    {
      name = "Tutorial item",
      path = "tutorial\\amm_props\\template_no_variants\\template_no_variants.ent",
      category = "Misc",
      distanceFromGround = 1,
    },
  }
}
```

Without a `lua` file, AMM won't know about your props, and thus can't spawn them.

Here's what the lines do:

<table data-header-hidden><thead><tr><th width="237"></th><th></th></tr></thead><tbody><tr><td><code>name</code></td><td>what you search for in AMM</td></tr><tr><td><code>category</code></td><td>what AMM sorty by (you can only reuse exisitng categories)</td></tr><tr><td><code>distanceFromGround</code></td><td>how far away from the ground should your prop be? (This moves the origin in Blender's 3d viewport)</td></tr><tr><td><code>appearances</code></td><td>If you're using a root entity, these are the appearance names to switch through and the entries in AMM's "appearance" dropdown / spawn tab</td></tr></tbody></table>

{% hint style="success" %}
When you edit the .lua, it's usually enough to `reload all mods` in CET.
{% endhint %}

#### Entity file

Defined in your `LUA` file, this file holds the **game entity** that AMM spawns when you click the button. There are two ways of using entity files:

#### [**Mesh entity**](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/entity-.ent-files#mesh-component-entity-simple-entity) **(the legacy version)**

{% hint style="info" %}
**Fun fact:** The cluttered prop browser annoyed manavortex so much that she helped Max implement the [alternative workflow](#root-entity) described below the picture, and wrote this guide!

It was **that** bad!
{% endhint %}

One entity file per variant. The props will not have appearances — AMM's prop browser has one entry per entity file (e.g. `cube_black`, `cube_white`, `cube_glowing`).

Edit this kind of prop by opening the following file in Wolvenkit:

<pre><code><strong>tutorial\amm_props\template_no_variants\template_no_variants.ent
</strong></code></pre>

You add props by putting meshes directly into the components array:

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-fd2f59814115931e6ce9b7142fdf133d3c91a5ed%2Fmesh_entity.png?alt=media" alt=""><figcaption><p>tutorial\amm_props\template_no_variants\template_no_variants.ent<br>Mesh/Component entity, loading something directly. You can read more about the theory <a href="https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/entity-.ent-files#mesh-component-entity-simple-entity">here</a> — you don't need to know for the rest of this guide.</p></figcaption></figure>

#### [**Root entity**](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/entity-.ent-files#root-entity)

One entity file per prop, one entry in AMM's prop browser (e.g. `cube`). After spawning it, you can toggle its appearances (`white`, `black`, `glowing`) the same way you do it with NPCs.

{% hint style="info" %}
If you have [added clothing items](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/items-equipment/adding-new-items), then this will be familiar to you. If you haven't, please ignore the link and keep reading — this is the simpler version!
{% endhint %}

Edit this kind of prop by opening the following file in Wolvenkit:

```
tutorial\amm_props\template\template.ent
```

Instead of adding items directly via the components array, we link **appearances** to an [.app file](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/appearance-.app-files). The only component we keep in the [root entity](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/entity-.ent-files#root-entity) is the **targeting component** for the CET cursor: this way, it will be added to each appearance in the .app file.

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-c3999f5858d8cbc55e6d4095b6268ae90b38544b%2Froot_entity.png?alt=media" alt=""><figcaption><p>tutorial\amm_props\template\template.ent<br>Root entity, pointing towards an .app file. You can read more about the theory <a href="https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/entity-.ent-files#root-entity">here</a> — you don't need to know for the rest of this guide.</p></figcaption></figure>

#### Appearance file

[This file](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/appearance-.app-files) holds a list of `appearances`. Inside each `appearance`, you can define any number of things to be loaded (components) and specify or override their behaviour.

{% hint style="info" %}
We will only use `entPhysicalMeshComponent`s, and they must be named `amm_prop_slot1` .. `amm_prop_slot4` if you want to enable scaling.
{% endhint %}

{% hint style="warning" %}
If you have more than four mesh files assigned to your app's components, the prop will no longer be scaleable (as of AMM 2.1). You can get around this limitation by **making meshes with more submeshes** instead of having individual files.
{% endhint %}

#### template\_textured.mesh

A pre-configured [mesh](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/3d-objects-.mesh-files) for a textured material. Uses the following files in the subfolder `textures`:

* `template_01_d.xbm`: A diffuse (albedo) map, colouring the mesh
* `template_01_n.xbm`: A normal (bump) map, adding depth to the object.

{% hint style="info" %}
If you stick to this naming convention and have your filenames end in `_d` or `_n`, Wolvenkit will recognize and identify the correct settings for image import.
{% endhint %}

You can learn more about textured materials [here](https://wiki.redmodding.org/cyberpunk-2077-modding/materials#textured). This is not necessary for the purpose of this guide.

{% hint style="info" %}
**Optional Blender helper — Atlasify Selected Object**\
If your source mesh comes with many material slots/textures but you only need a single textured mesh for `template_textured.mesh`, this Blender script duplicates the selected object, builds **BaseColor** and **Normal** atlases, remaps UVs to a new `BAKE_ATLAS`, and assigns a single material—so you end up with **one slot, one material, one base color and one normal texture**.\
**GitHub:** <https://github.com/AlexRynas/Atlasify\\_Selected\\_Object>
{% endhint %}

#### template\_multilayered.mesh

A pre-configured [mesh](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/3d-objects-.mesh-files) for a multilayered material. Uses the following files in the subfolder `textures`:

* `6_layers.mlsetup`: A [multilayer setup](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/items-equipment/editing-existing-items/changing-materials-colors-and-textures#multilayered-material) with colour properties
* `6_layers.mlmask`: A [multilayer mask](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/materials/multilayered), determining which parts of the mesh are affected by which layer of the mlsetup. In this case, it just contains six blank layers.
* `template_01_n.xbm`: A normal (bump) map, adding depth to the object.

You can learn more about multilayered materials [here](https://wiki.redmodding.org/cyberpunk-2077-modding/materials#multilayered). This is not necessary for the purpose of this guide.

{% hint style="success" %}
If you have downloaded the example Wolvenkit project, you can now install it and launch the game, seeing everything in action.
{% endhint %}

### Diagram

Okay, now that we've gone through the theory, let's have a quick overview how everything hangs together:

#### Without variants

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-b19383b0fd4f3942af92f3d83bf709d0def0c774%2Famm_prop_no_variants.jpg?alt=media" alt=""><figcaption><p>No app file, directly pulling in a mesh with defined appearance</p></figcaption></figure>

#### With variants

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-6d45907d074f9afa710d60f4f7b6ad2ca3efd170%2Famm_props_with_variants.jpg?alt=media" alt=""><figcaption><p>The better option — not actually that much more complex, is it? :)</p></figcaption></figure>

## Using other meshes

You can point the prop at a different mesh by changing the depot path of the **component**. If you have no idea how to do that, read on!

### With variants

1. Open the `appearance` file `tutorial\amm_props\template\template.app`
2. Find the array `appearances` at the top of the file
3. For each appearance, open the `components` array
4. Click on the first component `amm_prop_slot1`. In the panel to the right of the tree, change the following properties:
   * `mesh -> DepotPath`. Put the relative path to your .mesh (right-click on the file)
   * `mesh -> meshAppearance`. Put something that [actually exists in your file](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/3d-objects-.mesh-files#step-1-appearances), otherwise the first appearance from the list will be used as default.

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-31577769ceddf3445599b17268cad56f6f3fb2fa%2Fcuzstom_props_change_mesh_2.png?alt=media" alt=""><figcaption><p>For props with variants: <code>template.app</code></p></figcaption></figure>

5. If you want to use more than one mesh, repeat the process for the other components. If you want to use more than 4, check [#why-only-4-components](#why-only-4-components "mention") below.
6. Repeat the process for the other appearances.
7. Save the file and start the game. If you've done everything right, you will now see your new mesh.

### Without variants

1. Open the [`mesh entity`](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/entity-.ent-files#mesh-component-entity-simple-entity) `tutorial\amm_props\template_no_variants\template_no_variants.ent`
2. Find the `components` array and open it
3. Click on the first component `amm_prop_slot1`. In the panel to the right of the tree, change the following properties:
   * `mesh -> DepotPath`. Put the relative path to your .mesh (right-click on the file)
   * `mesh -> meshAppearance`. Put something that [actually exists in your file](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/3d-objects-.mesh-files#step-1-appearances), otherwise the first appearance from the list will be used as default.

<figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-daa869ae05ad4a016891d8c519d5c3dbde811fd2%2Fcustom_props_change_mesh.png?alt=media" alt=""><figcaption><p>For props without appearances: <code>template_no_variants.ent</code></p></figcaption></figure>

4. If you want to load more than one mesh, repeat the process for the other components. If you want to use more than four, read [#why-only-4-components](#why-only-4-components "mention")
5. If you don't want to load more than one mesh, select `amm_prop_slot2` and delete the `depotPath`. Otherwise, you'll see your prop and a floating cube.
6. Finally, change the `defaultAppearance` to [a valid appearance in your .mesh file](https://github.com/CDPR-Modding-Documentation/Cyberpunk-Modding-Docs/blob/main/for-mod-creators/files-and-what-they-do/3d-objects-.mesh-files#step-1-appearances). If no appearance with this name can be found, the prop will be invisible when it spawns.

### Why only 4 components?

Currently (October 31 2023), AppearanceMenuMod can only **scale objects** by targeting their components by name. For that reason, yours have to be named as they are.

If you use more than 4 components or change their name, then your prop will no longer scale.

## Creating another prop

{% hint style="success" %}
This step is **optional**. If you just want to see how this works, you can pack your project with Wolvenkit and search AMM for "tutorial item". However, assuming that you actually want to make cool things, you will be doing this a lot.
{% endhint %}

If you want to create another prop, here's the fastest non-script way to go about it (tried and tested by manavortex).

1. In Windows Explorer, duplicate the `template` folder
2. Rename the new folder (`template - Copy`) to the name of your prop (e.g. `baseball`).

{% hint style="danger" %}
It's important that you stick to a schema here, because otherwise, the search and replace below will **not work** and you have to change all the paths by hand.

Use the **exact same value** to replace `template` in both the folder and the file names!

Good: folder: baseball, file: baseball.ent\
Bad: folder: baseball, file: my\_baseball.ent
{% endhint %}

3. Rename all files inside of the folder: replace `template` with the name of your prop (e.g. `baseball`). Not all files will have template in their names; just ignore the ones that don't.

{% hint style="danger" %}
Capitalization matters. If you use uppercase letters in folder names, the game will get confused, and Wolvenkit will secretly convert them back to lowercase before packing.

Good: `baseball`\
Bad: `Baseball`
{% endhint %}

4. Back in Wolvenkit, right-click on your folder and [export the entire thing to json](https://app.gitbook.com/s/-MP_ozZVx2gRZUPXkd4r/wolvenkit-app/usage/import-export/import-export-as-json#export-as-json).
5. Switch to the `raw` tab in Wolvenkit and open your json files in Notepad++
6. Via `Search and Replace in Files` (Ctrl+Shift+F), replace `template` with the name of your new prop and folder (e.g. `baseball`). Replace it in all files, **using Match case**:

   <figure><img src="https://1427525421-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4gzcGtLrr90pVjAWVdTc%2Fuploads%2Fgit-blob-6bf95706ea13ad072ad3161e0d8655dc9a6b3d64%2Famm_customizable_props_replace_in_files.png?alt=media" alt=""><figcaption><p>Make sure to check "<strong>Match case</strong>", or you will be unable to re-import the .ent file!</p></figcaption></figure>
7. **Optional**: If you have changed the folder structure (e.g. moved your folder from the subfolder `stuff` to the subfolder `misc`), run another `Search and Replace in Files` (Ctrl+Shift+F) to adjust your file paths.
8. In the project browser's raw section, right-click on the folder and select `Convert from json`. This will have updated the relationships between the files to your renamed files.
9. Delete the files / appearances that you don't need. Save and close the mesh file.
10. Import your meshes and textures over the ones from the template. For a guide on how to do that, check [here](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/textures-and-luts/textured-items-and-cyberpunk-materials#importing-a-mesh).
11. To make sure that everything went okay, open your new root entity (`tutorial\\amm_props\\baseball\\baseball.ent`) in Wolvenkit and save it to trigger [file validation](https://app.gitbook.com/s/-MP_ozZVx2gRZUPXkd4r/wolvenkit-app/file-validation). Check the Wolvenkit log window for errors. If you made no mistakes in the renaming process, there shouldn't be any.
12. To register the prop with AMM, add another entry to the props array in your `LUA` file:

```
    {
      name = "Baseball (customizable)",
      path = "tutorial\\amm_props\\baseball\\baseball.ent",
      category = "Misc",
      distanceFromGround = 1,
      appearances = {
          "baseball_textured",
          "baseball_multilayered",
      }
    }, 
```

13. Save the LUA file.
14. Install and launch the game
15. Spawn your new prop `Baseball (customizable)` with AMM.

If everything went well, you should see something like this now:

<figure><img src="https://i.imgur.com/GQ8fELd.png" alt=""><figcaption><p>Not a moon</p></figcaption></figure>

If not, it is time to hit up the [troubleshooting](#troubleshooting).

## The final touches

Before you can share your custom props, you **have** to change the folder structure and file paths. Otherwise, two people overwrite `tutorial.lua`, and one of the mods stops working.

You can find a step-by-step guide on the process [here](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/items-equipment/moving-and-renaming-in-existing-projects).

## Troubleshooting

This section will only cover troubleshooting steps for this guide.\
For anything related to mesh imports, see [here](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/textures-and-luts/textured-items-and-cyberpunk-materials#troubleshooting).\
For general 3d model troubleshooting (including import errors), see [here](https://wiki.redmodding.org/cyberpunk-2077-modding/for-mod-creators-theory/3d-modelling/troubleshooting-your-mesh-edits).

### My prop doesn't even list in AMM!

The problem is in your .lua file. Use [this tool](https://www.tutorialspoint.com/execute_lua_online.php) to check the syntax and make sure that there are no errors - usually, it is missing/extra commas and/or missing/extra braces.

If the syntax is okay and your prop still doesn't show up, double-check your category and make sure that it is one of the existing ones.

### My prop won't spawn!

#### ... and I can't target it!

AMM can't find your .ent file. Make sure that your .lua points to the correct path in your archive (right-click -> copy relative path and paste it to your lua file.

{% hint style="info" %}
Make sure that you don't delete any quotation marks or commas while you do that. If you're unsure, you can double-check [this step](#my-prop-doesnt-even-list-in-amm).
{% endhint %}

#### ... it all looks good, but there is no prop!

Toy around with the **scaling**. Sometimes, your prop doesn't show because it's the size of Johnny's ego and hovers somewhere above your city block – or the opposite, it's microscopically tiny. Don't be afraid to change it by the factor 10 or even 100 and see if that does anything.

If that's not it and if you have a customizable prop (with a root entity), try adding an appearance `default` to the mesh. The game will fall back to that one if there are issues with your custom appearances.

### My prop spawns, but something about it is weird!

In general, your answer is probably in the guide on [textured-items-and-cyberpunk-materials](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/textures-and-luts/textured-items-and-cyberpunk-materials "mention"), section 2 ([processing the mesh](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/textures-and-luts/textured-items-and-cyberpunk-materials#step-2-processing-the-downloaded-mesh)) – check that guide's [troubleshooting section](https://wiki.redmodding.org/cyberpunk-2077-modding/modding-guides/textures-and-luts/textured-items-and-cyberpunk-materials#troubleshooting).

[^1]: Use the Windows Explorer to move the downloaded source folder on top of the Wolvenkit project's source folder.