[DONE] Verse VM test—Friday, September 11, 8am-12pm ET

[Flak]

EDIT:

@rhyan.smith

The test has concluded, and Public/Private UEFN sessions will no longer be running on the New VM. It may take some time (~4hrs) to fully propagate and reach all players/servers.

---

On Friday, September 11, we’re testing a new virtual machine (VM) for the Verse programming language on all Public and Private UEFN sessions, this does not include UEFN edit sessions. The test will run from 8am–12pm ET.

What should I expect?

During the test, UEFN development and Live Edit sessions should not be affected. Players shouldn’t notice any changes either.

Hit something you think is related to the VM test?

Submit a report in this thread and include the following information:

• Did this happen before the test window? If so, when?

• Which island code are you seeing it on?

• Steps to reproduce

• How often does it happen: 10/10 times, or 1/10?

We’ll collect these and prioritize fixes internally before the next test.

[Velocity_Zero]

Very excited to see this.

Does this affect all public sessions, in other words if I hop on my own game during that time frame, will it run on verse vm, so I can properly test it within the new conditions?

[im_a_lama (LAMA)]

I believe it should be random, they say they’re watching for related issues so it wouldn’t be safe to convert all servers ig

[Velocity_Zero]

Yeah I would understand if this is being tested on high ccu based experiences, but I would love to see how my own game behaves with VerseVM enabled under the hood (no promotional plug: 2892-4984-5194).

[rhyan.smith (Rhyan)]

Confirming, yes it affects all public and private UEFN sessions

[BloomCx (Bloom Games)]

Our game Zombie Escape Tag (5263-9200-9917) is currently crashing Verse every round, starting right at the beginning of this test window.

This seems to be happening every round, 10/10 times. We have a crashable script in place that will restart the round whenever a verse device crashes, which restarts the round. But I am not seeing the error in technical tab of creator portal like I normally would, and I cannot replicate this in edit session due to the VM not affecting UEFN sessions.

[IIsanderII]

Assuming this issue is because of this test

We’re using itemization and at the moment every item is showing the wrong icons

Island Code: 9546-9918-8917

[Uaitt]

[CRITICAL] Enabling Custom Items breaks weapon inventory

Summary When Custom Items are enabled, weapon icons are broken in the standard Fortnite UI. In the bottom-right in-game HUD, weapon icons are completely missing. When opening the full inventory, different weapons incorrectly display the Pump Shotgun icon instead of their actual icons. The issue does not occur when Custom Items are disabled. Please select what you are reporting on: Unreal Editor for Fortnite What Type of Bug are you experiencing? UI/Tools Steps to Reproduce Create or open a …

So, is this issue caused by the test?

[rhyan.smith (Rhyan)]

Thank you all for the current reports of bugs and crashes, we’ve got these all noted down and the team will investigate.

Please continue to send in anything else you find

[Klian]

FortPool is currently affected by this change. *timestamps in the video description

FortPool broken

Island’s module got stuck with update 42.0 already, somehow it got unstuck while I was changing modules structure of the whole project.

[Critical] Server's cooker stuck to a specific release.

Summary After the release of update 42.0, FortPool completely stopped working, including the currently released version. Attempting to access the map results in an error, and it is impossible to load the game experience. Original released island (Unlisted): 9311-9744-2560 The first time I launched UEFN after the patch, the project also started crashing in the editor. I therefore began a process of isolating and removing parts of the project to identify the cause. Initially, I identified two i…

• Did this happen before the test window? If so, when? - No, Editor Live Session is still fine
• Which island code are you seeing it on? - 9311-9744-2560
• Steps to reproduce - Join island, start a game (8 ball or 9 ball) and play
• How often does it happen: 10/10 times, or 1/10? - 10/10

[zoramaps]

This morning players can’t matchmake into my map at all: 2276-7799-6979

Steps to reproduce:

1. Select the map in the lobby

2. Queue for a public or private match (with or without a matchmaking code)

Happens 100% of the time, player count has dropped to 0

[Klian]

@zoramaps

2276-7799-6979

I got the same error after update 42.0 while my modules were stuck.
Have you tried pushing an update?

[most3r]

yes

[rhyan.smith (Rhyan)]

The test has concluded, and Public/Private UEFN sessions will no longer be running on the New VM. It may take some time (~4hrs) to fully propagate and reach all players/servers.

[Klian]

FortPool is back to normal. It’s pretty clear it has some issues with the new vm, I’ll be available if the team needs anything
Thanks

[zoramaps]

I published an update during the test window (an hour ago) that I submitted yesterday (20 hours ago), didn’t seem to resolve the issue. I tried launching a new memory calculation to publish that, but the test is over now and it’s working again

[vageuly]

Originally did not see this message when I logged on this morning and we were not given very much advance notice that it would be running, so I just thought our game was broken.

When entering our game Sidekick Masters 8402-7861-9119, players were unable to start the game from the Loading Area, so they were essentially barred from entering the game. This didn’t happen before the test window, and you can see in our CCU the decline after 8AM ET this morning.

Steps to reproduce:

1. Launch the game, get loaded into the loading box.

2. Player is unable to press the ‘Start Game’ button to exit the loading box.

Below is a player video of them unable to start our game.

Most players were unable to enter our game during the time the new Verse VM was testing.

[Klian]

Oh that’s great! I wasn’t able to push any update back then, “cooking internal error” in the creator portal.