Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
UE4 engine itself has bugs in it (D3D UE4 crash) that have been there since day one.
I suppose Epic Games are not professionals either 😪
I see u allot on the forums and i usually agree with you. But personally in this particular case im afraid i don't.
When a game that relies on killing things fails to allow you to kill things properly it is a real problem and should be dealt with. This desync issue has been here for years and the devs don't some to give a crap at all.
What's worse is that i find the desync on hit registration and rubber banding way worse on official servers than i do on my own private servers.
It's not the only problem they should have fixed along time ago before making DLC's, but it is definitely one of the biggest.
Imagine if Quake, Call of Duty, Borderlands, or any other game with shooting things had this issue :)
Ark is pretty much too complex for UE4 imo... however... UE4 is the only engine capable of allowing Ark/Atlas/Conan/DarknLight, to do what they do..... and they all have hit registration issues. Even Fortnite gets hit registration issues... and thats stick men drawings compared to Ark.
So the issue is bigger then WC... wich points towards inherent issues in UE4 as much as WC's coding.... its much better then it used to be.
Fair point.........................
.........Atlas doesn't count though.
Either way.... its a moot point... coz the problem is still annoying af.
It's also important to note if you're playing on a server where there is foundation spam, breeders with 100 deinonychus shaking their tails, etc. The whole server is going to lag and there's nothing WC can do about it.
Actually, Atlas is developed by grapeshot which is a subsidiary of Studio Wildcard.
The game began as a mod for Ark which the devs expanded and made into it's own standalone game creating a secondary dev team to further develop it.
The game itself isn't just a "template". It's straight up ark with some changes. and therefor i do not count it as it's own game. it has the same problems because at it's core it is Ark.
For a while I kinda accepted the idea that these creatures have thick hides and a direct shot was required but it gets harder and harder to fabricate fantasy reasons to make up for such nasty bugs when they keep popping up all over the place. When only 1 in 5 tranq darts registers on a bronto I can deal, but when an Ichthyornis steals a full stack of ammo or narcotics after I shot it a dozen or more times I get a little frustrated.
The 3 being WC/Grapeshot, Snail Games and Funcom.
Atlas is not straight up reskinned Ark.
In the same way DnL is not reskinned Ark.... they share assets absolutely.... they both used Ark assets as placeholders before making new models. But they use many different mechanics.
Atlas runs on the same base UE4 version that Ark does... but cannot run on the same heavily customized version that Ark is on.... the customized additions to Atlas are not backwards compatible.... water mechanics in particular.
I dont know when you played DnL last... or if you ever have.... but it is far closer to Ark then Atlas ever was.... and yet it is so utterly different.
That is imo 100% WC.