Reference ID
f19dc33a-45c9-77b8-8180-c18dd3971099
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Other
Summary
Since march 9 maps that have a specific verse file in it, makes my projects unable to launch session. I can only launch when I remove all my verse files. If I have even 1 verse file it gives the same error. The error is in ranks.verse but when deleted it still creates a new ranks.verse file on launch in the sys folder. It can be fixed by duping the project and removing the binds, but this creates a new island code.
I suspect the ranks.verse is stored out of my reach and somewhere on epics servers, maybe thats also why it says /projects.epicgames.com. I saw there is now urc for individual verse files, is that new since this season update, I think that caused the issue then.
This is really important for me since my maps have issues and bugs that I would like to fix and they currently have 3000 combined players playing. I can’t update the map now since I can not launch session
The Error:
C:/Documents/Fortnite Projects/OG_Realistic_1v1/Plugins/OG_Realistic_1v1/sys/published/Content/ranks.verse(17,11, 22,1) : Script error 3532: Duplicate explicit module definition (module has been previously defined as (/projects.epicgames.com/_10c3d3a27be34c04b9aafd9855b7e012:)Meshes )
Steps to Reproduce
Only I can repro
Expected Result
Launches session
Observed Result
Not launching
Platform(s)
PC
Island Code
6570-5231-1418
I’m looking into this currently. A possible workaround is to revert (via Creator Portal) to before the addition of any persistent weak_maps, delete the Meshes module in ranks.verse, publish that version and make it live (upon reverting, this step should succeed), then continue from there.
I dont think that would help cause it would not change anything on my pc. Also it would revert all progress. Here is a video https://youtu.be/IEl08axC5S8
I’m qualifying a fix and seeing about the best way to get the change out currently. For why the workaround may work (other than reverting of all progress): any project containing persistent weak_maps is subject to a backwards compat check. That check occurs both in UEFN and as part of Creator Portal publish. Both the UEFN and Creator Portal parts make use of the currently published Verse code - meaning Creator Portal changes (new published version, reverts, etc.) may impact what satisfies the backwards compat check that occurs in UEFN.
I am eagerly waiting with instructions as my maps are taking a big hit due to this. Also, why did this bug occur in the first place? It is very scary and I am worried its going to happen in the future.
It’s a bad interaction between special behavior for asset reflection (the Verse code generated in Assets.digest.verse) and the backwards compat checking. The compiler currently allows user-defined code to collide with asset-reflected definitions (Meshes in this case) without emitting an error. However, the backwards compat check, which makes use of the Verse compiler, did not properly consider the related published version of the Verse code (including the Verse code generated for assets) as allowing such collisions.
I understand… do you have an ETA for this fix as it’s really hurting my play time and analytics that I am not able to update my maps. Thank you so much Lambda!
I can’t give a lot of information as far as timeline is concerned (yet, anyway), but the change is currently on the fastest available path.
1 Like
7th map of mine just got affected, was working fine earlier today, publishes a few updates, now before bedtime tried to launch session and got the same error. I really hope I can get an ETA soon since now I can barely work on anything…
C:/Documents/Fortnite Projects/Realistic PvP FFA/Plugins/Realistic_PvP_FFA/sys/published/Content/ranks.verse(64,11, 69,1) : Script error 3532: Duplicate explicit module definition (module has been previously defined as (/projects.epicgames.com/_83e27acdc17c47beaac12d44829068b1:)Meshes).
This should all work now. The backwards compat check has been temporarily disabled in UEFN, but Creator Portal will still do the check. The check Creator Portal does has been patched to not fail with the error you have here.
1 Like
The status of FORT-772117 incident has been moved from ‘Needs Triage’ to ‘Closed’. Resolution Reason: ‘Fixed’
