Forum Discussion

TheRealMadCat's avatar
2 months ago
Solved

Unable to load my world in desktop editor

Hi, I have a serious issue, I am trying to do updates on my world Witch Woods Hollow, but I cannot get it to load in the desktop editor.  I am using Quest Link to open the desktop editor (the standalone version won't even open for months so had to resort to the quest link version)  I get a repeated message:  'Navigation Failed: We were unable to take you to your destination'  Please could someone help?  I have tried reporting this, but not sure what I can do, if anything, in the meantime.  Anyone have any fixes?  I restarted the desktop editor, but have the same error message each time.  I have also tried to access the world in edit mode using the headset editor and I get the same message.  At a loss as what to do!

  • SeeingBlue's avatar
    SeeingBlue
    2 months ago

    Not exactly, just be aware of any changes the restore removed. Sometimes we can try to do too much and lock up the world.

4 Replies

  • Hi I managed to restore a previous backup and now I can access the world again from that point.  Any ideas why the issue occurred, for future reference!  Many thanks as well for your quick reply, I still have some hair left haha😅

    • SeeingBlue's avatar
      SeeingBlue
      Mentor

      Not exactly, just be aware of any changes the restore removed. Sometimes we can try to do too much and lock up the world.

    • TheRealMadCat's avatar
      TheRealMadCat
      Member

      I can access other older published worlds and a world I'm currently working on that is not yet published, so it appears to  just be an issue with Witch Woods Hollow.  Not encountered this before!  I will try to rollback to the last backup version and see if it helps.  But I need to know why this has happened and what could be the cause? There have been a few strange issues recently, whereby visitors have been able to go to an older version of the world which was during Halloween, even today I had a  visitor say they had been taken to the old version and not the new Fire Night event one!  Could this be a caching issue on the meta servers?