Oh, I didn’t actually know that! Thank you for the clarification Vexar & Zeblote!
@Vexar & @Zeblote - Since I know now that 4.27 cannot be upgraded (Even though the Project I tested with does seem to upgrade most of the way, for some reason) to UE5 at this time. I’ll give a bit more context to what I was doing, that I think is worth mentioning now.
(1) When I first started on my project. I created 4.26 (in Windows) and everything was working as normal.
(2) I recently went on a trip and brought my Mac Laptop around to create a new project in 4.27, to do some Level Design. (This is the level that I pointed out that wouldn’t work in my UE5 project)
(3) After I returned, I wanted to migrate my 4.27 Level into my 4.26 project and learned that Maps were not cross-compatible and the way to address this. Was to upgrade my 4.26 project to 4.27 and then migrate my Level from my Mac to my newly upgraded project to combine the two.
(4) Everything seemed to be working fine in my upgraded 4.27 project.
(5) I thought I’d give upgrading my combined 4.27 project to UE5 a try and noticed that the one specific level that I wanted to use. Did not seem to be working.
The odd thing, is that I have other Levels that were originally created in 4.26, later upgraded to 4.27 that seem to be working in my UE5 upgrade.
I know UE5 is heavily under development, so their are bugs to be expected and I can’t speculate to why it failed. But it was still interesting, nonetheless.