There seems to be an error in a particular texture map, causing a crash during import. UE5.5

[novazen]

Describe the bug

Assertion failed: MipView.GammaSpace == LayerData.SourceGammaSpace [File:D:\build++UE5\Sync\Engine\Source\Runtime\Engine\Private\TextureDerivedDataTask.cpp] [Line: 410]

Screenshots, log

UnrealEngine Version:
[e.g. ue5.5]

Additional context
There seems to be an error in a particular texture map, causing a crash during VRM import. Collisions occur in the Selestia model.

[ruyo]

Hi.
Please try the next released version.
I have added the settings and it is probably fixed.

[DIONAPERSSON]

I have the same exact issue as the above poster, same error code.
Also using 5.5 and the latest version of the plugin for 5.5 😢

[tex111]

This is still an issue as of 20241206.

Assertion failed: MipView.GammaSpace == LayerData.SourceGammaSpace [File:D:\build++UE5\Sync\Engine\Source\Runtime\Engine\Private\TextureDerivedDataTask.cpp] [Line: 410]

[ruyo]

Fixed in version 20241213. Please use the latest version.

[DIONAPERSSON]

Fixed in version 20241213. Please use the latest version.

I'm afraid I just tried it with the latest version, and I still get this same issue at import.

(I also want to just thank you for this plugin, I used it for my master thesis and it really helped me out in the past <3)

[ruyo]

In the latest version, the crash in GammaSpace has been fixed.
If the problem still persists, it may be due to other factors.

[DIONAPERSSON]

In the latest version, the crash in GammaSpace has been fixed. If the problem still persists, it may be due to other factors.

I even tried on a new 5.5.1 project file. I get still get this on import of vrm file sadly:
Assertion failed: MipView.GammaSpace == LayerData.SourceGammaSpace [File:D:\build++UE5\Sync\Engine\Source\Runtime\Engine\Private\TextureDerivedDataTask.cpp] [Line: 410]

I then tried the new plugin but with5.4.4, and that works perfectly. So it seems to only be 5.5.

[ruyo]

Hmmm, it seems difficult to solve the problem as I cannot reproduce it.
If you don't mind, please share the VRM model where the problem occurs.

I have confirmed that the problem is no longer present in the VRM model reported in #455.

[DIONAPERSSON]

So, I tried a VRM model I found here: https://github.com/madjin/vrm-samples/tree/master/vroid/stable and that worked.

But any model that I've previously made myself, that works on the other versions, I still get the previous error. Ok -- i did do some futher testing on a clean new project, with a new model. I think the issue might happen when using the the 0.0 model export rather than the 1.0 one?