Material Instance refuse some texture

I’m making my Landscape material and run in a problem. My material got a texture object parameter. In the material itself I can use any texture I want as the parameter, but in the instance material, I can’t add texture from megascan for exemple (but I can choose some (all?) of the default one of UE). Any idea what I’ve done wrong?


[quote=“Inqui. Morphéus, post:1, topic:1710522, username:Inqui.Morpheus”]
specifically with textures from sources like Megascans. Here are a few steps you can take to troubleshoot this problem:

  1. Texture Import Settings: Ensure that the textures from Megascans are imported into Unreal Engine with the correct settings. Sometimes, textures may not be compatible with certain material parameters if they are not imported properly. Make sure the texture formats, compression settings, and mipmaps are set appropriately.

  2. Texture Size and Format: Check the size and format of the textures from Megascans. Unreal Engine has certain limitations on texture sizes and formats, and incompatible textures may not be selectable in material instances. Try using textures with standard sizes and formats supported by Unreal Engine.

  3. Material Instance Setup: Review the setup of your material instance to ensure that the texture object parameter is configured correctly. Make sure the parameter is set to accept textures and that the texture sample node in the material graph is connected to the correct parameter.

  4. Reimport Textures: Try reimporting the textures from Megascans into your project to refresh their settings and ensure they are recognized properly by Unreal Engine. Sometimes, reimporting can resolve compatibility issues with material parameters.

  5. Check Material Domain: Verify that the material domain of your landscape material and material instance is set appropriately. Texture object parameters may behave differently depending on whether the material is set to Surface or Landscape.

  6. Debugging in Material Editor: Open the material instance in the Material Editor and check if there are any error messages or warnings related to the texture object parameter. This can provide clues about what might be causing the issue.

  7. Community Support: If you’re still unable to resolve the issue, consider reaching out to the Unreal Engine community forums or other online resources for assistance. Other users may have encountered similar issues and can provide insights or solutions based on their experiences.
    THANKS.

I found the reason. Texture from megascan are “virtually streamed texture”, if you transform them in “streamed texture” you can put it in the material instance. It still feel weird since you can add virtually streamed texture in the material itself but alas, I now have a solution.
PS: Is just-in-e a chat bot, feel like IA response? but thanks anyway

Hey, I’m not an IA

sorry if you are not. The list, the bold, the thanks at the end all made me think of chat GPT. Still think you are BTW

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.