| Pages: [1] :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Messerschmitt facility
Amarr
Shinra
Shinra Alliance
   |
Posted - 2008.05.08 06:25:00 -
[1]
So I guess there is a memory leak when the ship is in flame.
Since when the ship start flamming my FPS dropped from 50 down to low 10 everytime I am zoomed in and able to see the flames.
Also my client consumming a whooping 1.7 GB of ram. If I zoom out so that the flames are not visible the FPS return to the normal 50-60 FPS.
This happens on premium graphics.
I got a 8600 GTS with Omega drivers, on a E6750 and 2 gig ram
Anyone else experiences this? I really hope I am not the only one.
_________________________________
A conclusion is the place where you got tired of thinking...
|
Huil Maar
|
Posted - 2008.05.08 09:01:00 -
[2]
I see the same thing with shadow quality extreme, high bloom. If I turn it down to high shadows, low bloom, then it seems to work fine. This is on an 8800GTS.
|
Vlad Dakovnovich
|
Posted - 2008.05.08 09:07:00 -
[3]
I see the same thing using the premium client, i do however have the graphics turned down a fair bit to avoid GFX card overheating. So I don't think it is related to the graphics quality.
Using a iMac with dual core 2.1GHz and 2 GB ram with ATI X1600
|
Ecky X
Universal Securities
|
Posted - 2008.05.08 09:10:00 -
[4]
 Originally by: Vlad Dakovnovich
I see the same thing using the premium client, i do however have the graphics turned down a fair bit to avoid GFX card overheating. So I don't think it is related to the graphics quality.
Using a iMac with dual core 2.1GHz and 2 GB ram with ATI X1600
If you turn the graphics down, your card just renders more frames. There is very little (if any) less load.
|
Tippia
Caldari
School of Applied Knowledge
|
Posted - 2008.05.08 11:32:00 -
[5]
Doesn't particularly sound like a memory leak – especially since you don't seem to monitor the change in memory usage. Does it increase a bit more every time you zoom in, and fail to return to a lower amount when you zoom out again?
Sounds more like a classic case of straining the GFX card by throwing too much alpha-bledning on the poor thing… Admittedly, an 8x00 series should be able to handle that, but still.
|
GB Man
|
Posted - 2008.05.08 13:19:00 -
[6]
This is certainly an issue, I remember posting in a different thread a while back. This was introduced in the last patch. If your ship has any structure damage that causes it to smoke. It will cause a sort of "Memory Leak". Your FPS will gradually get lower and lower and lower until you dock at a station. When you leave said station, everything will be back to normal until you start flying around. You can barely do 1-2 pockets in a mission before you have to stop what your doing, and redock, just to get this to go away. I believe this bug has something to do with the Camera bug as well, where your camera freezes and it appears as though your game crashed, clicking the reset camera button fixes this.
Quick fix, repair your ship.
|
FT Cold
Sky Net Industries
Pure.
|
Posted - 2008.05.08 13:26:00 -
[7]
Edited by: FT Cold on 08/05/2008 13:29:19
Originally by: GB Man
It will cause a sort of "Memory Leak". Your FPS will gradually get lower and lower and lower until you dock at a station. When you leave said station, everything will be back to normal until you start flying around. You can barely do 1-2 pockets in a mission before you have to stop what your doing, and redock, just to get this to go away. I believe this bug has something to do with the Camera bug as well, where your camera freezes and it appears as though your game crashed, clicking the reset camera button fixes this.
If it was a memory leak, it wouldn't fix itself and would eventually crash the application. Sounds to me like someone needs +(2-4) GB of ram.
Edit: 8600 GTS using premium graphics with HDR isn't helping the issue.
Originally by: CCP Wrangler
And always practice safe sex!
|
Xioden Acap
Lightspeed Enterprises
|
Posted - 2008.05.08 15:39:00 -
[8]
Originally by: FT Cold
Edited by: FT Cold on 08/05/2008 13:29:19
Originally by: GB Man
It will cause a sort of "Memory Leak". Your FPS will gradually get lower and lower and lower until you dock at a station. When you leave said station, everything will be back to normal until you start flying around. You can barely do 1-2 pockets in a mission before you have to stop what your doing, and redock, just to get this to go away. I believe this bug has something to do with the Camera bug as well, where your camera freezes and it appears as though your game crashed, clicking the reset camera button fixes this.
If it was a memory leak, it wouldn't fix itself and would eventually crash the application. Sounds to me like someone needs +(2-4) GB of ram.
Edit: 8600 GTS using premium graphics with HDR isn't helping the issue.
Turning off trails solved this problem for me, and I can still have all the fancy stuff on. As far as I can tell, turning off trails only turned off the burning/smokey effect when you have structure damage.
It very well may be a sort of memory leak in regards to the flame trails. While in space they may not clean up properly, but since they don't display at all while docked, docking can fix it.
|
FT Cold
Sky Net Industries
Pure.
|
Posted - 2008.05.08 15:56:00 -
[9]
Originally by: Xioden Acap
It very well may be a sort of memory leak in regards to the flame trails. While in space they may not clean up properly, but since they don't display at all while docked, docking can fix it.
Ummm... If the memory is "leaked" as a high level view, it's lost to that application. If docking fixes it, I'm betting it's either a slow algorithm or something with your system it doesn't particularly like. clicky
If it was as dramatic as flame = 50->10 fps, then compound that 2 or 3 times and the application would halt and crash, seeing as that's a 5x drop. Again, to reiterate, I doubt it's a memory leak, I'm betting it's something with your specific system.
Originally by: CCP Wrangler
And always practice safe sex!
|
Domania
Convergent
Firmus Ixion
|
Posted - 2008.05.08 16:10:00 -
[10]
I've been wanting to whine about this for awhile, but I forgot.
It's the flame that causes all the lag when you hit hull. It's like CCP smashed tons of flame effects and it just slows your computer to a halt. Yes I've zoomed in for fun and made my computer freeze for a minute. :P
I have a 4800x2, 8600GT, 2 GB RAM, and I have shadows off, bloom low, and HDR and AA 16x using Nhancer. The massive drop in FPS only happens when you zoom in on the flame.
|
P'uck
|
Posted - 2008.05.08 16:12:00 -
[11]
Edited by: P''uck on 08/05/2008 16:13:05
there is definetly something fishy with the hull flames.
as soon as you get hulldamage and your ship starts to burn framerate gradually drops. (at least it does with the premium client).
turning off trails helped a bit, but not too much, afaik the hullfire still gets displayed.
and boy, its extreme. it starts off with 10fps or so and sooner or later you hit 2 frames per minute, until you spin the mousewheel like mad so the camera gets zoomed out beyond a level where flames arent rendered anymore on the next frame.
8600 gts, slightly oc'ed, 2 gig of ram and an e4600 here.
|
Xioden Acap
Lightspeed Enterprises
|
Posted - 2008.05.08 16:18:00 -
[12]
Originally by: FT Cold
Originally by: Xioden Acap
It very well may be a sort of memory leak in regards to the flame trails. While in space they may not clean up properly, but since they don't display at all while docked, docking can fix it.
Ummm... If the memory is "leaked" as a high level view, it's lost to that application. If docking fixes it, I'm betting it's either a slow algorithm or something with your system it doesn't particularly like. clicky
If it was as dramatic as flame = 50->10 fps, then compound that 2 or 3 times and the application would halt and crash, seeing as that's a 5x drop. Again, to reiterate, I doubt it's a memory leak, I'm betting it's something with your specific system.
I sort of a memory leak. There are things similar to memory leaks. Things not getting properly cleaned up by the garbage collector, or not getting manually deleted properly can cause identical symptoms. While it isn't memory allocation directly getting lost to the application, having dead objects hanging around and building up has the same effect.
Something with trails causes it it seems. It's not normal trails, since otherwise the problem would occur while just flying around. But the second flame trail effects are brought into the picture, some people are having extreme FPS drops since a patch under a certain situation that didn't occur prior to that patch.
|
FT Cold
Sky Net Industries
Pure.
|
Posted - 2008.05.08 16:24:00 -
[13]
I guess I'll count myself lucky since this hasn't happened to me at all...
It also looks like everyone that posted is running premium + hdr with <= 2GB of ram. I am seeing a pattern... What are your cache sizes set to?
Now, now, now. Sounds like someone's got a case of the poor me's. If you were gonna die, you would have done it by now! Maybe you just need to realize you're gonna to have to live with intense pain |
P'uck
|
Posted - 2008.05.08 16:29:00 -
[14]
Edited by: P''uck on 08/05/2008 16:29:26
Originally by: FT Cold
I guess I'll count myself lucky since this hasn't happened to me at all...
It also looks like everyone that posted is running premium + hdr with <= 2GB of ram. I am seeing a pattern... What are your cache sizes set to?
it happens wether hdr is turned off or on, independently of cache size. and im not sure if it really makes that much sense running ghetto XP with more than 2 gig.
and just because it can get better with better hardware (but still theres this guy with the 8800 gt complaining...) it doesnt mean it isnt borked. oh and if ram is the issue here, and not gpu power, the problem is even weirder.
there IS something wrong. most definetly.
|
FT Cold
Sky Net Industries
Pure.
|
Posted - 2008.05.08 16:45:00 -
[15]
You almost always benefit from more ram (note the almost infront).
I have lost a ship recently and as I have not had the T3 afterburner graphics problems. I also know that one of my friends has lost a ship recently and also did not suffer from that problem.
I am running:
C2D E8400 - stock speeds + water
8 GB GSKILL 800
8800 GTX - stock speeds
Vista 64 Ultimate SP1
(Also haven't rebooted since SP1 was released so...)
My friend is running:
C2Q Q6600 - @3.0GHz + water
8 GB GSKILL 800
8800 GTX - Bios Flashed (don't know speeds of his)
Vista 64 Ultimate SP1
I use a single client but he uses multiple (3+) clients on the same machine.
Now, now, now. Sounds like someone's got a case of the poor me's. If you were gonna die, you would have done it by now! Maybe you just need to realize you're gonna to have to live with intense pain |
P'uck
|
Posted - 2008.05.08 16:47:00 -
[16]
Edited by: P''uck on 08/05/2008 16:50:46
you have to fly around with your ship in flames for some time. cant say how long tho. sit at safe spot with some hull damage for 10 to 15 minutes or so.
might be interesting to know if its an XP - only problem. edit: the guy with the mac client probably doesnt run XP 
another edit:
i cant tell for sure but im pretty sure it didnt happen when the premium client came out. i think it was one of that following patches that introduced it, but dont quote me on that.
|
Faife
Noctiscion
Twilight Trade Cartel
|
Posted - 2008.05.08 17:06:00 -
[17]
Please stop abusing the term "memory leak". You actually want to say "memory usage went up".
It's as annoying as people who when they run out of hard drive space keep saying that their computer needs more memory.
|
FT Cold
Sky Net Industries
Pure.
|
Posted - 2008.05.08 17:14:00 -
[18]
Originally by: Faife
Please stop abusing the term "memory leak". You actually want to say "memory usage went up".
It's as annoying as people who when they run out of hard drive space keep saying that their computer needs more memory.
Haha - see my 2nd post above. But P'uck and those are saying the game itself has a memory leak with the hull damage - though as you should see I don't think this is the problem - especially to the guy using a mac (not knocking on macs - if it's what you like then use it, I don't want to get into a mac/non-mac battle [which anymore is an osx/windows/linux battle]).
P'uck - any chance you could get a friend using a different setup to put you into hull ina relatively safe area and test it again? I'll get on tonight and get someone to put me into hull and fly around. I'll let you know.
Now, now, now. Sounds like someone's got a case of the poor me's. If you were gonna die, you would have done it by now! Maybe you just need to realize you're gonna to have to live with intense pain |
P'uck
|
Posted - 2008.05.08 17:23:00 -
[19]
Edited by: P''uck on 08/05/2008 17:25:40
Originally by: FT Cold
But P'uck and those are saying the game itself has a memory leak with the hull damage
HEY! I admit I once said in game "It feels like those sort of bugs people call memory leaks". notice me using that term very cautiously, since i dont have a clue what it actually means, apart from that number climbing in the taskmanager 
but in that thread i only called it "fishy" and "wrong", and both are VERY fitting and also VERY technical terms!
(just sayin, i aint abusing no terms)
and sorry, i wont have time for eve tonight, but maybe sometimes the next days i can bug a buddy (that usually claims not to encounter this problem) to test it with me.
edit: to test it, you can actually be quite safe: whenever you fly a shield tanking ship, get some % hull damage, rep up armor, and play as you normally would, just with a little less hp.
|
FT Cold
Sky Net Industries
Pure.
|
Posted - 2008.05.08 17:25:00 -
[20]
Sounds like a plan P'uck
Now, now, now. Sounds like someone's got a case of the poor me's. If you were gonna die, you would have done it by now! Maybe you just need to realize you're gonna to have to live with intense pain |
Messerschmitt facility
Amarr
Shinra
Shinra Alliance
|
Posted - 2008.05.08 17:44:00 -
[21]
Fine, call it as you want, but still the problem exists as I see not only me has the same problem.
Some people here said it perfectly. The frames DO get lower and lower until you go and dock. The smoke trail has to be the trigger of whatever this is. Also when you are zoomed out and you zoom in to see your ship, the client will freeze for 5-10 seconds.
CCP can you please acknowledge this issue?
_________________________________
A conclusion is the place where you got tired of thinking...
|
Sharp Feather
Gallente
Ministry of Natural Resources
|
Posted - 2008.05.08 18:42:00 -
[22]
talking about the big flame on the tail of ship when near the death... thats so frigging FUGLY.
Multiple littles flames >>>> one HUGE random flame on an akward place. 
|
GB Man
|
Posted - 2008.05.08 20:10:00 -
[23]
This is why I said a "Sort of memory leak". In the aspect that it acts like one. Simply put, it's a problem with the Graphics engine. There are many bugs that have popped up since the last patch in this area.
|
Winterblink
Body Count Inc.
Mercenary Coalition
|
Posted - 2008.05.08 20:14:00 -
[24]
Originally by: Sharp Feather
talking about the big flame on the tail of ship when near the death... thats so frigging FUGLY.
Multiple littles flames >>>> one HUGE random flame on an akward place.
You should see it on capital ships. Boy does it ever look out of place. Mostly because the flame is like the size of a station.
|
Vlad Dakovnovich
|
Posted - 2008.05.09 08:14:00 -
[25]
Edited by: Vlad Dakovnovich on 09/05/2008 08:15:24
Just to clarify, although using an iMac it is actually the windows premium client running on an XP partition (so basically a good looking PC) cos the mac client sucks abit although not noticed this problem with it.
If i remember correctly this started after the trinity 1.1 patch. I have my cache set the the required size for 2GB of ram (according to initial dev blogs) and i have HDR turned off.
|
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |