| Pages: [1] :: one page |
|
|
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Alena Ventrallis
Ahrendee Inc.
Negative-Feedback
2971
   |
Posted - 2015.04.08 00:26:00 -
[1] - Quote
So something I notice when we talk about framerate lag. I believe we are looking into the wrong area when we try to fix the lag. Now so far we have been looking at various areas, like comm channels and such, as possible fixes for the lag. However, I think the problem is down further in the code: a memory leak.
Here's my line of thought: if it was comms that was causing the problems, or number of suit fittings, we would see framerate lag spread out evenly over the entire match from start to finish. But instead, we have the match start out fine and get steadily worse as it progresses. This is most noticeable on Gallente Research Facility. Next time you deploy, notice how you deploy just like normal, but as you fight, the lag gets worse and worse and worse. This is symptomatic of a memory leak, although there are other possible reasons for this behavior.
Wikipedia decribes a memory leak as "a type of resource leak that occurs when a computer program incorrectly manages memory allocations[1] in such a way that memory which is no longer needed is not released." Imagine your PS3's memory (RAM) as table-space. The more RAM you have, the bigger your table. Now, when you use your table (say, to paint), after you finish whatever you are doing, you then put the stuff back in its place to keep the table clear for the next task (you put your paint and paper back in the closet). This is what your computer does with RAM; once it's done using RAM for one part of a program, it releases it so it can be used for another part of the program. Now a memory leak happens when your computer doesn't release the RAM like it should. Going back to the table analogy, it would be like leaving all the stuff you last used sitting on the table. So when you want to do something else with the table (like eating) all the paint and paper and brushes and stuff are still on the table in your way. This means your computer has less table-space to work with, which then causes the program to start run slower and slower as it has less and less RAM to work with..
Now, there are other possible causes for this behavior, and it would take a n actual programmer to disgnose and fix a memory leak if indeed it is one. It could also be that the game needs to clear its cahce more often. But I don't believe the framerate problems we are experiencing are because of comms or number of fittings. IF so, wouldn't we see lag happen as soon as the match begins instead of partially into it? So this is something Rattati can look into as a possible cause for the horrid framerate lag we are experiencing.
Whirly gun make much thunder! - Victor
|
KEROSIINI-TERO
The Rainbow Effect
2013
|
Posted - 2015.05.17 03:26:00 -
[2] - Quote
Bump as there might be some things someone wiser than me might understand.
Maybe even at CCP....
Looking at both sides of the coin.
Even Aurum one.
|
Scheneighnay McBob
And the ButtPirates
6622
|
Posted - 2015.05.17 04:04:00 -
[3] - Quote
CCP understands what a memory leak is. They patched a massive one from the orbital artillery outpost in beta.
Some details can be ignored
|
Henchmen21
Planet Express LLC
1307
|
Posted - 2015.05.17 05:21:00 -
[4] - Quote
PS3, now there is your problem.
Acquisition is terrible, matchmaking is terrible, your game is still riddled with bugs, you should feel bad.
|
Henrietta Unknown
Corrosive Synergy
Rise Of Legion.
1456
|
Posted - 2015.05.17 05:45:00 -
[5] - Quote
Mere speculation or not:
1) Unreal Engine 3 just sucks
2) Needs cache clearing
3) Proto suits' many slots take up memory
4) Map leak on Gallente Research Facility and Caldari Production Facility
5) High density of proto players in an area -> greater stress on memory
6) Deployment of more vehicles, equipment, and AV with fancy projectiles traveling long distances take up memory
etc.
Selling Items
Store - Player Trading
|
STYLIE77
KILL-EM-QUICK
Rise Of Legion.
682
|
Posted - 2015.05.17 05:57:00 -
[6] - Quote
I know this much, the Bridge map in PC is unplayable for me...
And most of the skirmish maps in pubs are unplayable as well.
I have frame rate loss so bad that I am getting headaches from it.
Can't deal with it...
So fac war is fkd for me, pc is fkd, and half the skirm pub maps, and 3 of the dom maps often lag up.
Resetting helps on some but others it doesn't matter it will lag.
What I don't understand is the 1 out of 10 games where it is fine... no lag at all.
It just sucks to play a game and have to reset your Ps3 2 or 3 times an hour in a futile attempt to fight lag.
Fracture road only has issues when the version that has the two new sockets comes up, so I know that there is a memory leak issue with those sockets.
It get's so bad that audio issues also come into play, silent vehicles and weapons... very annoying. You hear the bullets hit but no weapon fire, no vehicle engines... just sucks.
Yet there are people that can play Skirmish all day with no issues... I don't understand how that can be.
Some are on old fat boys on wireless connections others are on super slims with fiber connections so there is no common factor to why they have no issues.
http://caughtyouflinching.ytmnd.com/
|
CommanderBolt
KILL-EM-QUICK
Rise Of Legion.
3532
|
Posted - 2015.05.17 06:14:00 -
[7] - Quote
STYLIE77 wrote:I know this much, the Bridge map in PC is unplayable for me...
And most of the skirmish maps in pubs are unplayable as well.
I have frame rate loss so bad that I am getting headaches from it.
Can't deal with it...
So fac war is fkd for me, pc is fkd, and half the skirm pub maps, and 3 of the dom maps often lag up.
Resetting helps on some but others it doesn't matter it will lag.
What I don't understand is the 1 out of 10 games where it is fine... no lag at all.
It just sucks to play a game and have to reset your Ps3 2 or 3 times an hour in a futile attempt to fight lag.
Fracture road only has issues when the version that has the two new sockets comes up, so I know that there is a memory leak issue with those sockets.
It get's so bad that audio issues also come into play, silent vehicles and weapons... very annoying. You hear the bullets hit but no weapon fire, no vehicle engines... just sucks.
Yet there are people that can play Skirmish all day with no issues... I don't understand how that can be.
Some are on old fat boys on wireless connections others are on super slims with fiber connections so there is no common factor to why they have no issues.
Just gonna throw this out there....
Delete DUST from yoru PS3 and redownload the latest client. This alone has given me a much smoother experience.
Delete all mail, contacts and anything else you can do without to free up space / anything...
I also find having comms turned off in the options helps a lot, might be worth while getting your teams onto Teamspeak or another Voip chat service.
Vitantur Nothus wrote: Why hide a solution under frothy pile of derpa?
SCV Ready!
|
4lbert Wesker
Mithril Forge
E-R-A
197
|
Posted - 2015.05.17 06:38:00 -
[8] - Quote
Henrietta Unknown wrote:Mere speculation or not:
1) Unreal Engine 3 just sucks
2) Needs cache clearing
3) Proto suits' many slots take up memory
4) Map leak on Gallente Research Facility and Caldari Production Facility
5) High density of proto players in an area -> greater stress on memory
6) Deployment of more vehicles, equipment, and AV with fancy projectiles traveling long distances take up memory
etc.
Let's sum it up.... It's a goddamn PS3,ancient console played even by Jesus himself...
Public skirmish = camping games,
Public domination = officer sniping games,
Public ambush = russian roulette
|
Aeon Amadi
Negative-Feedback.
Negative-Feedback
10259
|
Posted - 2015.05.17 08:21:00 -
[9] - Quote
Considering that the Gallente Research Facility and the Caldari Production Facility sockets were merged as one in the trailer, I wouldn't be surprised if the memory leak was situated around the socket randomizer.
(Gê¬n+Ç-´)GèâGöüGÿån+ƒ.pâ+n+ín+ƒ. LASERS BTCH!!!!!!
|
deezy dabest
2291
|
Posted - 2015.05.17 08:52:00 -
[10] - Quote
OP you are correct that there is likely some memory leaks causing issues.
Developers far and wide have said that the PS3 is the most difficult system to code for and generally optimize for of any game console ever made.
What this means is that between the forced switch to unreal engine and the fact that CCP had little experience in the console itself Dust is almost guaranteed to poorly use system resources. It is not really CCPs fault as they had to make the jump some where if they wanted to move into consoles. I think the thing that is CCPs fault is that early on they put so much dedication to the PS3 without really dedicating the appropriate resources on the back end to adapt to the climate which they entered.
Now they are not only sticking to a more difficult and less powerful console but also have seriously cut back the resources which only makes the problems worse. What we have seen here is more of the terrible management from CCP that they have come to be known for across the programming community as well as the Eve community.
One can only hope that CCP will trip and fall on a way to actually manage console gaming as oppose to this blind leading the blind scenario which we have seen for so long. Ratatti seems to have talked more sense into them thus far maybe he will be able to get them more on a sensible path overall instead of just helping them tread water.
|
|
|
|
|
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |