![]() ![]() Is it possible to get some clarification on support for MacOS and Linux at least?Īlthough I don’t want to speak for Unreal them selfs, but I might be able to shed some light on the issue, both Lumen and Nanite has hardware incompatibilities with the Apple own hardware… its not a performance thing its a code compatibility thing.įor example the Lumen uses path tracing to deal with light dynamics, and although the Mac hard can do it, its completely different architecture to the Nvidia and AMD, They would need to support Metal for starters…įor a very similar reason the base engine would not able able to use Apple Graphics for like Nvidia Cuda or AMD equivalent so they would need to use Metal once more, and combine the logic of the Apple Neural engine, plus graphics cores. Lumin and Nanite support on Windows and Next gen consoles only at the moment. I was really interested to see how they performed and perhaps send a few test levels off to users to compare, but given that I can’t use them on my development platform - makes things a bit pointless to try. ![]() However, the lack of Lumen or Nanite support on MacOS at this point has stopped me a bit dead. Over various iterations of my projects I can be pretty confident that the executables I make will just work (although I can use a VM if I need to test on Windows/Mac specifically) One of my main reasons to use an engine is that I can very simply publish a game on multiple platforms - so I have pretty much the same code to produce a Steam distribution on Linux/Mac/Windows and the appropriate app stores for Android and iOS. Given that the beta of UE5 has created quite a stir, I was keen to jump and see if it was time to move away from Unity.
0 Comments
Leave a Reply. |