Please Help - Quixel import problem / UE 5.0.3

Hi Guys!

I have UE 5.0.3 and when im import asset from Quixel im got a blank white material and the textures are black or empty.
PC (Win 10 64-bit) and UE 5.0.3 is Freshly installed. (Drivers are freshly installed/updated too)
Bridge plugin installed from UE library.
Same problem with new and old projects too.
Someone can help me whats wrong?
If you need some pictures or info, tell me what.


Thanks for your help!
Greetings
Sven

Hey there @svenscottHUN! Welcome to the community! There’s a number of issues that could be occurring so let’s run through a couple.

When you were importing the decals, did you already have a master material? I believe Megascans uses the same one for all of it’s decals and just makes the decals a child instance of that MM. You can find this by checking it’s parent in that material instance’s details. If it is connected, could I see your instance settings?

2022-10-29_17-37-11

It looks like the textures are off as well, could you open them each up and check their compression settings? The color (first) should be default, the normal map (second) should be set to normal, the (third) should be masks.

Lastly is it only decals failing or is it all megascans assets?

Hi @SupportiveEntity !

Thanks for your help for my problem.
I’m attached a pictures what you need.

same problem with everything from Quixel, assets, decals too.



For me the parent is “M_MS_Default_Material”.

Hope this pictures help for you to know whats wrong.
Sorry for my badly english.
Thank you!

No worries, your English is perfect!

Hrm, so at first I was thinking it was an issue I solved before that involved the master material importing improperly, but it doesn’t seem like that is the problem here. The textures themselves are also completely blank. Could you check the settings for each of those textures? Mostly looking to the compression settings for each of the three textures.

Then if it doesn’t end up being compression based I’d like you to export each of those 3 files out and view them in another editor and verify they aren’t actually empty.

Let me know how that goes!

Hmm im checked all of three textures and here attached the settings.

Texture 1.:

Texture 2.:

Texture 3.:

The textures are empty / Blank.
i don’t know whats wrong, freshly installed pc and UE5 too, drivers are fresh too.

im tried an another method and another asset.
Downloaded bridge standalone software and Blender plugin, export asset (pillar) to blender from bridge software and export it and import to ue5 but same problem, but in blender looks correct.
here the pic in UE5:

here the pic in Blender:

*update: Im downloaded UE 5.1 and here Quixel works fine. Only issue with 5.0.3.

Hrm. That’s even more odd. So generally when we see these issues it’s the master material that’s corrupted in some way or a link between it and the textures that are broken. In your case however the textures are pitch black when read even with default compression, so it’s pointing to the either the textures being the issue or unreal is just failing to read it. Lastly you showed the textures are in fact there and readable through blender, so it seems that it’s something project specific that could be causing it. That said, I’m not sure other checks to run besides verifying it is only this project.

Thanks for your efforts! Unfortunately, it was not possible to find out what the problem was, but the same is true for version 4.27. Only UE 5.1. works perfectly.

Alright, could be involved with the presets MS uses may have been corrupted on your UE install. I want you to navigate in your content browser to Engine\Plugins\Bridge\Content\MSPresets\MSTextures and verify these files are there and intact.

image

If they are fine, then we might have to reach out to Quixel’s team over on their forums to see if they have an idea.

Disclaimer: One or more of these links are unaffiliated with Epic Games. Epic Games is not liable for anything that may occur outside of this Unreal Engine domain. Please exercise your best judgment when following links outside of the forums.

I see this, i think look like yours. That seems good.

I’ve exhausted my ideas for this one, the usual suspects aren’t the issue. I’d go ahead and try their support forums I linked before, or hopefully some material/quixel master community member on this side comes across the post and has seen this specific permutation of the issue. If they can’t resolve it there, it will warrant a bug report most likely.

Thank you for your help and effort. I’ll try the forum you linked too. Cheers

If they do figure it out over there, feel free to return to this post and let us know, it will help other forum users in the future if they end up with this wonderfully odd issue. Good luck!

hi, have you found a way to solve this problem?