"We Hit A RoadBlock" | UEFN Session infinite Loading / Won't launch

It turned out that my map was not in a version prior to 30.00, so I already had that disabled in my island settings.

I don’t have any custom static meshes created yet, so that checks off

I ran the Fix Validation errors through the Outline and it came back as no actors needed to be fixed.

i never had skydome devices in my world, just the day sequence device

GUYS I HAVE AN ANSWER. I had this problem too for 2 days, I tried a lot of different things but what worked out for me is just verifying the fortnite files in epic games.

@PeacefulGhost - did you get this resolved?

Well much of my time was spent on this just gave up. Told @PeacefulGhost that it was 28.30 and even though removed SkyDome device and put in the new device.
To bring this to current-day standards would require exporting 200 assets and on the new 32.00 when these then became over 100k. The reference system for Quixel assets would not work with Fab and the were numerous power of 2 errors . Further to that a new Verse update came in and all the paths changed. Any attempt to publish failed.
With so many errors we gave up. Lots of others tried but failed

1 Like

FORT-765056 has been ‘Closed’. We’re unable to reproduce this issue.

Having the same issue for the last week or two. My session doesnt launch in any of my islands.
I guess its happend in case of the latest update, because it worked earlier

hi @Y_a1 ,

This is a very old thread/post, it relates to 29.30, and could not be fixed, due to the age of the original island.

The error is “we-hit-a-roadblock” often means something different.

Often, this is an old island, and the simplest way is to open a new island to import all the assets

Possibly try an example

How to copy a UEFN project - Development / Getting Started & Setup - Epic Developer Community Forums

Migration is the only thing I tried

Found this

YouTube video

How to duplicate or copy a UEFN Project Easily! #uefn fortnite

This fixed the error for another user

If this does not fix this, open a new thread or search for the same error in the title of the thread