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
Discussions Rules and Guidelines
Report this post
You don't even have a sample count high enough to be saying these kind of things (like "nearly all" people use SLI). The other thread mentioned in this one points to pages upon pages of reports of various different settings and configurations, SLI or not, Nvidia/AMD, Intel/AMD, Windows 7/8/10, Latest Drivers/Updates or not. If you're saying yourself you play with everything maxed then it could be one of the middle settings. But again, I used to play on max settings and had to downgrade after 246 otherwise it'd crash in a min or so.
That all said, it's probably best if you just stay away from this thread since you don't experience the problem, like you just stated. Good night.
Total RAM usage 2.97GB.
I agree with you man, comparing and contrasting does need to be done - that's what we've been trying to do in the bug report thread. But sadly, to date, no comparison can be found.
I can't speak for others in this thread, but myself, I'm not uptight about trying to troubleshoot things. I'm just providing info when asked that might contribute to the brainstorm, like my comment about not having SLI just before. Just a bit of info from my end to add to the discussion, in the hopes of finding some cause.
However yeah, in the other thread we already have 18 pages of reports, and so far few commonallities have been found. It's definitely a client issue not a server problem, that we can say for sure. And it only starts when a world is loaded in, either single player or on a server - before loading a world, sitting at the main menu, RAM usage is stable and doesn't ramp up. But as soon as a world is loaded, the RAM starts to increase, and the only hunch we have so far is that it seems to go up faster in areas with lots of green trees and plants. We don't have any other leads to go on.
I saw this solution too, but sadly it does not work for the majority of people. I tried disabling it completely on my machine, along with Steam overlay and another monitoring program (EVGA Precision X) which has an overlay feature for good measure. RAM cranked up during play just the same as it did before the disable.
Additionally, a lot of people in the other thread are not running Nvidia hardware at all, so this cannot be the cause for them.
1. ark updatde
2. nvidia GPU drivers updated
and to pour flames on the fire ark does NOT need 16GB ram lmao
>twistedfirestarter<
Which totally makes sense. The problem is... standing still or doing next to nothing in a closed area and RAM going from 3-4GB to 11.
Two 980s and 8 core CPU 32 G of ram 500G SSD. I run a server and play on the same PC 11G ram usage and between 17 and 23 CPU.
For example, if I've been playing for a while and the game is taking 13-14GB, and I want to open Firefox to check something about the game on the wiki, it can take a good 2-3 minutes for the browser to open and display, and then another 2-3 minutes or more to navigate from one page to the next.
This continues until I shut the game down. I can back out of my world/server to the main menu, but the main menu takes a long time to load, and the mouse is extremely unresponsive on it. And when I click to quit the game from the main menu, it takes as much as 7-8 minutes for the game's process to fully close and my computer to return to standard operational speed again. The leak does not kick in until you open a world/server, but the memory usage remains even after you close said world/server, until you close the game completely.
I also run a locally hosted dedicated server on the same machine as my client, but this is not affected by the leak in any way. Once loaded, the server tends to sit at around 2-3GB of memory and never increases beyond that, no matter how long it is open for. The leak is exclusive to the client, and is not in the server.
Programs that I often have open when running the game, which I tend to have open no matter what I'm doing on my PC but they don't affect gameplay on any other game:
Steam (duh)
Skype
Windows Notepad (for writing notes to remind myself of things in game)
Windows Explorer (for server/savegame managment)
Windows Task Manager (I like to keep an eye on my performance etc.)
Occasionally Firefox
Background programs like antivirus, hardware drivers and management programs, etc.
Everytime I return to base I've been checking RAM usage and it always drops back to about 2.9, with a memory leak it wouldnt drop back at all.
Where specifically are you all building, operating, etc on the map? I'm trying to recreate the bug.
It'd be best if you can actually ask for settings of the guys that can actually play for some time with the leak. It literally takes less than a minute to crash if I don't launch Low Memory 4GB with my settings (a mix of high-epic atm), so I can't say what I'm doing when it crashes because it's literally walking around my base and checking equipment before it crashes. The guys on that thread can play for a few hours before crashing and IIRC they don't use low memory 4gb mode.
I agree and i was afraid of that :(.
Me personally, I've been playing a new save, so I've been collecting resources and building a base on the small plateau by the river NW of the redwood biome, with occasional trips through the forest south to my starter base in the sand dunes S of the red obelisk. I did seem to get marginally slower memory overload when in the sand dunes, which have less vegetation than the forest and the redwood biome, so that coupled with other people's reports of better performance away from foliage is the basis for our theory that it's to do with plant models or textures somehow.
But in the bug report thread there have been many people saying they were in other areas, or even on other maps altogether. So I'm not sure that location is really the issue, sadly. I appreciate your work in trying to replicate it though^^
Not all software problems are generally repeatable, there are several cumulatives that cant be replicated or reconstructed. Like i said, it isn't going to convince me or anyone else so respectfully, i suggest you stick to either providing possible solutions or walk away.
Like i said, AGAIN, i disabled SLI and the problem persisted.