On Friday, October 23rd, we’re testing a new virtual machine (VM) for the Verse programming language on all Public and Private UEFN sessions. The test will run from 8am–12pm ET.
2026-10-23T12:00:00Z→2026-10-23T16:00:00Z
What should I expect?
During the test, users loading into a UEFN session (live) private and public sessions will be on the New VM.
What’s New compared to the last test?
In 42.40, Creators are able to toggle between the New and Old VM in a UEFN development and Live Edit session by:
Selecting the three dot menu next to the Launch Session button
I was having issue when calculating private version for my map 6883-6554-3354 it was making me leave the the game to lobby then showed me connection error
We had a major game breaking bug that we received the first report for at 5:37AM PST (8:37 EST) which corrupted dozens our user persistent data that we couldn’t explain. We did a hotfix to our game last night and I thought it was related to that, but nothing we could see in code could explain it.
We had to unpublish our game, make a hotfix and have since published the change and things are mostly back to normal. That said, there are several other bugs that are now present that were not like that before (e.g. NPCs walking backwards).
The critical bug seems to have been due to a difference in how the Verse language was compiled and interpreted, and we had to make a change to code to accommodate. Is it possible the new VMs treat Verse code differently? We couldn’t explain why the bug occurred, so seeing this makes me think it might be related.
With this workaround, "Defer" is printed whether Foo completes normally or is cancelled.
However, the workaround no longer works in the new Verse VM. This caused some issues in our island 4388-4237-1339. Although we have no evidence that public sessions have been affected, the issue is consistently reproducible in edit sessions.
Hey, thanks for reporting this. This is actually an expected behavior change. The new Verse VM fixes a bug in tasks where a function return would cancel the task. This is why you saw that branch get cancelled when Foo returns. This was never the intended semantics. In the new VM, returning from a function doesn’t cancel the tasks that the function created. Instead, the task boundary is totally agnostic of function boundaries. The new VM also fixes the bug you notice in defer in the old VM.
Would you be able to update your code to account for this behavior change? You could even write some helpers to conditionally detect which VM is running and adapt the code at runtime to do the right thing for what you expect.
Thanks for the reply. So, is the intended behavior for branch to continue to run even after its enclosing function returns? In my tests, its lifetime appears to be tied to the top-level caller (e.g., OnBegin or OnSimulate), as long as the call chain is direct, with no calls inside race expressions. For reference, since we expected branch to finish when its enclosing function exited, we wrote the following workaround, which worked in both VMs:
Foo()<suspends> : void =
branch:
defer. Print("Sleeping branch workaround for the old VM")
Sleep(Inf)
race:
# Expressions.
# Call site (changed for the new VM).
# Foo() # <- defer expressions within Foo's branch expressions are not cancelled when calling Foo directly.
# When inside a race expression, defer expressions within Foo's branch expressions get called when Foo returns or gets cancelled.
race:
Foo()
Sleep(Inf)
In this scenario, is it intended behavior for the branch expressions to get cancelled?
Yes, exactly. The intention is for branch to continue running until its parent task ends, so either a top-level caller like OnBegin or some other task boundary like race/sync/rush/branch/spawn. Your new workaround should do what you want.
I’ve found a repro. It has to do with hashing structs with mixed default values vs derived values. We had a bug where our hash function would report different hash values for equivalent structs. Fix incoming for 43.10.
Apologies, I don’t get notifications on responses unless I’m on the forum directly, which I tend to only use when I have a bug to report. Glad to see you reproduced it.