I know the dev's know about this, but how many people are experiencing it?
out of 280 megs availible, it takes 200+ for me
start FAZ, play some, CTRL+ALT+DEL, check in processes how much space the client is taking up.
Memory leak
Did you get the latest client? 0712?
It uploaded it close to midnight (EST) last night.
Please get the lastest client and see if you still have the memory leak.
Since part of the sound problems were a buffer allocation problem I am hoping that backing out the sound changes also resolved the memory leak.
I should be on tonight and this weekend (on and off) testing the same.
Edit: For those that may not know we are talking about a ~200 KB per second steady increase in the reported memory size by the windows Task Manager for the Allegiance.exe process. If you have a dual monitor system or run windowed, fire up the Task Manager and leave it running while you play. You could also alt-tab out and check every 5 min or so. It is normal for the client to grow some, but not at this steady pace for a long period of time (I've seen it grow to 1 gig in about an hour /excl.gif" style="vertical-align:middle" emoid=":excl:" border="0" alt="excl.gif" /> )
Dog
It uploaded it close to midnight (EST) last night.
Please get the lastest client and see if you still have the memory leak.
Since part of the sound problems were a buffer allocation problem I am hoping that backing out the sound changes also resolved the memory leak.
I should be on tonight and this weekend (on and off) testing the same.
Edit: For those that may not know we are talking about a ~200 KB per second steady increase in the reported memory size by the windows Task Manager for the Allegiance.exe process. If you have a dual monitor system or run windowed, fire up the Task Manager and leave it running while you play. You could also alt-tab out and check every 5 min or so. It is normal for the client to grow some, but not at this steady pace for a long period of time (I've seen it grow to 1 gig in about an hour /excl.gif" style="vertical-align:middle" emoid=":excl:" border="0" alt="excl.gif" /> )
Dog
Last edited by Dogbones on Thu Jul 13, 2006 10:32 pm, edited 1 time in total.
DOG PROPERTY LAWS:
2. If it's in my mouth, it's mine.
[unless it tastes bad, then it is yours.]
I don't experience the memory leak... or at least I haven't been able to catch it, but I'm wondering if I don't have a related issue: stuttering sound and video. Let's see if I can explain better than on a in-game chat window:
Occasionally I experience sound stuttering... this usually happens when there is less than trivial activity in a sector (ie several ships all firing at each other, boosting, firing missiles, etc.). (In other words - many sound events happening at the same time.) The stuttering will stop very soon (immediately?) when some of these ships leave the sector, or are podded, or I enter base. When this stuttering happens so does the video. I've called it "lag" in the in-game chat for lack of a better and concise word.
I generally don't experience communication lag. It's a pretty reliable connection and whenever I check Alt-F-F I'm getting 14-16 reported. I will endeavour to check that whenever I experience the "video lag" - I haven't been able to yet since it doesn't last very long, sometimes for only a handful of seconds, but, as you can imagine, it happens at critical points in the game.
Alleg tends to use between 70-91 Megs as reported by Task Mangler with the most frequent readings in the lower quartile. I have 512 Megs of RAM.
I'm wondering if this stuttering is due to the lack of memory resources. Perhaps I'm not getting the memory allocation I need for smooth operation of the game, while others are getting too much?
Just a thought. Call me a loon if you like. /mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" />
Occasionally I experience sound stuttering... this usually happens when there is less than trivial activity in a sector (ie several ships all firing at each other, boosting, firing missiles, etc.). (In other words - many sound events happening at the same time.) The stuttering will stop very soon (immediately?) when some of these ships leave the sector, or are podded, or I enter base. When this stuttering happens so does the video. I've called it "lag" in the in-game chat for lack of a better and concise word.
I generally don't experience communication lag. It's a pretty reliable connection and whenever I check Alt-F-F I'm getting 14-16 reported. I will endeavour to check that whenever I experience the "video lag" - I haven't been able to yet since it doesn't last very long, sometimes for only a handful of seconds, but, as you can imagine, it happens at critical points in the game.
Alleg tends to use between 70-91 Megs as reported by Task Mangler with the most frequent readings in the lower quartile. I have 512 Megs of RAM.
I'm wondering if this stuttering is due to the lack of memory resources. Perhaps I'm not getting the memory allocation I need for smooth operation of the game, while others are getting too much?
Just a thought. Call me a loon if you like. /mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" />
The memory leak seems to be resolved with the latest client (which reverts to the old sound engine).
At least I did not have any problems last night with it. I will continue to test through the weekend.
Small games with everyone rushing to advanced tech is not a lot of fun, but I guess it is more fun than small games where you only get to adv tech in one path after 10 to 20 min.
At least I did not have any problems last night with it. I will continue to test through the weekend.
Small games with everyone rushing to advanced tech is not a lot of fun, but I guess it is more fun than small games where you only get to adv tech in one path after 10 to 20 min.
DOG PROPERTY LAWS:
2. If it's in my mouth, it's mine.
[unless it tastes bad, then it is yours.]
-
DreamWalker
- Posts: 183
- Joined: Sun Apr 24, 2005 7:00 am
I have played with those settings, but not enough to determine for sure if it has an effect or not. As I mentioned, I only experience it with a lot of sound events happening concurrently, and it's tricky to flip the settings while the furball is going on. /mrgreen.gif" style="vertical-align:middle" emoid=":D" border="0" alt="mrgreen.gif" />DreamWalker wrote:QUOTE (DreamWalker @ Jul 19 2006, 08:18 PM) I set the sound quality to default, and the problem was gone.
I will test some more and thanks for your comments.
-
Thalgor
- Posts: 246
- Joined: Tue Aug 13, 2002 7:00 am
- Location: Directly over the center of the earth
- Contact:
For all you guys who are NOT experiencing the memory leak, but are still having the stutter-with-activity problem...
...check your device manager (view / resources by type / IRQ under win2k...not sure about XP) and make sure plug-n-pray or ACPI hasn't piled a bunch of stuff under the same IRQ (in particular: network, sound, and video devices). This is especially true for those of you who may have just installed new stuff (motherboard, video/sound cards, etc.).
If EVERYTHING is under the SAME IRQ...this is ACPI doing it. Make sure you have the VERY LATEST drivers for EVERYTHING to make sure that everything is ACPI compliant. ACPI works IF everything is built to actually use it.
If you're simply out of IRQs and these particular functions just happened to be stacked on the same IRQ's...shut off stuff you don't use IN BIOS. For instance:If you don't use a parallel printer (most people don't anymore...they're almost all USB now), then disable your parallel port in BIOS. This will free up IRQ 7 for use by other things.If you don't use any of your actual serial ports...turn them off as well...this will free up IRQs 3 and 4. Or, if you only use one, shut off the other. Also, remove any unused modem cards.If you don't have an internally-cabled floppy drive (i.e. using a usb floppy or simply don't have one), make sure any existing internal floppy port is disabled. This will free up IRQ 2 or 6, depending on your motherboard.If you're using usb mice and keyboard, disable those ports. (Most motherboard BIOSs only give you the option to disable the mouse port, but some have a 'legacy free' option that turns off keyboard, mouse, and parallel at the same time).If you only have one hard drive and one CD/DVD drive...they are probably both on the primary controller. Disable the secondary, in this case.If you have some form of RAID controller built into your motherboard and aren't using it, disable it.Disable any other 'fun' features your motherboard might have available that you don't actually use.After you have disabled things in BIOS, make sure you ENABLE 'reset ECPI', 'reset configuration data', or something similar. This will make the motherboard rescan everything (assuming you have 'plug and play OS' set to 'yes') and redistribute the IRQs.
...check your device manager (view / resources by type / IRQ under win2k...not sure about XP) and make sure plug-n-pray or ACPI hasn't piled a bunch of stuff under the same IRQ (in particular: network, sound, and video devices). This is especially true for those of you who may have just installed new stuff (motherboard, video/sound cards, etc.).
If EVERYTHING is under the SAME IRQ...this is ACPI doing it. Make sure you have the VERY LATEST drivers for EVERYTHING to make sure that everything is ACPI compliant. ACPI works IF everything is built to actually use it.
If you're simply out of IRQs and these particular functions just happened to be stacked on the same IRQ's...shut off stuff you don't use IN BIOS. For instance:If you don't use a parallel printer (most people don't anymore...they're almost all USB now), then disable your parallel port in BIOS. This will free up IRQ 7 for use by other things.If you don't use any of your actual serial ports...turn them off as well...this will free up IRQs 3 and 4. Or, if you only use one, shut off the other. Also, remove any unused modem cards.If you don't have an internally-cabled floppy drive (i.e. using a usb floppy or simply don't have one), make sure any existing internal floppy port is disabled. This will free up IRQ 2 or 6, depending on your motherboard.If you're using usb mice and keyboard, disable those ports. (Most motherboard BIOSs only give you the option to disable the mouse port, but some have a 'legacy free' option that turns off keyboard, mouse, and parallel at the same time).If you only have one hard drive and one CD/DVD drive...they are probably both on the primary controller. Disable the secondary, in this case.If you have some form of RAID controller built into your motherboard and aren't using it, disable it.Disable any other 'fun' features your motherboard might have available that you don't actually use.After you have disabled things in BIOS, make sure you ENABLE 'reset ECPI', 'reset configuration data', or something similar. This will make the motherboard rescan everything (assuming you have 'plug and play OS' set to 'yes') and redistribute the IRQs.
Last edited by Thalgor on Mon Jul 24, 2006 4:23 am, edited 1 time in total.
"When the going gets weird, the weird turn pro."
The memory leak seems to have been caused by the sound engine update that was going to be in FAZ r2. I suspect that it is related to the sounds dropping some people reported (whether it is a cause or an effect, I have yet to determine). With the sound revert, there should be no leak, at least not one of that magnitude.
The only stuttering I know of is with some sounds (particularly turrets) under the old engine. That one’s related to an issue with DirectSound4 and sound cards in IRQ 16-23. Details are in the knowledge base.
That being said, Thal’s list of stuff-to-disable can’t hurt, unless you go and turn off something you need. If nothing else, it’ll give your system less to worry about.
The only stuttering I know of is with some sounds (particularly turrets) under the old engine. That one’s related to an issue with DirectSound4 and sound cards in IRQ 16-23. Details are in the knowledge base.
That being said, Thal’s list of stuff-to-disable can’t hurt, unless you go and turn off something you need. If nothing else, it’ll give your system less to worry about.