@ThisIsAnto_@TimSweeneyEpic@InputStarling Recent Macs, not macOS, are really great hardware that I much prefer to use compared to basically everything else.
It's silly I have to use a Windows workstation just for UEFN when everything else I do (including non-UEFN game development) is on Mac and even works better there.
@TimSweeneyEpic@InputStarling 🥀
This feud is blocking UEFN devs from using some of the best hardware. Surely there are solutions that can be found before the final resolution?
Epic wouldn't bring #UEFN to macOS, so I did*, with PIE support. It runs #Verse and devices without session.
Here are a couple unmodified UEFN templates running on a MacBook Air M5 without internet:
Epic wouldn't bring #UEFN to macOS, so I did*, with PIE support. It runs #Verse and devices without session.
Here are a couple unmodified UEFN templates running on a MacBook Air M5 without internet:
Having this version of ~UEFN also enables headless parallel workflows, which is arguably the most interesting part but not as easily showcase-able. I may post more on that later.
It should also be mentioned that a MacBook Air is not the right range of hardware to use this decently, but it makes for a nice catchy post. Of course higher range Apple hardware is better suited.
Here is another more concrete UEFN game example that's not just a template. What I mean by approximation is visible here, the movements and sword mechanics are not 1:1 to Fortnite but it doesn't matter to get the game iterated on.
Software that gets in your way and enforces arbitrary requirements, like long iteration times hopping through Epic's servers on a Windows-exclusive editor, can no longer exist in the age of AI. Years of annoyance can go away on your own initiative.
I would still much prefer this to become an official thing so this version doesn't need to keep being maintained through updates. The live bugs need to be reimplemented as features here. 🙃
@EpicVogel@TimSweeneyEpic
It runs natively (not emulated) built on top of UE6 with patches and shims to simulate the server. It can open and edit a real UEFN project without compatibility issues and sync/check-in to Lore.
*Things mostly work. It's not perfect, it's not 100% implemented either. It's close enough to be usable for the purposes of iterating on a game, and can keep being improved as parity issues are met.
For legal concerns, I didn't implement launching Fortnite sessions from it. Final testing and publishing still require a real UEFN instance.
Epic hasn't enabled PIE for UEFN because it requires the Fortnite servers’ code. What they missed is that for anti-cheat sensitive mechanics or other private service concerns, an approximation is sufficient. The goal is not to play competitive Fortnite inside the editor, only to build games. AI could build and maintain a non-sensitive server variant for them.