When I make changes to Verse and try to push those changes to a live session I get an error telling me I need to push the entire change log.
Steps to Reproduce
Edit Verse and try to Push changes.
Expected Result
The session reloads with the new Verse edits.
Observed Result
The following errors:
[2024.01.23-23.14.15:359][493]LogValkyrieActivityTracker: Warning: Session → Fail Activity: LoadingNewContent - Error updating content
[2024.01.23-23.14.15:359][493]LogValkyrieSummary: Failed to update content due to error.
[2024.01.23-23.14.15:360][493]VerseDiagnostics: Error: /opt/epic/offset_1/LinuxServer/FortniteGame/Saved/VerseProject/FortniteGame/Assets/a4650362-4e58-bd5b-890d-1480f6a818d1/a4650362-4e58-bd5b-890d-1480f6a818d1.assets.verse(12,1, 12,39): Script error 3507: (/Fortnite.com:)AI is not defined in the current package (a4650362-4e58-bd5b-890d-1480f6a818d1/Assets), and the current package is not explicitly dependent on a package that defines it. To fix this, consider modifying the dependencies of the .uplugin, .Build.cs or .vpackage file belonging to a4650362-4e58-bd5b-890d-1480f6a818d1/Assets
to include one of these packages:
VerseAIBase/VerseAIBase
VerseNPC/VerseNPC
VerseCreature/VerseCreature
CompanionAI/CompanionAI
VerseFortnite/VerseFortnite
[2024.01.23-23.14.15:360][493]VerseDiagnostics: Error: /opt/epic/offset_1/LinuxServer/FortniteGame/Saved/VerseProject/FortniteGame/Assets/a4650362-4e58-bd5b-890d-1480f6a818d1/a4650362-4e58-bd5b-890d-1480f6a818d1.assets.verse(12,1, 12,39): Script error 3507: (/Fortnite.com/AI:)VerseAIBase is not defined in the current package (a4650362-4e58-bd5b-890d-1480f6a818d1/Assets), and the current package is not explicitly dependent on a package that defines it. To fix this, consider modifying the dependencies of the .uplugin, .Build.cs or .vpackage file belonging to a4650362-4e58-bd5b-890d-1480f6a8 18d1/Assets to include one of these packages:
VerseAIBase/VerseAIBase
One terrible work around is to migrate the map to a new project every times this happens. Doing so seems to fix the issue for a day or so, but eventually it pops back up again.
Also migrated an old project to a new one yesterday.
I had to replace all verse devices in the map because they were not recognized, fortunately it’s a small prototype, but on a large scale project it’s not feasible.
For now, pushing verse changes works … waiting to see if the issue pops up again
P.S. I invoke the spirit of the Epic staff if you can hear us, we are facing a major bug, please come forward the post has been there for 9 days.
Thanks for the tips, seems to be the safer way to do the migration for now!
I had used the migration tool in the content contextual menu (it broke the project)
There maybe an explanation why the issue reappears on your side, when copying the old content there are some serialized files related to the compiled devices that need to be updated internally.
If within a week, the problem no longer appears on my side, the hypothesis will be confirmed.
Okay, interesting. Yeah, my approach only fixes the issue for a few hours normally (or at least until I need to cancel my session). A more permament fix would be greatly appreciated (but I also can’t really rebuild the project, haha).
Awesome. I’ve also been having no issues recently. Though, I think it might have been partially due to me deleting a bunch of old files. Regardless, seems to be working now! Great!