UE5 is a game changer in a lot of ways, but I personally would not begin to migrate any projects over to it yet. They are looking for people to hammer out the bugs with the early access (which is exactly what they should be doing), so you should know what you're getting into if you're going to convert your large project over. You could be in for a lot of pain. I have seen a few reports on /r/unrealengine of projects with custom C++ modules having very little support (docs or otherwise) post-migration.
That said, big features with UE5. Lumen is the biggest imo (bigger than Nanite) because it (in theory) achieves a holy grail of automatic dynamic global illumination, without a super expensive RTX-like raytracing card. The number of lighting problems and lighting-related workflows it will obsolete cannot be overstated.
Nanite is cool, but from my super high-level understanding of the tech, it is only going to work on static meshes where the engine can build the fancy indexes it needs to render dynamic LODs. My understanding is that it won't work on any mesh that needs deformation of any kind (someone correct me if I'm wrong here please).
That said, big features with UE5. Lumen is the biggest imo (bigger than Nanite) because it (in theory) achieves a holy grail of automatic dynamic global illumination, without a super expensive RTX-like raytracing card. The number of lighting problems and lighting-related workflows it will obsolete cannot be overstated.
Nanite is cool, but from my super high-level understanding of the tech, it is only going to work on static meshes where the engine can build the fancy indexes it needs to render dynamic LODs. My understanding is that it won't work on any mesh that needs deformation of any kind (someone correct me if I'm wrong here please).