Search the Community
Showing results for tags 'severe'.
Found 3 results
WTF is the point of creating a bug report? I've tried this game out again and it still won't let me on any servers, from day ONE. I tried being nice, I tried to help troubleshoot, but the developers are absolutely useless. Never buying a game from anyone related to... - Studio Wildcard - Instinct Games - Efecto Studios - Virtual Basement LLC or - Grapeshot Games ... EVER AGAIN! I'll also be strictly discouraging anyone else from doing so through my website, YouTube streams, and social media pages. This company has no idea how to create and manage a game. I should have learned my lesson with their failures in Ark. If the full team couldn't create a decently running game with a properly moderated multiplayer then there's no friggin way a small part of that team would be able to do anything decent in an MMO environment. I don't see the official servers for this game staying online longer than a year. What a failure. My Related Bug Report Topics: https://www.playatlas.com/index.php?/forums/topic/16605-never-able-to-connect-troubleshooting/ https://www.playatlas.com/index.php?/forums/topic/3363-56-still-timing-out/ https://www.playatlas.com/index.php?/forums/topic/7671-attention-developers-connection-troubleshooting/ https://www.playatlas.com/index.php?/forums/topic/5220-62-still-timing-out/ https://www.playatlas.com/index.php?/forums/topic/5952-north-amercian-servers-in-europe/
Before you call BS on that title please take a moment to hear me out there's a story. Server setup, unofficial server privately hosted on HP Workstation with an E5-2670 CPU, 64 Gb Ram, multiple SSDs. 2 ASUS Routers a RT-N56 and a RT-N66U. the N56 was setup as an AP. We have a 3x3 grid with 0,1 and 2,2 offline so basically a 2x3 with an extra tile in the middle. We are going to re-do our map so we had set up a new map B3, 1,2. This was a brand new zone. I was moving our galleon with 18 animals, 6 crew and myself driving. I had crossed several borders earlier and was heading into B3. Right as I went into the barrier suddenly the entire network goes offline. I was like WOW what insane luck that it goes offline literally as I'm transferring the bulk of our animals plus dozens of blueprints and resources. We had about 20 people on at the time mostly spread out but about 8 in B3, the new zone. I was crashed to desktop. I noticed that my entire LAN was offline not just inet but the LAN. I went and checked my routers and the N-56 was "on" but completely dead. It had the server connected to it via ethernet i was basically using it as a switch since I have to many hardline devices for the 4 meager ports on the N66U. Once I realized that my LAN was down I went to the server and shut down Atlas so that bad things wouldn't happen to everyone else, i.e. ships of the damned sinking ppl out sailing. I chalked the experience up to bad timing with my router kicking the bucket. I went and unplugged everything that didn't need to be hooked up at the time. I later got a 8 port gigabit switch to solve my not enough ports problem. Upon logging back in I was giving a spawn screen. It showed my Galleon and the 2 beds on it but when attempting to spawn it would attempt to load then kick back to the spawn screen. Over and Over. I was getting really worried. I finally spawned in B3 and when in B3 it didn't even show up on the map. But in C2 it shows as just a hair over the border into B3. After several fruitless hours of trying to find it and restarting the entire Atlas server and Redis multiple times it was gone. I logged out. While I am the admin that ship and everything on it was legit obtained. I had built it from scratch no cheats and was super bummed plus all the animals which was prob 20 Hours of taming work. Elephant, 2 Giraffes, Bears, Wolves and handful of chickens. Wolves were one of the worst tames cause frequently they get killed because they have their friends with them. One of the people in our company felt bad, he went over to where it showed it should be and criss-crossed the barrier multiple times. He messaged me hours later and said he found the animals they were all floating in the air right at the border and he was gonna try get close enough to whistle them. This made some sense as we had lost some animals before at the barrier they get de-sync'd off the boat and we'd actually recovered a giraffe that disappeared off the ship but still showed in the crew count after trying to whistle it where it had been did work and leaving the area and coming back it no longer registered in the crew. We found it about 3 hours later swimming at the barrier. This has also happened with ship crew they become ghosts. The ship thinks they are still on it and sails work like they are crewed, until you leave the ship for a while and it enters stasis or w/e Atlas does when nobody is around, then when you come back they are gone. We've found em at the border many times or sometimes in port after the ship leaves the area and comes back. Atlas has a WHOLE lot of bugs with this redis database business. Back to the story, when I got logged in he messaged me all upset, said when he got close to where they were at the barrier he crashed to desktop and when he logged in his ship was gone. He also had a galleon with 5-6 animals plus a few crew on it. Now things were getting nuts, we started calling this area the Bermuda Triangle. Because I am paranoid about data backups I had a FULL backup of entire save data, including the redis DB. We tried just rolling back the ocean.atlas files but it seems that the redis db has master control on things. So we did a full restore and rollback. It sucked but 2 galleons and dozens of animals and crew gone everyone agreed to do the rollback. When I was in the process of doing the rollback I was making a backup of the current save data, like I said i'm OCD about backing things up. I noticed that our redis_atlasdb.rdb had massively increased in size from 32mb to over 320mb. Using FastoRedis to view the file I looked at a copy and there was an entry for "travel data' that had hundreds of entries. It seems it was caught in some sort of loop which caused the redisdb file to massively bloat. This confirmed to me that we had to do a full rollback. Pre -Transfer Glitch size Post transfer glitch size with what appears to be thousands of "travel data" entries. Fast forward to Monday Evening. I was being super cautious about this xfer. I did it when almost no one was on. First I went from A2 to B2 and traveled the entire length of B2 before moving down to b3. It really seemed to have a hard time doing the transfer but it did work and everyone came through no crash. All seemed well, however we have been having a problem with the ocean.atlas files suddenly bloating to massive size. Sometime around patch 9 it seems our ocean.atlas files started to get huge and it seemed related to harvesting with animals. Our server has been up since the first day they put out unofficial server files. Our A1 save file is only 86mb and everyone who has played has come through there as it's the default homeserver. We only had the one initially. Dozens of boats were built but all the materials were gathered by hand. On the grids where we started getting animals for harvesting the file sizes started to get really huge around patch 9. Several are over 400mb seems to have created a ton of lag. Server framerate with only 1 person on literally doing nothing but standing there will vary wildly from 30 (server framerate), to 10, 15, etc in some crazy mish mash and sailing on the ocean is a horrible experience. We started getting the same crazy lag on B3 as we had on C2. It was at this time i also noticed the B3 ocean.atlas had grown from 6mb when we moved in to over 123 mb in 2 hours. We decided that we would nerf gathering rates all the way back to x1 vanilla. We had them at x5 at this time and the insane berry harvest from an elephant was crazy sometimes 12-18k in a single swipe. But we felt we needed to wipe B3. So time to pack up AGAIN and move. I decided to start up C3 server but completely empty but for 2 islands, no ships of damned, no rain (aka water spouts). I felt it would be safer to go over into a basically empty server. I sailed over and as I crossed into C3 I intense lag at the border and crashed, again. Right at this time I saw that we were getting massive packet loss on our internet. upwards of 20% total packet loss. I was just dumbfounded that we TWICE right as i crossed the barrier I had this INSANE internet/network problem at the same time. (I have to access Atlas via external connection due to Net Reflection problems, so my local computer accesses the server as a normal public user. I VPN out then come back in. I have a pretty solid VPN and despite some extra latency I'm still under 60ms to my server. I opened up pingplotter to see what was going on and saw this. This regular pattern was super suspicious. I thought i was being DDOS'd, which didn't really make sense, so I checked my router. CPU pegs correspond to packet drops exactly. This was crazy I was starting to think I was being DDOS'd. I then checked the connections log and it was incredible slow to load and what it did had hundreds of connections per second coming from my Atlas Server. I at first thought they were inbound then noticed source was the server. Sadly i didn't get a SS of that but it doesn't really matter at this point. I was pretty sure I knew what was going on. I shut down the Atlas server and as soon as I closed it all down including redis packet loss stopped instantly. I now was quite sure the problem was corruption in redis caused by some sort of bad coding with server grid xfers with ships with lots of animals on it. I went and looked at the redis db file size. In the span of 20 minutes it had gone form 26mb to 173mb. Again it was full of those Raw travel data entries. FYI: I am not accessing the atlasdb live I copied the file during shutdown and ran a seperate copy of redis on a different port even to load the db to then access it with FastoRedis. TLDR & Conclusion Atlas grid transfers are very buggy and when moving large number of animals apparently anything over 5-10 it has a very hard time dealing with it and is so badly coded it literally spams thousands of connections and burned out a consumer router and crippled another one. The Asus N56 is totally dead turns on but doesn't boot to a working state. The N66U has a bigger processor and was able to not vaporize from the spam but it wasn't really working very well. I would imagine this has happened to others but if they are using hosting providers the commercial routers are able to handle the load, although it prob crashes the Atlas server eventually if the redis db just balloons until it can't function anymore. So Grapeshot @Jatheish @DebbySaurus You might want to look into this. I still have all the files and am willing to send the redisdb files even the ocean.atlas files. I strongly suspect this post will never be read by anyone with any authority or knowledge of the internal workings of Atlas and Redis from Grapeshot. But let it serve as a informational, comedic, or warning post about the current state of the game. Also, Grapeshot you owe me a new router.
We have identified a severe save file bloat problem that strongly appears related to harvesting. One of our island save files has increased massively over the morning. Above are save files from today. From 11:52am to 1:52pm as seen above we harvested tens of thousands of materials to build a galleon. After we finished you can see file size stopped growing. We moved to a new grid due to the severe lag this file size caused. We had not determined what was causing the file size bloat at that time. We started building another ship when I noticed the file size jumped again while gathering. Our harvest rates are increased and we are going to nerf them but I don't think that will help. As you can see above again massive file size increase. All harvesting was done with tames, Elephants, Bears, Giraffe.