Cannot open specific project after update

General Issues and Bug Reporting
, , , ,
1

Summary

One of our projects (Has SG + phsyics if it matters?) is no longer opening and crashes on 71% loading. Crashes for all members.
Different projects load fine. Delete folder and resync from server doesn’t work either.

LoginId:3e695ab847819fa8f740b0b60438ab14
EpicAccountId:b7330695ae84486aab15dbdb184e2f17

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000000

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Stability

Steps to Reproduce

  1. Open UEFN
  2. Select project and open

Expected Result

  1. Open UEFN
  2. Select project and open
  3. Project opens

Observed Result

  1. Open UEFN
  2. Select project and open
  3. Crash at 71% loading

Platform(s)

All

Island Code

2268-7006-2196

Upload an image

image.png
image.png727×595 29.8 KB

2

Having this exact same issue, this is a major issue for us.

LoginId:9a3b3db34799942d62506eb90db2224e
EpicAccountId:3a4cf0801ec348aa9b4483f0a78d8c78

Unhandled Exception: EXCEPTION_ACCESS_VIOLATION reading address 0x0000000000000000

**Same as most other error logs
**
To also point out, the project it self was not using any beta or experemental features at all. Unable to access playtest builds either

3

Have the same bug here. Cannot open project, crashes on 72%

4

+1

image
image1119×899 122 KB

5

Same here I have same problem, anyone cant enter the project and i cant enter the map

1935-8084-1614

7

Thanks for reporting, we’ll get someone to take a look.

8

(post deleted by author)

9

Same here I have same problem, anyone cant enter the project and i cant enter the map

1935-8084-1614

10

Hey Flak,
I don’t see many creators mentioning this, but if you have this issue in UEFN, your map becomes inaccessible. Players can’t load into it and it results in a matchmaking error.

image
image1919×1079 646 KB

1 Like
11

We’re working on getting a fix out for this, but in the mean time have also been trying to identify a workaround to unblock anyone encountering this issue locally.

It looks like this crash is occurring when you have a UMG widget being instantiated as part of your verse class and are setting a default value for one of that widgets fields. Eg:

my_class := class:
    MyWidget:my_widget = my_widget{ MyInt := 1 }

And it seems this crash will go away and you can open your project if you remove the part which sets the field’s value. Eg:

my_class := class:
    MyWidget:my_widget = my_widget{}

If you are able to search through your verse code workspace and remove any examples of this, that should allow you to open your project again.

Instantiating widgets and initializing individual fields in normal functions should work and that can be left. So far this seems limited to just instantiation as part of the class definition.

If you do this and still hit the crash could you please report here with your project’s details like link code or module id and we can investigate further.

Thanks for your patience with this

12

Gonna give this a try, thanks.

1 Like
13

Hey i did it i was able to load in the project and verse is working fine, but when i make memory calculation. And Try to pbulish i get this

image
image597×290 20.9 KB

14

That looks to be a different issue, please start a new thread with your latest information.

1 Like
15

i made one: unable to publish due to verse "internal" error

16

FORT-1039002’s status has changed to ‘Ready for QA’. A member of the QA department is investigating the issue.

17

@Flak We have the same verse error when trying to publish actually! So don’t think it’s a seperate issue! Did the workaround above to unlock the project access.

18

i created a forum unable to publish due to verse "internal" error

19

Thanks, both.

1 Like
20

@flak I as well am having this issue after trying the workaround

21

Flak i think that the work-around doesnt work if your map has persistable because when that change is made you get modified-persisitable wich cant be in fortnite thats why e get the verse error