Summary
A creative_device that writes to properties (text/texture) on a level-placed Widget Entity (a UMG widget exposed to Verse via @editable) from a triggered event handler can cause a hard client crash when 2 or more players are present in the session. Immediately before the crash, the log shows:
LogScript: Warning: Script Msg: No world was found for object (.../LevelEntity.LevelEntity.<WidgetEntityName>) passed in to UEngine::GetWorldFromContextObject().
followed within roughly half a second to a second by:
LogWindows: Error: === Critical error: ===
LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x000000000000005c
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
UI/Tools
Steps to Reproduce
We reproduced this with two different device configurations:
- One Widget Entity shared across up to 4 players, with the device writing into player-indexed properties (
Field_0,Field_1, … /Field_P1,Field_P2, …) on that single entity. - One Widget Entity per player (dedicated 1:1 entities, no shared state at all), built specifically to test whether entity-sharing was the cause.
Both configurations produced the identical crash signature (“No world was found for object” naming the Widget Entity, then EXCEPTION_ACCESS_VIOLATION). This rules out cross-player entity sharing as the cause and points instead to: writing to a Widget Entity’s properties before that entity’s World/streaming context is fully established is unsafe and can hard-crash the client, and this condition is far more likely to be hit as the number of concurrent players (and therefore concurrent streaming load) increases.
Steps to Reproduce
- Place a UMG Widget Entity in the level and expose it to a
creative_devicevia an@editablefield (widget entity type, not a HUD/player-UI controller). - In the device, subscribe to a
volume_device’sAgentEntersEvent(and/orAgentExitsEventon a second volume), and in the handler, after a shortSleep, write player-specific data into the Widget Entity’s properties (e.g.set Widget.SomeTextProperty = ...). - Start a session with 2 or more players.
- Have players repeatedly walk through/return to the trigger volume (e.g. respawn and walk back to the area, or a second player entering shortly after the first is already established).
- Crash occurs intermittently, correlated with a second (or later) player’s re-entry into the area — not on the very first player’s initial entry, and not reproducible in single-player testing under the same repro steps.
Note: the timing-dependent nature of this means it isn’t a 100%-repro-every-time bug; it appears to be a race between the Widget Entity’s own streaming/replication and the Verse write into its properties, which becomes far more likely to lose under multiplayer load.
Expected Result
Writing to a Widget Entity’s properties from Verse should either (a) succeed safely once the entity is fully streamed/valid, or (b) fail gracefully/no-op (e.g. via a Verse failure context) if the entity isn’t ready yet — but should never cause a fatal, unrecoverable client crash.
Observed Result
The client hard-crashes with EXCEPTION_ACCESS_VIOLATION reading address 0x000000000000005c, immediately preceded by an engine log warning that the Widget Entity object being operated on has “no world,” i.e. UEngine::GetWorldFromContextObject() failed for that object. This is a full client crash requiring relaunch, not a recoverable script error.
Platform(s)
- PC (Windows) — reproduced
- Xbox Series X — reproduced
Additional Notes
- Reproduced with both a single shared Widget Entity (4-slot design) and a redesigned 1:1 per-player Widget Entity variant — same crash in both, which is why we believe the root cause is entity-streaming-readiness rather than data-sharing across players.
- crash logs
- Happy to provide the Verse source for both device variants if useful for repro on Epic’s end.
relevant crash log: _Verse/VNI/VerseFortnite.Characters_fort_character_component for object PlayerPawn_Athena_C_2147482643 (type: PlayerPawn_Athena_C)
[2026.08.18-09.28.58:356][983]LogDynamicUI: Warning: Tried to Remove a Scene that is not active: UIScene_GliderReleaseUI_AerialFeedback [FortLocalPlayer_2147482646]
[2026.08.18-09.28.58:571][996]LogScript: Warning: Script Msg: No world was found for object (/76d20fa3-46d9-6d05-2621-d48c16b52892/NewMap_LevelInstance_1.NewMap:PersistentLevel.LevelEntity.LevelEntity.UserInterfaces-Verse-InIslandTransactions-Demo02-Widgets-WBP_SessionP2_entity_76wvzkj2yhti_1270127965) passed in to UEngine::GetWorldFromContextObject().
[2026.08.18-09.28.59:118][996]LogWindows: Error: === Critical error: ===
[2026.08.18-09.28.59:118][996]LogWindows: Error:
[2026.08.18-09.28.59:118][996]LogWindows: Error: Fatal error!
[2026.08.18-09.28.59:118][996]LogWindows: Error:
[2026.08.18-09.28.59:118][996]LogWindows: Error: Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x000000000000005c
[2026.08.18-09.28.59:118][996]LogWindows: Error: