CRITICAL - Verse Devices are not spatially loaded anymore

General Issues and Bug Reporting
, ,
1

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Assets

Summary

Since the 26.20 update, all my Verse Devices are not spatially loaded anymore, which means they can’t reference any other spatially loaded asset (such as all the fortnite devices ?)

Steps to Reproduce

Place a Verse Device that references any device on which we can’t uncheck “Is Spatially Loaded”

Expected Result

Map should validate as before

Observed Result

This is one of my new 200 errors that are popping off :
Non-spatially loaded actor /FortTag_io/BACKUP_FortTag_io.name picker references Spatially loaded actor /FortTag_io/BACKUP_FortTag_io.Button41

image
image1215×71 4.05 KB

image

Platform(s)

PC

2

We are having the same issues with our devices, and there are many entries complaining about the “Device_Trigger_Perception_V2_C” being spatially loaded and this device doesn’t have the “Is Spatially Loaded” option to disable it.

3

Incident has been created. Status is ‘Awaiting Validation’.

4

same here:

image
image1920×1080 252 KB

1 Like
5

Here too:

image
image1897×950 232 KB

6

image

7

I have that problem too. The only work-around is switching off Level Streaming inside World Settings. I know that it’s far from ideal and may not be applicable in every case (bigger maps) but it’s the only one I came to. I hope Epic will fix it soon :upside_down_face:

8

same. only 500 errors :upside_down_face:

1 Like
9

Same for us with 265 errors

2 Likes
10

We’re taking a look, thank you for the report.

11

@im_a_lama

3 Likes
12

Thanks for the report.

We’re looking into a fix, but in the interim if you resave the devices that are listed as being spatially loaded it should address the issue.

E.g.

Non-spatially loaded actor /Project/SomeActor references Spatially loaded actor /Project/SomeName.HUD_Message_Device

Resave SomeName.HUD_Message_Device.

You should be able to do a bulk-save using the Outliner.

2 Likes
13

@GrantGoldkey This didn’t work for me. I have a mix of devices as well as normal actors that are referenced as “spatially loaded”, if that matters. In any case, resaving the referenced devices or other actors did not solve the problem for me.

Note, in my case, all the “non-spatially loaded actors” that reference the spatially loaded actors are my creative devices. Every one of them are throwing these errors at the moment.

Ex:
Non-spatially loaded actor /Grind/Grind.AnimatedBounce references Spatially loaded actor /Grind/Grind.Cube Disco Orange4

“AnimatedBounce” is a creative device.

For good measure, I also tried re-saving all the creative devices. That didn’t work either.

14

In this case can you try changing Grind.Cube Disco Orange4 so it’s not spatially loaded? It should be a property on the actor.

15

Hey everyone!

I wanted to follow up here with some clear steps to take to address this issue. For any maps that are still experiencing these errors, here are the steps to resolve / mitigate.

Steps to re-save all the Verse Device instances manually:

  1. Relaunch UEFN.
  2. Open affected project.
  3. Select all the Verse Device instances in the Outliner.
    FixNonSpatiallyLoadedActors_Step1_SelectAllVerseDevices
    FixNonSpatiallyLoadedActors_Step1_SelectAllVerseDevices1920×715 116 KB
  4. Right-click on the select actors and then choose to Save Selected Actors(s).
    FixNonSpatiallyLoadedActors_Step2_ManuallySaveVerseDevices
    FixNonSpatiallyLoadedActors_Step2_ManuallySaveVerseDevices664×539 47.3 KB
  5. After that the non-spatial actor errors will be cleared.
    (Optional) Creators can simply load recent levels to check if the errors are cleared or not, the errors would be displayed when the map is loaded.
    FixNonSpatiallyLoadedActors_Step3_Optional_ReloadLevelToTestFix

Apologies for the inconvenience and confusion this has caused, please don’t hesitate to reach out on this thread if you have any additional concerns or are having issues clearing out the errors. Thanks yall!

20 Likes
16

This worked for me! Thank you

1 Like
17

Hey, this is happening with the Constraints Manager but the re-saving doesn’t fix it, do you know what the solution could be?

18

@DimensionDragon Thank you for your report! Can you please re-post using the “New Issue” option on the Issues and Bug Reporting forums? Posts with this feature are connected directly into our development team so we can quickly get to them!

For more information, such as how to get the reference ID, please check out the article here: Using the Creative and UEFN Bug Reporting Form

1 Like