WinEQ2 registered version potential prob.

WinEQ 2.0 Lite discussion

Moderators: Lavish Software Team, Moderators

Post Reply
fabshant
GamingTools Subscriber
Posts: 16
Joined: Wed Aug 31, 2005 6:17 am

WinEQ2 registered version potential prob.

Post by fabshant » Fri Sep 09, 2005 8:12 am

hi,

Running WinEQ2 with everquest 1 gets me in the following situation.

1- The first character i log in, gets a black screen after some minutes playing..then goes LD...while the 2nd one i logged in stays on no problem there.
2- if i take off EQPlayNice option (EQplaynice=off), then I do not get the black screen after some time playing BUT i do get giant polygones going around BOTH toons during play.

Anybody has had ( or still have ) same kid of issue ?

Thanks,


G.

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

Post by Lax » Fri Sep 09, 2005 9:21 am

Can you post your sysinfo.txt for me?

fabshant
GamingTools Subscriber
Posts: 16
Joined: Wed Aug 31, 2005 6:17 am

Post by fabshant » Fri Sep 09, 2005 10:14 pm

Hi again,

Here is the sysinfo file as requested.

=============================
WinEQ 2 System Information
System:
-----------------------------------
Windows Version: Microsoft Windows XP/Service Pack 2/2600.xpsp_sp2_rtm.040803-2158
System Physical RAM: 415/1023MB
Page File: 3082/3997MB
Virtual Memory: 1284/2047MB (Extended: 0MB)
CPU 1: Intel(R) Pentium(R) 4 CPU 3.00GHz @ 3006MHz
CPU 2: Intel(R) Pentium(R) 4 CPU 3.00GHz @ 3006MHz
CPU Affinity Mask: 2
Video 1: \\.\DISPLAY1/NVIDIA GeForce FX 5700LE
Video 2: \\.\DISPLAYV1/NetMeeting driver
Video 3: \\.\DISPLAYV2/RDPDD Chained DD
Monitor 1: \\.\DISPLAY1 (0,0,1280,1024) (1280x1024) PRIMARY
Sound: ¨
DirectX: 4.09.00.0904
Internet Explorer: 6.0.2900.2180
WinEQ: 2.11

Loaded Modules:
-----------------------------------
Module 0: E:\everquest\AKLEM\eqgame.exe
Module 1: C:\WINDOWS\system32\ntdll.dll
Module 2: C:\WINDOWS\system32\kernel32.dll
Module 3: E:\everquest\AKLEM\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: C:\WINDOWS\system32\IMM32.dll
Module 15: E:\everquest\AKLEM\DSETUP.dll
Module 16: C:\WINDOWS\system32\VERSION.dll
Module 17: C:\WINDOWS\system32\ole32.dll
Module 18: C:\WINDOWS\system32\SHELL32.dll
Module 19: C:\WINDOWS\system32\SHLWAPI.dll
Module 20: C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.2180_x-ww_a84f1ff9\comctl32.dll
Module 21: C:\WINDOWS\system32\comctl32.dll
Module 22: E:\WinEQ2\WinEQ2.dll
Module 23: C:\WINDOWS\Lavish.dll
Module 24: C:\WINDOWS\system32\PSAPI.DLL
Module 25: E:\WinEQ2\WinEQ2-EQ.dll
Module 26: C:\WINDOWS\system32\MSIMG32.dll
Module 27: E:\WinEQ2\WinEQ2-D3D9.dll
Module 28: E:\WinEQ2\WinEQ2-D3D8.dll
Module 29: E:\WinEQ2\WinEQ2-DI8.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\pnrpnsp.dll
Module 37: C:\WINDOWS\system32\rasadhlp.dll
Module 38: C:\WINDOWS\system32\uxtheme.dll
Module 39: C:\WINDOWS\system32\NTMARTA.DLL
Module 40: C:\WINDOWS\system32\SAMLIB.dll
Module 41: E:\everquest\AKLEM\EQGraphicsDX9.DLL
Module 42: C:\WINDOWS\system32\d3d9.dll
Module 43: C:\WINDOWS\system32\d3d8thk.dll
Module 44: E:\everquest\AKLEM\dpvs.dll
Module 45: C:\WINDOWS\system32\usp10.dll
Module 46: C:\WINDOWS\system32\HID.DLL
Module 47: C:\WINDOWS\system32\SETUPAPI.DLL
Module 48: C:\WINDOWS\system32\WINTRUST.dll
Module 49: C:\WINDOWS\system32\CRYPT32.dll
Module 50: C:\WINDOWS\system32\MSASN1.dll
Module 51: C:\WINDOWS\system32\IMAGEHLP.dll
Module 52: E:\everquest\AKLEM\eqmain.dll

Direct3D9:
-----------------------------------
Driver: NVIDIA GeForce FX 5700LE/nv4_disp.dll/6/14/10/7777
Adapter Display Mode: 1280x1024 D3DFMT_X8R8G8B8
Game Display Mode: 1280x1024 D3DFMT_UNKNOWN
Current Adapter: 0
Available Texture Memory: 402MB
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: AKLEM
EQ Path: E:\everquest\AKLEM
EQClient.ini: .\eqclient.ini
Patch: OFF Test Server: OFF Locale: us
Video Adapter: Application Controlled
Luclin models: 29 (+145 min RAM)
Dynamic Lighting: ON (+4 min RAM)
Texture Quality: MEDIUM (+30 min RAM)
Sky: COMPLEX (+10 min RAM)
Calculated minimum RAM: 472MB (BASE+189MB)
Level of Detail: 0
MaxFPS: 57
Additional setting: HardwareTnL=TRUE
Additional setting: VertexShaders=TRUE
Additional setting: 20PixelShaders=0
Additional setting: 1xPixelShaders=0

===========================

As additional information, we did try to "test" the thing on another comp who was acting also strangely...
It "seems" to me that, also on another machine, just about same config hadware wise ( same proc, same ram, same video card) and same softwares on it ( mine just has VC6.0 / .net /sql server that about the only difference), it happens same way : it seems it is always the FIRST account you launch that goes LD with black screen...

Thanks for your help guys,


G.

fabshant
GamingTools Subscriber
Posts: 16
Joined: Wed Aug 31, 2005 6:17 am

Post by fabshant » Fri Sep 09, 2005 10:38 pm

See Also a post in this forum

Post subject: 2 Instances EQ1 +P4 (Hyperthreaded) Crashing since today

description seems similar.( black screen mouse released ...)

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

Post by Lax » Sat Sep 10, 2005 9:27 am

I did an update to WinEQ 2 today that should resolve this issue. Please restart it, let it patch, and let me know

fabshant
GamingTools Subscriber
Posts: 16
Joined: Wed Aug 31, 2005 6:17 am

It is a no go for update :(

Post by fabshant » Sun Sep 11, 2005 8:21 am

Hi there,

Sorry to be carrier of bad news, but the fix made it worse actually...

On bright side, we do NOT get the black screen, but toon windows get badly mixed up, i explain...

3 Toons, EQ1, let call them : G, C, B

Loading G..ok 1st logged in
Loading C..ok 2nd logged in
Loading B..ok 3rd logged in

After a little tick of buffing, switching windows and all...well it gets tricky.

Switching from G window to B window is ok.
Switching from G window to C window gave me THE SAME WINDOW set up and view than window G, but i was seeing my toon (C) at 3rd person view and was able to move her around, but seeing thru G's setup.
Switching on B i was seeing all correctly.

Just in case i explain myself like a cow, another way of saying it :
I get after a while 2 sessions having the same exact set up, mixed up together; basically if i want C to buff G, i have to go on G's window, target self and come back on C's window.
What i see thru C's window is equal to what i see thru G's window.

Good Luck LaX !! =)


G.

PS: if u eventually need some modules / exe / code to be ran in background for debug purpose, I volunteer on that one.

fabshant
GamingTools Subscriber
Posts: 16
Joined: Wed Aug 31, 2005 6:17 am

DISREGARD PREVIOUS answer

Post by fabshant » Sun Sep 11, 2005 8:30 am

Disregard...was wrong set up of mine(took a while to realise)

As said.. NO black screen at the moment, other comments (mixed windows) are NOT correct.

(SorrY)


G.

fabshant
GamingTools Subscriber
Posts: 16
Joined: Wed Aug 31, 2005 6:17 am

Post by fabshant » Mon Sep 12, 2005 11:40 am

After 2 days, 2 toons same comp with EQ1 :

I do not get the black screen anymore, so it seems.

The only down side i would see, is that instead of having a black screen then LD, you freeze for 1 or 2 sec, but you do not get LD.


G.

fabshant
GamingTools Subscriber
Posts: 16
Joined: Wed Aug 31, 2005 6:17 am

Post by fabshant » Wed Sep 14, 2005 2:28 am

After a couple of days using it, here is my feedback on the multi-threaded window change:

- no black screen anymore ( instead a slight slower moment, lagy but livable)
- WAY LONGER zone time if more than one toon is zoning
- if one toon is zoning now, the other(s) is(are) REALLY laggy.


Gal.

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

Post by Lax » Wed Sep 14, 2005 9:58 am

Thanks for the feedback. I am a little concerned that the lag you are experiencing actually has nothing to do with the change, and everything to do with running out of system RAM on your machine.

From your posted SysInfo.txt I see that your machine has 1GB of RAM in it, and your EQ settings say that you will be using at least 472MB per session (I am assuming your other sessions are similar, because I do not have further information). If you're running 2 sessions, that means at least 944MB of RAM is being used just to enter the game, leaving roughly 80MB of RAM for anything else... so if you're running a web browser, an email client, instant messaging, ventrilo/teamspeak, virus or spyware protection, etc you're probably actually running out of system RAM just playing 2. If you add in 3, almost the entire 3rd session is going to be stored in virtual memory, which is on your hard drive, instead of in physical RAM. When this happens, you will get HUGE performance issues when zoning.

I would be happy for you to prove me wrong if this is not the case, and I would look into the problem. Here's what to do... Launch 3 sessions as you would normally play them, all the way into the game. Spin around in a circle on each of them. Now for each individual session, shift+right click to bring up the WinEQ 2 context menu (if you disabled that in the hotkey preferences for WinEQ 2, you can release the mouse and right click on the window's title bar instead) and click Generate System Info. Paste them individually here.

This will show a) your EQ settings and how much RAM each session is expected to take, and b) your available system RAM and virtual memory.

fabshant
GamingTools Subscriber
Posts: 16
Joined: Wed Aug 31, 2005 6:17 am

Post by fabshant » Thu Sep 15, 2005 5:56 am

hi LaX,

for the logging process ( laggy), i reckon your explanation is correct and logical. I always have the memory indicator on when i play ( to know waht to expect regarding lag peak and such) and it happens as you described.

Now i will just compare previous version of WinEQ and this one : it "felt" less laggy with the previous one, even with 3 toons; maybe it is just an impression, dunno.. :). toons "feel heavier" than they use to.

But hey, my turn to do an upgrade, i'll go and get some RAM, on extra gig and check back with you here.

I keep you updated after i would have added the RAM and played 1 or 2 days with it. Until then, as test i will remove all new toon textures, this should save up some memory and verify if the lag is only due to lack of RAM.


Have a good one,


Gal.

Post Reply