Blender Basics

Overview

This section provides solutions to the most common issues you may encounter when using the model in Blender. It covers topics such as missing or pink textures, version compatibility warnings, Python script messages, and general performance or rendering problems.

Each topic includes a clear explanation and step-by-step instructions to help you identify the cause and fix it quickly, even if you are not an advanced Blender user.

Before troubleshooting, make sure you are using Blender 4.0 or newer, and that the folder structure of the model remains unchanged. The .blend file and its “textures” folder must stay together in the same directory for Blender to locate all linked files correctly.

Following the instructions in this section will help you restore missing textures, enable scripts safely, improve performance, and ensure the model displays and functions as intended.

Package Contents

After downloading your purchase, you will find four main files inside the product folder:

LICENSE_RoyaltyFree.txt or LICENSE_Studio.txt

Specifies the type of license you have acquired. Please review it to understand the usage rights and limitations here.

Model file (.blend)

This is the main Blender file of the product. The name follows the format:

ModelName_ModelType_ModelEdition.blend

Example: Natalia_Character_Cinematic.blend

OMNIA Pro Addon (.zip)

The optional add-on used to enable extended features and controls for the model inside Blender.

UNZIP_FIRST.zip

This compressed folder contains all texture files required for the model.

It must be extracted before opening the .blend file.

Important:

Always extract the “UNZIP_FIRST.zip” file in the same directory where the .blend file is located.

Once extracted, you should see a folder named “textures” alongside the .blend file. The structure should look like this:

/YourModelFolder/

├── ModelName_ModelType_ModelEdition.blend

├── textures/

├── LICENSE_RoyaltyFree.txt

├── omnia_pro.zip

└── UNZIP_FIRST.zip

Keeping the “textures” folder in the same location ensures that Blender can automatically locate all materials and image files when the model is opened.

Missing or Pink Textures

If the model appears in bright pink (magenta) after opening the .blend file, it means Blender cannot find the texture files. This usually happens when the “textures” folder has not been extracted from the UNZIP_FIRST.zip file, or if it was moved to a different location.

To fix it:

1. Make sure the “textures” folder is correctly extracted in the same directory as the .blend file.

Example:

/YourModelFolder/

├── ModelName_ModelType_ModelEdition.blend

└── textures/

2. If you already moved or renamed folders and the textures are missing, you can manually relink them in Blender:

- Go to the top menu: File > External Data > Find Missing Files

- Select the folder where the textures are located

- Blender will automatically relink all missing files

Once the textures are found, the materials will return to their normal appearance.

This process only needs to be done once, as long as the folder structure remains the same.

You can also visit this explanatory video:

UDIM Textures Configuration

Some materials in the model, such as skin or nails, use UDIM textures. This means that multiple texture tiles are used to cover different areas of the model with higher detail.

If the UDIM configuration is accidentally changed or removed, Blender may display the same texture across all tiles, causing visible repetition or incorrect mapping.

To verify and correct it:

1. Open the Shader Editor and select the material (for example, “Skin” or “Nails”).

2. Locate the Image Texture node connected to the Base Color input.

3. Make sure the texture type is set to “UDIM Tiles” in the drop-down menu inside the node.

4. If it shows “Single Image” instead, click the menu and change it back to “UDIM Tiles”.

5. Blender will automatically restore the correct texture distribution across all tiles.

Note:

You should not rename or move UDIM texture files manually. Keep them inside the “textures” folder next to the .blend file to ensure they load correctly.

Version Compatibility in Blender

All models are usually created using the latest stable version of Blender, but I always make sure they are compatible with version 4.0 and up.

All files are tested on their respective compatible versions before being released.

Common Warnings and Messages

When opening the model for the first time, Blender may display some warning messages. These are completely normal and do not indicate any problem with the model. Below are the most common ones and how to handle them.

1. Overwrite file with an older Blender version?

This message appears when the .blend file was created in a newer Blender version than the one you are currently using.

Example:

“This file was saved by a newer version of Blender (4.3). Saving it with this Blender (4.0) may cause loss of data.”

Solution:

Simply click “Save As…” to save a new copy of the file instead of overwriting the original. This prevents possible data conflicts.

It is always recommended to use Blender 4.0 or newer to ensure full compatibility with the model.

2. File written by newer Blender binary

This warning appears in the lower status bar and has the same meaning as the previous message: the file was saved in a newer version of Blender.

Example:

“File written by newer Blender binary (403.34), expect loss of data!”

Solution:

You can safely ignore this warning if you are using Blender 4.0 or later. It only serves as a notice. No actual data will be lost when working within compatible versions.

3. Python script execution disabled

When opening the file, Blender may display a security warning like this:

“For security reasons, automatic execution of Python scripts in this file was disabled.”

This appears because the file includes a Python script (rig_ui.py and OMNIA_Panel.py) used to control the interface of the rig.

Solution:

Click “Allow Execution” to enable the script.

If you want Blender to always allow scripts from this file, check the box “Permanently allow execution of scripts” before confirming.

Alternatively, you can enable this globally from:

Edit > Preferences > Save & Load > Auto Run Python Scripts.

Note:

This script is completely safe and required for the rig to function correctly. Blender shows this message as a general security precaution for any file containing scripts.

Simplify and Performance

Simplify is a Blender feature designed to reduce scene complexity while working, without affecting the final render quality. It temporarily limits subdivision levels, particle counts, and other heavy elements to improve viewport performance.

In the model, Simplify may be active by default to ensure smooth navigation, especially on systems with limited resources. This does not affect the final render — Blender automatically ignores Simplify when rendering and always displays the full resolution.

To adjust Simplify manually:

Go to the “Render Properties” tab (camera icon) in the Properties panel.
Open the “Simplify” section.
Enable or disable the checkbox to toggle the effect.
You can adjust the maximum subdivision levels or particle visibility if needed.

In addition, the OMNIA Panel includes a dedicated “Performance” section that provides quick access to Simplify and other optimization controls such as hair curve reduction. More info.

Moving and Posing the Model

The model should always be manipulated through its rig, not by selecting or transforming the mesh directly. The geometry is parented and linked to the rig, so moving the mesh manually can break its relationship with the controllers.

To move, rotate, or scale the character correctly:

1. Select the main rig object in the scene (for example, “OMNIA_Rig”).

2. Use the standard move (G), rotate (R), and scale (S) shortcuts in Object Mode.

3. Avoid applying transformations (Ctrl + A) unless absolutely necessary, as this can cause deformation issues in the rig.

Recommended modes of interaction:

Object Mode: Move, rotate, or position the entire model in the scene.
Pose Mode: Use this mode to animate or pose the model using its rig controllers. More info.

Final Rendering

The model is ready to render immediately after opening the file. All materials, lighting, and settings are optimized to deliver the same level of visual quality shown in the product previews, without the need for additional configuration.

Each edition of the model is preconfigured for its intended render engine:

Cinematic and Customizable editions use Cycles, providing maximum realism through physically accurate materials and subsurface effects.
Realtime editions use Eevee, optimized for fast performance and interactive rendering.

It is important to use the render engine for which each model has been designed. Switching engines may alter shadows, reflections, or skin behavior, especially in materials that rely on subsurface scattering or transparency.

A sample HDRI is already integrated into the scene for lighting, with proper credit to HDRI Haven (https://polyhaven.com/hdris). You can replace it or adjust its intensity depending on your artistic needs.

You are free to modify render settings such as resolution, sampling, or denoising according to your hardware performance. The base configuration, however, is already tuned to achieve a realistic and well-balanced result across all supported systems.