ThatOneGuyVI

+1 for possible workaround

Come to think of it, i created my own Company last night and since then i haven't crashed when opening the map.

It lets you open your map/respawn/change to another server.

To everyone having this issue, if you somehow manage to get out of the assertion failed hell, not all freeports cause the crash. E4 works for me. You can change your home server to this one and go from there.

Just a quick update, traveled from Northeast Tundra Freeport and made it to K4 and it works fine without crashing. Everything in between gave the same error though.

Pretty much, yea. G12 was the only one that didn't crash.(of all the ones i checked) Now im in the northern tundra checking to see if any of the server up there work.(plus less people, meaning less fully claimed islands)

I honestly think this is our only option atm. Get a raft with a bed and keep sailing to different servers checking to see if you crash, if you do crash keep sailing until you get to a server where you don't crash whenever you try to fast travel with the bed. Unless a dev wants to chime in here and give an actual solution. -cough- -cough-

No, all of the islands were completely claimed, so I changed home server, and the one I changed to has the same error.

Checking the time it was more like 7+, nope i didn't open the map the entire ride I only checked the bed whenever i crossed into a new server and I just followed the wind.

Here's a little update for you. After 7+ hours of sailing i finally found 1 server that doesn't crash. And of course when i check out the three islands there they're fully claimed with this games broken claim system(off topic but 1 person should not be able to claim 10+ areas that's just ridiculous, a tribe should have 1 claim area per person for each server). So little ole me decides to tempt fate and change my home server. The change home server worked. But now i'm back at square 1. The reason i'm posting this is because all of these previous servers had claims that I could of placed down, but it wouldn't of meant anything since I wouldn't of been able to re spawn when I died, seeing as how vultures glitch through bases and kill you. Someone should acknowledge that this is an issue and is being worked on or looked at.(The assertion failed issue not the claim system, that's a separate issue) Also, Happy New Year!

So I went ahead and took the time to give a visual representation for whichever dev decides to take a look at this. Here I am sailing away from the Southern desert freeport.(can't use that bed for right now because the game crashes whenever the map gets pulled up in this server) Here I am crossing into another server cluster.(will i finally be liberated from this hell?) 2. I've successfully crossed into a new server.(Woohoo!!!! Freedom!!! I can finally use a bed/respawn/teleport/change home server without being sent back to that pit!!!) 3. Oh..Ok...(I guess I can play the game on hardcore mode....haha.) 4.

Just here for an update. Managed to get in with the "work-a-round" opened up the map to test and see if the problem had been fixed. Nope, and still not a single mention from the devs or anyone else really.

Issue still persists. Still no word from devs.

Welp they've been ignoring us here, let's see if they acknowledge it on twitter >.>.

Still not working, and still no word from the devs.