FANOVO Studio

FANOVO ACADEMY · VERSION 0.46

Tutorials for every feature

From your first launch to a finished export: find your workflow and follow each step in the editor.

Updated 16 November 2026 for version 0.46. English guides retain German editor labels so you can find the correct controls. Examples do not replace testing in the target game.

30 guides

Getting started · 5 steps

Install, sign in and start

Requirements: Windows x64, internet and an active licence.

Step by step

  1. Open fanovo.de/konto.html, create an account and choose your plan. Wait until the account confirms payment.
  2. Download and run the setup EXE from your account. Choose German or English and the installation folder. Setup detects existing setup installations; save open files and close FANOVO first.
  3. Start FANOVO Studio using its shortcut. Select German or English at the top right. Open Help → Licence (Hilfe → Lizenz) and sign in with your purchasing account.
  4. Start the tour under Hilfe. Then use Datei → Ordner öffnen to open a working copy of your resource.
  5. Open a file in the explorer and check the output at the bottom. Save a small test change before moving on to your main project.
Expected result

A signed-in Studio with a resource folder open.

Limits & troubleshooting

Online licence verification is required. One installation is enabled per account. English tutorials retain the editor’s German control labels.

Getting started · 5 steps

Files, folders and workspace tabs

Requirements: A local working copy of your resource.

Step by step

  1. Choose Datei → Ordner öffnen. Open the folder containing the manifest and stream folder.
  2. Expand folders on the left and click a file. Use the file filter to find items in large projects.
  3. Right-click an entry. Create a folder or rename an item; then update affected references in scripts or the manifest.
  4. Use Löschen in the context menu to remove an item. Check the selected path before confirming.
  5. Tools appear as workspace tabs. Dateien & Vorschau returns to files. Explicitly save edits before closing an edited tab.
Expected result

An organised local project structure.

Limits & troubleshooting

Renaming does not automatically update every reference. The recycle bin and save backups do not replace your own project backup.

Models & collisions · 5 steps

Inspect 3D models and dimensions

Requirements: A supported YDR, YDD, YFT, GLB or OBJ file.

Step by step

  1. Open the file in the explorer or with Datei öffnen. Wait for the preview; read the output if geometry is missing.
  2. Drag to rotate and use the wheel to zoom. Ansicht zurücksetzen restores a useful starting camera.
  3. Enable Ursprung / Mitte, Bodenraster and the size reference. The 2-metre figure helps compare size; use the tape measure for individual distances.
  4. Use Fokusansicht for more space. Compare wireframe, lighting and material views to distinguish geometry issues from texture issues.
  5. Inspect the textures on the right. Missing textures may belong to another local resource or game archive.
Expected result

Check size, orientation and materials before exporting.

Limits & troubleshooting

The preview is not a full game engine. Not every YFT, shader or skinning format is rendered completely.

Models & collisions · 6 steps

Create a prop from GLB or OBJ

Requirements: A static model with UVs; for OBJ, matching MTL and image files.

Step by step

  1. Open Erstellen → + Prop erstellen. Enter a unique name without spaces, such as fv_workbench.
  2. Choose FiveM or RedM and select the 3D file. Import preview processing starts after you confirm.
  3. Set source up-axis, scale and origin. Unten mittig is often useful for furniture. Compare the model against the 2-metre reference.
  4. Assign missing material textures. Choose a collision mode; use the custom collision tutorial for multiple bodies.
  5. Confirm creation or export the target resource from the prop builder. Check the displayed destination: the prop folder is created under the open project path; without a project, choose a destination.
  6. Inspect fxmanifest.lua and stream contents. Copy the generated resource to your test server and add ensure followed by its resource folder name to server.cfg.
Expected result

A resource folder containing a manifest and the files generated by the supported exporter.

Limits & troubleshooting

Static props only: no automatic rigging or animation export. RedM export is experimental. A successful local export does not replace an in-game test.

Models & collisions · 5 steps

Set scale, origin and orientation

Requirements: An imported GLB/OBJ prop.

Step by step

  1. Write down the intended real size, for example a table height of 0.8 metres. Read the target dimensions in the import preview.
  2. Calculate the factor: intended size divided by current size. For 8 metres instead of 0.8 metres, use 0.1.
  3. Change Maßstab in the prop builder. Check Quellmodell oben: GLB often uses Y-up, while many game models use Z-up.
  4. Choose an origin suited to the prop and apply the preview. Check ground height and the size reference from several angles.
  5. Export a new resource and check dimensions and destination in the report. Test that exact export; use a new unique model name if caching causes confusion.
Expected result

Geometry and custom collision boxes are transformed consistently during prop export.

Limits & troubleshooting

General model transform fields initially affect the preview only. A matching export is needed to write new model geometry.

Models & collisions · 6 steps

Author multiple collision boxes

Requirements: Version 0.45 or newer and an imported prop; native export is for FiveM.

Step by step

  1. In the prop builder, open Eigene Kollisionsboxen setzen … . The model is used as a reference; existing custom boxes are loaded again.
  2. Choose + Box. Add a body for each solid area, such as a tabletop and its legs. Avoid a large box across openings that should remain passable.
  3. Select a body in Kollisionskörper. Set position X/Y/Z, width X, depth Y, height Z and rotation. Enter or leaving a numeric field commits the change.
  4. Use the 3D handles for position, size or rotation. Snapping helps with regular spacing. Duplizieren creates similar bodies; Löschen removes the selected body.
  5. Inspect the boxes from every angle. Orange marks the selection and blue marks other bodies. Undo a mistaken step and save a working draft if needed.
  6. Click Kollisionen für dieses Prop übernehmen. Then export the FiveM resource and inspect its report. Check the updated preview again after changing scale, axis or origin.
Expected result

Multiple independent boxes are embedded as a combined collision in the FiveM prop.

Limits & troubleshooting

RedM currently supports saving a working draft of these multiple bodies only; no native multi-body export. Boxes are coarse solid bodies, not automatically generated exact mesh collisions.

Models & collisions · 5 steps

Edit existing GTA collisions

Requirements: A supported GTA YBN or collision draft.

Step by step

  1. Open the collision file and launch the visual collision editor under Werkzeuge.
  2. Select a body from the list. Inspect its hull alongside an open reference model.
  3. Move the body using numeric fields or handles. Size and rotation editing currently targets boxes.
  4. Add further boxes as needed. Save a draft before making substantial changes.
  5. Choose Neue GTA-YBN exportieren … and a new filename. Reopen the exported copy and then test it in game.
Expected result

A new edited GTA collision file while preserving the source.

Limits & troubleshooting

Some non-box bodies are shown only as simplified hulls. Native RDR2 YBN editing is not supported.

Textures & liveries · 6 steps

Add liveries and multiple textures

Requirements: A prop with suitable UVs and your own texture images.

Step by step

  1. Open the imported prop and find Liveries / Texturvarianten on the right.
  2. Under Textur ersetzen für, select the material that needs a new colour or graphic.
  3. Enter a variant name and choose Livery hinzufügen … . Select an image matching the UV layout.
  4. For a multi-material prop, use Weitere Textur zur Livery … to add more images to the same variant.
  5. Switch Livery-Vorschau between Original and your variants. Check seams, back faces and material assignment.
  6. Export the resource. Read the generated model names and spawn the desired model variant during testing.
Expected result

Multiple designs as separate model variants in one resource.

Limits & troubleshooting

This is not a universal native livery switch like those used for vehicles or horses. A replacement image does not automatically adapt to a different UV layout.

Textures & liveries · 6 steps

Paint directly on the 3D model

Requirements: A model with complete UVs and an available diffuse texture.

Step by step

  1. Open the model in the 3D view and click Textur malen.
  2. Select the texture or material to paint. Wait for the paint texture to finish loading.
  3. Set brush colour, size and opacity. Start with a small test stroke on a visible surface.
  4. Paint onto the surface with the left mouse button. Use the camera controls described in the paint panel to rotate; Alt bypasses painting input.
  5. Inspect back faces and UV seams. Use undo and redo to correct mistakes.
  6. Save the painted texture as PNG. For a prop, apply it through the texture/livery workflow and export the resource again.
Expected result

Your own painted texture file and, after re-export, a new prop variant.

Limits & troubleshooting

Shared or mirrored UV areas share the same pixels. Painting does not create missing UVs, bones or geometry. Saving a PNG alone does not automatically rewrite every native YTD.

Textures & liveries · 5 steps

Open YTD, export and replace textures

Requirements: A supported YTD and, for RDR2 where needed, Oodle from your installation.

Step by step

  1. Open the YTD in the explorer. Wait for the texture list and select a texture.
  2. Check its name, resolution, transparency and preview. Record the original properties before editing.
  3. Export a DDS copy for external editing. Use the texture batch tool for image copies or resizing.
  4. Replace a supported texture, preserving suitable dimensions and its alpha channel. Use the offered save/export action and check the destination.
  5. Reopen the new file. Compare it on the model and test the resource in the target game.
Expected result

Checked texture copies or a supported edited texture file.

Limits & troubleshooting

GTA and RDR2 resources are not interchangeable. Renaming cannot fix a missing decoder or unsupported compression.

Textures & liveries · 5 steps

Inspect UVs, materials and missing textures

Requirements: A loaded model and matching local texture sources.

Step by step

  1. Open the model and read Material- und Texturprüfung on the right.
  2. Open UV-Layout to inspect which image areas the material uses.
  3. Check a recognisable graphic on the model. If it appears mirrored or rotated, first compare UVs and the source image instead of rotating every texture.
  4. Use Material / UV bearbeiten … for supported preview adjustments. Compare lit and unlit views.
  5. Save the image or export a supported new model copy. Inspect the exported result again.
Expected result

Narrow a display issue down to the image, UVs or material.

Limits & troubleshooting

Shininess and some shaders are preview approximations. Material changes become permanent only through the appropriate export.

Textures & liveries · 5 steps

Batch-export textures

Requirements: Local YTDs or images and a separate destination folder.

Step by step

  1. Open the texture batch tool under Werkzeuge and select source files.
  2. Choose PNG or DDS for your next step. PNG suits image editing; DDS suits the corresponding game workflows.
  3. Set the target size deliberately. Downsizing saves memory but can remove fine details.
  4. Enable mipmaps for a supported DDS export and select a new destination folder.
  5. Run processing and read the report. Inspect several bright, dark and transparent output textures.
Expected result

New PNG/DDS copies with source files preserved.

Limits & troubleshooting

Batch output is not automatically a repacked YTD resource. Check compression and alpha in the target game.

Models & collisions · 5 steps

Static model copies and LODs

Requirements: A supported static model.

Step by step

  1. Open the model and inspect the unchanged preview first.
  2. Set the desired transforms. Compare original and edited views before export.
  3. Compare existing LOD levels side by side. When simplification is supported, use moderate reduction and inspect the silhouette.
  4. Use Statische Modellkopie als Ressource exportieren … and enter a new name.
  5. Reopen the result. Check materials, origin and the distances at which individual levels become visible.
Expected result

A new static resource or supported simplified geometry.

Limits & troubleshooting

Rebuilding can simplify materials. Full bones or animations are not preserved; native LOD chains depend on the format.

Mapping & MLO · 5 steps

Edit YMAPs and place objects

Requirements: Readable YMAP XML and locally available models.

Step by step

  1. Open a supported map or start Erstellen → + YMAP. Keep a working copy.
  2. Load locally resolvable models. Missing models or archetypes must first be made available in the project.
  3. Select an object and adjust position, rotation and scale. Check both numeric values and spatial placement.
  4. Use multi-selection and named groups to move related objects together.
  5. Save or export the offered XML working format. Check the native conversion step required by your game before deploying the map to a server.
Expected result

Edited local placements in a supported map working format.

Limits & troubleshooting

Not every binary YMAP schema can be read or exported losslessly. An XML file is not automatically a streamable native YMAP.

Mapping & MLO · 6 steps

Export map regions as working packages

Requirements: A project folder with readable maps and matching local assets.

Step by step

  1. Open the project folder and Werkzeuge → Kartenübersicht & Ausschnitt exportieren.
  2. Choose Karten im Projekt indexieren. Read Nicht geladene Karten und Hinweise before relying on the result.
  3. Drag an area in the overview or enter X/Y minimum and maximum values. Selection uses object origins.
  4. Choose Bereich in 3D laden and inspect the selected placements. Reduce the area for large projects.
  5. Enter a package name and choose Zielordner wählen & Arbeitspaket exportieren.
  6. Read the report and supply unresolved dependencies. Use the package as a starting point for your mapping workflow.
Expected result

YMAP XML excerpts, resolvable local assets and a report.

Limits & troubleshooting

Not an automatically playable MLO, terrain/collision clipping tool or full world browser. RDR2 PRD0 support is experimental and has only been tested with synthetic data.

Mapping & MLO · 5 steps

Object rows, placement brush and heights

Requirements: A local scene with loaded geometry.

Step by step

  1. Load the scene and the object to place. Check its origin and size first.
  2. Select the placement tool and set count and spacing for a row.
  3. Enable reproducible variation if needed. Start with a few objects and inspect overlaps.
  4. Place objects onto geometry that is actually loaded. Compare queried heights with the visible surface.
  5. Inspect the final selection, group it where useful and save the supported map format.
Expected result

Regular or deliberately varied object arrangements.

Limits & troubleshooting

Height queries use loaded local geometry, not the entire game world automatically.

Mapping & MLO · 5 steps

YTYP, MLO rooms and portals

Requirements: A readable supported YTYP and a working copy.

Step by step

  1. Open the YTYP and read the explanations for its properties. Record archetype and resource references.
  2. For an MLO, inspect rooms and their object assignments. Start with a small, manageable change.
  3. Select a portal and check its corner points and the adjoining room assignments.
  4. Check references and indices after editing. Use project checks to locate missing local dependencies.
  5. Save or export a new supported version and test visibility, passages and room transitions in the target game.
Expected result

Targeted edits to supported archetypes, rooms and portals.

Limits & troubleshooting

Not an automatic complete MLO generator. Native capabilities depend on the format and game.

Mapping & MLO · 5 steps

Find duplicate stream files

Requirements: A parent folder containing multiple resources.

Step by step

  1. Open the common parent project folder containing, for example, MLO1 and MLO2.
  2. Run the duplicate stream file check under Werkzeuge.
  3. Inspect matching paths and file hashes where shown. The same name can cause overriding; identical content is not automatically safe to delete.
  4. Decide which resource should provide the asset. Check manifests, load order and dependent maps.
  5. Back up, clean up deliberately and run the check again. Then test both MLOs together.
Expected result

Conflicts become visible and can be resolved deliberately.

Limits & troubleshooting

Matches are warnings, not an automatic decision to delete files.

Models & collisions · 5 steps

Use a prop as a scripted door

Requirements: A usable static prop and a test project.

Step by step

  1. Open the model and Tür-Scharnier bearbeiten … or Erstellen → Türen.
  2. Place the hinge at the intended rotation axis. Inspect it from above and from the side.
  3. Set the closed and open angles. Check the swing path and surrounding geometry.
  4. Generate the offered door script resource and read its model and position settings.
  5. Include the door model and script resource on your test server. Adapt interaction, permissions and networking to your framework where required.
Expected result

A script scaffold for a moving prop door.

Limits & troubleshooting

No automatic native door conversion or guaranteed physics/framework integration. Moving collisions require in-game testing.

NUI designer · 6 steps

Design and export an NUI

Requirements: A local project and an interface concept.

Step by step

  1. Open Erstellen → NUI-Designer. Start blank or use an inventory, shop, HUD, dialogue or character selection template.
  2. Add panels, text, images, buttons and inputs. Select an element to edit position, size, colours and text.
  3. Import your own images. Check usage rights and actual image size; inspect transparency and cropping.
  4. Use snapping, alignment, multi-selection and groups. Set anchors so important elements stay near the intended screen edge.
  5. Test fullscreen preview and the available resolutions. Check wide and narrow screens as well as long text.
  6. Save your draft and export the resource. Inspect its HTML, CSS, JavaScript, Lua and manifest before integrating it into your script.
Expected result

A designed interface with an exported resource structure.

Limits & troubleshooting

Templates do not contain complete inventory, purchasing or character logic. Previewing does not replace testing in the game’s CFX browser.

NUI designer · 6 steps

Connect NUI buttons to Lua

Requirements: An NUI draft with a button and an exportable resource.

Step by step

  1. Give a button a unique action name, such as confirm_selection.
  2. Add JSON test data and check the action in interactive preview. Also test empty input.
  3. Export the resource and find the generated Lua callback example. Integrate the relevant sections into your client script.
  4. Use the generated examples to open and close the NUI. Ensure focus is released when closing.
  5. Forward server-relevant actions to your server code. Validate permissions, price, ownership and all received values there.
  6. Test locally in game, including Escape/close, repeated clicks and invalid input.
Expected result

An interface whose actions can be connected to your own game logic.

Limits & troubleshooting

Browser test data is not trusted server data. A button must not grant money or items using client-side validation alone.

NUI designer · 5 steps

NUI resolutions, anchors and animations

Requirements: A saved NUI draft.

Step by step

  1. Test the same draft at 16:9, ultrawide and 5:4. Note clipped or overlapping elements.
  2. Choose an appropriate screen anchor or proportional layout for each important element.
  3. Group elements that should move together. Inspect the group after each size change.
  4. Add fade, slide, zoom or hover effects sparingly. Check initial and final states and clickability.
  5. Repeat preview with long text and varied test data, then export the checked version.
Expected result

A more robust interface across screen formats.

Limits & troubleshooting

Groups are flat. Arbitrary nested layout behaviour is not generated automatically.

Lua & scripts · 5 steps

Create and check Lua scripts

Requirements: A resource project; basic Lua knowledge is helpful.

Step by step

  1. Open Erstellen → + Lua-Script and choose client or server according to the task.
  2. Check filename and resource structure. Add extra files to fxmanifest.lua if they are not already included.
  3. Write a small self-contained section and save. Use Lua prüfen to find syntax errors.
  4. Open Hilfe → CFX/Lua to check function parameters and target game. Do not assume FiveM and RedM natives are interchangeable.
  5. Test the resource on your local test server and read both client and server consoles. Expand the logic afterwards.
Expected result

A saved script with a local syntax check.

Limits & troubleshooting

Syntax checking does not run the script or prove correct game logic or security.

Characters · 5 steps

Bones, poses and custom motion

Requirements: A supported model with bones or a suitable rigged GLB.

Step by step

  1. Open the model and inspect its bone display. Alternatively import a rigged GLB into the animation tool.
  2. Open Erstellen → Animationen and select a bone. Start with a simple pose.
  3. Set keyframes at different times. Change only a few bones at a time so problems remain traceable.
  4. Play the preview and inspect transitions. Save a JSON working project regularly.
  5. Export the supported GLB/JSON format for further editing in suitable animation software.
Expected result

An editable pose/keyframe draft.

Limits & troubleshooting

No native YCD compiler, complete rigging or guaranteed skin deformation. A JSON or GLB export is not a directly playable new RDR2 animation.

Characters · 5 steps

Manage clothing and outfit projects

Requirements: Your own or lawfully available supported clothing files.

Step by step

  1. Open Erstellen → Kleidung importieren and select existing native files.
  2. Check preview, textures and target game. Keep male/female bases and different rigs distinct.
  3. Use Outfit-Projekt öffnen … to organise compatible parts in a working project.
  4. Record components and texture variants. Check that all required files are available locally.
  5. Save the working project and test the actual combination in the target game with the correct character.
Expected result

An organised outfit working project using existing assets.

Limits & troubleshooting

Not an automatic converter from arbitrary geometry to fully rigged clothing. Preview cannot fully reproduce actual character deformation.

Game archives · 6 steps

Browse RPF and RDR2 game archives

Requirements: Your own game installation and enough space for local exports.

Step by step

  1. Open the RDR2 game archive or relevant RPF tool under Werkzeuge.
  2. Select the installation folder containing the game EXE. Configure Oodle from your own installation when needed.
  3. Run the available indexing action and wait for completion. If keys are missing, follow the specific displayed guidance.
  4. Search by filename or model term and check path and file type before exporting.
  5. Extract selected files into a separate local folder. Open the copies in FANOVO to inspect them.
  6. Keep texture and dependency relationships intact. Check usage rights before any redistribution.
Expected result

Local working copies of selected supported assets.

Limits & troubleshooting

Archive access depends on the game version and available keys. Not all archives or character parts are guaranteed to resolve completely.

Projects & help · 5 steps

Sessions, backups and recovery

Requirements: A local project with edited files.

Step by step

  1. Explicitly save important changes and keep an additional backup outside the working folder.
  2. Use session actions under Datei to resume supported open workspaces later.
  3. After an unexpected shutdown, open Datei → Ungespeicherte Texte wiederherstellen.
  4. Select an entry and open it as an unsaved tab. Compare it against the original before saving.
  5. Use project snapshots or change previews for targeted restoration. Check hash conflicts when files have changed externally.
Expected result

Recovered supported text documents and traceable project changes.

Limits & troubleshooting

Automatic text recovery is not a full backup of all models, textures or unsaved tool states.

Projects & help · 5 steps

Dependencies, quality and export reports

Requirements: A resource folder and optionally a completed export.

Step by step

  1. Open the project and run quality and dependency checks under Werkzeuge.
  2. Distinguish missing references, duplicate names and unsupported formats. Address issues affecting your specific export first.
  3. Check the manifest and stream files. Supply missing local dependencies instead of merely hiding warnings.
  4. After prop export, use Letzten Export prüfen and inspect dimensions, file lists and validation.
  5. Create a targeted project copy or resource package where useful. Perform the final test on your own target server.
Expected result

An inspectable package with clear outstanding issues.

Limits & troubleshooting

Checks are not engine certification. Not every external game reference is an error, and not every in-game issue can be detected locally.

Projects & help · 6 steps

Updates, diagnostics and help

Requirements: A running Studio and internet for online features.

Step by step

  1. Open Hilfe and check the installed version under Version.
  2. Use the update action or compare against the customer account download. Back up projects before switching versions.
  3. For setup installations: use Help → Updates to download the signature-verified update, launch setup, save open files and close FANOVO. Existing setup settings are migrated. Old portable installations are not imported automatically.
  4. For an issue, record file type, target game, version, exact step and output message.
  5. Create a diagnostic package under Hilfe if needed. Explicitly select attachments and inspect the package before sharing.
  6. Open the FANOVO community for support and provide concise reproduction steps without passwords or secret keys.
Expected result

An up-to-date workspace or a useful support report.

Limits & troubleshooting

A new customer account download may not be offered through every automatic update channel at the same time. Diagnostic attachments may contain your own project content.