Pushing changes fails the game to stop.

Summary

This happens when a game is running in edit session and u push changes. To push changes it needs to stop the game first but it fails at that.
This happens since the 42.00 update.
It happens a lot.

It get stuck at the stopping game text and then u get error saying connection lost.
After that u cant just launch a new session it says failed to connect to beacon.
You have to restart uefn for it to work again.

It happens like 50 times a day and it makes it hard to work in uefn.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Stability

Steps to Reproduce

Make some changes so push changes becomes yellow.
And then push changes while a game is running.

It doesnt happen everytime but it happens a lot.

Expected Result

It should stop the game and changes should be pushed to the server.

Observed Result

Instead you get the stopping game progressbar stuck at 25%
After few minutes in game it kick u out and says connection lost.
If u try pressing launch session again it fails and it says : failed to connect to beacon.

So you have to restart uefn to start a new session.

Platform(s)

pc

Upload an image

Additional Notes

This is happening after the latest update. i have scene graph enabled and i have UEFN mcp toolset enables, i dont know if the mcp is the reason. But i have mcp enabled since latest update.

1 Like

I have this same issue. I notice it happens most if my game client is in “Game Mode” and I leave to make edits in the editor. Then I want to push those changes and the game gets hung up and I can’t get the game to stop, implement changes and then continue in edit mode after the changes (that’s how it’s set up in my settings to work: start in edit mode, and then start game manually).

1 Like

Hi

Thanks for reporting this issue, I’ve escalated it internally.
Could you provide me with your island code so we can reproduce the issue?

1 Like

This happens to me as well. after some digging yesterday. it’s directly related to the number of object / devices / props in the level. I added a few hundred yesterday and it went from taking a long time to actually timing out. Once I removed them it went back to taking a long time but not timing out.

Hey!,

This is not island specific. It happens UEFN in every project/island.
I am working on a new project which doesnt have a island code.

I think its not only with pushing changes, also when u compile verse code.
It makes it really hard to work i restart uefn like 50 times a day.
I really hope it gets fixed. if you need logs let me know.

1 Like

Hey,

I am not sure but i dont think it has something to do with that, My project has 80 objects in the level ( its pretty empty ) And it keeps happening like every 5 minutes.

1 Like

Same here. My project is fairly small right now and I still get this issue very consistently.

1 Like

I’m now getting an additional issue that I believe is related. I have the game client in edit mode int the background, and I make changes for a while in uefn, and then I go to push changes and refresh of edit mode times out and I crash to the game lobby after being stuck on the loading screen for a minute or two.

I have to completely exit fortnite, and uefn, and then restart uefn in order to test my map again. It’s consistent. It’s bad. I might have to exit fortnite every time I’m done testing the map for a while, and launch a new session for the new tests.

1 Like

Yeah seems like similar issue as mine.

You push changes or compile and the game doesnt stop or respond anymore and connection just drops.

U get kicked to the lobby after a few minutes.
And when u try to start new session it says failed to connect to beacon.
Only way is to restart uefn to be able to connect again to a new session.

Are you using the MCP toolbelt? this issue is since the latest update so idk if that is causing it or something else.

I’m not using the “MCP toolbelt” or anything mcp yet. That a future endeavor for me that i’m not ready to tackle yet.

Yeah, it seems as though our issues are highly similar.

1 Like

FORT-1144724 has been ‘Closed’ as a duplicate of an existing known issue. Origin Issue: FORT-1146853

FORT-1146853 is ‘Closed’ as ‘Fixed’. The issue will be addressed in 42.10.

1 Like