# Autodesk/FBX (Noesis)
{% hint style="info" %}
Noesis is an **alternative** to exporting with WolvenKit. There are legitimate use cases for why you would want this. If you don't know them, **you probably don't.**
{% endhint %}
### TL;DR:
Noesis is outdated. Go import/export [with Wolvenkit](/cyberpunk-2077-modding/for-mod-creators-theory/3d-modelling/exporting-and-importing-meshes.md).
### Explanation
5000 years ago on the slopes of Mount Doom, mods were created with nothing but pickaxes, home-spun hemp, and hex editing. Older guides will refer to Noesis as **the way to go** — but Wolvenkit has come a long way since then. The import/export is reliable and works, and unless you [run into issues](/cyberpunk-2077-modding/for-mod-creators-theory/3d-modelling/troubleshooting-your-mesh-edits.md), you will probably want to [stick to it](/cyberpunk-2077-modding/for-mod-creators-theory/3d-modelling/exporting-and-importing-meshes.md).
Given that you're still reading this, you probably have a reason to use Noesis, so here we go.
{% hint style="warning" %}
To use Noesis, you need the [Noesis Import/Export Plugin](https://github.com/alphazolam/fmt_CP77mesh?msclkid=384152bfaa5611ecbad0234dbe6a5c45).
{% endhint %}
## Exporting from the Wolvenkit project
1. Navigate the Noesis browser to your file on the disk (you can right-click on the mesh in Wolvenkit and select "`Open in File Explorer`")
2. Right-click it in the Noesis Browser and select "Export"
3. Export with default settings:
Done. You can now import the fbx to Blender.
### Blender: Saving for import
Simply export as fbx, Blender's standard settings are fine for Noesis.
## Importing
Noesis is an **alternative** to importing with WolvenKit.
* Find your fbx in the Noesis browser
* Right-click it and select "Export"
* Set the `Main output type` to `.mesh - CyberPunk 2077 mesh [PC]`
* A dialogue asks you for a file to overwrite. Make sure that it has your mesh!
## Troubleshooting
### Noesis Split Meshes
Noesis-split meshes are essentially how Noesis copes with higher vertex counts. It will automatically divide up your submeshes into smaller parts, which is why Noesis will often display there being more meshes than intended.
This is caused by the vertex count being too high, and will often result in the applicable submeshes not converting with the rest of the mesh, resulting in those submeshes being non-existent in the .mesh file. The solution is to simply reduce the number of vertices in the given submesh with the goal being to get the count lower than 65,000 vertices on the given submesh.
The best way to tell how many vertices a given mesh has is to open the "Viewport Overlays" drop-down menu and select "Statistics". This will allow for data on the meshes within the .blend. To narrow this down to a specific submesh, open edit mode with that submesh as active and "select all" (CTRL + A) and you will see the vertex count for that submesh.
Once you know how many vertices you have, use either "Decimate Geometry" or "Merge By Distance" to simplify the topography of the mesh, or to merge two or more vertices that are a given distance apart from one another into one.
Once this has been done, export from blender and try the conversion again.
If this doesn't quite do the trick, convert the fbx to fbx (just leave the output type set to fbx) and enter "-fbxmeshmerge" in the advanced options text box before clicking export. (It is recommended that you set an output location when doing this so as to avoid accidentally overwriting the original mesh)
### Duplicate meshes detected
This often accompanies the "Noesis-split meshes" warning. A common cause for this is the use of Blender's "duplication" feature. To solve it, follow the steps above for "Noesis-split meshes" then import the resulting mesh back in to blender, and you should see that you have several blank "Objects" that came in along with your mesh. Delete those, export back out of blender, convert the fbx to fbx, then import the result into blender and repeat if needed.
Following the deletion of these Objects, you may notice deformations in the submesh/submeshes, if this is the case, replace the armature (and update the armature modifier) with a new one and export again.
## Differences between fbx and glb
There are a few differences between Noesis and WolvenKit when it comes to exporting your meshes:
Note the differently named submeshes
| | Autodesk (fbx) | glTF Binary (glb) |
| ------------- | -------------- | ------------------- |
| Armature | Rotation W: 0 | Rotation W: 1 |
| | Rotation Z: -1 | Rotation Z: 0 |
| Submesh names | submesh0 | submesh\_00\_LOD\_1 |
You can easily convert between the two formats by hand — or use [this script](https://github.com/manavortex/code_snippets/blob/master/py/blender/convert_gltf_fbx.py): Switch to Blender's Scripting perspective, create a new file, paste the contents in, and run it.
---
# 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/for-mod-creators-theory/3d-modelling/exporting-and-importing-meshes/autodesk-fbx-noesis.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.
