I think there may be a memory leak while in ground combat... my away team like joins me half way through the mission randomly and it gets really laggy and then eventually crashes my computer. I know its not my personal system, I just built this thing a month ago.
IDK about memory leak, in my performance monitor, the game seems to be using a very steady ~1GB. Have you confirmed a memory leak with the monitor? Any specific error messages? What's your system specs? (I'm sure all this info would help cryptic a lot)
I've been getting the same issues as well on certain ground combat missions.
I've seen them happen consistently on the Starbase 24 ground combat component; i'd be shooting my way through the Klingons and all of a sudden my PC reboots. After the reboot, I'd try again and get the exact same behavior nearly the same amount of time into the mission.
Not really sure what's going on. Any tips on what other data I need to submit a bug?
Win xp
AMD Phenom Quad core 3.2gz
ATI Radion HD 4800
4GB DDR3 3328
Anything else im missin?
have you checked your task manager performance monitor to see what your RAM usage is like? A leak would mean the RAM usage would slowly climb to 100% usage and will not be able to free up space (ie. remove data it doesn't need at the time).
Also, when it crashes do you get an error message? Have you checked your GPU temperatures?
I've been getting the same issues as well on certain ground combat missions.
I've seen them happen consistently on the Starbase 24 ground combat component; i'd be shooting my way through the Klingons and all of a sudden my PC reboots. After the reboot, I'd try again and get the exact same behavior nearly the same amount of time into the mission.
Not really sure what's going on. Any tips on what other data I need to submit a bug?
software causing a reboot is pretty uncommon. if you're running XP, if your graphics driver fails, I believe (IIRC) that it can cause a reboot.
Try to put off the auto-stabilize framerate on Options->Video->Troubleshooting
I no have more crashes on ground when i put this option off and srry my english im spanish xd
software causing a reboot is pretty uncommon. if you're running XP, if your graphics driver fails, I believe (IIRC) that it can cause a reboot.
Hmm...odd...I'm working off a relatively fresh install of WinXP 32-bit. I also just uninstalled Catalyst 9.11 and installed 9.12.
I'll try the auto-stabilize option when I get back from work.
On a related note, I can't seem to enable Geometry Instancing with Catalyst 9.11 & 9.12. The "More Settings" option just isn't there. And ATITools just doesn't work for me so any other tips would be great
Hmm...odd...I'm working off a relatively fresh install of WinXP 32-bit. I also just uninstalled Catalyst 9.11 and installed 9.12.
I'll try the auto-stabilize option when I get back from work.
On a related note, I can't seem to enable Geometry Instancing with Catalyst 9.11 & 9.12. The "More Settings" option just isn't there. And ATITools just doesn't work for me so any other tips would be great
you can always pull up the windows crash logs and see if there's anything that stands out; could be a BSOD even happening but way too fast to even notice.
There is a memory leak, or very poor memory handling in the graphics area. I have 8600GTS SLI, with 256megs each, which is the minimum video memory to have. When I have AA, shadows, lighting all turned up rather high the game crashes when loading new areas. The most I got through were like 4 or 5 space areas before crashing. Loading a ground area even after 1 or 2 space areas causes it to crash quite often too. An error pops up after the game crashes saying "ran out of memory" and mentions Direct3D. I know DirectX is installed "correctly" (it is a microsoft product) because I play several other modern games.
I have not had it crash because of effects from AoE or anything. Just when loading the next area.
I know, just turn down my settings right? But I shouldn't be forced too. I get good frame rate and it looks nice with everything turned up to at least medium if not higher. I turned off SLI and I went a bit longer before crashing, but all the missions were in space so it wasn't a fair test.
There is a memory leak, or very poor memory handling in the graphics area. I have 8600GTS SLI, with 256megs each, which is the minimum video memory to have. When I have AA, shadows, lighting all turned up rather high the game crashes when loading new areas. The most I got through were like 4 or 5 space areas before crashing. Loading a ground area even after 1 or 2 space areas causes it to crash quite often too. An error pops up after the game crashes saying "ran out of memory" and mentions Direct3D. I know DirectX is installed "correctly" (it is a microsoft product) because I play several other modern games.
I have not had it crash because of effects from AoE or anything. Just when loading the next area.
I know, just turn down my settings right? But I shouldn't be forced too. I get good frame rate and it looks nice with everything turned up to at least medium if not higher. I turned off SLI and I went a bit longer before crashing, but all the missions were in space so it wasn't a fair test.
I can see what you're saying. The newer version of EVGA Precision actually shows you what GPU memory you're using, and I go up to around 400MB (maximum) video memory used at all highest settings @ 1680x1050.
A memory leak or leakage in computer science is a particular type of memory consumption by a computer program where the program is unable to release memory it has acquired
Unless the game is consuming memory that slowly increases until the memory is completely full and can't hold anymore, then it's not a memory leak. Granted it could use some kind of hard drive cache for the data that can't be stored in the GPU memory instead of crashing, but in that case your CPU and HDD load would increase, crippling performance anyway.
256MB of GPU memory is pretty low when playing at higher resolution and turning up AA. Whether your GPU can render the frames sent to it wouldn't matter if you don't have the memory to support all the textures, etc. that the game is trying to load into the card. You're just going to have to turn down your res to maybe 1440x900 or lower and lower the AA setting.
I've gotten this same thing at least 3 or 4 times yesterday. Ever since I applied that last patch I've been crashing A LOT between zones. It always says "E_OUTOFMEMORY" as the error code. That's bad because I have 6GB of system memory and 2GB of video memory. How do you run out of space for video memory with 2GB?!
I have noticed that from initial memory consumption of 1GB, after an hour or more of play it shoots up to around 3GB, although I never thought to question this as a memory leak.
Same here. It only started since the last patch for me too. I have 6GB of ram and a Radeon 5750 with 1GB of vram. There is defiantly something causing it to eat up more memory than it should.
guys remember, this is a 32-bit app therefore is restricted to a private memory limit of 2gb therefore you will never see the process climb to 100% mem usage.
Comments
AMD Phenom Quad core 3.2gz
ATI Radion HD 4800
4GB DDR3 3328
Anything else im missin?
I've seen them happen consistently on the Starbase 24 ground combat component; i'd be shooting my way through the Klingons and all of a sudden my PC reboots. After the reboot, I'd try again and get the exact same behavior nearly the same amount of time into the mission.
Not really sure what's going on. Any tips on what other data I need to submit a bug?
have you checked your task manager performance monitor to see what your RAM usage is like? A leak would mean the RAM usage would slowly climb to 100% usage and will not be able to free up space (ie. remove data it doesn't need at the time).
Also, when it crashes do you get an error message? Have you checked your GPU temperatures?
software causing a reboot is pretty uncommon. if you're running XP, if your graphics driver fails, I believe (IIRC) that it can cause a reboot.
I no have more crashes on ground when i put this option off and srry my english im spanish xd
Hmm...odd...I'm working off a relatively fresh install of WinXP 32-bit. I also just uninstalled Catalyst 9.11 and installed 9.12.
I'll try the auto-stabilize option when I get back from work.
On a related note, I can't seem to enable Geometry Instancing with Catalyst 9.11 & 9.12. The "More Settings" option just isn't there. And ATITools just doesn't work for me so any other tips would be great
you can always pull up the windows crash logs and see if there's anything that stands out; could be a BSOD even happening but way too fast to even notice.
I have not had it crash because of effects from AoE or anything. Just when loading the next area.
I know, just turn down my settings right? But I shouldn't be forced too. I get good frame rate and it looks nice with everything turned up to at least medium if not higher. I turned off SLI and I went a bit longer before crashing, but all the missions were in space so it wasn't a fair test.
I can see what you're saying. The newer version of EVGA Precision actually shows you what GPU memory you're using, and I go up to around 400MB (maximum) video memory used at all highest settings @ 1680x1050. Unless the game is consuming memory that slowly increases until the memory is completely full and can't hold anymore, then it's not a memory leak. Granted it could use some kind of hard drive cache for the data that can't be stored in the GPU memory instead of crashing, but in that case your CPU and HDD load would increase, crippling performance anyway.
256MB of GPU memory is pretty low when playing at higher resolution and turning up AA. Whether your GPU can render the frames sent to it wouldn't matter if you don't have the memory to support all the textures, etc. that the game is trying to load into the card. You're just going to have to turn down your res to maybe 1440x900 or lower and lower the AA setting.
WIndows XP 32bits
2Go Ram, Radeon 5850 drivers updated this week-end.
I crashed on almost every ground mission. Never had a crash in space battles or sol starbase.
I'll try to keep an eye on the STO process with process explorer on my next ground mission.