Hello folks,
First of all I decided to make this thread to report every kind of issues that I encountered using Unreal Editor Fortnite with CrossOver (surprisingly it does not need Fortnite/EAC to run.)
I'm using a MacBook Pro M1 16GB with CrossOver 24.0.5 (latest stable) + the following options turned on in the bottle: D3DMetal + MSync + High Resolution Mode.
1. Installation problems (very complicated)
Not really a CrossOver issue I know but still impacting users (and maybe that way you can test it yourself). To install the app you would need to download Fortnite and the Unreal Editor Fortnite using Legendary (Heroic won't work, see https://github.com/Heroic-Games-Launcher/HeroicGamesLauncher/issues/4089 for more details) which is very inconvenient despite having it fixed using CrossOver Preview as it makes the Epic Games Store compatible right out of the package.
2. Unreal Revision Control not working while a project is opened.
This is the Github equivalent for UEFN devs to save their projects in the Epic Games servers. I've been testing UEFN with CrossOver since months along a friend, the URC never worked. Let me explain how it's behaving. Basically, when it's behaving correctly you move an element, UEFN automatically detects that a change has been made and show you got unsaved files + show a blue text saying "Check-In a Change" to save the edits in the cloud, that's how it does work using Parallels Desktop or any other Windows machine. But using CrossOver, the "Check-In a Change" button does not turn in blue and keeps the grayed "No changes" text button until you decide either to close UEFN and reload your project OR to load another project then reopen the one you just closed, that's the only way to make it work until you need another change, you need to redo the same steps again and again. I believe it must be an issues due to paths or something I'm not sure but it's very inconvenient. Also, CrossOver should add directly the URC.exe to PATH by default when installing UEFN on CrossOver so people could also use directly the URC out of the package using cmd.exe as the URC CLI works perfectly when running it under cmd.
You can see the issue there on YouTube (unlisted video):
URC not working
And how it should NORMALLY looks after even moving a single object:
3. Black windows artifacts/Slow selection menus
Honestly just watch this video to understand what I mean. Also it's not memory issue as the slow issue seems to have been fixed using CrossOver Preview BUT even using that one, the black artifacts are still present (see even more present than on the stable 24.0.5 version).
4. Bunch of FPath related issues in the UEFN logs
Cxlogs results:
I don't know how to share the cxlog as it has a lot of line and I feel there's a lot of issues that devs could look into. Just run UEFN with logging enabled and open a dummy project, enable URC and test moving some object then close UEFN. You'll see by yourself because I don't know how to send you a 48MB cxlog file but note that there's a lot of "not found" stuff in it that I don't understand.
URC & Editor logs
You can find them in AppData. I can't share it all again it's too big.
Thanks in advance! 😎