[DISREGARD] Turns out someone removed a weak_map associated with the player that is present in our published version, so it was the comparison between the current code and the published code that caused the error. And you obviously can’t remove a player persistence weak_map if it’s in the published build. All the old code I was seeing was, I would guess, from our currently published version.
Sorry for the false alarm.
Summary
After successfully compiling verse locally, Attempting to launch a session fails with Verse errors, referencing verse code that no longer exists.
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Verse
Steps to Reproduce
Update UEFN to 37.20
Launch UEFN - Select Project (we’re using Perforce)
Compile Verse through verse menu - witness successful compilation
Click Launch Session button and monitor validation
Expected Result
Expect to see successful verse compilation, as the local menu verse compilation succeeded
Observed Result
Failed verse compilation with errors that show significantly outdated code. There are files that are being compiled that no longer exist in our project, and errors that indicate the code being compiled is not the same code we have in our local environment.
When I compare the contents of the generated ‘published’ folder that the Launch Session appears to be trying to compile to the contents of our Content folder, the files and the file contents are completely different.
We are having a potentially related issue on several projects, here’s a sample of the most egregious one. This is preventing us from launching sessions today. Prior to the patch, we had no issues and none of the logic has been altered.
[DISREGARD] Turns out someone removed a weak_map associated with the player that is present in our published version, so it was the comparison between the current code and the published code that caused the error. And you obviously can’t remove a player persistence weak_map if it’s in the published build. All the old code I was seeing was, I would guess, from our currently published version.
We did not remove a weak_map, so would be good to not disregard and I guess create another ticket since mdko edited the original which breaks your ticketing system…
Thanks, I didn’t realize editing broke the ticketing system.
Your logs look slightly similar to what we were seeing, although we only saw it with one error.
From the language of the log, it seems like they’ve implemented a new feature to compare the latest published version with the verse code that you’re trying to launch. Are those first 3 objects listed in the first 3 lines in your current codebase? and if not, have you checked your source control history for them? In our case it was just that we removed it and the comparison logic was throwing that same error.
No worries. Yeah, if you edit the OP I guess it breaks the ticketing system (pinned thread at the top of this forum). I bet most people don’t know, I only discovered it this week
We believe it’s a mistake on the backwards compatibility check because this same code had no problems before and it’s an unpublished project. Just to validate an us vs. Epic comparison, I ran a Verse Persistence check on a private version we built before the 37.20 update and it clears with no issues (screenshot attached).
