Pook wrote:QUOTE (Pook @ Jul 15 2006, 04:19 PM) When Allegiance isn't running ASGS isn't doing anything.
Yes exactly that is why I wondered why it still claims 100% Cpu.
If Allegiance were running I would not wonder this :-)
Allegiance was not running at the point of time when this screenshot was taken. I quit Allegiance, ASGS succeeded to log off. And about 5 minutes later while surfing the forums I noticed that the processor load is still at 100%. That caused me to look for the cause. If Allegiance is running I see it as Allegiance.exe.
But anyway it does not really seem to be a major problem just a weird occurence.
I think it would be interesting if other users experience it. (thats why I posted) After all it is easy to miss it as ASGS produces only nice CPU load.
I think I will beign to check my taskmanager everytime after I ran Allegiance too see I can determine a pattern.
Edit: Just created two more screenshots which are perhaps interesting:
http://static.flickr.com/57/190047751_a6d7b1c9a8_o.jpg
This one shows the processes while Allegiance and ASGSClient are both running.
In the beginning I am on the desktop and Allegiance is minimized.
Note the sharp increase in Allegiance.exe's CPU cycles as I switched to Alleg and flew a bit around in the training mission. Simultaneously ASGS "makes way" for Allegiance so that it can perform unhindered.
So far so good. It is a behavior that I as a user do judge as perfectly normal.
http://static.flickr.com/68/190047812_c7a68fd6c8_o.jpg
As one can see, I have closed Allegiance now. (using escape and the exit allegiance)
ASGS Client's CPU load drops as allegiance is closed and it logs out of ASGS.
But the suddenly (without relogin or allegiance running) the CPU load climbs again.
That is the behavior that I found curious.
Edit2:
While performing one of the trial runs I noticed that the CPU Cycle gobbling does already begin before I even log into Allegiance. (had ASGSClient closed and sarted it up again, jumped to 100% CPU at once) So one of my thoughts that it might have been an unloaded part of Alleg go yonder into the trash as well. (lets reboot and try again.. to make absolutely sure)
Edit3:
Well the reboot did indeed remove the problem for some time. But as this is not the first instance that I notice this I am quite sure it will return. I just need to find some pattern as to why it happens. (Guess it will only show if I either connect to a server or play for a longer time)
*sigh* I have a foreboding feeling that this is a needle in the haystack thing. :-/
Let us just see what happens after all Alleg still runs and thus I am not at risk regarding Alleg. withdrawal symptoms.
Edit4:
Gee it seems I might have found a pattern only a very strange on... I do not believe it completely yet and certainly do need to do some more test. The idle cpu problem does only happen if I start ASGSClient /while/ Teamspeak is running. Strange aye? But if I start it before I do start Teamspeak it behaves normally... *bonk* sometimes I have this urge to give windows a good kick in its kernel.
Will try to see if I can reproduce this behavior consistently. Mayhap reinstall Teamspeak and so on...
