Quixel Help Center home page

A broken form of modeling is imported.

Completed

Comments

6 comments

  • Hello hong123,

    Thanks for writing in. Within Bridge please check your Download and Export Settings to ensure that you're downloading LODs with lower numbers. For example, LOD0 will be a higher polycount mesh than LOD1, 2, or 3. 

    The higher the LOD number, the more decimated the asset will be, resulting in a lower visual quality when viewed up close.

    If you're experiencing the same issue when exporting LOD0, please feel free to let us know!

    0
    Comment actions Permalink
  • hong123

    hello! LAN.

    Even if i change the lod number, the modeling is exported the same. I have the same problem on my home computer and my company computer. I didn't change the initial export settings.

     

    0
    Comment actions Permalink
  • PaN*

    I have faced the same problem and i think i've found a solution. 

    Click on your model in blender and check your shader editor, i think your problem is the same as mine, by default when importing from bridge things seems pretty fu**ed up :

    - Roughness map is connected to "Specular" in the BSDF window, it should connect with "Roughness"
    - Normal map is connected  to "emission strength", you should connect it to "Normal"
    - Clearcoat is set to 1,450, you should set it around 0 for that kind of rock.

    Pretty annoying to do for each tecture but i hope it will be fixed soon (i'm looking at you, Quixel staff :D )

    Let us know if you face the same issues, maybe it could help Quixel team.

    I hope it will help some of you, sorry if my english is not that good, i'm french !

    1
    Comment actions Permalink
  • PaN*

    To prove my point, here is what i get in "shader editor" when importing a model from bridge : 

    1
    Comment actions Permalink
  • hong123

    Thank you PAN! It was a simpler problem than I thought, but I didn't know at all. Thank you!

    I can't speak English well either. I'm a Korean.

    0
    Comment actions Permalink
  • hong123 PaN*,

    Thanks for updating the thread - please note that the nodes in Blender's material editor are misconfigured because Blender 3.0+ isn't currently supported by our plugin. The latest supported version is 2.93.

    I'm glad to hear you're up and running by manually configuring the maps though. I apologize for my previous misunderstanding!

    0
    Comment actions Permalink

Please sign in to leave a comment.