v43.00 Known Issues and Pre-Release Updates

Here’s what to know ahead of v43.00: the known issues we are tracking, the community fixes shipping in this release, and updates to previously announced fix versions.

For the latest on known issues and recent fixes for the Discover redesign, see Discover redesign known issues. Discover Redesign Known Issues

v43.00 Known Issues

SceneGraph: deleting a referenced entity doesn’t clear the reference when Entity Proxy Actors are disabled

  • When Entity Proxy Actors are disabled, deleting an entity that other entities reference doesn’t immediately clear those references. You don’t need to remove them manually: the references clear when you save, and the scene loads correctly the next time you open the project.
  • Fix targeted for v44.00 (December 5)

Pump & Dump’s Shotgun and SMG fire together when pressing the secondary fire button

  • With the Pump & Dump equipped, the secondary fire button fires both the Shotgun and the SMG, so players can’t fire the SMG on its own.
  • This affects all rarities and the Lawless Blink Pump & Dump.
  • Fix targeted for v43.10 (November 12)

Standalone entities you copy and paste don’t live edit into a running session

  • If you copy and paste a standalone entity after launching a session from UEFN, the entity is added to your project in the editor but does not appear in the running session.
  • Workaround: Click Push Changes after pasting to update the running session, or use a prefab instead of a standalone entity.
  • Fix targeted for v43.10 (November 12)

“Ensure condition failed” error when launching a project or clicking Push Changes

  • When you launch a project from UEFN for the first time or click Push Changes, an “Ensure condition failed: Attempt to retrieve FApp time on a thread where there is no inherited time context” error appears. This doesn’t affect functionality.
  • Fix targeted for v44.00 (December 5)

Updated Fix Version
The following fix has moved to v44.00 (December 5):

  • Non-leader party members get a Matchmaking Error #1 when readying up after Retry, instead of being sent back to the lobby.

v43.00 Top Community Fixes
These fixes come from issues you reported on the forums. Thanks for flagging them.

Fixed an issue that allowed players to equip Pickaxes with built-in emotes while Pickaxes were disabled, letting them damage other players.
Forum Post Pickaxes with Built-in Emotes can be equipped when Pickaxes are off, ruining round-based PvP experiences

Fixed an issue that prevented basic_interactable_component.Cooldown from running when an Interactable Duration was also set.
Forum Post basic_interactable_component.Cooldown doesn't execute when we have an Interactable Duration

Fixed an issue that prevented migrated assets from appearing in the destination project until UEFN was restarted.
Forum Post UEFN Asset Migration requires UEFN restart to work

Fixed an issue that prevented the Virtual Pointer from being moved or used with a controller on PS5.
Forum Post Virtual Pointer does not work with a controller on PS5

Fixed an issue that prevented VFX from playing when activated through Sequencer.
Forum Post VFX being activated and deactivated through Sequencer doesn't work

Fixed an issue that caused Material Editor error hyperlinks to open the Content Drawer instead of jumping to the error’s location in the graph.
Forum Post The error tracing functionality added to the Material Editor in 39.00 is not working.

Fixed an issue that caused an interaction prompt to appear on screen when Disable() was called on an interaction_component in Verse.
Forum Post When you Disable() interaction_component in verse it shows the msg on the ui before its disabled

Fixed an issue that caused UEFN to crash when assigning a device to an optional @editable property on a Verse component.
Forum Post Editor Crash When Assigning a Device to an Optional Editable Property on a Verse Component

For the full list of fixes scheduled for v43.00, see this search on the Epic Developer Community Forums Search results for ''Closed' as 'Fixed'. The issue will be addressed in 43.00 order:votes' - Epic Developer Community Forums

PCG Mode spline meshes made with the Spline Mesh tool render with the default gray material in sessions

  • Structures built along a spline with the Spline Mesh tool in PCG Mode, such as fences, walls, and railings, look correct in the editor but render with the default gray material in sessions and for players. The editor shows no warning.
  • Workaround: Place the mesh along the spline with the Spacing tool instead. The meshes won’t bend to follow the curve, but they keep their material.
  • Fix targeted for v43.10 (November 12)

PCG Toolset: Distance node with a To Point-converted volume as Target hangs the editor

  • If you work with PCG through UEFN MCP, a Distance node that targets a volume converted with To Point can hang the editor with no timeout, cancel option, or warning. You have to force-quit the editor, and unsaved work is lost.
  • Workaround: Save before running large graphs. Using a Create Points node with a single point as the Distance target may avoid the hang.
  • Fix targeted for v44.00 (December 5)

PCG Toolset: call_tool rejects dotted tool names with a vague “not found” error

  • If you call PCG toolset tools through UEFN MCP, a fully dotted tool name returns a vague “not found” error instead of explaining that the toolset name and tool name are separate fields.
  • Workaround: Pass the toolset name and tool name as separate fields (toolset_name and tool_name).
  • Fix targeted for v44.00 (December 5)

Verse: false errors on Await() for events in Visual Studio Code

In 43.00, Visual Studio Code may show errors when you call Await() on an event or a listenable, for example Interactable.SucceededEvent.Await(). You may see:

  • Unknown member Await in listenable(agent)
  • Invalid access of internal function (/Verse.org/Verse/event:)Await
  • All the top level expressions in a ‘race’ macro must be async
  • We’re investigating now

The VS Code Verse extension shows incorrect errors when you call Await() on an event or listenable, for example Interactable.SucceededEvent.Await(). Errors include Unknown member Await in listenable(agent) and Invalid access of internal function (/Verse.org/Verse/event:)Await. Your Verse code still compiles and runs correctly in UEFN, so these errors can be ignored.

Widget Blueprints: adding an Event variable causes compile errors

In 43.00, adding a Verse Event variable to a Widget Blueprint causes the widget to fail to compile, and the event can’t be used from Verse. Widget Blueprints created before 43.00 that already have Event variables still compile.
Workarounds:

  • Top-level widget: after adding the Event variable, reload the asset (right-click it in the Content Browser and select Reload) or restart UEFN.*
  • Child widgets: add the Event variables to the parent widget instead.*
  • We’re working on a fix.

Unreported Memory Calculation Blocking Publishing

  • We are investigating an issue in UEFN where the Memory calculation is not being reported correctly, which could block publishing.
  • We will provide an update when we have more information or a fix.

This issue has been resolved. Thank you for your reports!

Verse Validation Error [FIXED]

  • We’ve deployed a fix for an issue where some islands couldn’t publish because of a Verse validation error about ambiguous identifiers, even though the code compiled in UEFN.
  • If you were affected, upload a new version from UEFN (no changes needed) and publish that version.
  • Older versions may still show the previous error.

Thank you for your patience while we worked through this!

Verse Language Server Regression

  • A regression in 43.00 caused the Verse language server to falsely report usages of Await or other transitive references to it as errors in your user code, even if it compiled fine in UEFN.
  • This has been fixed in an upcoming release.
  • In the meantime, we are providing a .vsix extension that you can install separately that will temporarily work around the issue.
  • You can install this manually in VS Code.
  • We are actively working on a separate update to make the Verse language server more reliable and not report spurious errors in a future release.

If you are seeing that your project is falsely reporting errors in your code related to usages of `Await`, you can install this extension in your VS Code session by opening VS Code, going to [View → Command Palette], and then choosing [Extensions: Install from VSIX…] and choosing the `.vsix` file provided here, then restarting VS Code.

verse-0.0.59596594.vsix (22.8 MB)

Publishing blocked due to backend dependency returning an unexpected error

  • We are aware and looking into fixing this issue

Publishing has been resolved!