When trying to create an environment with nanite assets from megascans, they look blurry. Been trying to follow this youtube tutorial Unreal Engine 5 Beginner Tutorial | Desert Canyons - YouTube but the render i do looks nothing like it. Seems like something is off. Been searching every corner of the internet for the last 6 hours but haven’t found a solution yet. Have anyone got the same issues? Tried with 2 different computers as well.
Check the resolution of your imported textures.
Might have been imported at a lower resolution.
Hmm that is strange indeed.
Try creating a new material and adding the textures manually to see if it makes a difference.
I use the desktop version of bridge and import myself.
So im not sure if it’s something that the plugin does when importing that is messing something up.
edit: just quickly imported one of the sandstone cliff ridges at only 4k resolution at lod0 and it looked fine.
Hi there,
I have the exact same problem 
I am happy to see that I am not the only one that encounter this problem…
For my level design, I am using 3D assets from Megascan, imported with bridge. (nanite quality selected)
I don’t know if the problem is from the material, or the mesh…
the assets of the demo level from Epic looks the same,
Hardware is ok, i9 12900k & 3090
All drivers are updated too
There’s a few different things going on in the different posts.
Those models are about a million tris, sounds like a lot, but that’s not going to hold up from a normal third person view, to an ant view. You still need to be smart about how you are using meshes and understanding how much detail there is, and from what distances they will be viewed from. Often with these demo scenes, small detailed meshes are placed close to the camera, larger less detailed models are placed further away.
Same thing with 8k textures, 8k sounds like a lot, but if you’re zoomed in looking at 1/8th of the model, the texture resolution is only going to hold up on 1080p displays. This is why tiling/detail textures are super important.
Make sure you increase the position precision under nanite settings in the static mesh editor if a model is going to be close to the camera. You can see what resolution nanite is using with auto on the top left of the viewport.
To make sure Quixel Bridge / Megascan models are coming in with full detail, you can disable nanite and check the triangle count.
2 Likes
Yeah have the same problem. If i go nanine visualization the colse object got fewer, bigger triangles… so I dont think thats right?
Josh
Yo,
had this issue yesterday- solved it.
The reason why - I’m not sure.
The solution, verify you’re using the right resolutions, build your lighting in “Production” and then you should notice the detail has been built into the project, if it persists you can try baking the material onto the mesh.
i don’t have this issue no more.
also, try rotating or moving your lights or supplying a little more.
Distance is part of it, but not all Megascans are equal, something to keep in mind. For me issue is sometimes the Nanite settings themselves need to be changed in the static mesh settings, I think minimum residency and position precision set to 1/8192 or something like that. Doesn’t fix it all the time and is expensive in render but can add detail back in not loaded for some reason by default.
I would imagine newly released Megascans would have MUCH better detail and fidelity than those of two or three years ago, so maybe some users are running into old models expecting 5.1 quality. But for 8k maps to look that bad on import is just a big fault on Quixel’s part, import bridge should be working fine after 3 years of this pretty inexcusable.
On your console enter the following:
r.streaming.poolsize 0
Then look closely at the debug messages when playing in viewport, it seems like that you’ve hit the limit on the texture budget (8k Textures)…
In my case is due to Texture Streaming. But if I disable it in project settings the editor become very laggy and the GPU crashes. Trying to keep the streaming on but setting the PoolSize to a big value like 5000 or 10000 doesn’t resolve the problem completely but causes already a few crashes… I don’t know what to do
In my case the problem was with virtual textures, when i’m blending objects with lanscape. If i turn it off everything is sharp and high res eaven in far distance.