This Is Why Your Normal Maps Are Broken In Unreal Engine - DirectX vs OpenGL 

The original marketing caused a huge misunderstanding of nanite and it's true purpose. Nanite's main purpose is as a replacement for the old LOD system. The showcase showed bringing assets straight from ZBrush mostly for marketing. UE5 has been out for a while now and this has been tested extensively across the game industry and in reality, that just doesn't work in a production environment. Sure, you can do that to make some pretty little localized projects, but anything in the real world of games you don't ever want to use that workflow. We tried it at my day job for a while and it ended up not working for three main reasons: 1. There were still performance hits when using nanite meshes that were too high poly. The ultimate decision we came to as a company was to limit our environment assets to 50k triangles. 2. The size on disk was massive. There is a reason why the Valley of the Ancients install was 100GB yet it was a single tiny little level (about a 10th of the size of a typical modern game level). If we had used this workflow, our game would have been at least 2 terabytes in size. 3. It crashed the editor. Opening a 3 million triangle mesh from the content browser would take 5+ minutes on a good day, and just straight up crash the engine on a typical day. Long story short, how nanite is being taken advantage of in real production environments: you still need normal maps and standard game art workflows, but you can get away with a lot more geometry. You can worry less about your triangle count. You don't have to fight your way to reduce something down to 2k triangles, it's okay to leave it at that 10k triangles from the decimated workflow. But using the 2 million triangle ZBrush sculpt of it just isn't worth it.

Here's a video I did a couple years ago when it was first introduced. This section I directly compare a super high poly nanite mesh with a standard low poly version. ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-E0mynSXZYpE.html

@@DigitalAlchemy3D Alright, that clears out a lot!! Thanks so much, man. I am definitely giving it a watch, along all other videos. Really appreciate help.