Search the Community

Server: NA PVE Region B4 Island: Malarwood Chain Coordinate (ccc) : cheat TP B4 229161 406297 108 Claimed enemy Land but some structures did not convert ownership to my company even after setting up claimed flags build setting to company only.

[4852] 31 Jan 07:04:04.534 # rdbSave failed in qfork: Input/output error [5216] 31 Jan 07:04:04.622 # fork operation complete [5216] 31 Jan 07:04:05.083 # Background saving error [5216] 31 Jan 07:04:05.185 * 1 changes in 900 seconds. Saving... [5216] 31 Jan 07:04:05.294 * Background saving started by pid 2072 [2072] 31 Jan 07:04:14.163 # Error moving temp DB file temp-2072.rdb on the final destination redis_atlasdb.rdb (in server root dir C:\Jeux\Atlas\AtlasTools\RedisDatabase): Input/output error

My boat and me are stuck between H5/G6 since yesterday. When i try to log in game i've this message "you are currently travelling to another server ..." https://image.noelshack.com/fichiers/2019/05/4/1548934327-20190131122833-1.jpg

Every time we "dock" or "undock" at or base, most if not all of our crew teleport / bounce to new locations. For example they will be standing on the top deck raised platform then suddenly poof and appear halfway down the ship, stuck between decks. We have lost several crew like this because we have no idea where they warped to. This is on a Brig and by dock i mean pull up next to our ship yard which has a walkway next to it so we can get on and off easier. We are close to, but not touching the walkway. This doesn't seem to happen when we dock in open water, though they do get squirrely when you unseat them.

I have created a ticket for this but I will also make this bug thread since it is also a bug that is being taken advantage of by a Company known as "The doves". This Company has been using an exploit/bug to clear out other Company's claims. According to people who witnessed this when you drop a claim flag down, you can drop another one in a place you normally couldn't while the first one is claiming. They left these overlapped, please go to it for proof. Or alternatively, monitor them as they do it.

We were traveling from L4 to L3, and now our ship is just appearing moving forward and then disappearing, endless loop, the game crashes everytime you join in saying changing servers. We sailed a boat to it from a homeport and that boat too crashed when changing zones, but we were able to get back onto it. If we crash into the boat it hits us. If you swim to the boat it will teleport and appear on top of you as if you are on the ship, and as soon as that happens it says its teleporting you back to L4 where it then crashes, so endless spawn loop trying to get into the ship and get it to stop warping. Please, admins, we need help resolving this issue! Ship name: Gallileo, Coordinates in L3 are 51.21 x 61.29 Please help.

on our island we have palm leafs on the ground which gave thatch before the patch. now they don´t give it anymore. intended?

--------------------------- The UE4-ShooterGame Game has crashed and will close --------------------------- Fatal error! VERSION: 16.31 PhysX3_x64.dll!physx::Sq::BucketPrunerCore::removeMarkedObjects() (0x00007ff9c66a2264) + 0 bytes [e:\arksvn_pc\engine\source\thirdparty\physx\physx_3.4\source\scenequery\src\sqbucketpruner.cpp:794] PhysX3_x64.dll!physx::Sq::ExtendedBucketPruner::removeMarkedObjects() (0x00007ff9c66aa6db) + 0 bytes [e:\arksvn_pc\engine\source\thirdparty\physx\physx_3.4\source\scenequery\src\sqextendedbucketpruner.cpp:476] PhysX3_x64.dll!physx::Sq::AABBPruner::commit() (0x00007ff9c6698791) + 0 bytes [e:\arksvn_pc\engine\source\thirdparty\physx\physx_3.4\source\scenequery\src\sqaabbpruner.cpp:491] PhysX3_x64.dll!physx::Sq::SceneQueryManager::afterSync() (0x00007ff9c6696f45) + 0 bytes [e:\arksvn_pc\engine\source\thirdparty\physx\physx_3.4\source\scenequery\src\sqscenequerymanager.cpp:433] PhysX3_x64.dll!physx::NpScene::fetchResultsPostContactCallbacks() (0x00007ff9c65ca600) + 0 bytes [e:\arksvn_pc\engine\source\thirdparty\physx\physx_3.4\source\physx\src\npscene.cpp:2259] PhysX3_x64.dll!physx::NpScene::fetchResults() (0x00007ff9c65c5c42) + 0 bytes [e:\arksvn_pc\engine\source\thirdparty\physx\physx_3.4\source\physx\src\npscene.cpp:2327] APEXFramework_x64.dll!nvidia::apex::ApexScene::fetchResults() (0x00007ff9ea611225) + 21 bytes [e:\arksvn_pc\engine\source\thirdparty\physx\apex_1.4\framework\src\apexscene.cpp:1366] AtlasGame.exe!FPhysScene::ProcessPhysScene() (0x00007ff60e479145) + 0 bytes [h:\yarkupdatelivereal_live_archive\engine\source\runtime\engine\private\physicsengine\physscene.cpp:677] AtlasGame.exe!TBaseStaticDelegateInstance_ThreeParams<void,bool,__int64,int>::ExecuteIfSafe() (0x00007ff60c47275a) + 0 bytes [h:\yarkupdatelivereal_live_archive\engine\source\runtime\core\public\delegates\delegateinstancesimpl.inl:691] AtlasGame.exe!TGraphTask<FDelegateGraphTask>::ExecuteTask() (0x00007ff60db73306) + 0 bytes [h:\yarkupdatelivereal_live_archive\engine\source\runtime\core\public\async\taskgraphinterfaces.h:872] AtlasGame.exe!FNamedTaskThread::ProcessTasksNamedThread() (0x00007ff60d6a88b8) + 0 bytes [h:\yarkupdatelivereal_live_archive\engine\source\runtime\core\private\async\taskgraph.cpp:939] AtlasGame.exe!FNamedTaskThread::ProcessTasksUntilQuit() (0x00007ff60d6a7a6d) + 0 bytes [h:\yarkupdatelivereal_live_archive\engine\source\runtime\core\private\async\taskgraph.cpp:680] AtlasGame.exe!FTaskGraphImplementation::WaitUntilTasksComplete() (0x00007ff60d6aa830) + 0 bytes [h:\yarkupdatelivereal_live_archive\engine\source\runtime\core\private\async\taskgraph.cpp:1777] AtlasGame.exe!FTickTaskSequencer::ReleaseTickGroup() (0x00007ff60e16195c) + 0 bytes [h:\yarkupdatelivereal_live_archive\engine\source\runtime\engine\private\ticktaskmanager.cpp:205] AtlasGame.exe!FTickTaskManager::RunTickGroup() (0x00007ff60e16775c) + 0 bytes [h:\yarkupdatelivereal_live_archive\engine\source\runtime\engine\private\ticktaskmanager.cpp:999] AtlasGame.exe!UWorld::RunTickGroup() (0x00007ff60df9a4b6) + 0 bytes [h:\yarkupdatelivereal_live_archive\engine\source\runtime\engine\private\leveltick.cpp:701] AtlasGame.exe!UWorld::Tick() (0x00007ff60df9b9dd) + 0 bytes [h:\yarkupdatelivereal_live_archive\engine\source\runtime\engine\private\leveltick.cpp:1268] AtlasGame.exe!UGameEngine::Tick() (0x00007ff60decdbe4) + 0 bytes [h:\yarkupdatelivereal_live_archive\engine\source\runtime\engine\private\gameengine.cpp:1183] AtlasGame.exe!FEngineLoop::Tick() (0x00007ff60c468b4a) + 0 bytes [h:\yarkupdatelivereal_live_archive\engine\source\runtime\launch\private\launchengineloop.cpp:2449] AtlasGame.exe!GuardedMain() (0x00007ff60c4635fc) + 0 bytes [h:\yarkupdatelivereal_live_archive\engine\source\runtime\launch\private\launch.cpp:140] AtlasGame.exe!GuardedMainWrapper() (0x00007ff60c46b5aa) + 5 bytes [h:\yarkupdatelivereal_live_archive\engine\source\runtime\launch\private\windows\launchwindows.cpp:125] AtlasGame.exe!WinMain() (0x00007ff60c46b6d8) + 8 bytes [h:\yarkupdatelivereal_live_archive\engine\source\runtime\launch\private\windows\launchwindows.cpp:209] AtlasGame.exe!__tmainCRTStartup() (0x00007ff60f1a8bad) + 21 bytes [f:\dd\vctools\crt\crtw32\dllstuff\crtexe.c:618] KERNEL32.DLL!UnknownFunction (0x00007ff9f92b3034) + 0 bytes [UnknownFile:0] ntdll.dll!UnknownFunction (0x00007ff9fb863691) + 0 bytes [UnknownFile:0] ntdll.dll!UnknownFunction (0x00007ff9fb863691) + 0 bytes [UnknownFile:0] --------------------------- OK ---------------------------

Claimed tames recieved from another company are invisible. Recent patch made both elephants we received from another tribe to be invisible. character having clipping issues where tames should be. Occurring for all players.

This has happened before. I just played yesterday with no issue, updated everything and now get stuck on the load-in screen again. Is anyone else having this issue again? I'm on Siren EU PVE.

It is virtually impossible to find a sweet spot when the animal you are taming continuously hits you. It is impossible to tame some animals, like a giraffe, since every time you get close enough for the feeding spot, the giraffe then attacks you knocking you back. The most feedings I can get in on these creatures (giraffe, elephant, etc) is 3-6, then the creature starts attacking, and the taming percent falls so fast that I need to start over. Less attacks? Slower percentage loss so that one can get ahead and eventually tame? I tried for an hour today, wasting a lot of beets. The highest I got was 20-something %, then the animal started attacking every time I got near it. By the time it stopped, the percentage would be zero again. I understand the need for hardcore struggle, but making it impossible will just drive people away from playing out of frustration. Needs balanced? Also, issue with taming a horse. The run from you far too fast and long for taming. There Is no way to get them in a pen to tame them and no way to tame them in the wild. Best you can hope for is set up a trap and wait until something worthwhile gets in it. There needs to be a different mechanic for taming creatures that run, including lions as they run more than they attack. Looking forward to a solution. Thank you.

Often times when moving an animal to a ship, three times in the last 24 hours, we have lost tames. When attempting to move the animal to the boat it will disappear from view. Sometimes you can whistle all follow or something and it will pop back up. Sadly in these cases it will not. Shortly after you receive a message it has died. My assumption is that its drowning but there is never a description in the death message or company log. I have even tried to rush to the wheel to raise and drop anchor or move a little to get it to reset but they are just gone. We have lost an elephant, bear and now a wolf. Is there any precautions we can do to prevent this? Have tried having them on follow, not follow, passive and neutral.

I only get a white page when i either click top five on main page or the link Dynamic Atlas Map. Tried different browsers, same result though. Anyone else has the same problem?

Reporting this bug. i spent 4 to 5 hours discovering From A8 to G15 . Left A8 Max lvl 54. 89 discoveries unlocked. discovered up to 110 unlocked max lvl 55. Killed A monstrous sperm whale max lvl 57-58.. logged out and when i logged back im back to max lvl 54. 4 other company members have had this happened.. and it was all after we killed the whale..

I have tested with: ConfigOverrideItemCraftingCosts=(ItemClassString="PrimalItemStructure_Ceiling_Stone_C",BaseCraftingResourceRequirements=((ResourceItemTypeString="PrimalItemResource_Thatch_Base_C",BaseResourceRequirement=20.0,bCraftingRequireExactResourceType=false),(ResourceItemTypeString="PrimalItemResource_Stone_Base_C",BaseResourceRequirement=60.0,bCraftingRequireExactResourceType=false),(ResourceItemTypeString="PrimalItemResource_Wood_Base_C",BaseResourceRequirement=30.0,bCraftingRequireExactResourceType=false))) Using any "_BASE_C" sets requirements to " 32759 x 1 " like shown here: Using "PrimalItemResource_Stone_C" requires Ark resources. Using "PrimalItemResource_Stone_Coquina" doesn't have the bug with " 32759 x 1 ", but it always wants EXACTLY coquina even if it's "bCraftingRequireExactResourceType=false".

Alpha Horse able to kill a large bull named (GoNads), 2 chickens (hotSupper & FogHorn), rabbit (Velvet Cake), sheep (Dumb*ss), 2 cows (Vitamin D & Betsy Ross), and destroyed cage that said rabbit and 2 chickens were locked within feed troth also destroyed by Alpha Horse too. Logged on to discover nothing but the messages. I guess I can't sleep for 5 hours in reality. Somehow Alph Horse able to jump up and over already elevated structures and land inside a 3 x 3 walled in area. My 230 hours invested will stay that way for a while. Just need a break.

Today I was parked in a free port and a player from barry sails emptied both of my storage boxes as I was in the middle of placing items into them. They did it to both my boat and a persons next to me. When he was spotted they teleported out. it was fun loosing all the high quality schematics Link to screen shot. https://imgur.com/gallery/YXcjQWm

Good evening, While I was doing the server change on the official [UE -pvp ] server, to go to a lower area to get friends, the system gave me lost connction, and now when I try to get back into the game it makes me recreate the characters, giving me no PG in Possession. Miss a pg of lvl 39 and very annoying I ask for help! Thank you

When raising babies if they a left alone and not loaded in they no longer continue to eat, I assume this is not intentional. Kinda ridiculous spending so long keeping a babies temperature right only for it to die with 1000 food on it or even eating out of a full trough because someone isn't near by which makes it forget to eat. I also know this was an Ark bug at one point and was successfully fixed.

elephant and giraffe flew away we moved them to the boat on top of a bear. a few seconds later we saw the elephant fly away in one go, we tried to whistle at him but did not work. they arer still stuck at the ceiling of the map we think.

the spawn prevention radius is way to large for resources people have put foundations down on our island and have blocked resources for miles around them please reduce it to a sensible size also you need to remove the blocking from other peoples foundations on claimed land so we dont get blocked by others foundations when building on our claim

Look im all for cargo harness cannons. BUT THEY SHOULDNT BE ALLOWED TO SHOOT UNDER WATER! THAT IS BROKEN AS FUCK! we just lost like 5 brigs and 10 schooners to 1 guy we couldnt see in the dark water. npc could not taget that low in the water but they can light a fuse from the bear mounted cannon... how is the harness floating in the water in the first place.

Every time I play ATLAS, I click "Return to Atlas", wait a moment, and then have to destroy 1 or more structures immediately after spawning into the game. This is because, without fail, every time I spawn in I am stuck inside my structures foundation. I'm not sure if the game is loading my position as a player incorrectly (eg, marking the origin of my sleeping model as the origin of my standing model, thereby placing my feet beneath the ground level), too early (eg. loading the origin before it loads the structures surrounding it, and in the process of loading said structures applying gravity, causing me to fall to the lowest point on the baked map), or just with incomplete data (eg only marking my lat/long, and not my altitude, resulting in the game placing my character at the lowest point on the map and building structures around me), but the result is a base which is looking more and more like Swiss Cheese with every log-out cycle: https://imgur.com/a/Yn0pYzK Now, I'm in PvE, and the damages are relatively low for me. No one is coming to demolish my base in my sleep, for instance. But I don't think the devs intended for us to start making pillboxes jut to be able to log out. But recently, its been happening upon server-switch when traveling from a bed on one server to another, as well, to the point that we now build our beds and log-out points on thatch ceilings suspended above the ground: https://imgur.com/a/b9dDIZI I doubt the devs intended for this to be the solution to what I assume is a loading error-- especially when it ends up resulting in a bunch of 1x2x1 pillboxes. and I'm even more sure that they didn't intend for players who fall asleep in more costly locations, such as on the foundation holding up their tower's ceilings, to have to destroy all supported structures (smithy's, storage boxes, ship resource boxes...) all because they fell asleep next to their valuables. Isn't sleeping in a pile of treasure the entire point of being a dragon pirate? What's the point in building a base if I'm just going to have to rebuild it every single time I log in [note: thank you for the nomination of "Most PvE Statement of 2019," please send the award and check to me via post]? Any info needed to help solve this issue on my end will be happily provided. Below is everything I thought might be helpful in weeding out client-side/user-specific issues: CCC: cheat TP N6 -126906 -267383 135 System specs: Mobo: MSI x399 Creation CPU: 1950x Threadripper GPU: Nvidia 2080 TI RAM: 4x16 DDR4 2666MHz Corsair Vengance RGB Storage: 2TB Samsung 970 EVO NVMe PCIe m.2 2280 SSD Network specs (via Speedtest.net): Ping: 27 ms Download: 118.45 Mbps Upload: 11.75 Mbps In Game Settings: Custom, Epic plus everything epic forgets to enable (eg high level LOD streaming, sky quality maxed, etc.)

We were on a high ping server and the enemy players kept glitching INSIDE our boat. They didn't climb up or use a grapling hook, they just swam infont of the ship and they glitched in on the bottom floor, due to the high lag. Placed the barrels and our ship went south. you really need to fix this. It has happened to multiple people, there are videos of how people use this bug. Can you for once do something about that? We lost so many ships to this.... Look into this! Its not fair losing your ships and not being able to continue fighting because someone exploited a bug.

Okay, I THINK that this is a bug because I can't see why else it would have happened. Myself and my Company have managed on 2 separate occasions over a weeks time to tame 3 different Rhinos and transport them back to the base at C-11 on the NA-PvE server. Both times after taming the Rhinos I've come back the next day to find the rhinos missing and the Company Log reporting that they had been "Killed" with not notice of by what. In both cases the rhinos were safely stowed away in my animal pen along with an Elephant, Horse, 3 Bears, 3 Cows, and 4 Chickens. Nothing else has had an issues like this and none of the other animals have been touched, so it's not like something got in and attacked them. There is also a feeding trough in the pen stocked with Berries, Onions, Beans, and Carrots. So it's not like they starved to death, which leads me into thinking that the rhinos for some reason have a tendency to want to glitch through that part of the map. cheat TP C11 171214 219123 170 Can someone look into that location and see if there is some sort of hidden "hole" in the code that is cause the rhinos to be deleted? I kind of don't want to get another rhino again for fear that something will happen to it like the last three.