I cannot update my map Backrooms Roguelike using private versions created after 38.00.
When trying to publish, the verse persistence check throws the error below.
My code doesn’t have any reference to that UI module anymore, as shown in the second picture.
My code doesn’t have that error anymore. I changed my folder structure names completely, and there’s no track of a UI module that would go in conflict with the Verse.org/SceneGraph/UI module.
There is a very odd coincidence with how URC is working in my project, I will add many details about this below, but I’m not sure the two things are correlated.
Please select what you are reporting on:
Verse
What Type of Bug are you experiencing?
Publishing
Steps to Reproduce
This problem likely can’t be reproduced with a new project.
Expected Result
The project can be published as I don’t have that error anymore.
When i rename a folder itll create a new one with the name then i right click on the top project name folder and update redirectors then delete the og folder.
Not saying this is the issue but try this
I think it keeps refs in the redirectors to the og folder name could be the issue
Not sure how they work with the asset digest but try anyways
URC also seems to be bugged in my project. In my local copy of the project, I can see all snapshots, including URC2 snapshots. But if I sync the project to the latest snapshot on a different pc (so a fresh/clean sync) it syncs the project to the last URC1 snapshot, which is Snapshot 122. (I’m now at snapshot 1320 with URC2), and I can’t see URC2 snapshots at all.
I wanted to try to sync a fresh copy in a different pc, so maybe it could’ve fixed the publishing issue.
I’m including this as an additional detail. Not sure if it can be helpful.
We probably have the same issue. I spoke to @Flak and she said to make a forum bug report on this, so hopefully this will help Epic devs fix this issue. Let’s just provide as many details as we can and hope🤞
Yeah I stopped using URC a little over a year ago due to issues with restore and snapshots. I’m using Perforce and I don’t think this issue is client side however as I’ve tested different accounts, different machines, fixing the file, deleting the file, changing the line number as to where the issue would be and everything points to Nomad (the cook service) caching the verse code and not refreshing. Hopefully theres a way to flush it…
Yeah there’s a condition that probably doesn’t update the cached code, as my error was never there since it started happening after 38.00, I fixed it way before than 38.00. Also, old versions work, I’ve sent a version made before 38.00 and it passed the persistence check
Hi folks: we’ve identified a regression here in our backwards compatibility checker that is giving these false positives that are preventing you from publishing. We have a solution that we’re working on trying to deploy. Please bear with me.
