No replies to this topic

[Elkarlo]

Don't know where to post it, so i try it here.

As far as i understand from the hearings in TS and Observation
the 4FPS bug is Memory leak related.

The Memory Leak is good observable by simply opening the Taskmanager
while in Mechlab.

When you change from one Mech to another SLOWLY then the Memory goes back
to the Status before, but when you swap it fast, then your client will consume more and more Memory. It seems that some Dynamic Memory Pages are not freed up when it got fast.
This can be an Issue with the OS or other Matters, fakt is, that loading tons of Different Mechs
use up Memory, especially when you had been in Combat your Memory usage goes up.
And i guess lot of the Memory used is Dead.

Lot of people have the 4 FPS Bug when they have played 3-5 Games, personally i don't have it, or just registered it once but my Graficcard recovered, but i suffer from more and more HUD bugs after i hit 700MB of memory used in Mechlab, thats around 15-16 games, then it is more Likely for me that i will have Bugs next Game.

My Suggestion would be to make a Function into the Client for Memorydump/Refresh before the Launch of every Game, so when you leave Mechlab the Grafiksection of Cryengine is totally shut down, or refreshed ( don't know how it directly works in Cryengine) so that the Memory is dumped. This should reduce the FPS bug enormously, but would be a performance breater for going into the Match ( as you have to reload everything),
maybe putting this Function as an Optional task.

In a normal Gaming day i don't need it in Example.

I think the Problem is that we have the Cryengine 3D Mechlab with UI overlay and go over to the 3D Gaming source, so Leaks are carried over from Instance to Instance, a hard break like most other Games to would reduce the Problem greatly. I notice that you have already done
something to reduce the Memory leak, as the crow of Leaked Memory used.
But Maybe the Cheater Option ( like my Programming Trainer would say) is more wise, as the Problem may even be in the Operating System. Clean Programming is good and solves Problems before they occure but sometimes a sloppy Method like a refresh maybe good to implement and even when it is as Option, for the People still having the Bug ever 4-5 Games without restart of the Client.
( Some of them only have 4GB Ram, and or Nvidia Cards, which are known to leak "better" then AMD Cards )

The Drawback of a Restart of the 3D engine maybe:
Problems on Connecting Clients to Games
Increased loading Time for the Maps
Greater Chance of CTD while starting

So i would make the Function maybe as Option to Choose