Search
-
Re: Best practices when creating assets specifically for Nanite
Hi guys, thanks for all the information, it`s a bit hard to find practical information that its reliable right now... I am currently trying to build a small, stylized, ancient sci-fi environment with nanite workflow, I'm still trying to give the first pass on everything. The idea is to have a dense environment, with more… -
Re: Best practices when creating assets specifically for Nanite
Interesting about continuous meshes. That might actually be very relevant to some of the kitbashed models we're doing, I'll make sure to look into that. Re: large polygons, let's say I have a large flat plane as the floor of a building, for example, is there a chance it'd be beneficial to add otherwise unnecessary loops… -
Re: Best practices when creating assets specifically for Nanite
- I like to keep meshes 1 million or less just because much larger slows down iteration and import times. -Try to use mostly continuous meshes and avoiding really large polygons is ideal. If you have a pile of small rocks for example, your better off booleaning it together or shrink wrapping a grid on top of it. Culling is… -
Re: Best practices when creating assets specifically for Nanite
Under a million tris without long thin triangles is better. You can have 1-2 mil tri meshes too but UV ing those is a nightmare. You have two bake options, one is to bake the nanite mesh with itself or have one mesh under million tris and bake high on top of it. Above million its going to be an issue with file size… -
Re: Best practices when creating assets specifically for Nanite
It's also important to know that Nanite does use Fallback meshes, depending on the platform the original mesh topology and workflow is required. Your tech artists will thank you for maintaining baked workflow. Like others have said, baked workflow is generally always still required because texturing workflow will also…
5 results