So when I try and import my world state to Xbox One, it says that it doesn't exist. But when I look at the Keep, it says that it does. and has a green check next to DA:I.
So when I try and import my world state to Xbox One, it says that it doesn't exist. But when I look at the Keep, it says that it does. and has a green check next to DA:I.
A big part of the problem is that the World State in The Keep cannot be changed from "Default."
I have no option to change it to the Custom World State that I spent two hours making.
I have successfully replaced the Default World State with my Custom World State, but only in The Keep. For anyone who needs to know how to do this, click the button in the top left corner, select "World States," and click next to the name of the World State to change it from "Default." You can add a description here, as well.
Unfortunately, Dragon Age: Inquisition is incapable of importing a Custom World State from The Keep, making the entire process pretty pointless.
Did you export your world state into DA:I?
If not, click the globe in the upper right corner of the tapestry. Your profile should pop up to the right,
scroll down and press "Export to DA Inquisition".
You can also choose your different World states here by pressing "Load another world state". A page with all your WS will show,
pick one and click "edit in tapestry".
Yes, I did all of that.
Have you started a new game, as in used the character creator? Because the choise to import World state comes up after you pick
your race, class and difficulty if I remember correctly.
Yes, that's when I receive the message that a Custom World State doesn't exist for import, and I'm forced to use the Default World State.
I've double-checked all the steps. While searching the forums, I've found over a dozen people with the same problem, but no workaround or solution.
That's strange...I'm on X1 too and I've never had problems with the ws. Have you locked in the choises of the ws before you export?
Is there a lock on the globe?
The first time I exported, no.
When I went back into the Keep, I changed the name from "Default World State" to "Custom World State" and locked the choices, then exported again. I received the same error message on Xbox when I went through character creation.
As at least one other person who had the problem mentioned, eventually, with no action or changes on my part, a World State was able to import successfully.
I'll check to confirm that the World State is intact as I made it before proceeding.
I do hope BioWare addresses this issue soon, since I can imagine a lot of people would be reluctant to start the game while The Keep isn't working properly.
If you go to worldstates you can choose to load another into the tapestry and edit it. You can also call it other things then "Custom World State"
Check that your Xbox Live Id is linked to your origin id. If it still doesnt work check your network settings (try on a different network). If that still doesnt work then pm one of the keep devs
Just changed the name or did you pick another ws than the default one? How many World states do you have?
I didn't do or change anything in between my last 3 attempts to import. I tried twice in a row the night before, and nothing happened, and then I tried again in the morning, and it worked.
If you go to worldstates you can choose to load another into the tapestry and edit it. You can also call it other things then "Custom World State"
Check that your Xbox Live Id is linked to your origin id. If it still doesnt work check your network settings (try on a different network). If that still doesnt work then pm one of the keep devs
I've already addressed all of that in previous posts, except for the network one. I only have one network, and it was repeatedly tested to be sure that it wasn't the issue.
And as previously stated, the problem did not respond to any of those efforts. I made no changes in between the attempts that failed last night, and the one that worked this morning.
I had the same issue this morning, third play through, but when i restarted the game it seemed to fix the issue.