Asset can't be reimported and read-only mount points

[K.Wagrez]

Hello everyone,

I would like to understand something about a recurring error message that I have. Our projects have read-only mount points to folders which contain textures (as dds files) and their associated meta files. They have been migrated through Unigine Editor. We have no runtime for these files.

When I open up the editor, I have this error message for every asset in my mount point:
"UnigineEditor::AssetManager::validate(): Asset is invalid and can't be reimported because it is located inside a read-only mount point. GUID: 69413792e9787e7de4c675e1568edad848fdf79b, new filepath: XXXX/textures/my_texture.dds."

I don't remember the editor doing that all the time. I don't understand what's the problem with the assets. 

But the key question here is "what does the editor mean by Invalid?". Why would he need to reimport it ?

And what means "new filepath" ? I can't see my assets anymore in the asset browser.

I have this problem in 2.19.1 but I'm not sure if it's a migration thing.

I join the meta file of the texture.

my_texture.dds.meta

Edited October 20, 2025 by K.Wagrez

[silent]

Hi Kevin,

According to the .meta file, this asset should have runtime:

<parameter type="bool" name="unchanged">0</parameter>

When the Editor validates the asset, it checks the runtime outputs and finds that the corresponding texture is missing. It then attempts to generate the missing runtime, but the operation fails because the mount is read-only.

If there would be unchanged=1, that would mean that texture should be used as-is:

<parameter type="bool" name="unchanged">1</parameter>

So in order to fix this you would need to give an RW access to this mount and do a full reimport. That would generate runtime for the texture (step 1).

After that in the texture parameters inside the editor you need to enable "unchanged" option. That would remove runtime and .meta file will be regenerated. Now correct hash and options will be store in the .meta file and you can switch mount to RO again.

--

It’s likely this started during a recent migration (possibly in 2.19.x). We no longer treat .DDS textures as runtime formats. We did attempt to convert these assets automatically, but some legacy content may still be used as-is, which can lead to runtime mismatches.

Going forward, we recommend migrating .DDS assets to the .TEXTURE format. It supports mipmap streaming and typically reduces disk footprint as well as RAM/VRAM consumption. While .DDS will continue to work for some time, it’s considerably less efficient for large content libraries with heavy streaming (frequent loading and unloading).

Thank you.