Eq1 Innerspace .093 CPU 100 % constantly

Discussion of Inner Space

Moderators: Lavish Software Team, Moderators

Post Reply
Breiben
GamingTools Subscriber
Posts: 3
Joined: Sun Feb 06, 2005 2:47 pm

Eq1 Innerspace .093 CPU 100 % constantly

Post by Breiben » Tue May 17, 2005 11:28 pm

Lax,
Not sure if it is on my end or not, got version 093 tonight and the CPU was pegged at 100% as soon as acct 2 loaded into the world. Normally as I remember the CPU kinda settled down after both sessions loaded into the game world....

One process of everquest.exe ( in taskmanager) had around 300k of memory and the other only had 54k. That seemed really strange to me. Innerspace had around 4k of memory in task manager process list ( not sure if that is normal I never benchmarked it). The CPU pegged was so bad that the mouse would release, like I hit the scroll lock key, like it was iterating a constant loop.

I'll look into re-installing IS and see if that helps as I am unshure if this is a config issue with eq1 on my end.

I have noticed, not sure when it started, that mouse release on eq1 zoning seems to not work anymore. If one session's char gets killed you cannot ctrl-alt-x to the next session until that char loads back at thier bind point....

Just thought this was a strange event that you may want to see if you can duplicate since I have had no issue like this since I started using IS.

Let me know your thoughts..

Bre

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Wed May 18, 2005 12:09 pm

Well, the amount of memory is in mb not k but thats ok :) Inner Space will use about 4mb, sure. I dont know why one EQ would only use 54mb, unless the rest was hiding in the virtual part. View->Select Columns, click "Virtual Memory Size".

I'll run some tests real quick and see if I can duplicate your issue

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Wed May 18, 2005 12:51 pm

Looking 100% OK here. Auto-release on zoning, etc. Ctrl+Alt+X during zoning was probably never available in IS though, because the game doesnt process input until it's done loading, and we're using the game's input system. You can use Ctrl+Alt+1, Ctrl+Alt+2, etc.

Post Reply