I'm in a group of 4 players and two of us have consistently not been able to open the maps that the DM sets up on DnDB. We all have the same laptops and use Chrome (up to date). I and another player always get an error saying that we should refresh and if the problem persists to contact support through a link. The link didn't seem to work when I tried it, however. Our next session in next week, and I'd like to see if anyone has any suggestions for getting past this problem.
Our workaround is simply for the two of us to look over the other two's shoulders. Could be worse, but I'd like to be able to move my own token around :).
Anyone have this experience before? Did you get it to work? How?
Works fine for me when testing with Chrome, Firefox, Edge and Opera GX.
I would recommend you ensure you are using the correct link, check extensions or VPNs that may be running, and check your character is in the campaign. The DM needs to ensure they have an up-to-date Master tier subscription.
Rollback Post to RevisionRollBack
Click ✨ HERE ✨ For My Youtube Videos featuring Guides, Tips & Tricks for using D&D Beyond. Need help with Homebrew? Check out ✨ thisFAQ/Guide thread ✨ by IamSposta.
Link is straight from the character sheet ("play button") that is in the campaign. Like I said, two of our four (we all game in person, but use DNDB) get in just fine and we all get in the same way. I don't use a VPN and the DM's sub is up-to-date.
Thanks for the suggestions, though. I might just meet up with him before game day and see if we can troubleshoot it together.
Update: I tried a different character in a different campaign and got the same issue. The error is that the map cannot sync. I see all the sidebar stuff and can click it. I see the new initiative tracker at the top. I just can't see the map and the error just tells me to refresh (which I've done tons of times). I tried disabling my extensions and that didn't have an effect either.
That said, I did try it on Safari and that worked, so at least I have a work around...
I also have an OS update that I haven't implemented yet, so that's next to try.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I'm in a group of 4 players and two of us have consistently not been able to open the maps that the DM sets up on DnDB. We all have the same laptops and use Chrome (up to date). I and another player always get an error saying that we should refresh and if the problem persists to contact support through a link. The link didn't seem to work when I tried it, however. Our next session in next week, and I'd like to see if anyone has any suggestions for getting past this problem.
Our workaround is simply for the two of us to look over the other two's shoulders. Could be worse, but I'd like to be able to move my own token around :).
Anyone have this experience before? Did you get it to work? How?
Works fine for me when testing with Chrome, Firefox, Edge and Opera GX.
I would recommend you ensure you are using the correct link, check extensions or VPNs that may be running, and check your character is in the campaign. The DM needs to ensure they have an up-to-date Master tier subscription.
Click ✨ HERE ✨ For My Youtube Videos featuring Guides, Tips & Tricks for using D&D Beyond.
Need help with Homebrew? Check out ✨ this FAQ/Guide thread ✨ by IamSposta.
Link is straight from the character sheet ("play button") that is in the campaign. Like I said, two of our four (we all game in person, but use DNDB) get in just fine and we all get in the same way. I don't use a VPN and the DM's sub is up-to-date.
Thanks for the suggestions, though. I might just meet up with him before game day and see if we can troubleshoot it together.
Update: I tried a different character in a different campaign and got the same issue. The error is that the map cannot sync. I see all the sidebar stuff and can click it. I see the new initiative tracker at the top. I just can't see the map and the error just tells me to refresh (which I've done tons of times). I tried disabling my extensions and that didn't have an effect either.
That said, I did try it on Safari and that worked, so at least I have a work around...
I also have an OS update that I haven't implemented yet, so that's next to try.