FPS in background

eolewis · Post by **eolewis** » Sat Jun 03, 2006 1:46 pm

Out of curiousity, I have noticed that when I have EQ in the background, the FPS drops from 20-30 down to around 3-5 if Im using IS. If Im using WinEQ2 the FPS drops from 20 down to 16. I have tried disabling the limiters in IS and using the EQPlaynice function in WinEQ2 like suggested in a previous post sometime last year. I noticed that even that way, IS still drops from 20-30FPS down to around 3-5 FPS. I am wondering if this is how IS is designed, if its an unknown flaw, or if I just have a crappy setting somewhere...

eolewis · Post by **eolewis** » Sat Jun 03, 2006 1:51 pm

WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_gdr.050301-1519
System Physical RAM: 605/1535MB
Page File: 2662/3431MB
Virtual Memory: 1310/2047MB (Extended: 0MB)
CPU 1: AMD Athlon(tm) 64 Processor 3200+ @ 2009MHz
CPU Affinity Mask: 1
Video 1: \\.\DISPLAY1/NVIDIA GeForce 6600 GT
Video 2: \\.\DISPLAYV1/NetMeeting driver
Video 3: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1600,1200) (1600x1200) PRIMARY
Sound: ¨
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180
WinEQ: 2.13

Loaded Modules:
-----------------------------------
Module 0: D:\Sony\Everquest Trilogy\eqgame.exe
Module 1: C:\WINDOWS\system32\ntdll.dll
Module 2: C:\WINDOWS\system32\kernel32.dll
Module 3: D:\Sony\Everquest Trilogy\mss32.dll
Module 4: C:\WINDOWS\system32\USER32.dll
Module 5: C:\WINDOWS\system32\GDI32.dll
Module 6: C:\WINDOWS\system32\WINMM.dll
Module 7: C:\WINDOWS\system32\ADVAPI32.dll
Module 8: C:\WINDOWS\system32\RPCRT4.dll
Module 9: C:\WINDOWS\system32\WSOCK32.dll
Module 10: C:\WINDOWS\system32\WS2_32.dll
Module 11: C:\WINDOWS\system32\msvcrt.dll
Module 12: C:\WINDOWS\system32\WS2HELP.dll
Module 13: C:\WINDOWS\system32\DINPUT8.dll
Module 14: D:\Sony\Everquest Trilogy\DSETUP.dll
Module 15: C:\WINDOWS\system32\VERSION.dll
Module 16: C:\WINDOWS\system32\ole32.dll
Module 17: C:\WINDOWS\system32\WININET.dll
Module 18: C:\WINDOWS\system32\CRYPT32.dll
Module 19: C:\WINDOWS\system32\MSASN1.dll
Module 20: C:\WINDOWS\system32\OLEAUT32.dll
Module 21: C:\WINDOWS\system32\SHLWAPI.dll
Module 22: C:\WINDOWS\system32\SHELL32.dll
Module 23: C:\WINDOWS\system32\IMM32.dll
Module 24: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll
Module 25: C:\WINDOWS\system32\comctl32.dll
Module 26: D:\Sony\WinEQ2\WinEQ2.dll
Module 27: C:\WINDOWS\system32\PSAPI.DLL
Module 28: C:\WINDOWS\Lavish.dll
Module 29: C:\WINDOWS\system32\iphlpapi.dll
Module 30: C:\WINDOWS\system32\mswsock.dll
Module 31: C:\WINDOWS\system32\hnetcfg.dll
Module 32: C:\WINDOWS\System32\wshtcpip.dll
Module 33: C:\WINDOWS\system32\DNSAPI.dll
Module 34: C:\WINDOWS\System32\winrnr.dll
Module 35: C:\WINDOWS\system32\WLDAP32.dll
Module 36: C:\WINDOWS\system32\rasadhlp.dll
Module 37: D:\Sony\WinEQ2\WinEQ2-EQ.dll
Module 38: C:\WINDOWS\system32\MSIMG32.dll
Module 39: D:\Sony\WinEQ2\WinEQ2-D3D9.dll
Module 40: C:\WINDOWS\system32\d3dx9_27.dll
Module 41: D:\Sony\WinEQ2\WinEQ2-D3D8.dll
Module 42: D:\Sony\WinEQ2\WinEQ2-DI8.dll
Module 43: D:\Sony\WinEQ2\EQPlayNice.dll
Module 44: C:\WINDOWS\system32\NTMARTA.DLL
Module 45: C:\WINDOWS\system32\SAMLIB.dll
Module 46: D:\Sony\Everquest Trilogy\EQGraphicsDX9.DLL
Module 47: C:\WINDOWS\system32\d3d9.dll
Module 48: C:\WINDOWS\system32\d3d8thk.dll
Module 49: D:\Sony\Everquest Trilogy\dpvs.dll
Module 50: C:\WINDOWS\system32\usp10.dll
Module 51: C:\WINDOWS\system32\HID.DLL
Module 52: C:\WINDOWS\system32\SETUPAPI.DLL
Module 53: C:\WINDOWS\system32\WINTRUST.dll
Module 54: C:\WINDOWS\system32\IMAGEHLP.dll
Module 55: C:\Program Files\Yahoo!\Messenger\idle.dll
Module 56: C:\Program Files\Yahoo!\Messenger\MSVCR71.dll

Direct3D9:
-----------------------------------
Driver: NVIDIA GeForce 6600 GT/nv4_disp.dll/6/14/10/8421
Adapter Display Mode: 1600x1200 D3DFMT_X8R8G8B8
Game Display Mode: 1600x1172 D3DFMT_X8R8G8B8 (Full Screen)
Current Adapter: 0
Available Texture Memory: 314MB
Direct3D8:
-----------------------------------
Adapter Display Mode: 0x0 D3DFMT_UNKNOWN
Game Display Mode: 0x0 D3DFMT_UNKNOWN
Current Adapter: 0
Available Texture Memory: (not currently available)
DirectInput8:
-----------------------------------

EverQuest:
-----------------------------------
Profile 2: Siwel
EQ Path: D:\Sony\Everquest Trilogy
EQClient.ini: .\siwel.ini
Patch: OFF Server Type: Normal Locale: us
Video Adapter: Application Controlled
Luclin models: 5 (+25 min RAM)
Texture Compression: ON (+0 min RAM)
Texture Caching: ON (+0 min RAM)
Texture Quality: INVALID VALUE 3
Load Velious Armors with Luclin: ON (+51 min RAM)
Calculated minimum RAM: 359MB (BASE+76MB)
Level of Detail: 0
MaxFPS: 25
Additional setting: HardwareTnL=TRUE
Additional setting: VertexShaders=1
Additional setting: 20PixelShaders=0
Additional setting: 1xPixelShaders=0

EQPlayNice:
-----------------------------------
EQ Version: eqgame.exe Apr 17 2006 14:53:02
Foreground
Mode: FPS Limiter
Max FPS: 20
Rendering: 1/1
Background
Mode: CPU Limiter
Max FPS: 20
Rendering: 1/30

eolewis · Post by **eolewis** » Sat Jun 03, 2006 2:01 pm

Cant find a way to get the same type of info from IS... if I can get it, ill post it also. I just find it strange that IS FPS drops way lower then it does on WinEQ2 and wanted to see if there was a problem somewhere

Post by **Lax** » Sat Jun 03, 2006 2:31 pm

I am wondering if this is how IS is designed, if its an unknown flaw, or if I just have a crappy setting somewhere...

Probably just something you're not expecting (which is why you're posting about it). IS doesnt have a system info dump because it's generally unnecessary (except for crashing, which is automatically generated and can be sent directly to us by clicking a button). IS doesn't really interfere with the way games operate.

Right now I see multiple problems. One of them is that your EQ setting for Max FPS is 25. If you're using IS, WinEQ 2/EQPlayNice, etc, you should simply raise it all the way to 100. You only want 1 thing limiting it. If you have WinEQ 2 (with EQPN enabled), IS, and EQ's limiters on, well, thats probably going to be causing problems.

Another is that IS is going to be using a different eqclient.ini file, based on your IS profile name by default, and you may not realize that it might have some different EQ settings just because of that.

I basically recommend closing WinEQ 2 (and thus EQPN), launch EQ through IS, make sure the FPS limit in EQ is set to 100, and then you can disable the FPS limiting in IS (type "maxfps -bg -disable" in the console), and you should get maximum framerate. If that doesn't change the behavior, then there is something going on with your system that isnt coming to light here.

eolewis · Post by **eolewis** » Sat Jun 03, 2006 6:01 pm

Well, I did as you said and my FPS in IS is between 40 and 50... if I bring up the IS console (out of game) the FPS drops way down to 8... not sure whats going on there. Just for fun, I disablesd the forground also and it jumps up to around 60FPS but if I switch to the IS console again, if still drops down to 8fps

What kind of info would you need in order to help me figure this out.

Post by **Lax** » Mon Jun 05, 2006 12:15 am

It sounds like you're confused about what "the IS console" means. What I assume here is that you're bringing up the console in the uplink (e.g. what you say is "the IS console"), and typing what I said into it, rather than bringing up the console window in the game by hitting `. It might be easier to tell you to change the FPS limiting settings through the IS configuration window: FPS limiter tab, background, uncheck "Enable Limiter", hit Apply, and then launch the game

eolewis · Post by **eolewis** » Tue Jun 06, 2006 2:35 am

I tried the command in both the console for IS1 and IS2 as well as unchecking enable limiter in the IS config window. the background sessions still drop from 50 FPS down to 6-8 FPS so not sure whats going on. I know when I have the EQPlaynice in WinEQ2 set to the same framerate as the forground, it drops from 20FPS down to 16FPS and doesn't lag while autofollowing.

If Im on the character that is autofollowing the main character, they can have bard speed horse going and the character following without speed adjustments, and I still catch and stop the lead character, so Im not sure whats going on.