Does this game still suffer from memory loss issues in mp?

[iSurvivedRKelly]

Havn't played in a while. Loved the game when i did, but we all noticed when playing mp that the longer you played the worse performance got.
Found a fix by setting up a schedule in windows to empty your memory reserve every 10-15 mins.
Does the game still have this issue? Just wondering if i need to set this up again.

[Good Old Gamer]

it still suffers it in SP:

Here are my specs (every website including *Can my PC run it* says i can)

Nitro 5 - i5 11400H
3050ti
16 gig ram
Windows 11
M2 SSD

But, as well as i can play it (on medium > low) without issue, when i try to Stream it on twitch, the stream keeps dying, so yes... mem leak for sure

**Regardless MP/SP

[iSurvivedRKelly]

Cheers, oh well guess i'll set it up again then hehe

[iSurvivedRKelly]

Originally posted by Carbon:

There is no memory leak, only users who haven't optimized their systems, but running ISLC is always a good idea within a Windows environment as a general rule.

Describe optimizing your system if you can please. I've been gaming for years never really had any issues nor even with this but.. last time i played the longer our sessions were the lower the fps got. And memory usage was off the charts.

I've never had to set up a memory schedule for any other game tbh. And SP i never had the problem. This was about 6-8 months ago though.

RTX 4090
AMD Ryzen 9 7900X
32g Ram
SSD m2
Win 11

[Carbon]

There is no memory leak, only users who haven't optimized their systems, but running ISLC is always a good idea within a Windows environment as a general rule.

Unfortunately, sites like "Can I run it" don't factor in user experience or knowledge, which is the primary cause of problems, particularly with mature games that have been patched to the point that they are running well on the majority of properly configured systems. Anyone still having issues with the game at this point is to blame.

Icarus is in a very good state right now, some stutters aside, but this is common with UE games and there are a few workarounds that can mitigate.

Regarding MP performance, since the game moved away from centralized servers, hosting a MP session on your system will have a performance effect, naturally. This is not a problem with the game per se, but the nature of hosting a game on the same rig with which you're playing.

I'm no apologist, nor blindly defending the game against anything but ignorant and misleading accusations.

Basic activities: manually set your pagefile size and put it on the same drive as the game (M.2 or SSD), update your drivers, run ISLC, set the Windows power plan to Ultimate Performance, verify the game files and minimize background tasks and it should go well.

[iSurvivedRKelly]

Originally posted by Carbon:

There is no memory leak, only users who haven't optimized their systems, but running ISLC is always a good idea within a Windows environment as a general rule.

Unfortunately, sites like "Can I run it" don't factor in user experience or knowledge, which is the primary cause of problems, particularly with mature games that have been patched to the point that they are running well on the majority of properly configured systems. Anyone still having issues with the game at this point is to blame.

Icarus is in a very good state right now, some stutters aside, but this is common with UE games and there are a few workarounds that can mitigate.

Regarding MP performance, since the game moved away from centralized servers, hosting a MP session on your system will have a performance effect, naturally. This is not a problem with the game per se, but the nature of hosting a game on the same rig with which you're playing.

I'm no apologist, nor blindly defending the game against anything but ignorant and misleading accusations.

Basic activities: manually set your pagefile size and put it on the same drive as the game (M.2 or SSD), update your drivers, run ISLC, set the Windows power plan to Ultimate Performance, verify the game files and minimize background tasks and it should go well.

Yeah that's all the basics. I've never need to create a larger file page though. Not for any other survival, 7 days to die etc. Basically it's Unreal 4 engine is enough info for me as to why it has issues and looks a lot nicer than 7 days. Not my pc.

I don't even get stutters really, but once it starts dropping in this game it just gets worse and worse. Though hangs around the 60 fps mark at worst.

Plus, increasing page file just makes everything else slower and make your drive work harder. Rather just use the scheduler for this game only. As no other game runs out of 32g ram, literally only this one. Well did anyways. Guess i'll go test it out again.

[Good Old Gamer]

the only thing you don't mention is how fast that would kill a laptop ;)

[Carbon]

Originally posted by iSurvivedRKelly:

Plus, increasing page file just makes everything else slower and make your drive work harder.

Not true. Increasing the pagefile doesn't make the PC necessarily use it more (it's an ugly hack that 'tricks' certain software) and additionally, setting the size manually restricts it from growing and shrinking, reducing I/O thrash.

Anyhow, doing that solves the vast majority of memory-related errors, such as that which the first respondent is experiencing. They rarely act upon the advice to manually set it because first, it isn't a particularly intuitive solution and second, they think they know better.

[iSurvivedRKelly]

Originally posted by Carbon:

Originally posted by iSurvivedRKelly:

Plus, increasing page file just makes everything else slower and make your drive work harder.

Not true. Increasing the pagefile doesn't make the PC necessarily use it more (it's an ugly hack that 'tricks' certain software) and additionally, setting the size manually restricts it from growing and shrinking, reducing I/O thrash.

Anyhow, doing that solves the vast majority of memory-related errors, such as that which the first respondent is experiencing. They rarely act upon the advice to manually set it because first, it isn't a particularly intuitive solution and second, they think they know better.

Yeah mines always set to 5gb which has always been adequate for any game.

[Carbon]

Originally posted by iSurvivedRKelly:

Yeah mines always set to 5gb which has always been adequate for any game.

Sure, do as you wish, but this is the same argument I mentioned earlier, that we think we know better. In truth, different programs behave differently and while 99% of them indeed act predictably, Icarus seems to occupy that 1%. Memory consumption issues in general or the "out of video memory" errors and variants are all remedied by manually setting the pagefile, a problem/solution which does not potentially exclude your situation. It doesn't hurt to try, as it's easily reversed.

Anyhow, I'll stop beating the drum...hope it goes well.

[ZombieHunter]

I have not noticed any memory leaks. Also I would not be so quick to diagnose something as a memory leak without using proper tools in the process. Not everything in software is a memory leak. There are many more issues that can arise related to memory that are not leaks.

Usually when a game slows down over time it is not evidence of a leak. It is evidence of fragmentation. It is the same concept as disk fragmentation. This can be avoided somewhat by using stack and block allocators instead of the default C++ memory allocation. What happens over time in the default allocation scheme is that due to many small allocations and de-allocations the memory layout becomes quite fragmented. The whole process of how and why this happens is beyond the scope of anything that could be posted here but you can go research it if you want to.

A memory leak is usually, but not always, indicated by constantly rising memory usage. However constantly rising memory usage is not a sure sign of a leak rather it could be a sign that your game has not yet reached its maximum plateau usage of memory.

I have played Icarus for upwards of 6 to 8 hours in one session before and never noticed any degradation in performance. The memory usage seemed to top out and then bounce up and down from there which is what it should do. VRAM usage on my 16GB card was near maxed out which is what I would expect.

Icarus definitely has performance issues when loading in new data as you traverse the map. This is mitigated somewhat by using some flavor of solid state drives but not eliminated entirely. I've never seen Icarus smoothly transition from one area of the map to another without some kind of issue.

Also keep in mind that using virtual RAM is not bad when it is managed properly. Many games use this to swap in data and swap out data for huge worlds. It is easy to use from a development perspective and memory mapped file I/O is quite performant overall. The problem comes when every single allocation must use it. At any given time there might be all kind of different apps and processes using virtual RAM. It is not as simple as 'use virtual RAM' and you get bad performance.

Also note that unless the supposed, and as of yet unverified 'leak', was large you would not notice it for a very long time.

[Spook]

I cant tell you any specific technical info, but I can tell you they fixed a major problem that was a result of forest fires from about a year ago. There had been a render bug where a burned forest was trying to render all the charcoal nodes in a burned tree, the previous state of the tree, and the lack of the tree when it was chopped down, all at the same time. When people ignored forest fires and just let them spread and burn themselves out, this caused massive amounts of trees trying to render three completely different states simultaneously across the entire burn map. Compound this by the number of players trying to render the same area simultaneously and the maps devoured themselves and crashed constantly after a fire.

I still sometimes have issues around really big fires, and my four player squad has been experiencing issues with desert storms, but things have improved substantially from where they were.

[Rocket]

Do note that with ICARUS we aimed the bar very high for scale. So *every* tree on the map can be cut down, etc. This means that, depending on actions in the world, a lot of memory can be used. Given it is a PC only game, we also wanted to make something that could grow with improvements to PC's over the years, hence depending on settings and usage, the game could end up using a lot of RAM.

[Carbon]

Originally posted by Rocket:

Do note that with ICARUS we aimed the bar very high for scale. So *every* tree on the map can be cut down, etc. This means that, depending on actions in the world, a lot of memory can be used. Given it is a PC only game, we also wanted to make something that could grow with improvements to PC's over the years, hence depending on settings and usage, the game could end up using a lot of RAM.

Oddly, only modest system - 10700k, 2070 Super, 16GB - I have never seen the total system memory usage over 60%, even after hours of playing with setting all on Epic (no AA) and DLSS on Balanced. I'd personally say that memory usage is not at all an issue.

[WarNerve]

Originally posted by Survive or Die:

it still suffers it in SP:

Here are my specs (every website including *Can my PC run it* says i can)

Nitro 5 - i5 11400H
3050ti
16 gig ram
Windows 11
M2 SSD

But, as well as i can play it (on medium > low) without issue, when i try to Stream it on twitch, the stream keeps dying, so yes... mem leak for sure

**Regardless MP/SP

Your system is kind of on the low end of specs for streaming.

[kyraeus]

Yeah, but even on low settings, the game overutilizes the GPU and basically destroys anything other than top end gear. Specifically AMD gear. Seems kind of ridiculous you'd bar half your market by not properly testing with most common gear on both sides of the divide.

ESPECIALLY with a game as intensive as this one on GPU.

For example I've had several questions in regarding lightning strikes taking down to 1fps and massive GPU hits on a 6600 for months, haven't heard a word. Or with massive lag spikes to video on opening the map, specifically. Inventory/crafting screens are fine, but open the map, and it lags to about 1 fps. And it's not all the time, it'll do that for a while then open the map normally, then go back to lagging when it's opened.