Background CPU usage with InnerSpace

[eolewis]

Finally got around to doing mine...

Inner Space Kernel 1.07 Build 4034

System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_gdr.050301-1519
Process Memory Usage: 387MB
System Physical RAM: 725/1535MB
Page File: 2633/3431MB
Virtual Memory: 1423/2047MB (Extended: 0MB)
CPU 1: AMD Athlon(tm) 64 Processor 3200+ @ 2009MHz
CPU Affinity Mask: 0x1
Video 1: \\.\DISPLAY1/NVIDIA GeForce 6600 GT
Video 2: \\.\DISPLAYV1/NetMeeting driver
Video 3: \\.\DISPLAYV2/RDPDD Chained DD
Sound: ¨
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180

Loaded Modules:
-----------------------------------
Module 0x00320000-0x00334000: d:\sony\everquest trilogy\DSETUP.dll (Wed Dec 11 09:58:30 2002)
Module 0x00400000-0x00A1E000: d:\sony\everquest trilogy\eqgame.exe (Thu Jun 15 18:25:41 2006)
Module 0x00A20000-0x00C80000: C:\WINDOWS\system32\d3dx9_30.dll (Fri Mar 31 19:32:20 2006)
Module 0x01B80000-0x01BA1000: D:\Sony\InnerSpace\IS-D3D9.dll (Mon Jun 26 23:49:02 2006)
Module 0x01BC0000-0x01C24000: D:\Sony\InnerSpace\IS-D3D8.dll (Sat May 27 05:29:06 2006)
Module 0x01C40000-0x01C58000: D:\Sony\InnerSpace\IS-OpenGL.dll (Mon Jun 19 18:50:29 2006)
Module 0x02410000-0x02437000: D:\Sony\InnerSpace\IS-VirtualInput.dll (Wed May 31 19:31:28 2006)
Module 0x02680000-0x026D8000: d:\sony\everquest trilogy\dpvs.dll (Fri Nov 12 09:16:21 2004)
Module 0x02890000-0x02A18000: d:\sony\everquest trilogy\EQGraphicsDX9.DLL (Thu Jun 15 18:22:57 2006)
Module 0x03000000-0x03121000: D:\Sony\InnerSpace\IS-Kernel.dll (Tue Jun 27 17:26:10 2006)
Module 0x04000000-0x04048000: D:\Sony\InnerSpace\InnerSpace.dll (Tue Jun 27 17:26:16 2006)
Module 0x05000000-0x05133000: D:\Sony\InnerSpace\ISUI.dll (Tue Jun 27 17:25:39 2006)
Module 0x10000000-0x1001E000: C:\WINDOWS\Lavish.dll (Tue Jun 27 16:45:45 2006)
Module 0x21060000-0x210E3000: D:\Sony\InnerSpace\Extensions\isxeq.dll (Tue Jun 20 12:32:17 2006)
Module 0x21100000-0x2115F000: d:\sony\everquest trilogy\mss32.dll (Tue Jul 09 21:33:51 2002)
Module 0x4FDD0000-0x4FF76000: C:\WINDOWS\system32\d3d9.dll (Wed Aug 04 07:56:03 2004)
Module 0x5D090000-0x5D127000: C:\WINDOWS\system32\comctl32.dll (Wed Aug 04 07:56:31 2004)
Module 0x5ED00000-0x5EDCC000: C:\WINDOWS\system32\OPENGL32.dll (Wed Aug 04 07:57:44 2004)
Module 0x60300000-0x60307000: C:\Program Files\Yahoo!\Messenger\idle.dll (Tue May 02 22:16:29 2006)
Module 0x662B0000-0x66308000: C:\WINDOWS\system32\hnetcfg.dll (Wed Aug 04 07:56:16 2004)
Module 0x688F0000-0x688F9000: C:\WINDOWS\system32\HID.DLL (Wed Aug 04 07:56:12 2004)
Module 0x68B20000-0x68B40000: C:\WINDOWS\system32\GLU32.dll (Wed Aug 04 07:56:07 2004)
Module 0x6CE10000-0x6CE48000: C:\WINDOWS\system32\DINPUT8.dll (Wed Aug 04 07:56:32 2004)
Module 0x6D990000-0x6D996000: C:\WINDOWS\system32\d3d8thk.dll (Wed Aug 04 07:56:02 2004)
Module 0x71A50000-0x71A8F000: C:\WINDOWS\system32\mswsock.dll (Wed Aug 04 07:59:20 2004)
Module 0x71A90000-0x71A98000: C:\WINDOWS\System32\wshtcpip.dll (Wed Aug 04 07:57:49 2004)
Module 0x71AA0000-0x71AA8000: C:\WINDOWS\system32\WS2HELP.dll (Wed Aug 04 07:57:39 2004)
Module 0x71AB0000-0x71AC7000: C:\WINDOWS\system32\WS2_32.dll (Wed Aug 04 07:57:38 2004)
Module 0x71AD0000-0x71AD9000: C:\WINDOWS\system32\WSOCK32.dll (Wed Aug 04 07:57:51 2004)
Module 0x71BF0000-0x71C03000: C:\WINDOWS\system32\SAMLIB.dll (Wed Aug 04 07:56:29 2004)
Module 0x73760000-0x737A9000: C:\WINDOWS\system32\DDRAW.dll (Wed Aug 04 07:56:16 2004)
Module 0x73BC0000-0x73BC6000: C:\WINDOWS\system32\DCIMAN32.dll (Wed Aug 04 07:56:15 2004)
Module 0x74D90000-0x74DFB000: C:\WINDOWS\system32\usp10.dll (Wed Aug 04 07:56:42 2004)
Module 0x76390000-0x763AD000: C:\WINDOWS\system32\IMM32.dll (Wed Aug 04 07:56:30 2004)
Module 0x76B40000-0x76B6D000: C:\WINDOWS\system32\WINMM.dll (Wed Aug 04 07:57:10 2004)
Module 0x76BF0000-0x76BFB000: C:\WINDOWS\system32\PSAPI.DLL (Wed Aug 04 07:56:58 2004)
Module 0x76C30000-0x76C5E000: C:\WINDOWS\system32\WINTRUST.dll (Wed Aug 04 07:56:41 2004)
Module 0x76C90000-0x76CB8000: C:\WINDOWS\system32\IMAGEHLP.dll (Wed Aug 04 07:56:25 2004)
Module 0x76D60000-0x76D79000: C:\WINDOWS\system32\iphlpapi.dll (Wed Aug 04 07:56:10 2004)
Module 0x76F20000-0x76F47000: C:\WINDOWS\system32\DNSAPI.dll (Wed Aug 04 07:56:45 2004)
Module 0x76F60000-0x76F8C000: C:\WINDOWS\system32\WLDAP32.dll (Wed Aug 04 07:56:43 2004)
Module 0x76FB0000-0x76FB8000: C:\WINDOWS\System32\winrnr.dll (Wed Aug 04 07:56:35 2004)
Module 0x76FC0000-0x76FC6000: C:\WINDOWS\system32\rasadhlp.dll (Wed Aug 04 07:56:24 2004)
Module 0x77120000-0x771AC000: C:\WINDOWS\system32\OLEAUT32.dll (Wed Aug 04 07:57:39 2004)
Module 0x771B0000-0x77259000: C:\WINDOWS\system32\WININET.dll (Wed May 10 05:25:22 2006)
Module 0x773D0000-0x774D2000: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll (Wed Aug 04 07:55:56 2004)
Module 0x774E0000-0x7761D000: C:\WINDOWS\system32\ole32.dll (Tue Jul 26 04:39:47 2005)
Module 0x77690000-0x776B1000: C:\WINDOWS\system32\NTMARTA.DLL (Wed Aug 04 07:57:02 2004)
Module 0x77920000-0x77A13000: C:\WINDOWS\system32\SETUPAPI.dll (Wed Aug 04 07:56:32 2004)
Module 0x77A80000-0x77B14000: C:\WINDOWS\system32\CRYPT32.dll (Wed Aug 04 07:56:01 2004)
Module 0x77B20000-0x77B32000: C:\WINDOWS\system32\MSASN1.dll (Wed Aug 04 07:57:23 2004)
Module 0x77C00000-0x77C08000: C:\WINDOWS\system32\VERSION.dll (Wed Aug 04 07:56:39 2004)
Module 0x77C10000-0x77C68000: C:\WINDOWS\system32\msvcrt.dll (Wed Aug 04 07:59:14 2004)
Module 0x77D40000-0x77DD0000: C:\WINDOWS\system32\USER32.dll (Wed Mar 02 18:09:29 2005)
Module 0x77DD0000-0x77E6B000: C:\WINDOWS\system32\ADVAPI32.dll (Wed Aug 04 07:56:23 2004)
Module 0x77E70000-0x77F01000: C:\WINDOWS\system32\RPCRT4.dll (Wed Aug 04 07:56:30 2004)
Module 0x77F10000-0x77F57000: C:\WINDOWS\system32\GDI32.dll (Thu Dec 29 02:54:35 2005)
Module 0x77F60000-0x77FD6000: C:\WINDOWS\system32\SHLWAPI.dll (Wed May 10 05:25:21 2006)
Module 0x7C340000-0x7C396000: C:\Program Files\Yahoo!\Messenger\MSVCR71.dll (Fri Feb 21 12:42:20 2003)
Module 0x7C800000-0x7C8F4000: C:\WINDOWS\system32\kernel32.dll (Wed Aug 04 07:56:36 2004)
Module 0x7C900000-0x7C9B0000: C:\WINDOWS\system32\ntdll.dll (Wed Aug 04 07:56:36 2004)
Module 0x7C9C0000-0x7D1D5000: C:\WINDOWS\system32\SHELL32.dll (Fri Mar 17 04:03:51 2006)

Display
-------------------------------------
Adapter resolution: 1600x1200
Current display mode: 1600x1172 (windowed)
Window viewable size: 1600x1172
Display Scale: 100.0%x100.0%, Distortion: 0.0%
MaxFPS Foreground: Disabled
MaxFPS Background: Disabled

[eolewis]

Out of curiosity, any ideas/updates on this problem yet, Lax?

[Lax]

Unfortunately I'm unaware of any reason that this would happen, and it certainly doesnt happen to me... so I dont have any further help at this time

[qinen]

Same background fps problem here. I read earlier you were going to add some diagnostics in. Do you have some info on how to run the diagnostics if they've been implemented ?

[Lax]

The part that needs to be implemented in ISXEQ isnt there yet, but you can type "diag" in an IS console to open a diagnostics report. But, without the ISXEQ part, it's unlikely to show the problem.

[Krustov]

I started looking into this problem again and I found this interesting thread.

In short the EQ client is forcing the framerate to 10 FPS when the process goes into the background. If I set the MaxFPS slider in EQ to 10 (limiting the EQ client to 10 FPS in the foreground), EQ then behaves the same way whether it's in the foreground or the background, confirming this 10 FPS number.

What's interesting is that when running under WinEQ 2.0 (with EQPlayNice *DISABLED*), when EQ is made a background process the framerate is not slowed to 10 FPS. I've been dual boxing this way for a few months now with good success. God bless WinEQ 2.0.

A few posters in that thread I linked had confirmed that running the EQ client under EQWindows also prevented the framerate from being dropped when running in the background. Unfortunately this behavior is not observed when running under InnerSpace. The framerate is dropped to 10 FPS just like when the client is running on its own.

In summary, it would appear from these findings that there may be some difference in the way WinEQ 2.0 and IS are managing the EQ process. I'm hoping these findings will give you a starting point should you have time to take a look at this. I know a few of us that would be very happy if this problem could be resolved!

Thanks for you time, Lax. IS is just so amazing, I wish I could use it.

[Lax]

That's pretty old news. When using any FPS limiter other than EQ's, you want to put EQ's MaxFPS all the way up to 100. The reason it doesnt drop with WinEQ or EQWindows is that both of those programs prevent EQ from realizing that it has gone into the background. You can get the same effect from Inner Space by enabling "Lock Foreground" in the IS configuration window for the EQ settings. Let me know if that solves the problem for you

[Krustov]

Old news it may be, but it's the best news I've heard in a long time. That solved my problem, EQ now runs smooth as butter in the background.

Perhaps this question could be added to the FAQ?

[Lax]

Interesting.

I'll set it to be default for EQ1 for new installations.

[mdar]

I'm so glad I read this thread - I've been noticing the same issues and was wondering if was going to be worthwhile working on IS scripts - I'll try this tonight - if it works - let the scripting commence